linux-kernel - Re: [PATCH] perf_events: AMD event scheduling (v3)

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: <1265818441.11509.305.camel@laptop>
Date:	Wed, 10 Feb 2010 17:14:01 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Robert Richter <robert.richter@....com>
Cc:	eranian@...gle.com, linux-kernel@...r.kernel.org, mingo@...e.hu,
	paulus@...ba.org, davem@...emloft.net, fweisbec@...il.com,
	perfmon2-devel@...ts.sf.net, eranian@...il.com
Subject: Re: [PATCH]  perf_events: AMD event scheduling (v3)

On Wed, 2010-02-10 at 17:09 +0100, Robert Richter wrote:
> On 10.02.10 12:59:26, Peter Zijlstra wrote:
> > On Mon, 2010-02-08 at 17:17 +0200, Stephane Eranian wrote:
> > >         This patch adds correct AMD Northbridge event scheduling.
> > >         It must be applied on top tip-x86 + hw_perf_enable() fix.
> > > 
> > >         NB events are events measuring L3 cache, Hypertransport
> > >         traffic. They are identified by an event code  >= 0xe0.
> > >         They measure events on the Northbride which is shared
> > >         by all cores on a package. NB events are counted on a
> > >         shared set of counters. When a NB event is programmed
> > >         in a counter, the data actually comes from a shared
> > >         counter. Thus, access to those counters needs to be
> > >         synchronized.
> > > 
> > >         We implement the synchronization such that no two cores
> > >         can be measuring NB events using the same counters. Thus,
> > >         we maintain a per-NB * allocation table. The available slot
> > >         is propagated using the event_constraint structure.
> > > 
> > >         The 2nd version takes into account the changes on how
> > >         constraints are stored by the scheduling code.
> > > 
> > >         The 3rd version fixes formatting issues, code readability
> > >         and one bug in amd_put_event_constraints().
> > > 
> > >         Signed-off-by: Stephane Eranian <eranian@...gle.com>
> > 
> > OK, took this with the below merged in.
> 
> Peter,
> 
> will this go to tip/perf/core? Or is there another tree?

Currently my quilt queue, should end up in tip/perf/core in a day or so.

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