From: Andi Kleen <andi@firstfloor.org>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, fengguang.wu@intel.com,
akpm@linux-foundation.org
Subject: Re: RFC: Implement hwpoison on free for soft offlining
Date: Tue, 12 Oct 2010 10:11:04 +0200 [thread overview]
Message-ID: <87aamj3k6f.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1286402951-1881-1-git-send-email-andi@firstfloor.org> (Andi Kleen's message of "Thu, 7 Oct 2010 00:09:10 +0200")
Andi Kleen <andi@firstfloor.org> writes:
> Here's a somewhat experimental patch to improve soft offlining
> in hwpoison, but allowing hwpoison on free for not directly
> freeable page types. It should work for nearly all
> left over page types that get eventually freed, so this makes
> soft offlining nearly universal. The only non handleable page
> types are now pages that never get freed.
>
> Drawback: It needs an additional page flag. Cannot set hwpoison
> directly because that would not be "soft" and cause errors.
Ping? Any comments on this patch?
Except for the page flag use I think it's nearly a no brainer.
A lot of new soft hwpoison capability for very little additional code.
Has anyone a problem using up a 64bit page flag for that?
Thanks,
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, fengguang.wu@intel.com,
akpm@linux-foundation.org
Subject: Re: RFC: Implement hwpoison on free for soft offlining
Date: Tue, 12 Oct 2010 10:11:04 +0200 [thread overview]
Message-ID: <87aamj3k6f.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1286402951-1881-1-git-send-email-andi@firstfloor.org> (Andi Kleen's message of "Thu, 7 Oct 2010 00:09:10 +0200")
Andi Kleen <andi@firstfloor.org> writes:
> Here's a somewhat experimental patch to improve soft offlining
> in hwpoison, but allowing hwpoison on free for not directly
> freeable page types. It should work for nearly all
> left over page types that get eventually freed, so this makes
> soft offlining nearly universal. The only non handleable page
> types are now pages that never get freed.
>
> Drawback: It needs an additional page flag. Cannot set hwpoison
> directly because that would not be "soft" and cause errors.
Ping? Any comments on this patch?
Except for the page flag use I think it's nearly a no brainer.
A lot of new soft hwpoison capability for very little additional code.
Has anyone a problem using up a 64bit page flag for that?
Thanks,
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-10-12 8:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 22:09 RFC: Implement hwpoison on free for soft offlining Andi Kleen
2010-10-06 22:09 ` Andi Kleen
2010-10-06 22:09 ` [PATCH] HWPOISON: Implement hwpoison-on-free " Andi Kleen
2010-10-06 22:09 ` Andi Kleen
2010-10-12 12:26 ` Wu Fengguang
2010-10-12 12:26 ` Wu Fengguang
2010-10-12 12:37 ` Andi Kleen
2010-10-12 12:37 ` Andi Kleen
2010-10-12 12:41 ` Wu Fengguang
2010-10-12 12:41 ` Wu Fengguang
2010-10-12 8:11 ` Andi Kleen [this message]
2010-10-12 8:11 ` RFC: Implement hwpoison on free " Andi Kleen
2010-10-12 9:20 ` KOSAKI Motohiro
2010-10-12 9:20 ` KOSAKI Motohiro
2010-10-12 13:14 ` Andi Kleen
2010-10-12 13:14 ` Andi Kleen
2010-10-13 0:15 ` KOSAKI Motohiro
2010-10-13 0:15 ` KOSAKI Motohiro
2010-10-15 8:50 ` Andi Kleen
2010-10-15 8:50 ` Andi Kleen
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=87aamj3k6f.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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.