linux-kernel - Re: [patch 2/2] keep on ticking if oprofile is active

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

Message-ID: <20090601122234.725c1e97@skybase>
Date:	Mon, 1 Jun 2009 12:22:34 +0200
From:	Martin Schwidefsky <schwidefsky@...ibm.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-kernel@...r.kernel.org, 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: Re: [patch 2/2] keep on ticking if oprofile is active

On Mon, 01 Jun 2009 10:09:27 +0200
Andi Kleen <andi@...stfloor.org> wrote:

> Martin Schwidefsky <schwidefsky@...ibm.com> writes:
> 
> > From: Martin Schwidefsky <schwidefsky@...ibm.com>
> >
> > On a NOHZ system with oprofile enabled the timer tick should not be
> 
> The old style profile=... profiler should do that too.

Technically the old style profiler and NOHZ can be combined (see patch
#1 plus a fix as discussed with Thomas). On the other hand it would make
the code simpler if we just fallback to the standard tick if profile= is
used. My personal preference would be to use my patch.

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