linux-kernel - Re: [PATCH 1/1] perf, Add support for Xeon-Phi PMU

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]

Date:	Tue, 25 Sep 2012 16:23:21 +0400
From:	Cyrill Gorcunov <gorcunov@...nvz.org>
To:	stephane eranian <eranian@...glemail.com>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Vince Weaver <vincent.weaver@...ne.edu>,
	linux-kernel@...r.kernel.org, Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	"Meadows, Lawrence F" <lawrence.f.meadows@...el.com>
Subject: Re: [PATCH 1/1] perf, Add support for Xeon-Phi PMU

On Tue, Sep 25, 2012 at 04:22:29PM +0400, Cyrill Gorcunov wrote:
> On Tue, Sep 25, 2012 at 02:05:58PM +0200, stephane eranian wrote:
> > On Tue, Sep 25, 2012 at 2:01 PM, Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
> > > On Tue, 2012-09-25 at 15:42 +0400, Cyrill Gorcunov wrote:
> > >
> > >> Guys, letme re-read this whole mail thread first since I have no clue
> > >> what this remapping about ;)
> > >
> > > x86_setup_perfctr() / set_ext_hw_attr() have special purposed 0 and -1
> > > config values to mean -ENOENT and -EINVAL resp.
> > >
> > > This means neither config value can be a 'real' event. Now it turns out
> > > Xeon-Phi has an actual event 0, which is masked by these special case
> > > thingies.
> > 
> > Then how about using -1 or -2 for ENOENT and EINVAL?
> 
> -2 can't be a valid p4 config as far as i can tell.

I mean such value can be easily recognized by p4 code and treated
specially if needed.
--
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/