linux-kernel - Re: [PATCH] perf, x86: add Intel IvyBridge event scheduling constraints

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: <20130220220802.GE23293@tassilo.jf.intel.com>
Date:	Wed, 20 Feb 2013 14:08:02 -0800
From:	Andi Kleen <ak@...ux.intel.com>
To:	Stephane Eranian <eranian@...gle.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	"mingo@...e.hu" <mingo@...e.hu>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Jiri Olsa <jolsa@...hat.com>,
	Namhyung Kim <namhyung.kim@....com>
Subject: Re: [PATCH] perf, x86: add Intel IvyBridge event scheduling
 constraints

> > Except for LDM_PENDING the CYCLE_ACTIVITY events have been also added to Sandy Bridge.
> > So it should be also added there.
> >
> As far as I know and I double-checked the documentation I have, there
> is no CYCLE_ACTIVITY
> event on SNB or SNB-EP.

page 19-28 in the Jan 2013 SDM. It was only recently added.
It's only a subset of what you have on Ivy Bridge.

> 
> > In fact I think you can still share the table because it would just add some
> > non existent events to Sandy Bridge, which is a noop.
> >
> I don't see the point of this, except saving a few bytes. Isn't it
> better to keep each PMU separate?

Ok, as long as you update the SNB table too.

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