[Patch 0/2] Exclude hwpoison page from vmcore dump

Eric W. Biederman ebiederm at xmission.com
Thu Nov 1 06:40:56 EDT 2012

Mitsuhiro Tanino <mitsuhiro.tanino.gm at hitachi.com> writes:

> Hi Vivek,
> (2012/10/31 23:14), Vivek Goyal wrote:
>> If hwpoision functionality is not available in hardware, then respective
>> bit will not be even set in struct page and it will be saved by default.
>> So it should not matter whether hardware has hwpoision functionality
>> or not.
> Thanks, I understand.
>> I think that removing hwpoisno pages by default makes sense. If somebody
>> does have a reasonable case of not doing so, then we could either
>> introduce anther filtering level (based on type) or add another command
>> line option like (--no-hwposion-filtering) etc.
> I agree with you.
> If somebody requests to support for disabling the filter of hwpoison pages,
> this option will be discussed.

I agree.  If we are performing filtering filtering out of poisoned pages
seems very reasonable.  So ack on the basic concept.


More information about the kexec mailing list