From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>, Mel Gorman <mel@csn.ul.ie>,
lizf@cn.fujitsu.com, nishimura@mxp.nes.nec.co.jp,
menage@google.com, linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC][PATCH 0/4] memcg: add support for hwpoison testing
Date: Tue, 1 Sep 2009 08:46:26 +0900 [thread overview]
Message-ID: <20090901084626.ac4c8879.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090831102640.092092954@intel.com>
On Mon, 31 Aug 2009 18:26:40 +0800
Wu Fengguang <fengguang.wu@intel.com> wrote:
> Hi all,
>
> In hardware poison testing, we want to inject hwpoison errors to pages
> of a collection of selected tasks, so that random tasks (eg. init) won't
> be killed in stress tests and lead to test failure.
>
> Memory cgroup provides an ideal tool for tracking and testing these target
> process pages. All we have to do is to
> - export the memory cgroup id via cgroupfs
> - export two functions/structs for hwpoison_inject.c
>
> This might be an unexpected usage of memory cgroup. The last patch and this
> script demonstrates how the exported interfaces are to be used to limit the
> scope of hwpoison injection.
>
> test -d /cgroup/hwpoison && rmdir /cgroup/hwpoison
> mkdir /cgroup/hwpoison
>
> usemem -m 100 -s 100 & # eat 100MB and sleep 100s
> echo `pidof usemem` > /cgroup/hwpoison/tasks
>
> ==> memcg_id=$(</cgroup/hwpoison/memory.id)
> ==> echo $memcg_id > /debug/hwpoison/corrupt-filter-memcg
>
> # hwpoison all pfn
> pfn=0
> while true
> do
> let pfn=pfn+1
> echo $pfn > /debug/hwpoison/corrupt-pfn
> if [ $? -ne 0 ]; then
> break
> fi
> done
>
I don't like this.
1. plz put all under CONFIG_DEBUG_HWPOISON or some
2. plz don't export memcg's id. you can do it without it.
3. If I was you, just adds following file
memory.hwpoison_test
Then, if you allow test
#echo 1 > memory.hwpoison_test
4. I can't understand why you need this. I wonder you can get pfn via
/proc/<pid>/????. And this may insert HWPOISON to page-cache of shared
library and "unexpected" process will be poisoned.
Thanks,
-Kame
> Comments are welcome, thanks!
>
> Cheers,
> Fengguang
> --
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
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:[~2009-08-31 23:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 10:26 Wu Fengguang
2009-08-31 10:26 ` [RFC][PATCH 1/4] memcg: show memory.id in cgroupfs Wu Fengguang
2009-08-31 10:26 ` [RFC][PATCH 2/4] memcg: rename and export try_get_mem_cgroup_from_page() Wu Fengguang
2009-08-31 10:26 ` [RFC][PATCH 3/4] memcg: add accessor to mem_cgroup.css Wu Fengguang
2009-08-31 10:26 ` [RFC][PATCH 4/4] HWPOISON: memory cgroup based hwpoison injection filtering Wu Fengguang
2009-08-31 12:49 ` [RFC][PATCH 0/4] memcg: add support for hwpoison testing Balbir Singh
2009-08-31 12:59 ` Wu Fengguang
2009-08-31 23:46 ` KAMEZAWA Hiroyuki [this message]
2009-09-01 2:25 ` Wu Fengguang
2009-09-01 2:32 ` KAMEZAWA Hiroyuki
2009-09-01 6:46 ` Wu Fengguang
2009-09-01 7:12 ` KAMEZAWA Hiroyuki
2009-09-01 8:55 ` Wu Fengguang
2009-09-01 16:31 ` Balbir Singh
2009-09-02 2:47 ` Wu Fengguang
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=20090901084626.ac4c8879.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=mel@csn.ul.ie \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=riel@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox