1. 23 10月, 2008 24 次提交
  2. 21 10月, 2008 2 次提交
    • A
      [PATCH] switch ubd · a625c998
      Al Viro 提交于
      ubd_ioctl() doesn't need BKL, so unlocked_ioctl() it becomes...
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      a625c998
    • A
      [PATCH] beginning of methods conversion · d4430d62
      Al Viro 提交于
      To keep the size of changesets sane we split the switch by drivers;
      to keep the damn thing bisectable we do the following:
      	1) rename the affected methods, add ones with correct
      prototypes, make (few) callers handle both.  That's this changeset.
      	2) for each driver convert to new methods.  *ALL* drivers
      are converted in this series.
      	3) kill the old (renamed) methods.
      
      Note that it _is_ a flagday; all in-tree drivers are converted and by the
      end of this series no trace of old methods remain.  The only reason why
      we do that this way is to keep the damn thing bisectable and allow per-driver
      debugging if anything goes wrong.
      
      New methods:
      	open(bdev, mode)
      	release(disk, mode)
      	ioctl(bdev, mode, cmd, arg)		/* Called without BKL */
      	compat_ioctl(bdev, mode, cmd, arg)
      	locked_ioctl(bdev, mode, cmd, arg)	/* Called with BKL, legacy */
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      d4430d62
  3. 20 10月, 2008 2 次提交
    • W
      uml: fix a compile error · 966c8079
      WANG Cong 提交于
      Fix
      
      arch/um/sys-i386/signal.c: In function 'copy_sc_from_user':
      arch/um/sys-i386/signal.c:182: warning: dereferencing 'void *' pointer
      arch/um/sys-i386/signal.c:182: error: request for member '_fxsr_env' in something not a structure or union
      Signed-off-by: NWANG Cong <wangcong@zeuux.org>
      Cc: Jeff Dike <jdike@addtoit.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      966c8079
    • M
      container freezer: implement freezer cgroup subsystem · dc52ddc0
      Matt Helsley 提交于
      This patch implements a new freezer subsystem in the control groups
      framework.  It provides a way to stop and resume execution of all tasks in
      a cgroup by writing in the cgroup filesystem.
      
      The freezer subsystem in the container filesystem defines a file named
      freezer.state.  Writing "FROZEN" to the state file will freeze all tasks
      in the cgroup.  Subsequently writing "RUNNING" will unfreeze the tasks in
      the cgroup.  Reading will return the current state.
      
      * Examples of usage :
      
         # mkdir /containers/freezer
         # mount -t cgroup -ofreezer freezer  /containers
         # mkdir /containers/0
         # echo $some_pid > /containers/0/tasks
      
      to get status of the freezer subsystem :
      
         # cat /containers/0/freezer.state
         RUNNING
      
      to freeze all tasks in the container :
      
         # echo FROZEN > /containers/0/freezer.state
         # cat /containers/0/freezer.state
         FREEZING
         # cat /containers/0/freezer.state
         FROZEN
      
      to unfreeze all tasks in the container :
      
         # echo RUNNING > /containers/0/freezer.state
         # cat /containers/0/freezer.state
         RUNNING
      
      This is the basic mechanism which should do the right thing for user space
      task in a simple scenario.
      
      It's important to note that freezing can be incomplete.  In that case we
      return EBUSY.  This means that some tasks in the cgroup are busy doing
      something that prevents us from completely freezing the cgroup at this
      time.  After EBUSY, the cgroup will remain partially frozen -- reflected
      by freezer.state reporting "FREEZING" when read.  The state will remain
      "FREEZING" until one of these things happens:
      
      	1) Userspace cancels the freezing operation by writing "RUNNING" to
      		the freezer.state file
      	2) Userspace retries the freezing operation by writing "FROZEN" to
      		the freezer.state file (writing "FREEZING" is not legal
      		and returns EIO)
      	3) The tasks that blocked the cgroup from entering the "FROZEN"
      		state disappear from the cgroup's set of tasks.
      
      [akpm@linux-foundation.org: coding-style fixes]
      [akpm@linux-foundation.org: export thaw_process]
      Signed-off-by: NCedric Le Goater <clg@fr.ibm.com>
      Signed-off-by: NMatt Helsley <matthltc@us.ibm.com>
      Acked-by: NSerge E. Hallyn <serue@us.ibm.com>
      Tested-by: NMatt Helsley <matthltc@us.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      dc52ddc0
  4. 17 10月, 2008 1 次提交
  5. 14 10月, 2008 1 次提交
  6. 09 9月, 2008 1 次提交
    • M
      kernel/cpu.c: create a CPU_STARTING cpu_chain notifier · e545a614
      Manfred Spraul 提交于
      Right now, there is no notifier that is called on a new cpu, before the new
      cpu begins processing interrupts/softirqs.
      Various kernel function would need that notification, e.g. kvm works around
      by calling smp_call_function_single(), rcu polls cpu_online_map.
      
      The patch adds a CPU_STARTING notification. It also adds a helper function
      that sends the message to all cpu_chain handlers.
      
      Tested on x86-64.
      All other archs are untested. Especially on sparc, I'm not sure if I got
      it right.
      Signed-off-by: NManfred Spraul <manfred@colorfullife.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      e545a614
  7. 07 9月, 2008 2 次提交
  8. 29 8月, 2008 1 次提交
    • T
      sound: make OSS sound core optional · d886e87c
      Tejun Heo 提交于
      sound/sound_core.c implements soundcore.ko and contains two parts -
      sound_class which is shared by both ALSA and OSS and device
      redirection support for OSS.  It's always compiled when any sound
      support is enabled although it's necessary only when OSS (the actual
      one or emulation) is enabled.  This is slightly wasteful and as device
      redirection always registers character device region for major 14, it
      prevents alternative implementation.
      
      This patch introduces a new config SOUND_OSS_CORE which is selected
      iff OSS support is actually necessary and build the OSS core part
      conditionally.
      
      If OSS is disabled, soundcore merely contains sound_class but leaving
      it that way seems to be the simplest approach as otherwise sound_class
      should be in ALSA core file if OSS is disabled but should be in
      soundcore if OSS is enabled.  Also, there's also the user confusion
      factor.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      Signed-off-by: NJaroslav Kysela <perex@perex.cz>
      d886e87c
  9. 15 8月, 2008 1 次提交
  10. 31 7月, 2008 1 次提交
  11. 27 7月, 2008 1 次提交
  12. 25 7月, 2008 3 次提交
新手
引导
客服 返回
顶部