linux-kernel - [patch 0/2] NOHZ vs. profile/oprofile

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]

Message-Id: <20090528150447.152019714@de.ibm.com>
Date:	Thu, 28 May 2009 17:04:47 +0200
From:	Martin Schwidefsky <schwidefsky@...ibm.com>
To:	linux-kernel@...r.kernel.org
Cc:	Rob van der Heij <rvdheij@...il.com>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	john stultz <johnstul@...ibm.com>
Subject: [patch 0/2] NOHZ vs. profile/oprofile

Greetings,
Rob pointed me to a deficiency with the current profile/oprofile
code together with NOHZ. For us this problem crept in with the
conversion of s390 to generic clock events, git commit 5a62b192
If the system is running with the HZ-tick disabled and the cpu spents
time in idle we see skewed percentages e.g. with the oprofile output.
On an I/O bound system the number of idle ticks is way to small. The
reason is that the generic clock events code reports either zero or
one tick to profile/oprofile on wakeup from idle even if the cpu has
slept much longer.
I've tried to fix that with the two patches in this series and
another pure s390 specific fix (profile_tick is called from
clock_comparator_work which is nonsense). These three do correct the
oprofile output on s390. The best idea I had to get oprofile in good
shape again is to let the system tick at the HZ rate while oprofile
is working. Better ideas welcome.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

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