From: Naoya Horiguchi <naoya.horiguchi@linux.dev>
To: David Hildenbrand <david@redhat.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Alistair Popple <apopple@nvidia.com>,
Peter Xu <peterx@redhat.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Konstantin Khlebnikov <koct9i@gmail.com>,
Bin Wang <wangbin224@huawei.com>, Yang Shi <shy828301@gmail.com>,
Naoya Horiguchi <naoya.horiguchi@nec.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] mm, pagemap: expose hwpoison entry
Date: Mon, 4 Oct 2021 23:32:28 +0900 [thread overview]
Message-ID: <20211004143228.GA1545442@u2004> (raw)
In-Reply-To: <258d0ddb-6c82-0c95-a15e-b085b59d2142@redhat.com>
On Mon, Oct 04, 2021 at 01:55:30PM +0200, David Hildenbrand wrote:
> On 04.10.21 13:50, Naoya Horiguchi wrote:
> > From: Naoya Horiguchi <naoya.horiguchi@nec.com>
> >
> > A hwpoison entry is a non-present page table entry to report
> > memory error events to userspace. If we have an easy way to know
> > which processes have hwpoison entries, that might be useful for
> > user processes to take proper actions. But we don't have it now.
> > So make pagemap interface expose hwpoison entries to userspace.
>
> Noting that this is only a way to inspect hwpoison set for private anonymous
> memory. You cannot really identify anything related to shared memory.
>
> Do you also handle private hugetlb pages?
I think yes. As long as hugepages are mmap()ed, we should be able to
identify them with hwpoison entry (even if used via private/shared mapping).
>
> >
> > Hwpoison entry for hugepage is also exposed by this patch. The below
> > example shows how pagemap is visible in the case where a memory error
> > hit a hugepage mapped to a process.
> >
> > $ ./page-types --no-summary --pid $PID --raw --list --addr 0x700000000+0x400
> > voffset offset len flags
> > 700000000 12fa00 1 ___U_______Ma__H_G_________________f_______1
> > 700000001 12fa01 1ff ___________Ma___TG_________________f_______1
> > 700000200 12f800 1 __________B________X_______________f______w_
> > 700000201 12f801 1 ___________________X_______________f______w_ // memory failure hit this page
> > 700000202 12f802 1fe __________B________X_______________f______w_
> >
> > The entries with both of "X" flag (hwpoison flag) and "w" flag (swap
> > flag) are considered as hwpoison entries. So all pages in 2MB range
> > are inaccessible from the process. We can get actual error location
> > by page-types in physical address mode.
> >
> > $ ./page-types --no-summary --addr 0x12f800+0x200 --raw --list
> > offset len flags
> > 12f800 1 __________B_________________________________
> > 12f801 1 ___________________X________________________
> > 12f802 1fe __________B_________________________________
> >
> > Signed-off-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
> > ---
> > fs/proc/task_mmu.c | 41 ++++++++++++++++++++++++++++++++---------
> > include/linux/swapops.h | 13 +++++++++++++
> > tools/vm/page-types.c | 7 ++++++-
> > 3 files changed, 51 insertions(+), 10 deletions(-)
>
>
> Please also update the documentation located at
>
> Documentation/admin-guide/mm/pagemap.rst
I will do this in the next post.
Thanks,
Naoya Horigcuhi
next prev parent reply other threads:[~2021-10-04 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 11:50 Naoya Horiguchi
2021-10-04 11:55 ` David Hildenbrand
2021-10-04 14:32 ` Naoya Horiguchi [this message]
2021-10-26 23:27 ` Naoya Horiguchi
2021-10-27 2:09 ` Peter Xu
2021-10-27 6:45 ` Naoya Horiguchi
2021-10-27 7:02 ` Peter Xu
2021-10-27 7:15 ` David Hildenbrand
2021-10-04 20:17 ` kernel test robot
2021-10-05 2:53 ` kernel test robot
2021-10-13 2:49 ` Peter Xu
2021-10-14 13:36 ` Naoya Horiguchi
2021-10-14 23:32 ` Peter Xu
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=20211004143228.GA1545442@u2004 \
--to=naoya.horiguchi@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=david@redhat.com \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@nec.com \
--cc=peterx@redhat.com \
--cc=shy828301@gmail.com \
--cc=wangbin224@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