linux-kernel - Re: [patch 02/24] perfmon: base code

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: <alpine.LFD.2.00.0811271933500.3325@localhost.localdomain>
Date:	Thu, 27 Nov 2008 19:36:34 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Andi Kleen <andi@...stfloor.org>
cc:	eranian@...il.com, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, mingo@...e.hu, x86@...nel.org,
	sfr@...b.auug.org.au
Subject: Re: [patch 02/24] perfmon: base code

On Thu, 27 Nov 2008, Andi Kleen wrote:

> > Well, where is it checked ? Where is checked whether Oprofile runs or not ?
> 
> That is done using the perfctr reservation. I saw that somewhere in the
> patchkit. The NMI watchdog uses that too.
> 
> > > The Oprofile reservation you see is built on top of the cpumask reservation.
> > > It tries to allocate in one call and atomically ALL the CPUs as this is the way
> > > Oprofile operates. Thus it fails if one perfmon system-wide session or one
> > > perfmon per-thread exists.
> > 
> > This only prevents oprofile from starting, but it does neither prevent
> > thread sessions nor does it prevent a perfmon per cpu session on a cpu
> > which was onlined after oprofile started, simply because it's bit is
> > missing in the CPU mask. 
> 
> The perfctr reservation is global over all CPUs.

So this mean we manage resources on multiple levels, some bits here
and some bits there and five checks in each code path do get them all.

Really convincing concept.

Thanks,

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