linux-toradex.git, branch v3.10.26

Linux 3.10.26

2014-01-09T20:25:15+00:00

sh: add EXPORT_SYMBOL(min_low_pfn) and EXPORT_SYMBOL(max_low_pfn) to sh_ksyms_32.c

2014-01-09T20:24:27+00:00

commit ad70b029d2c678386384bd72c7fa2705c449b518 upstream.

Min_low_pfn and max_low_pfn were used in pfn_valid macro if defined
CONFIG_FLATMEM.  When the functions that use the pfn_valid is used in
driver module, max_low_pfn and min_low_pfn is to undefined, and fail to
build.

  ERROR: "min_low_pfn" [drivers/block/aoe/aoe.ko] undefined!
  ERROR: "max_low_pfn" [drivers/block/aoe/aoe.ko] undefined!
  make[2]: *** [__modpost] Error 1
  make[1]: *** [modules] Error 2

This patch fix this problem.

Signed-off-by: Nobuhiro Iwamatsu 
Cc: Kuninori Morimoto 
Cc: Paul Mundt 
Cc: Geert Uytterhoeven 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

ext4: fix bigalloc regression

2014-01-09T20:24:27+00:00

commit d0abafac8c9162f39c4f6b2f8141b772a09b3770 upstream.

Commit f5a44db5d2 introduced a regression on filesystems created with
the bigalloc feature (cluster size > blocksize).  It causes xfstests
generic/006 and /013 to fail with an unexpected JBD2 failure and
transaction abort that leaves the test file system in a read only state.
Other xfstests run on bigalloc file systems are likely to fail as well.

The cause is the accidental use of a cluster mask where a cluster
offset was needed in ext4_ext_map_blocks().

Signed-off-by: Eric Whitney 
Cc: Theodore Ts'o 
Signed-off-by: Greg Kroah-Hartman

arm64: Use Normal NonCacheable memory for writecombine

2014-01-09T20:24:27+00:00

commit 4f00130b70e5eee813cc7bc298e0f3fdf79673cc upstream.

This provides better performance compared to Device GRE and also allows
unaligned accesses. Such memory is intended to be used with standard RAM
(e.g. framebuffers) and not I/O.

Signed-off-by: Catalin Marinas 
Cc: Mark Brown 
Signed-off-by: Greg Kroah-Hartman

arm64: Do not flush the D-cache for anonymous pages

2014-01-09T20:24:27+00:00

commit 7249b79f6b4cc3c2aa9138dca52e535a4c789107 upstream.

The D-cache on AArch64 is VIPT non-aliasing, so there is no need to
flush it for anonymous pages.

Signed-off-by: Catalin Marinas 
Reported-by: Will Deacon 
Acked-by: Will Deacon 
Cc: Mark Brown 
Signed-off-by: Greg Kroah-Hartman

arm64: Avoid cache flushing in flush_dcache_page()

2014-01-09T20:24:27+00:00

commit b5b6c9e9149d8a7c3f1d7b9d0c046c6184e1dd17 upstream.

The flush_dcache_page() function is called when the kernel modified a
page cache page. Since the D-cache on AArch64 does not have aliases
this function can simply mark the page as dirty for later flushing via
set_pte_at()/__sync_icache_dcache() if the page is executable (to ensure
the I-D cache coherency).

Signed-off-by: Catalin Marinas 
Reported-by: Will Deacon 
Acked-by: Will Deacon 
Cc: Mark Brown 
Signed-off-by: Greg Kroah-Hartman

ARM: KVM: arch_timers: zero CNTVOFF upon return to host

2014-01-09T20:24:26+00:00

commit f793c23ebbe5afd1cabf4a42a3a297022213756f upstream.

To use the virtual counters from the host, we need to ensure that
CNTVOFF doesn't change unexpectedly. When we change to a guest, we
replace the host's CNTVOFF, but we don't restore it when returning to
the host.

As the host sets CNTVOFF to zero, and never changes it, we can simply
zero CNTVOFF when returning to the host. This patch adds said zeroing to
the return to host path.

Signed-off-by: Mark Rutland 
Acked-by: Marc Zyngier 
Acked-by: Santosh Shilimkar 
Acked-by: Christoffer Dall 
Cc: Mark Brown 
Signed-off-by: Greg Kroah-Hartman

ARM: hyp: initialize CNTVOFF to zero

2014-01-09T20:24:26+00:00

commit 0af0b189abf73d232af782df2f999235cd2fed7f upstream.

In order to be able to use the virtual counter in a safe way,
make sure it is initialized to zero before dropping to SVC.

Signed-off-by: Marc Zyngier 
Signed-off-by: Mark Rutland 
Acked-by: Santosh Shilimkar 
Cc: Dave Martin 
Cc: Mark Brown 
Signed-off-by: Greg Kroah-Hartman

clocksource: arch_timer: use virtual counters

2014-01-09T20:24:26+00:00

commit 0d651e4e65e96989f72236bf83bd4c6e55eb6ce4 upstream.

Switching between reading the virtual or physical counters is
problematic, as some core code wants a view of time before we're fully
set up. Using a function pointer and switching the source after the
first read can make time appear to go backwards, and having a check in
the read function is an unfortunate block on what we want to be a fast
path.

Instead, this patch makes us always use the virtual counters. If we're a
guest, or don't have hyp mode, we'll use the virtual timers, and as such
don't care about CNTVOFF as long as it doesn't change in such a way as
to make time appear to travel backwards. As the guest will use the
virtual timers, a (potential) KVM host must use the physical timers
(which can wake up the host even if they fire while a guest is
executing), and hence a host must have CNTVOFF set to zero so as to have
a consistent view of time between the physical timers and virtual
counters.

Signed-off-by: Mark Rutland 
Acked-by: Catalin Marinas 
Acked-by: Marc Zyngier 
Acked-by: Santosh Shilimkar 
Cc: Rob Herring 
Cc: Mark Brown 
Signed-off-by: Greg Kroah-Hartman

arm64: Remove unused cpu_name ascii in arch/arm64/mm/proc.S

2014-01-09T20:24:26+00:00

commit f3a1d7d53dccf51959aec16b574617cc6bfeca09 upstream.

This string has been moved to arch/arm64/kernel/cputable.c.

Signed-off-by: Catalin Marinas 
Cc: Mark Brown 
Signed-off-by: Greg Kroah-Hartman