From: Don Zickus <dzickus@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, Cyrill Gorcunov <gorcunov@gmail.com>,
aris@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: introduce NMI_AUTO as nmi_watchdog option
Date: Wed, 13 Jan 2010 11:25:34 -0500 [thread overview]
Message-ID: <20100113162534.GX24885@redhat.com> (raw)
In-Reply-To: <1263388422.4244.214.camel@laptop>
On Wed, Jan 13, 2010 at 02:13:42PM +0100, Peter Zijlstra wrote:
> On Wed, 2010-01-13 at 10:32 +0100, Ingo Molnar wrote:
> > other architectures have NMI concepts as well, such as Sparc64.
>
> I think both sparc64 and ppc64 fake NMIs by playing games with hw IRQ
> priorities and partial masks. But yes.
>
> One interesting 'feature' for the perf-nmi interaction is creating an
> idle scheduling class for counters, because as long as there is a
> counter present you can use his NMIs to drive the watchdog, but as soon
> as there are non left, you need to install one.
Interesting idea. How can I guarantee the frequency of the NMI I want to
piggyback off of? A breakpoint that takes an hour to trigger may not be
the best NMI to use? Then again I am still trying to understand the perf
event code a little better.
Cheers,
Don
next prev parent reply other threads:[~2010-01-13 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 19:16 introduce NMI_AUTO as nmi_watchdog option Don Zickus
2010-01-11 20:27 ` Cyrill Gorcunov
2010-01-11 20:33 ` Don Zickus
2010-01-11 20:51 ` Cyrill Gorcunov
2010-01-13 9:32 ` Ingo Molnar
2010-01-13 13:13 ` Peter Zijlstra
2010-01-13 16:25 ` Don Zickus [this message]
2010-01-13 16:42 ` Peter Zijlstra
2010-01-13 16:35 ` Ingo Molnar
2010-01-13 16:23 ` Don Zickus
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=20100113162534.GX24885@redhat.com \
--to=dzickus@redhat.com \
--cc=aris@redhat.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
/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.