Re: [PATCH 00/22] HWPOISON: Intro (v5)
From: Andi Kleen
Date: Mon Jun 15 2009 - 03:01:20 EST
On Mon, Jun 15, 2009 at 08:44:47AM +0200, Nick Piggin wrote:
> > So IMHO it's OK for .31 as long as we agree on the user interfaces,
> > ie. /proc/sys/vm/memory_failure_early_kill and the hwpoison uevent.
> > It comes a long way through numerous reviews, and I believe all the
> > important issues and concerns have been addressed. Nick, Rik, Hugh,
> > Ingo, ... what are your opinions? Is the uevent good enough to meet
> > your request to "die hard" or "die gracefully" or whatever on memory
> > failure events?
> Uevent? As in, send a message to userspace? I don't think this
> would be ideal for a fail-stop/failover situation.
For failover you typically want a application level heartbeat anyways
to guard against user space software problems and if there's a kill then it
would catch it. Also again in you want to check against all corruptions you
have to do it in the low level handler or better watch corrected
events too to predict failures (but the later is quite hard to do generally).
To some extent the first is already implemented on x86, e.g. set
the tolerance level to 0 will give more aggressive panics.
> I can't see a good reason to rush to merge it.
The low level x86 code for MCA recovery is in, just this high level
part is missing to kill the correct process. I think it would be good to merge
a core now. The basic code seems to be also as well tested as we can do it
right now and exposing it to more users would be good. It's undoubtedly not
perfect yet, but that's not a requirement for merge.
There's a lot of fancy stuff that could be done in addition,
but that's not really needed right now and for a lot of the fancy
ideas (I have enough on my own :) it's dubious they are actually
> IMO the userspace-visible changes have maybe not been considered
> too thoroughly, which is what I'd be most worried about. I probably
> missed seeing documentation of exact semantics and situations
> where admins should tune things one way or the other.
There's only a single tunable anyways, early kill vs late kill.
For KVM you need early kill, for the others it remains to be seen.
> I hope it is going to be merged with an easy-to-use fault injector,
> because that is the only way Joe kernel developer is ever going to
> test it.
See patches 13 and 14. In addition there's another low level x86
There's also a test suite available (mce-test on kernel.org git)
ak@xxxxxxxxxxxxxxx -- Speaking for myself only.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/