From: Ingo Molnar <mingo@elte.hu>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Greg KH <gregkh@suse.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kurt Garloff <garloff@suse.de>,
linux-kernel@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH] x86: sysctl to allow panic on IOCK NMI error
Date: Wed, 1 Jul 2009 13:10:03 +0200 [thread overview]
Message-ID: <20090701111003.GC15958@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.00.0907010148490.23134@eddie.linux-mips.org>
* Maciej W. Rozycki <macro@linux-mips.org> wrote:
> On Tue, 30 Jun 2009, Greg KH wrote:
>
> > > These days an IOCK NMI typically happens in response to a PCI
> > > SERR -- it may be useful to traverse PCI buses to find the
> > > offender and dump this information on this occasion too. The
> > > south bridge may have additional status too.
> >
> > Sure, that would be great to have. Care to make a patch? :)
>
> ENOTIME, sorry. Next year perhaps. Or a homework project for
> one of the newbies. ;)
You know that this project would kill a newbie, right? :)
We have no real southbridge drivers on x86 - but we should certainly
add some. Also, walking the PCI device tree from NMI context is
tricky as the lists there are not NMI safe - we could crash if we
happen to get a #IOCK while loading/unloading drivers (which is rare
but could happen).
IMHO it's all very much desired functionality, but highly
non-trivial.
Ingo
next prev parent reply other threads:[~2009-07-01 11:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 21:32 [PATCH] x86: sysctl to allow panic on IOCK NMI error Greg KH
2009-06-25 9:16 ` [tip:x86/urgent] x86: Add " tip-bot for Kurt Garloff
2009-06-25 18:15 ` [PATCH] x86: " Eric W. Biederman
2009-06-25 20:07 ` Greg KH
2009-06-25 20:18 ` Ingo Molnar
2009-06-25 20:16 ` Greg KH
2009-06-25 20:06 ` [tip:x86/urgent] x86: Add " tip-bot for Kurt Garloff
2009-06-25 20:09 ` tip-bot for Kurt Garloff
2009-06-30 22:27 ` [PATCH] x86: " Maciej W. Rozycki
2009-06-30 22:30 ` Greg KH
2009-07-01 0:50 ` Maciej W. Rozycki
2009-07-01 11:10 ` Ingo Molnar [this message]
2009-07-01 17:30 ` Jesse Barnes
2009-07-01 17:37 ` Maciej W. Rozycki
2009-07-02 7:53 ` Ingo Molnar
2009-07-02 10:41 ` Borislav Petkov
2009-07-03 7:59 ` Ingo Molnar
2009-07-03 21:35 ` Maciej W. Rozycki
2009-07-03 9:19 ` Kurt Garloff
2009-07-03 9:24 ` Ingo Molnar
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=20090701111003.GC15958@elte.hu \
--to=mingo@elte.hu \
--cc=garloff@suse.de \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.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.