From: Scott Wood <scottwood@freescale.com>
To: Micha Nelissen <micha.nelissen@Prodrive.nl>
Cc: Martijn de Gouw <martijn.de.gouw@Prodrive.nl>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: powerpc: Don't silently handle machine checks from userspace
Date: Tue, 6 Nov 2012 14:13:07 -0600 [thread overview]
Message-ID: <1352232787.21833.6@snotra> (raw)
In-Reply-To: <39F93B8F6D09AC4DA45E2F19603FA69C324F2605@exc02.bk.prodrive.nl> (from micha.nelissen@Prodrive.nl on Tue Nov 6 10:43:19 2012)
On 11/06/2012 10:43:19 AM, Micha Nelissen wrote:
> From: Scott Wood [mailto:scottwood@freescale.com]
> >> Hmm I guess there is no simple solution then, since the "recover"
> >> function also prints the kernel messages about the machine check
> >> being in kernel mode without having checked whether it really was =20
> in
> >> kernel mode. In the past the user mode check was in between.
> >
> > It shouldn't be that difficult to make it say "in user mode" or "in
> > kernel mode" depending on which it was... or just remove that phrase
> > altogether and let the following output indicate whether it was in
> > kernel mode.
>=20
> Well printing the correct message is only part of it: do "we" want to =20
> pass guarded load errors (RapidIO bus errors) to user space or not?
Yes.
> And if we pass them, should we print a kernel message at all?
Yes (but maybe ratelimited).
-Scott=
prev parent reply other threads:[~2012-11-06 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 11:48 powerpc: Don't silently handle machine checks from userspace Martijn de Gouw
2012-11-02 16:36 ` Scott Wood
2012-11-06 9:21 ` Micha Nelissen
2012-11-06 16:34 ` Scott Wood
2012-11-06 16:43 ` Micha Nelissen
2012-11-06 20:13 ` Scott Wood [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=1352232787.21833.6@snotra \
--to=scottwood@freescale.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=martijn.de.gouw@Prodrive.nl \
--cc=micha.nelissen@Prodrive.nl \
/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.