1. 13 10月, 2012 6 次提交
  2. 12 10月, 2012 9 次提交
    • K
      xen/bootup: allow {read|write}_cr8 pvops call. · 1a7bbda5
      Konrad Rzeszutek Wilk 提交于
      We actually do not do anything about it. Just return a default
      value of zero and if the kernel tries to write anything but 0
      we BUG_ON.
      
      This fixes the case when an user tries to suspend the machine
      and it blows up in save_processor_state b/c 'read_cr8' is set
      to NULL and we get:
      
      kernel BUG at /home/konrad/ssd/linux/arch/x86/include/asm/paravirt.h:100!
      invalid opcode: 0000 [#1] SMP
      Pid: 2687, comm: init.late Tainted: G           O 3.6.0upstream-00002-gac264ac-dirty #4 Bochs Bochs
      RIP: e030:[<ffffffff814d5f42>]  [<ffffffff814d5f42>] save_processor_state+0x212/0x270
      
      .. snip..
      Call Trace:
       [<ffffffff810733bf>] do_suspend_lowlevel+0xf/0xac
       [<ffffffff8107330c>] ? x86_acpi_suspend_lowlevel+0x10c/0x150
       [<ffffffff81342ee2>] acpi_suspend_enter+0x57/0xd5
      
      CC: stable@vger.kernel.org
      Signed-off-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      1a7bbda5
    • K
      xen/bootup: allow read_tscp call for Xen PV guests. · cd0608e7
      Konrad Rzeszutek Wilk 提交于
      The hypervisor will trap it. However without this patch,
      we would crash as the .read_tscp is set to NULL. This patch
      fixes it and sets it to the native_read_tscp call.
      
      CC: stable@vger.kernel.org
      Signed-off-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      cd0608e7
    • J
      kgdb,x86: fix warning about unused variable · 42c12213
      Jason Wessel 提交于
      When compiling without CONFIG_DEBUG_RODATA the following
      compiler warning is generated:
      
      arch/x86/kernel/kgdb.c: In function 'kgdb_arch_set_breakpoint':
      arch/x86/kernel/kgdb.c:749: warning: unused variable 'opc'
      
      The variable instantiation needs to be inside the #ifdef to
      make the warning go away.
      Reported-by: NThiago Rafael Becker <trbecker@trbecker.org>
      Signed-off-by: NJason Wessel <jason.wessel@windriver.com>
      42c12213
    • J
      mips,kgdb: fix recursive page fault with CONFIG_KPROBES · f0a996ee
      Jason Wessel 提交于
      This fault was detected using the kgdb test suite on boot and it
      crashes recursively due to the fact that CONFIG_KPROBES on mips adds
      an extra die notifier in the page fault handler.  The crash signature
      looks like this:
      
      kgdbts:RUN bad memory access test
      KGDB: re-enter exception: ALL breakpoints killed
      Call Trace:
      [<807b7548>] dump_stack+0x20/0x54
      [<807b7548>] dump_stack+0x20/0x54
      
      The fix for now is to have kgdb return immediately if the fault type
      is DIE_PAGE_FAULT and allow the kprobe code to decide what is supposed
      to happen.
      
      Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
      Cc: David S. Miller <davem@davemloft.net>
      Cc: <stable@vger.kernel.org>
      Signed-off-by: NJason Wessel <jason.wessel@windriver.com>
      f0a996ee
    • A
      ppc: eeh_event should just use kthread_run() · ecf89e58
      Al Viro 提交于
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      ecf89e58
    • A
      alpha: get rid of switch_stack argument of do_work_pending() · cb450766
      Al Viro 提交于
      ... and now the asm glue side of that.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      cb450766
    • A
      alpha: don't bother passing switch_stack separately from regs · d9d0738a
      Al Viro 提交于
      It's needed only in setup_sigcontext() and it's always reg - <constant>;
      no point passing it all way down through the call chain.  This is just
      the signal.c side of that stuff; next will come the asm glue one...
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      d9d0738a
    • A
      alpha: take SIGPENDING/NOTIFY_RESUME loop into signal.c · 6972d6f2
      Al Viro 提交于
      Turn the slow side of work_pending into C function, including all
      the looping.  What we get out of that:
      	* we do _not_ call get_signal_to_deliver() with IRQs disabled
      anymore
      	* no need to save/restore volatiles on each pass if there
      turns to be more than one (unlikely, but still)
      	* all double-restart prevention is in C now.
      	* glue gets simpler.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      6972d6f2
    • A
      alpha: simplify TIF_NEED_RESCHED handling · 7721d3c2
      Al Viro 提交于
      In case we have both NEED_RESCHED and SIGPENDING/NOTIFY_RESUME,
      handle the latter first.  We'll get to original priorities in
      the next commit, but now that allows to simplify the treatment
      of NEED_RESCHED-only case nicely.  Namely, now there no need to
      preserve the data for restarts across the call of schedule() in
      $work_resched; we can get there only if we had either returned
      from syscall without SIGPENDING (in which case we should've
      had no restart-worthy return value and want no restarts) or
      already got through do_notify_resume() call (in which case we
      want no restarts anymore).  So we can just slap 0 into $19
      instead of preserving it (and $20).
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      7721d3c2
  3. 11 10月, 2012 8 次提交
  4. 10 10月, 2012 10 次提交
  5. 09 10月, 2012 7 次提交
    • A
      ARM: integrator: use __iomem pointers for MMIO, part 2 · 21c8715f
      Arnd Bergmann 提交于
      Due to some interesting merges in the integrator code, not
      all users of mmio pointers were converted before, this
      fixes all warnings that got introduced as a consequence.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Linus Walleij <linus.walleij@linaro.org>
      Cc: Russell King <rmk+kernel@arm.linux.org.uk>
      21c8715f
    • A
      ARM: assabet: fix bogus warning in get_assabet_scr (again) · c6e9fbbf
      Arnd Bergmann 提交于
      Russell fixed this bogus warning before in 2f3eca8b "Shut up gcc
      warning in assabet.c", but apparently gcc has become smarter (or dumber)
      since 2005, and the same warning came up again.
      
      This uses the uninitialized_var() macro to convince gcc that the
      variable is actually being initialized. 100 times in fact.
      
      Without this patch, building assabet_defconfig results in:
      
      arch/arm/mach-sa1100/assabet.c: In function 'fixup_assabet':
      arch/arm/mach-sa1100/assabet.c:397:6: warning: 'scr' may be used uninitialized in this function [-Wuninitialized]
      arch/arm/mach-sa1100/assabet.c:389:16: note: 'scr' was declared here
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Russell King <rmk+kernel@arm.linux.org.uk>
      c6e9fbbf
    • A
      ARM: shmobile: mark shmobile_init_late as __init · b3796d92
      Arnd Bergmann 提交于
      Patch 35f2b0bd "ARM: shmobile: Move definition of shmobile_init_late()
      to header" moved the definition of the shmobile_init_late function, but
      dropped the __init annotation, which is now causing warnings because
      the function calls shmobile_suspend_init, which is also marked init.
      
      Without this patch, building kota2_defconfig results in:
      
      WARNING: vmlinux.o(.text+0xb7c8): Section mismatch in reference from the function shmobile_init_late() to the function .init.text:shmobile_suspend_init()
      The function shmobile_init_late() references
      the function __init shmobile_suspend_init().
      This is often because shmobile_init_late lacks a __init
      annotation or the annotation of shmobile_suspend_init is wrong.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Rafael J. Wysocki <rjw@sisk.pl>
      Cc: Magnus Damm <damm@opensource.se>
      Cc: Simon Horman <horms@verge.net.au>
      b3796d92
    • O
      ARM: integrator_cp: fix build failure · 6e3a78d9
      Olof Johansson 提交于
      arch/arm/mach-integrator/integrator_cp.c:272:32: error: 'of_aliases'
      undeclared (first use in this function)
      
      Move the OF-only timer init under #ifdef CONFIG_OF, just like
      integrator_ap has it.
      Reviewed-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      6e3a78d9
    • M
      s390/entry: fix svc number for TIF_SYSCALL system call restart · 450e47da
      Martin Schwidefsky 提交于
      The load of the svc number in the TIF_SYSCALL restart path needs to be
      done with an instruction that loads all 64 bits of %r1, 'lh' only loads
      32 bits. If the upper half of %r1 is not zero and has the msb set,
      entry64.S will try to execute an svc with a really large number.
      What will be in the upper half of %r1 depends on the code generated by
      gcc for the functions on the do_signal() callchain.
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      450e47da
    • H
      s390/mm,vmem: fix vmem_add_mem()/vmem_remove_range() · fc7e48aa
      Heiko Carstens 提交于
      vmem_add_mem() should only then insert a large page if pmd_none() is true
      for the specific entry. We might have a leftover from a previous mapping.
      In addition make vmem_remove_range()'s page table walk code more complete
      and fix a couple of potential endless loops (which can never happen :).
      Signed-off-by: NHeiko Carstens <heiko.carstens@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      fc7e48aa
    • H
      s390/vmalloc: have separate modules area · c972cc60
      Heiko Carstens 提交于
      Add a special module area on top of the vmalloc area, which may be only
      used for modules and bpf jit generated code.
      This makes sure that inter module branches will always happen without a
      trampoline and in addition having all the code within a 2GB frame is
      branch prediction unit friendly.
      Signed-off-by: NHeiko Carstens <heiko.carstens@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      c972cc60