1. 15 5月, 2013 2 次提交
    • T
      cgroup: drop hierarchy_id_lock · 54e7b4eb
      Tejun Heo 提交于
      Now that hierarchy_id alloc / free are protected by the cgroup
      mutexes, there's no need for this separate lock.  Drop it.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Acked-by: NLi Zefan <lizefan@huawei.com>
      54e7b4eb
    • T
      cgroup: refactor hierarchy_id handling · fa3ca07e
      Tejun Heo 提交于
      We're planning to converting hierarchy_ida to an idr and use it to
      look up hierarchy from its id.  As we want the mapping to happen
      atomically with cgroupfs_root registration, this patch refactors
      hierarchy_id init / exit so that ida operations happen inside
      cgroup_[root_]mutex.
      
      * s/init_root_id()/cgroup_init_root_id()/ and make it return 0 or
        -errno like a normal function.
      
      * Move hierarchy_id initialization from cgroup_root_from_opts() into
        cgroup_mount() block where the root is confirmed to be used and
        being registered while holding both mutexes.
      
      * Split cgroup_drop_id() into cgroup_exit_root_id() and
        cgroup_free_root(), so that ID release can happen before dropping
        the mutexes in cgroup_kill_sb().  The latter expects hierarchy_id to
        be exited before being invoked.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Acked-by: NLi Zefan <lizefan@huawei.com>
      fa3ca07e
  2. 10 5月, 2013 16 次提交
  3. 09 5月, 2013 3 次提交
  4. 08 5月, 2013 4 次提交
  5. 06 5月, 2013 1 次提交
    • B
      irqdomain: Allow quiet failure mode · 5fe0c1f2
      Benjamin Herrenschmidt 提交于
      Some interrupt controllers refuse to map interrupts marked as
      "protected" by firwmare. Since we try to map everyting in the
      device-tree on some platforms, we end up with a lot of nasty
      WARN's in the boot log for what is a normal situation on those
      machines.
      
      This defines a specific return code (-EPERM) from the host map()
      callback which cause irqdomain to fail silently.
      
      MPIC is updated to return this when hitting a protected source
      printing only a single line message for diagnostic purposes.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      5fe0c1f2
  6. 05 5月, 2013 2 次提交
  7. 04 5月, 2013 3 次提交
    • F
      sched: Keep at least 1 tick per second for active dynticks tasks · 265f22a9
      Frederic Weisbecker 提交于
      The scheduler doesn't yet fully support environments
      with a single task running without a periodic tick.
      
      In order to ensure we still maintain the duties of scheduler_tick(),
      keep at least 1 tick per second.
      
      This makes sure that we keep the progression of various scheduler
      accounting and background maintainance even with a very low granularity.
      Examples include cpu load, sched average, CFS entity vruntime,
      avenrun and events such as load balancing, amongst other details
      handled in sched_class::task_tick().
      
      This limitation will be removed in the future once we get
      these individual items to work in full dynticks CPUs.
      Suggested-by: NIngo Molnar <mingo@kernel.org>
      Signed-off-by: NFrederic Weisbecker <fweisbec@gmail.com>
      Cc: Christoph Lameter <cl@linux.com>
      Cc: Hakan Akkan <hakanakkan@gmail.com>
      Cc: Ingo Molnar <mingo@kernel.org>
      Cc: Kevin Hilman <khilman@linaro.org>
      Cc: Li Zhong <zhong@linux.vnet.ibm.com>
      Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
      Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: Steven Rostedt <rostedt@goodmis.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      265f22a9
    • F
      rcu: Fix full dynticks' dependency on wide RCU nocb mode · 73c30828
      Frederic Weisbecker 提交于
      Commit 0637e029
      ("nohz: Select wide RCU nocb for full dynticks") intended
      to force CONFIG_RCU_NOCB_CPU_ALL=y when full dynticks is
      enabled.
      
      However this option is part of a choice menu and Kconfig's
      "select" instruction has no effect on such targets.
      
      Fix this by using reverse dependencies on the targets we
      don't want instead.
      Reviewed-by: NPaul E. McKenney <paulmck@linux.vnet.ibm.com>
      Signed-off-by: NFrederic Weisbecker <fweisbec@gmail.com>
      Cc: Christoph Lameter <cl@linux.com>
      Cc: Hakan Akkan <hakanakkan@gmail.com>
      Cc: Ingo Molnar <mingo@kernel.org>
      Cc: Kevin Hilman <khilman@linaro.org>
      Cc: Li Zhong <zhong@linux.vnet.ibm.com>
      Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: Steven Rostedt <rostedt@goodmis.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      73c30828
    • S
      ring-buffer: Select IRQ_WORK · 22287688
      Steven Rostedt (Red Hat) 提交于
      As the wake up logic for waiters on the buffer has been moved
      from the tracing code to the ring buffer, it requires also adding
      IRQ_WORK as the wake up code is performed via irq_work.
      
      This fixes compile breakage when a user of the ring buffer is selected
      but tracing and irq_work are not.
      
      Link http://lkml.kernel.org/r/20130503115332.GT8356@rric.localhost
      
      Cc: Arnd Bergmann <arnd@arndb.de>
      Reported-by: NRobert Richter <rric@kernel.org>
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      22287688
  8. 02 5月, 2013 4 次提交
  9. 01 5月, 2013 5 次提交