linux/arch/tile, branch v3.12-rc2

tile: remove stray blank space

2013-09-16T19:47:32Z

The compat sys_llseek() definition addition added a bogus space on an otherwise-blank line. Signed-off-by: Chris Metcalf

tile: header updates from upstream

2013-09-16T19:47:26Z

The hardware architecture descriptor headers have been updated, in particular to reflect some larger MMIO fields on the mPIPE shims for controlling the network hardware, from the recent Gx72 release. Signed-off-by: Chris Metcalf

tile: improve gxio iorpc autogenerated code style

2013-09-16T19:47:20Z

Fix some whitespace style issues in some auto-generated files. Signed-off-by: Chris Metcalf

tile: double default VMALLOC space

2013-09-16T19:47:14Z

With per-cpu data as well as loaded kernel modules coming from the vmalloc arena, we get close to the line all the time and occasionally need more than we had, so just double it up by default. Signed-off-by: Chris Metcalf

tile: remove stale arch/tile/kernel/futex_64.S

2013-09-13T15:15:24Z

This should have been removed with commit 47d632f9f8f3, but it was overlooked. Signed-off-by: Chris Metcalf

tile: remove HUGE_VMAP dead code

2013-09-13T15:15:24Z

A config option to allow a variant vmap() using huge pages that was never upstreamed had some bits of code related to it scattered around the tile architecture; the config option was removed downstream and this commit cleans up the scattered evidence of it from the upstream as well. Signed-off-by: Chris Metcalf

tile: use pmd_pfn() instead of casting via pte_t

2013-09-13T15:14:25Z

Signed-off-by: Chris Metcalf

tile: fix typos in comment in arch/tile/kernel/unaligned.c

2013-09-13T14:57:54Z

Signed-off-by: Chris Metcalf

Remove GENERIC_HARDIRQ config option

2013-09-13T13:09:52Z

After the last architecture switched to generic hard irqs the config options HAVE_GENERIC_HARDIRQS & GENERIC_HARDIRQS and the related code for !CONFIG_GENERIC_HARDIRQS can be removed. Signed-off-by: Martin Schwidefsky

arch: mm: pass userspace fault flag to generic fault handler

2013-09-12T22:38:01Z

Unlike global OOM handling, memory cgroup code will invoke the OOM killer in any OOM situation because it has no way of telling faults occuring in kernel context - which could be handled more gracefully - from user-triggered faults. Pass a flag that identifies faults originating in user space from the architecture-specific fault handlers to generic code so that memcg OOM handling can be improved. Signed-off-by: Johannes Weiner Reviewed-by: Michal Hocko Cc: David Rientjes Cc: KAMEZAWA Hiroyuki Cc: azurIt Cc: KOSAKI Motohiro Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds