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:	Wed, 12 Jan 2011 12:22:33 -0800
From:	Corey Ashford <cjashfor@...ux.vnet.ibm.com>
To:	Stephane Eranian <eranian@...gle.com>
CC:	LKML <linux-kernel@...r.kernel.org>,
	Frédéric Weisbecker 
	<fweisbec@...il.com>, Arnaldo Carvalho de Melo <acme@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>, mingo@...e.hu,
	Robert Richter <robert.richter@....com>
Subject: Re: [BUG] perf sched broken

On 01/12/2011 11:52 AM, Stephane Eranian wrote:
> On Wed, Jan 12, 2011 at 8:41 PM, Corey Ashford
> <cjashfor@...ux.vnet.ibm.com>  wrote:
>> On 01/12/2011 01:29 AM, Stephane Eranian wrote:
>>>
>>> Hi,
>>>
>>> I am trying to use perf sched from tip-x86 but it fails for all my
>>> attempts.
>>
>> So far I have been unsuccessful in reproducing this problem, but I suspect
>> that I have the wrong git tree or branch.  The git tree I've cloned is:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
>>
> I was using this branch.
> I also tried running the tool on ubuntu lucid (2.6.32-based).
>
> Didn't you have to at least fixup the sched event names to drop :r?
> Once you have the perf.data file, how do you dump it?
>
> I tried:
> - perf sched trace ->  error
> - perf sched replay ->  error
> - perf script sched-migration  ->  hangs
> - perf report -D
>
>> I've tried the branches master, x86/urgent, and x86-urgent-for-linus. All of
>> those produce correct results, as far as I can tell.
>>
>> Which tree / branch should I be using?
>>
>> - Corey
>>

I made a stupid mistake!  When I ran perf, it was picking up the 
executable from /usr/bin instead of the kernel build tree.

I am seeing the problem you are reporting now.

Thanks for your patience,

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ