linux-kernel - Re: [PATCH 4/4] perf script: Add script to collect and display IBS samples

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: <20111223163930.GA5983@elte.hu>
Date:	Fri, 23 Dec 2011 17:39:30 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Robert Richter <robert.richter@....com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Stephane Eranian <eranian@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/4] perf script: Add script to collect and display IBS
 samples


* Robert Richter <robert.richter@....com> wrote:

> On 23.12.11 15:40:40, Ingo Molnar wrote:
> > 
> > * Peter Zijlstra <peterz@...radead.org> wrote:
> > 
> > > On Fri, 2011-12-23 at 14:53 +0100, Ingo Molnar wrote:
> > > > * Robert Richter <robert.richter@....com> wrote:
> > > > 
> > > > > > Also, could you quote example output of "perf script report 
> > > > > > ibs"?
> > > > > 
> > > > > IBS_FETCH sample on cpu6	IBS0: 0x00170003186a186a IBS1: 0x0000000000444780 IBS2:0x000000041af26780
> > > > > IBS_FETCH sample on cpu6	IBS0: 0x00170003186a186a IBS1: 0x00007f5efb44e3b2 IBS2:0x000000042fcff3b2
> > > > > IBS_FETCH sample on cpu6	IBS0: 0x01370003186a186a IBS1: 0xffffffff81065273 IBS2:0x0000000001065273
> > > > > IBS_FETCH sample on cpu6	IBS0: 0x01370003186a186a IBS1: 0xffffffff811a6320 IBS2:0x00000000011a6320
> > > > > IBS_FETCH sample on cpu6	IBS0: 0x01370003186a186a IBS1: 0xffffffff81065255 IBS2:0x0000000001065255
> > > > > IBS_FETCH sample on cpu7	IBS0: 0x00170004186a186a IBS1: 0x00007fbf0c687ca0 IBS2:0x000000041d345ca0
> > > > > IBS_FETCH sample on cpu7	IBS0: 0x00170003186a186a IBS1: 0x000000000043bb80 IBS2:0x000000041c351b80
> > > > > IBS_FETCH sample on cpu7	IBS0: 0x01370003186a186a IBS1: 0xffffffff813d5790 IBS2:0x00000000013d5790
> > > > > IBS_FETCH sample on cpu7	IBS0: 0x00030001186a186a IBS1: 0xffffffff8102bd00 IBS2:0x00000000013d5d00
> > > > 
> > > > That does not look very usable to users. So why should we merge 
> > > > this new ABI in its incomplete form with no complete usecase? 
> > > > Being usable is clearly not outside the scope of a new feature 
> > > > ...
> 
> So is it not useful to pull ibs data with native perf tools to 
> userspace? Is it not useful to have a dump of the raw data 
> too? Is it not useful to have perf script support that allows 
> user to easy implement their own script to parse the data they 
> are interested in? IBS is for experienced users, even I don't 
> know *everything* about what this data can be used for, but I 
> know people who know it. And they want to get this data out of 
> the kernel, using the perf_event syscall. Maybe they also 
> improve the perf tool with their knowledge.

No, i think you misunderstood me, i definitely think getting all 
the data out is perfectly fine and useful, if the hardware 
provides it. No need to make 'every' conceivable piece of IBS 
data useful straight away.

All i want is at least *one* common usecase to work fine. This 
allows us to see things in practice and it also provides the 
seed for further improvements.

Right now this does not seem to be the case: the 'report' 
portion only reports a raw hexa dump, not very useful to users.

Once something like 'perf report' works for some useful looking 
sub-case you can also tack on all the extra IBS goodies that 
specialized tools might need as well, i have no problem with 
providing that.

It's the same deal as with -rt or with LWP: niches are fine as 
long as they improve the common case as well.

Thanks,

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