All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Don Zickus <dzickus@redhat.com>, 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: Sun, 17 Oct 2010 20:08:16 +0400	[thread overview]
Message-ID: <20101017160816.GC7925@lenovo> (raw)
In-Reply-To: <20101017085828.GA7925@lenovo>

On Sun, Oct 17, 2010 at 12:58:28PM +0400, Cyrill Gorcunov wrote:
...
> >  How different is it to the other two send_IPI shorthand calls?  Or the 
> > fully-fledged one?  I gather from this thread they already handle NMIs 
> > properly, so what is there within that cannot simply be copied over to 
> > this one?
> > 
> >   Maciej
> > 
> 
>  Hmm, good question ;) I thought about 82489dx which required level
> trigger mode for nmi delivery, new (or present day) apics always
> use edge trigger mode so indeed there is no need for level assert/deassert.
> 
>   Cyrill

I'll try to cook a patch for this.

  Cyrill

      reply	other threads:[~2010-10-17 16:08 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
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 [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=20101017160816.GC7925@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.