1. 30 10月, 2007 1 次提交
  2. 20 10月, 2007 1 次提交
  3. 11 10月, 2007 2 次提交
  4. 22 7月, 2007 2 次提交
  5. 22 5月, 2007 1 次提交
    • A
      Detach sched.h from mm.h · e8edc6e0
      Alexey Dobriyan 提交于
      First thing mm.h does is including sched.h solely for can_do_mlock() inline
      function which has "current" dereference inside. By dealing with can_do_mlock()
      mm.h can be detached from sched.h which is good. See below, why.
      
      This patch
      a) removes unconditional inclusion of sched.h from mm.h
      b) makes can_do_mlock() normal function in mm/mlock.c
      c) exports can_do_mlock() to not break compilation
      d) adds sched.h inclusions back to files that were getting it indirectly.
      e) adds less bloated headers to some files (asm/signal.h, jiffies.h) that were
         getting them indirectly
      
      Net result is:
      a) mm.h users would get less code to open, read, preprocess, parse, ... if
         they don't need sched.h
      b) sched.h stops being dependency for significant number of files:
         on x86_64 allmodconfig touching sched.h results in recompile of 4083 files,
         after patch it's only 3744 (-8.3%).
      
      Cross-compile tested on
      
      	all arm defconfigs, all mips defconfigs, all powerpc defconfigs,
      	alpha alpha-up
      	arm
      	i386 i386-up i386-defconfig i386-allnoconfig
      	ia64 ia64-up
      	m68k
      	mips
      	parisc parisc-up
      	powerpc powerpc-up
      	s390 s390-up
      	sparc sparc-up
      	sparc64 sparc64-up
      	um-x86_64
      	x86_64 x86_64-up x86_64-defconfig x86_64-allnoconfig
      
      as well as my two usual configs.
      Signed-off-by: NAlexey Dobriyan <adobriyan@gmail.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      e8edc6e0
  6. 09 5月, 2007 1 次提交
    • C
      move die notifier handling to common code · 1eeb66a1
      Christoph Hellwig 提交于
      This patch moves the die notifier handling to common code.  Previous
      various architectures had exactly the same code for it.  Note that the new
      code is compiled unconditionally, this should be understood as an appel to
      the other architecture maintainer to implement support for it aswell (aka
      sprinkling a notify_die or two in the proper place)
      
      arm had a notifiy_die that did something totally different, I renamed it to
      arm_notify_die as part of the patch and made it static to the file it's
      declared and used at.  avr32 used to pass slightly less information through
      this interface and I brought it into line with the other architectures.
      
      [akpm@linux-foundation.org: build fix]
      [akpm@linux-foundation.org: fix vmalloc_sync_all bustage]
      [bryan.wu@analog.com: fix vmalloc_sync_all in nommu]
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Cc: <linux-arch@vger.kernel.org>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Signed-off-by: NBryan Wu <bryan.wu@analog.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      1eeb66a1
  7. 27 6月, 2006 1 次提交
  8. 12 1月, 2006 1 次提交
    • E
      [PATCH] i386/x86-64: Don't IPI to offline cpus on shutdown · 6e3fbee5
      Eric W. Biederman 提交于
      So why are we calling smp_send_stop from machine_halt?
      
      We don't.
      
      Looking more closely at the bug report the problem here
      is that halt -p is called which triggers not a halt but
      an attempt to power off.
      
      machine_power_off calls machine_shutdown which calls smp_send_stop.
      
      If pm_power_off is set we should never make it out machine_power_off
      to the call of do_exit.  So pm_power_off must not be set in this case.
      When pm_power_off is not set we expect machine_power_off to devolve
      into machine_halt.
      
      So how do we fix this?
      
      Playing too much with smp_send_stop is dangerous because it
      must also be safe to be called from panic.
      
      It looks like the obviously correct fix is to only call
      machine_shutdown when pm_power_off is defined.  Doing
      that will make Andi's assumption about not scheduling
      true and generally simplify what must be supported.
      
      This turns machine_power_off into a noop like machine_halt
      when pm_power_off is not defined.
      
      If the expected behavior is that sys_reboot(LINUX_REBOOT_CMD_POWER_OFF)
      becomes sys_reboot(LINUX_REBOOT_CMD_HALT) if pm_power_off is NULL
      this is not quite a comprehensive fix as we pass a different parameter
      to the reboot notifier and we set system_state to a different value
      before calling device_shutdown().
      
      Unfortunately any fix more comprehensive I can think of is not
      obviously correct.  The core problem is that there is no architecture
      independent way to detect if machine_power will become a noop, without
      calling it.
      Signed-off-by: NAndi Kleen <ak@suse.de>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      6e3fbee5
  9. 15 11月, 2005 2 次提交
  10. 27 7月, 2005 4 次提交
  11. 26 6月, 2005 1 次提交
  12. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4