From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: Simon Jeons <simon.jeons@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
WuJianguo <wujianguo@huawei.com>, Liujiang <jiang.liu@huawei.com>,
Vyacheslav.Dubeyko@huawei.com, Borislav Petkov <bp@alien8.de>,
andi@firstfloor.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, wency@cn.fujitsu.com
Subject: Re: [PATCH V2] MCE: fix an error of mce_bad_pages statistics
Date: Tue, 11 Dec 2012 16:02:37 +0800 [thread overview]
Message-ID: <20121211080236.GA29541@hacker.(null)> (raw)
In-Reply-To: <50C6D762.4030507@huawei.com>
On Tue, Dec 11, 2012 at 02:49:06PM +0800, Xishi Qiu wrote:
>>>> Hi Simon,
>
>>>>
>>>> If we use "/sys/devices/system/memory/soft_offline_page" to offline a
>>>> free page, the value of mce_bad_pages will be added. Then the page is marked
>>>> HWPoison, but it is still managed by page buddy alocator.
>>>>
>>>> So if we offline it again, the value of mce_bad_pages will be added again.
>>>> Assume the page is not allocated during this short time.
>>>>
>>>> soft_offline_page()
>>>> get_any_page()
>>>> "else if (is_free_buddy_page(p))" branch return 0
>>>> "goto done";
>>>> "atomic_long_add(1, &mce_bad_pages);"
>>>>
>>>> I think it would be better to move "if(PageHWPoison(page))" at the beginning of
>>>> soft_offline_page(). However I don't know what do these words mean,
>>>> "Synchronized using the page lock with memory_failure()"
>>
>> Hi Xishi,
>>
>> Unpoison will clear PG_hwpoison flag after hold page lock, memory_failure() and
>> soft_offline_page() take the lock to avoid unpoison clear the flag behind them.
>>
>> Regards,
>> Wanpeng Li
>>
>
>Hi Wanpeng,
>
>As you mean, it is the necessary to get the page lock first when we check the
>HWPoison flag every time, this is in order to avoid conflict, right?
>
Hi Xishi,
Avoid race.
>So why not use a globe lock here? For example lock_memory_hotplug() is used in
>online_pages() and offline_pages()?
Just for a single page, a global lock maybe more contend.
Regards,
Wanpeng Li
>
>Thanks,
>Xishi Qiu
--
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:[~2012-12-11 8:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 8:48 [PATCH V2] MCE: fix an error of mce_bad_pages statistics Xishi Qiu
2012-12-07 14:33 ` Borislav Petkov
2012-12-07 22:11 ` Andrew Morton
2012-12-07 22:41 ` Borislav Petkov
2012-12-10 4:33 ` Xishi Qiu
2012-12-10 8:33 ` Wanpeng Li
2012-12-10 9:06 ` Xishi Qiu
2012-12-10 10:47 ` Simon Jeons
2012-12-10 11:16 ` Xishi Qiu
2012-12-10 11:39 ` Wanpeng Li
2012-12-10 11:54 ` Xishi Qiu
2012-12-10 12:11 ` Borislav Petkov
2012-12-10 15:39 ` Andi Kleen
2012-12-10 11:39 ` Wanpeng Li
2012-12-10 11:58 ` Simon Jeons
[not found] ` <1355140561.1821.5.camel@kernel.cn.ibm.com>
[not found] ` <50C5D844.8050707@huawei.com>
2012-12-10 12:47 ` Simon Jeons
2012-12-11 1:16 ` Wanpeng Li
2012-12-11 6:49 ` Xishi Qiu
2012-12-11 8:02 ` Wanpeng Li [this message]
2012-12-11 8:02 ` Wanpeng Li
2012-12-11 1:16 ` Wanpeng Li
2012-12-10 15:38 ` Andi Kleen
2012-12-11 1:49 ` Simon Jeons
2012-12-11 2:03 ` Andi Kleen
2012-12-11 2:14 ` Simon Jeons
2012-12-11 3:01 ` Andi Kleen
2012-12-11 3:13 ` Simon Jeons
2012-12-11 3:19 ` Andi Kleen
2012-12-11 3:48 ` Simon Jeons
2012-12-11 5:55 ` Xishi Qiu
2012-12-11 6:34 ` Wanpeng Li
2012-12-11 6:34 ` Wanpeng Li
2012-12-11 2:25 ` Xishi Qiu
2012-12-11 2:45 ` Fengguang Wu
2012-12-11 2:58 ` Andi Kleen
2012-12-11 3:25 ` Xishi Qiu
2012-12-11 3:36 ` Andi Kleen
2012-12-10 8:33 ` Wanpeng Li
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='20121211080236.GA29541@hacker.(null)' \
--to=liwanp@linux.vnet.ibm.com \
--cc=Vyacheslav.Dubeyko@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=jiang.liu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qiuxishi@huawei.com \
--cc=simon.jeons@gmail.com \
--cc=wency@cn.fujitsu.com \
--cc=wujianguo@huawei.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;
as well as URLs for NNTP newsgroup(s).