From: Pavel Machek <pavel@ucw.cz>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
markus.t.metzger@gmail.com, linux-kernel@vger.kernel.org,
a.p.zijlstra@chello.nl
Subject: Re: [patch] x86, perf_counter, bts: optimize BTS overflow handling
Date: Tue, 15 Sep 2009 13:34:08 +0200 [thread overview]
Message-ID: <20090915113408.GD1328@ucw.cz> (raw)
In-Reply-To: <20090908083110.A7541@sedona.ch.intel.com>
On Tue 2009-09-08 08:31:10, Markus Metzger wrote:
> Draining the BTS buffer on a buffer overflow interrupt takes too long
> resulting in a kernel lockup when tracing the kernel.
Wait. If 'takes too long' leads to 'lockup'...solution is not making
it faster. Solution should be making kernel robust -- maybe disable
tracing when it can't keep up or something...? or maybe disabling
interrupt until you handle the previous one...?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-09-15 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 6:31 [patch] x86, perf_counter, bts: optimize BTS overflow handling Markus Metzger
2009-09-15 11:34 ` Pavel Machek [this message]
2009-09-15 12:07 ` Metzger, Markus T
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=20090915113408.GD1328@ucw.cz \
--to=pavel@ucw.cz \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@gmail.com \
--cc=markus.t.metzger@intel.com \
--cc=mingo@elte.hu \
--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