From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Gerald Schaefer <gerald.schaefer@de.ibm.com>,
linux-mm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] numa: fix /proc/<pid>/numa_maps for hugetlbfs on s390
Date: Mon, 25 Jan 2016 14:51:16 -0800 [thread overview]
Message-ID: <20160125145116.30603e678b1f787d51ab3f5e@linux-foundation.org> (raw)
In-Reply-To: <1453739442-57738-1-git-send-email-holzheu@linux.vnet.ibm.com>
On Mon, 25 Jan 2016 17:30:42 +0100 Michael Holzheu <holzheu@linux.vnet.ibm.com> wrote:
> When working with hugetlbfs ptes (which are actually pmds) is not
> valid to directly use pte functions like pte_present() because the
> hardware bit layout of pmds and ptes can be different. This is the
> case on s390. Therefore we have to convert the hugetlbfs ptes first
> into a valid pte encoding with huge_ptep_get().
>
> Currently the /proc/<pid>/numa_maps code uses hugetlbfs ptes without
> huge_ptep_get(). On s390 this leads to the following two problems:
>
> 1) The pte_present() function returns false (instead of true) for
> PROT_NONE hugetlb ptes. Therefore PROT_NONE vmas are missing
> completely in the "numa_maps" output.
>
> 2) The pte_dirty() function always returns false for all hugetlb ptes.
> Therefore these pages are reported as "mapped=xxx" instead of
> "dirty=xxx".
>
> Therefore use huge_ptep_get() to correctly convert the hugetlb ptes.
I'm aiming this at 4.5 only. Please let me know if you think that a
-stable backport is warranted.
next prev parent reply other threads:[~2016-01-25 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 16:30 Michael Holzheu
2016-01-25 22:51 ` Andrew Morton [this message]
2016-01-26 10:56 ` Michael Holzheu
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=20160125145116.30603e678b1f787d51ab3f5e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gerald.schaefer@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=schwidefsky@de.ibm.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
all inboxes | Powered by JetHome®