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] [day] [month] [year] [list]

Message-ID: <20120322075159.GC31810@gmail.com>
Date:	Thu, 22 Mar 2012 08:51:59 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Robert Richter <robert.richter@....com>
Cc:	Ingo Molnar <mingo@...e.hu>, 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:

> Ingo,
> 
> On 09.03.12 12:41:12, Robert Richter wrote:
> > > I suspect being able to skid-less profile on AMD CPUs, using 
> > > IBS, would be a useful feature to users. What would be required 
> > > for that to work?
> > 
> > thanks for putting this into tip. This helps a lot.
> > 
> > I am just looking into skid-less sampling. The effort of attaching the
> > rip taken from the IBS sample for events 0x76/0xc1 should be feasable.
> 
> I have some patches ready for release after the merge window. 
> I noticed conflicts between my development tree on top of 
> tip/perf/x86-ibs and tip/perf/core. Could you merge 
> tip/perf/core into tip/perf/x86-ibs? I will rebase my current 
> patches then. This avoids diverging the trees to much and 
> reduces later conflicts.

Feel free to do the merge yourself - that way you can also test 
the merged tree.

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/