linux-kernel - Re: [RFC GIT PULL] nohz: Kconfig layout improvements

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <0000013df44667bc-a362bd49-dc4f-47c3-9220-87f54bf7d079-000000@email.amazonses.com>
Date:	Wed, 10 Apr 2013 14:08:08 +0000
From:	Christoph Lameter <cl@...ux.com>
To:	Frederic Weisbecker <fweisbec@...il.com>
cc:	Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Chris Metcalf <cmetcalf@...era.com>,
	Geoff Levand <geoff@...radead.org>,
	Gilad Ben Yossef <gilad@...yossef.com>,
	Hakan Akkan <hakanakkan@...il.com>,
	Kevin Hilman <khilman@...aro.org>,
	Li Zhong <zhong@...ux.vnet.ibm.com>,
	Namhyung Kim <namhyung.kim@....com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Michal Marek <mmarek@...e.cz>
Subject: Re: [RFC GIT PULL] nohz: Kconfig layout improvements

On Wed, 10 Apr 2013, Frederic Weisbecker wrote:

> I don't know which tree you are using. But if you have that patch in:

This is tip timers/nohz

> http://git.kernel.org/cgit/linux/kernel/git/frederic/linux-dynticks.git/commit/?h=3.9-rc1-nohz1&id=451128553e5e827dccc6cbcd24238470ec693d90
> looking at the traces on that CPU may give you a few hints. Then you can
> dig deeper by looking at the sched_switch, timers, irq, ... events

The last time when I checked this before testing this rev it turned out
that nr_running was always > 1. Traces did only show that the timer
interrupt was still on. I added printks to figure out what was up at that
time which was a bit awkward since the kernel is a bit sensitive about
doing printks in these functions.

Sadly, I am suffering from manageritis these days and probably wont have
the time to get into this again for the next two weeks.



--
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/