linux-kernel - Re: [tip:perf/urgent] perf/x86: Enable raw event access to Intel offcore events

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: <CABPqkBQwvWiaMfAiKAea9WJwJF6ZTwN9e16=VFLQ_cQsfY_FHQ@mail.gmail.com>
Date:	Mon, 21 Nov 2011 22:45:21 +0100
From:	Stephane Eranian <eranian@...gle.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Vince Weaver <vweaver1@...s.utk.edu>, mingo@...hat.com,
	hpa@...or.com, linux-kernel@...r.kernel.org, tglx@...utronix.de,
	mingo@...e.hu
Subject: Re: [tip:perf/urgent] perf/x86: Enable raw event access to Intel
 offcore events

On Mon, Nov 21, 2011 at 10:42 PM, Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
> On Mon, 2011-11-21 at 22:39 +0100, Stephane Eranian wrote:
>> To solve this problem (in the general case), you need to know which
>> counter is taken (or required)
>> by ALL pinned system-wide events across all CPUs. Once you've
>> constructed the bitmap, you can
>> use it as the basis (used_mask) to try and schedule the group events.
>>
> Its worse, you also need to consider all task-pinned events if you want
> to be complete. That's an even worse problem.
>
But that you know because by the time you do the simulation you already
know the task the events are attached to. You can get to the list of events
already attached to the task. Again this is a best effort, it could well be
that someone else attaches pinned task events just after the simulation.
--
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/