From: Andi Kleen <ak@linux.intel.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"Yan, Zheng" <zheng.z.yan@intel.com>
Subject: Re: [RFC] perf/x86: PMU IRQ handler issues
Date: Wed, 28 May 2014 19:56:55 -0700 [thread overview]
Message-ID: <20140529025655.GA8876@tassilo.jf.intel.com> (raw)
In-Reply-To: <53864517.3040503@intel.com>
> actual numbers describing the issues that you're seeing, including the
> ftrace that Andi was asking for? There are also some handy tracepoints
> for NMI lengths that I stuck in.
Another good thing would be to plot the periods (from perf report -D)
-Andi
prev parent reply other threads:[~2014-05-29 2:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 19:48 [RFC] perf/x86: PMU IRQ handler issues Stephane Eranian
2014-05-28 19:55 ` Andi Kleen
2014-05-28 19:56 ` Stephane Eranian
2014-05-28 20:06 ` Andi Kleen
2014-05-28 20:20 ` Dave Hansen
2014-05-29 2:56 ` Andi Kleen [this message]
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=20140529025655.GA8876@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=dave.hansen@intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=zheng.z.yan@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.