linux-kernel - [PATCH 0/7] printk: Make it usable on nohz CPUs v4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu,  8 Nov 2012 14:14:51 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	Anish Kumar <anish198519851985@...il.com>
Subject: [PATCH 0/7] printk: Make it usable on nohz CPUs v4

Hi,

There are rough changes in this series, the patchset is much simpler:

* Include the two fixes for SMP-safe irq_work claim [1/7],[2/7] 

* Split the part that prevent to stop the tick with pending work
on the queue, to make the review easier.

* Don't care anymore whether the arch can send self-IPIs or not. The real point
of it is for when we stop the tick outside idle, we'll require the self IPI
support from arch. We'll deal with that later.

* Drop the set_need_resched() hack when we enqueue in dyntick idle mode. I'm
just too worried that printk() calls in idle loop may prevent the tick from ever
beeing stopped, and even the CPU from halting.

* When the work is lazy, just never raise unless the tick is stopped. We don't care
whether the arch has obscure way to raise it or not. In any case, the hook in
update_process_times() can take care of it.

* Don't raise an IPI after queueing if there is a pending one already.

* Use per cpu irq work for printk because the printk_pending flags are per CPU
and thus can't be handled remotely.

* Queue an irq work in case of printk_sched() as well.

You can fetch from:

git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
	nohz/printk-v4

Thanks.

Frederic Weisbecker (7):
  irq_work: Fix racy IRQ_WORK_BUSY flag setting
  irq_work: Fix racy check on work pending flag
  irq_work: Remove CONFIG_HAVE_IRQ_WORK
  nohz: Add API to check tick state
  irq_work: Don't stop the tick with pending works
  irq_work: Make self-IPIs optable
  printk: Wake up klogd using irq_work

 arch/alpha/Kconfig                  |    1 -
 arch/arm/Kconfig                    |    1 -
 arch/arm64/Kconfig                  |    1 -
 arch/blackfin/Kconfig               |    1 -
 arch/frv/Kconfig                    |    1 -
 arch/hexagon/Kconfig                |    1 -
 arch/mips/Kconfig                   |    1 -
 arch/parisc/Kconfig                 |    1 -
 arch/powerpc/Kconfig                |    1 -
 arch/s390/Kconfig                   |    1 -
 arch/sh/Kconfig                     |    1 -
 arch/sparc/Kconfig                  |    1 -
 arch/x86/Kconfig                    |    1 -
 drivers/staging/iio/trigger/Kconfig |    1 -
 include/linux/irq_work.h            |   20 +++++++++
 include/linux/printk.h              |    3 -
 include/linux/tick.h                |   17 +++++++-
 init/Kconfig                        |    5 +--
 kernel/irq_work.c                   |   76 +++++++++++++++++++++++-----------
 kernel/printk.c                     |   36 +++++++++-------
 kernel/time/tick-sched.c            |    7 ++-
 kernel/timer.c                      |    1 -
 22 files changed, 112 insertions(+), 67 deletions(-)

-- 
1.7.5.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/