linux-kernel - Re: [PATCH 1/1] perf,tools: error out unsupported group leader immediately for perf stat

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150611142952.GE2696@kernel.org>
Date:	Thu, 11 Jun 2015 11:29:52 -0300
From:	Arnaldo Carvalho de Melo <acme@...nel.org>
To:	"Liang, Kan" <kan.liang@...el.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"andi@...stfloor.org" <andi@...stfloor.org>
Subject: Re: [PATCH 1/1] perf,tools: error out unsupported group leader
 immediately for perf stat

Em Thu, Jun 11, 2015 at 02:26:47PM +0000, Liang, Kan escreveu:
> > Em Thu, Jun 11, 2015 at 02:32:40AM -0400, kan.liang@...el.com escreveu:
> > > With this patch:
> > > $ perf stat -x, -e '{node-prefetch-refs,cycles}' --  sleep 1
> > > Error:
> > > The node-prefetch-refs event is not supported.

> > I get something different, maybe I am missing a patch?

> > With this patch:

> >   [acme@zoo linux]$ perf stat -x, -e '{node-prefetch-refs,cycles}' -- sleep 1
> >   Error:
> >   The sys_perf_event_open() syscall returned with 22 (Invalid argument)
> >   for event (node-prefetch-refs).
> >   /bin/dmesg may provide additional information.
> >   No CONFIG_PERF_EVENTS=y kernel support configured?

> I don't have other patches for this issue.
> It looks they have different error code, ENOENT VS. EINVAL. 
> I have no idea why. 

Well, here I have:

[acme@zoo ~]$ uname -a
Linux zoo.ghostprotocols.net 3.19.7-200.fc21.x86_64 #1 SMP Thu May 7
22:00:21 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

I am rebooting now, due to an unrelated reason, to 4.1.0-rc5+, lets see
if this explains this discrepancy...
 
> > Applying it anyway, as it avoids a core dump and the message, albeit not
> > optimal, points to a problem with that event.

> > Have you tried this with other tools, like perf record?
 
> Yes. Perf record and perf top  will error out immediately if any unsupported event found.
> So they don't have such issue.

Ok, need to revisit the event setup code again and remove the code
duplication once and for all :-\

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