Initial commit for GCC 4.8

Signed-off-by: kecinzer <kecinzer@gmail.com>

Conflicts:
	Makefile
	arch/arm/kernel/return_address.c
Linaro 4.8 fixes

Conflicts:
	arch/arm/boot/compressed/Makefile
	arch/arm/lib/memset.S
	drivers/usb/gadget/f_qdss.c
	fs/namespace.c
	net/bluetooth/hci_conn.c
	net/unix/af_unix.c
Booting fix

Change-Id: I228570756281be6f1234b9544fdbdb5e021fa542
Signed-off-by: kecinzer <kecinzer@gmail.com>

Conflicts:
	arch/arm/lib/memset.S
	include/sound/pcm.h
	sound/core/pcm.c
3.4.73

Signed-off-by: kecinzer <kecinzer@gmail.com>

Conflicts:
	Makefile
3.4.74

Signed-off-by: kecinzer <kecinzer@gmail.com>
3.4.75

Signed-off-by: kecinzer <kecinzer@gmail.com>
3.4.76

Signed-off-by: kecinzer <kecinzer@gmail.com>
3.4.77

Signed-off-by: kecinzer <kecinzer@gmail.com>
3.4.78

Signed-off-by: kecinzer <kecinzer@gmail.com>

Conflicts:
	arch/x86/kernel/cpu/perf_event_amd_ibs.c
3.4.79

Signed-off-by: kecinzer <kecinzer@gmail.com>
3.4.80

This patch is different from francos hammerhead one because of CAF audio patches!

Signed-off-by: kecinzer <kecinzer@gmail.com>
3.4.81

Signed-off-by: kecinzer <kecinzer@gmail.com>
3.4.82

Signed-off-by: kecinzer <kecinzer@gmail.com>
3.4.83

Signed-off-by: kecinzer <kecinzer@gmail.com>
update Makefile
ARM: be strict about FP exceptions in kernel mode

The support code in vfp_support_entry does not care whether the
exception that caused it to be invoked occurred in kernel mode or
in user mode. However, neither condition that could trigger this
exception (lazy restore and VFP bounce to support code) is
currently allowable in kernel mode.

In either case, print a message describing the condition before
letting the undefined instruction handler run its course and trigger
an oops.

Signed-off-by: Ard Biesheuvel <ard.biesheuvel at linaro.org>
Acked-by: Nicolas Pitre <nico at linaro.org>
Signed-off-by: Paul Reioux <reioux@gmail.com>
ARM: add support for kernel mode NEON

In order to safely support the use of NEON instructions in
kernel mode, some precautions need to be taken:
- the userland context that may be present in the registers (even
  if the NEON/VFP is currently disabled) must be stored under the
  correct task (which may not be 'current' in the UP case),
- to avoid having to keep track of additional vfpstates for the
  kernel side, disallow the use of NEON in interrupt context
  and run with preemption disabled,
- after use, re-enable preemption and re-enable the lazy restore
  machinery by disabling the NEON/VFP unit.

This patch adds the functions kernel_neon_begin() and
kernel_neon_end() which take care of the above. It also adds
the Kconfig symbol KERNEL_MODE_NEON to enable it.

Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Acked-by: Nicolas Pitre <nico@linaro.org>

Signed-off-by: Paul Reioux <reioux@gmail.com>
enable KERNEL_MODE_NEON in defconfig
ARM: move VFP init to an earlier boot stage

In order to use the NEON unit in the kernel, we should
initialize it a bit earlier in the boot process so NEON users
that like to do a quick benchmark at load time (like the
xor_blocks or RAID-6 code) find the NEON/VFP unit already
enabled.

Replaced late_initcall() with core_initcall().

Signed-off-by: Ard Biesheuvel <ard.biesheuvel at linaro.org>
Acked-by: Nicolas Pitre <nico at linaro.org>

Signed-off-by: Paul Reioux <reioux@gmail.com>
ARM: crypto: add NEON accelerated XOR implementation

Add a source file xor-neon.c (which is really just the reference
C implementation passed through the GCC vectorizer) and hook it
up to the XOR framework.

Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Acked-by: Nicolas Pitre <nico@linaro.org>