linux-kernel - Re: [PATCH v7 1/4] spinlock: A new lockref structure for lockless update of refcount

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:	Mon, 02 Sep 2013 10:09:35 -0600
From:	David Ahern <dsahern@...il.com>
To:	sedat.dilek@...il.com
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Waiman Long <waiman.long@...com>,
	Ingo Molnar <mingo@...nel.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Alexander Viro <viro@...iv.linux.org.uk>,
	Jeff Layton <jlayton@...hat.com>,
	Miklos Szeredi <mszeredi@...e.cz>,
	Ingo Molnar <mingo@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Andi Kleen <andi@...stfloor.org>,
	"Chandramouleeswaran, Aswin" <aswin@...com>,
	"Norton, Scott J" <scott.norton@...com>
Subject: Re: [PATCH v7 1/4] spinlock: A new lockref structure for lockless
 update of refcount

On 9/2/13 4:30 AM, Sedat Dilek wrote:
> On Sun, Sep 1, 2013 at 5:55 PM, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
>> On Sun, Sep 1, 2013 at 8:45 AM, Sedat Dilek <sedat.dilek@...il.com> wrote:
>>>
>>> Samples: 160K of event 'cycles:pp', Event count (approx.): 77003901089
>>> +  12,46%  t_lockref_from-  [kernel.kallsyms]     [k] irq_return
>>> +   4,86%  t_lockref_from-  [kernel.kallsyms]     [k] lockref_get_or_lock
>>> +   4,42%  t_lockref_from-  [kernel.kallsyms]     [k] __ticket_spin_lock
>>> +   4,28%  t_lockref_from-  [kernel.kallsyms]     [k] __acct_update_integrals
>>
>> You need to go into __ticket_spin_lock to see who the callers are.
>>
>> Just go down to it and press enter to expand it (and then you need to
>> go and expand that entry too to get the callers)
>>
>
> I am new to perf usage.

One option for you is 'perf report --stdio ..'. That bypasses the tui.

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