linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: wangbin <wangbin224@huawei.com>
To: <naoya.horiguchi@nec.com>
Cc: <akpm@linux-foundation.org>, <linux-kernel@vger.kernel.org>,
	<linux-mm@kvack.org>, <mike.kravetz@oracle.com>,
	<nao.horiguchi@gmail.com>, <wangbin224@huawei.com>,
	<wuxu.wu@huawei.com>
Subject: Re: Re: [PATCH] mm: hugetlbfs: add hwcrp_hugepages to record memory failure on hugetlbfs
Date: Wed, 9 Jun 2021 10:23:11 +0800	[thread overview]
Message-ID: <20210609022311.2102-1-wangbin224@huawei.com> (raw)
In-Reply-To: <20210608091352.GA943097@hori.linux.bs1.fc.nec.co.jp>

> If you can use root privilege in your use-case, an easy way to get the
> number of corrupted hugepages is to use page-types.c (which reads
> /proc/kpageflags) like below:
> 
>     $ page-types -b huge,hwpoison=huge,hwpoison
>                  flags      page-count       MB  symbolic-flags                     long-symbolic-flags
>     0x00000000000a8000               1        0  _______________H_G_X_______________________        compound_head,huge,hwpoison
>                  total               1        0
> 
> But I guess that many usecases do not permit access to this interface,
> where some new accounting interface for corrupted hugepages could be
> helpful as you suggest.

Thanks for your suggestion very much. This approach is helpful to me.
But as you say, root privilege is not permitted in most cases. And I
also want to know the number of corrupted hugepages per node.

--
Bin Wang


  reply	other threads:[~2021-06-09  2:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 14:16 [PATCH] mm: hugetlbfs: add hwcrp_hugepages to record memory failure on hugetlbfs wangbin
2021-06-07 19:07 ` Mike Kravetz
2021-06-07 19:13 ` Mike Kravetz
2021-06-08  2:24   ` wangbin
2021-06-08  9:13     ` HORIGUCHI NAOYA(堀口　直也)
2021-06-09  2:23       ` wangbin [this message]
2021-06-08  8:01   ` HORIGUCHI NAOYA(堀口　直也)

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=20210609022311.2102-1-wangbin224@huawei.com \
    --to=wangbin224@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=nao.horiguchi@gmail.com \
    --cc=naoya.horiguchi@nec.com \
    --cc=wuxu.wu@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).