From: Cyrill Gorcunov <gorcunov@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>,
Don Zickus <dzickus@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
mingo@elte.hu, fweisbec@gmail.com, robert.richter@amd.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] arch generic way to trigger unknown NMIs
Date: Mon, 11 Oct 2010 00:23:57 +0400 [thread overview]
Message-ID: <20101010202357.GA28938@lenovo> (raw)
In-Reply-To: <alpine.LFD.2.00.1010072342170.15889@eddie.linux-mips.org>
On Thu, Oct 07, 2010 at 11:45:59PM +0100, Maciej W. Rozycki wrote:
> On Thu, 7 Oct 2010, Don Zickus wrote:
>
> > No I prefer a single one too, but there didn't seem to be a
> > send_IPI_self() command, so I took the short route and sent it to
> > everyone. :-(
>
> Odd, APIC hardware does explicitly support such a mode (there are three
> shorthands like this actually: all-but-self, all and self), so why don't
> just add a suitable wrapper?
>
> Maciej
>
We have send_IPI_self which can't be used for NMI delivery mode (ie with
self shortland) but still can be used as say (didn't test)
apic->send_IPI_mask(cpumask_of(cpu), NMI_VECTOR)
where cpu is a target.
Cyrill
next prev parent reply other threads:[~2010-10-10 20:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 3:08 [RFC] arch generic way to trigger unknown NMIs Don Zickus
2010-10-07 7:26 ` Andi Kleen
2010-10-07 14:01 ` Don Zickus
2010-10-07 15:11 ` Andi Kleen
2010-10-07 15:47 ` Don Zickus
2010-10-07 16:17 ` Andi Kleen
2010-10-07 22:45 ` Maciej W. Rozycki
2010-10-10 20:23 ` Cyrill Gorcunov [this message]
2010-10-16 7:24 ` Maciej W. Rozycki
2010-10-16 15:32 ` Cyrill Gorcunov
2010-10-16 16:15 ` Maciej W. Rozycki
2010-10-16 16:36 ` Cyrill Gorcunov
2010-10-16 23:59 ` Maciej W. Rozycki
2010-10-17 8:58 ` Cyrill Gorcunov
2010-10-17 16:08 ` Cyrill Gorcunov
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=20101010202357.GA28938@lenovo \
--to=gorcunov@gmail.com \
--cc=andi@firstfloor.org \
--cc=dzickus@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=robert.richter@amd.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.