[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A380767.6080304@zytor.com>
Date: Tue, 16 Jun 2009 13:58:15 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Russ Anderson <rja@....com>
CC: Andi Kleen <andi@...stfloor.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Hugh Dickins <hugh.dickins@...cali.co.uk>,
Wu Fengguang <fengguang.wu@...el.com>,
Balbir Singh <balbir@...ux.vnet.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
Mel Gorman <mel@....ul.ie>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Nick Piggin <npiggin@...e.de>,
"riel@...hat.com" <riel@...hat.com>,
"chris.mason@...cle.com" <chris.mason@...cle.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH 00/22] HWPOISON: Intro (v5)
Russ Anderson wrote:
>>
>> However, the more fundamental thing is that it is always trivial to
>> promote an error to a higher severity; the opposite is not true. As
>> such, it becomes an administrator-set policy, which is what it needs to be.
>
> Good point. On ia64 the recovery code is implemented as a kernel
> loadable module. Installing the module turns on the feature.
>
> That is handy for customer demos. Install the module, inject a
> memory error, have an application read the bad data and get killed.
> Repeat a few times. Then uninstall the module, inject a
> memory error, have an application read the bad data and watch
> the system panic.
>
> Then it is the customer's choice to have it on or off.
>
There are a number of ways to set escalation policy. Modules isn't
necessarily the best, but it doesn't really matter what the exact
mechanism is.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists