linux-kernel - Re: perf, how to support multiple x86 hw pmus?

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: <1281949925.1926.1081.camel@laptop>
Date:	Mon, 16 Aug 2010 11:12:05 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Lin Ming <ming.m.lin@...el.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Robert Richter <robert.richter@....com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Don Zickus <dzickus@...hat.com>,
	Cyrill Gorcunov <gorcunov@...il.com>,
	"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
	"Fu, Michael" <michael.fu@...el.com>
Subject: Re: perf, how to support multiple x86 hw pmus?

On Mon, 2010-08-16 at 16:39 +0800, Lin Ming wrote:
> > After that and some patches adding per pmu contexts adding multiple
> > hardware pmus should be simple.
> 
> I didn't see the per pmu contexts patches, are you still working on
> them?
> 
Yes, although 3 weeks of holidays and a week of LinuxCon didn't help to
finish that work ;-)

I hope to be back to that soon ;-)

> > 
> > uncore should not share any code with the regular pmu, since they're
> > mostly unrelated.
> 
> But should they share code like collect_events, schedule_events,
> x86_perf_event_set_period(with some modification) etc...?
> 
Maybe, I'd have to look at the uncore stuff again, I can't remember if
it has much in the way of event scheduling constraints and if the
counter programming is close enough to the regular pmu to make it worth
sharing code over.


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