From: Ingo Molnar <mingo@elte.hu>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: "hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"a.p.zijlstra@chello.nl" <a.p.zijlstra@chello.nl>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:perfcounters/core] x86, perf_counter, bts: Optimize BTS overflow handling
Date: Mon, 21 Sep 2009 09:32:32 +0200 [thread overview]
Message-ID: <20090921073232.GC24467@elte.hu> (raw)
In-Reply-To: <928CFBE8E7CB0040959E56B4EA41A77EC69BA609@irsmsx504.ger.corp.intel.com>
* Metzger, Markus T <markus.t.metzger@intel.com> wrote:
> >-----Original Message-----
> >From: tip tree robot [mailto:bounces.tip@hpa.at.zytor.com] On Behalf Of tip-bot for Markus Metzger
> >Sent: Friday, September 18, 2009 9:19 PM
> >To: linux-tip-commits@vger.kernel.org
> >Cc: linux-kernel@vger.kernel.org; hpa@zytor.com; mingo@redhat.com; a.p.zijlstra@chello.nl; Metzger,
> >Markus T; tglx@linutronix.de; mingo@elte.hu
> >Subject: [tip:perfcounters/core] x86, perf_counter, bts: Optimize BTS overflow handling
> >
> >Commit-ID: 5622f295b53fb60dbf9bed3e2c89d182490a8b7f
> >Gitweb: http://git.kernel.org/tip/5622f295b53fb60dbf9bed3e2c89d182490a8b7f
> >Author: Markus Metzger <markus.t.metzger@intel.com>
> >AuthorDate: Tue, 15 Sep 2009 13:00:23 +0200
> >Committer: Ingo Molnar <mingo@elte.hu>
> >CommitDate: Fri, 18 Sep 2009 20:43:20 +0200
> >
> >x86, perf_counter, bts: Optimize BTS overflow handling
> >
> >Draining the BTS buffer on a buffer overflow interrupt takes too
> >long resulting in a kernel lockup when tracing the kernel.
> >
> >Restructure perf_counter sampling into sample creation and sample
> >output.
> >
> >Prepare a single reference sample for BTS sampling and update the
> >from and to address fields when draining the BTS buffer. Drain the
> >entire BTS buffer between a single perf_output_begin() /
> >perf_output_end() pair.
> >
> >Signed-off-by: Markus Metzger <markus.t.metzger@intel.com>
> >Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> >LKML-Reference: <20090915130023.A16204@sedona.ch.intel.com>
> >Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
>
> Ingo,
>
> This change should speed up BTS overflow handling enough to support
> branch tracing the kernel.
> Would you please drop 1653192f510bd8114b7b133d7289e6e5c3e95046
> that disabled kernel tracing to work around the issue.
Please send a proper patch that re-enables the (previously unreliable)
aspect of BTS tracing, with a changelog that explains that the feature
now works and with an indication that you've tested it.
Ingo
prev parent reply other threads:[~2009-09-21 7:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 11:00 [patch, resend] x86, perf_counter, bts: optimize BTS overflow handling Markus Metzger
2009-09-15 11:12 ` Peter Zijlstra
2009-09-15 11:18 ` Metzger, Markus T
2009-09-15 11:25 ` Peter Zijlstra
2009-09-15 11:35 ` Metzger, Markus T
2009-09-15 11:40 ` Peter Zijlstra
2009-09-15 12:19 ` Metzger, Markus T
2009-09-18 19:18 ` [tip:perfcounters/core] x86, perf_counter, bts: Optimize " tip-bot for Markus Metzger
2009-09-21 7:25 ` Metzger, Markus T
2009-09-21 7:32 ` Ingo Molnar [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=20090921073232.GC24467@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=markus.t.metzger@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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