From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Steven Noonan <steven@uplinklabs.net>,
Ben Guthro <ben@guthro.net>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: bisected: 'perf top' causing soft lockups under Xen
Date: Tue, 20 Mar 2012 16:33:30 +0100 [thread overview]
Message-ID: <1332257610.18960.430.camel@twins> (raw)
In-Reply-To: <20120320152354.GB29135@phenom.dumpdata.com>
On Tue, 2012-03-20 at 11:23 -0400, Konrad Rzeszutek Wilk wrote:
> But in the meantime, are there any good docs to look over to get a good idea
> of how the perf code works?
Nope.. I don't think anybody bothered to write it down, and if they did
keep it up to date.
Best option is to just ask specific questions, either via email or irc.
But in particular the self-ipi stuff is contained in kernel/irq_work.c.
Its a lock-less list of work-items to be ran from irq-context on the cpu
that queues them. Typical usage would be from NMI context, although you
could equally well use it from any other context.
next prev parent reply other threads:[~2012-03-20 15:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 2:32 bisected: 'perf top' causing soft lockups under Xen Steven Noonan
2012-02-10 16:12 ` Konrad Rzeszutek Wilk
2012-02-10 17:24 ` Peter Zijlstra
2012-02-10 17:28 ` Peter Zijlstra
2012-02-10 19:04 ` Konrad Rzeszutek Wilk
2012-02-11 2:34 ` Ben Guthro
2012-02-12 20:50 ` Steven Noonan
2012-02-15 8:57 ` Steven Noonan
2012-02-15 9:25 ` Peter Zijlstra
2012-02-15 9:32 ` Steven Noonan
2012-02-15 17:14 ` Konrad Rzeszutek Wilk
2012-02-15 16:17 ` Konrad Rzeszutek Wilk
2012-03-20 15:23 ` Konrad Rzeszutek Wilk
2012-03-20 15:33 ` Peter Zijlstra [this message]
2012-02-10 19:14 ` Steven Noonan
2012-02-10 19:27 ` Steven Noonan
2012-02-10 19:29 ` Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1332257610.18960.430.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=ben@guthro.net \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=steven@uplinklabs.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox