From: Borislav Petkov <borislav.petkov@amd.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
bluesmoke-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 17/63] edac_mce: Add an interface driver to report mce errors via edac
Date: Fri, 25 Sep 2009 16:40:38 +0200 [thread overview]
Message-ID: <20090925144037.GA16340@aftab> (raw)
In-Reply-To: <20090925160501.03a0f37d@infradead.org>
On Fri, Sep 25, 2009 at 04:05:01PM +0200, Arjan van de Ven wrote:
> On Fri, 25 Sep 2009 15:56:26 +0200
> > > 1) edac_mce is not a module (see patch 18). So, just calling a
> > > routine on edac_mce should be safe, even at NMI;
> >
> > no, I mean the ->check_error member - it could call into a module if
> > i7core_edac is compiled as such.
>
> calling modular code from NMI is not a fatal event though.
No, not really. However, I remember Andi raising a stability concern one
time whether it'd be such a good idea to allow modules to hook into MCE
critical path when the system is already unstable and about to panic.
Therefore, we might want to decode critical MCEs in core kernel code and
non-critical later, at a more appropriate time (aka in modules).
Hmm?
--
Regards/Gruss,
Boris.
Operating | Advanced Micro Devices GmbH
System | Karl-Hammerschmidt-Str. 34, 85609 Dornach b. München, Germany
Research | Geschäftsführer: Andrew Bowd, Thomas M. McCoy, Giuliano Meroni
Center | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
(OSRC) | Registergericht München, HRB Nr. 43632
next prev parent reply other threads:[~2009-09-25 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 22:27 [PATCH 17/63] edac_mce: Add an interface driver to report mce errors via edac Mauro Carvalho Chehab
2009-09-25 9:48 ` Borislav Petkov
2009-09-25 12:11 ` Mauro Carvalho Chehab
2009-09-25 12:47 ` Arjan van de Ven
2009-09-25 14:54 ` Mauro Carvalho Chehab
2009-09-25 13:56 ` Borislav Petkov
2009-09-25 14:05 ` Arjan van de Ven
2009-09-25 14:40 ` Borislav Petkov [this message]
2009-09-25 15:00 ` Arjan van de Ven
2009-09-25 14:46 ` Mauro Carvalho Chehab
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=20090925144037.GA16340@aftab \
--to=borislav.petkov@amd.com \
--cc=arjan@infradead.org \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=mingo@elte.hu \
/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.