From: Hugh Dickins <hughd@google.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [PATCH mmotm] thp: transparent hugepage core fixlet
Date: Tue, 11 Jan 2011 14:59:43 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.00.1101111318190.26539@sister.anvils> (raw)
In-Reply-To: <20110111163120.GR9506@random.random>
On Tue, 11 Jan 2011, Andrea Arcangeli wrote:
> On Tue, Jan 11, 2011 at 03:04:21PM +0100, Andrea Arcangeli wrote:
> > architectural bug to me. Why can't pud_huge simply return 0 for
> > x86_32? Any other place dealing with hugepages and calling pud_huge on
> > x86 noPAE would be at risk, otherwise, no?
>
> Isn't this better solution?
[Better solution than my patch to follow_page() in mmotm, to fix crash
with Transparent Huge Pages by duplicating Andrea's pmd_huge VM_HUGETLB
check to the pud_huge line too.]
The truth is, I'm sure one of the solutions is better than the other,
but I'm too confused by p?d folding to know which is which ;)
Certainly I don't oppose your patch as a replacement for mine,
if you're sure yours is better.
There are only two places which are using pud_huge() anyway:
follow_page() and apply_to_pmd_range(). Is the latter's
BUG_ON(pud_huge) safe? Safe in the THP world?
And I never quite understood why we have both pmd_huge and pmd_large,
pud_huge and pud_large.
There are answers to these questions, but it would take me hours and
hours of easily-confused research (across several arches) to decide.
I'm hoping someone else has a surer grasp: Andi introduced pud_huge(),
and Jeremy is the most active in the pagetable layers nowadays -
perhaps they can tell us more quickly.
Hugh
>
> ======
> Subject: avoid confusing hugetlbfs code when pmd_trans_huge is set
>
> From: Andrea Arcangeli <aarcange@redhat.com>
>
> If pmd is set huge by THP, pud_huge shouldn't return 1 when pud doesn't exist
> and it's just a 1:1 bypass over the pmd (like it happens on 32bit x86 because
> there are at most 2 or 3 level of pagetables). Only pmd_huge can return 1.
>
> Signed-off-by: Andrea Arcangeli <aarcange@redhat.com>
> ---
>
> diff --git a/arch/x86/mm/hugetlbpage.c b/arch/x86/mm/hugetlbpage.c
> --- a/arch/x86/mm/hugetlbpage.c
> +++ b/arch/x86/mm/hugetlbpage.c
> @@ -227,7 +227,15 @@ int pmd_huge(pmd_t pmd)
>
> int pud_huge(pud_t pud)
> {
> +#ifdef CONFIG_X86_64
> return !!(pud_val(pud) & _PAGE_PSE);
> +#else
> + /*
> + * pud is a bypass with 2 or 3 level pagetables, only pmd_huge
> + * can return 1.
> + */
> + return 0;
> +#endif
> }
>
> struct page *
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-01-11 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 0:55 Hugh Dickins
2011-01-11 1:57 ` Andrea Arcangeli
2011-01-11 2:29 ` Hugh Dickins
2011-01-11 14:04 ` Andrea Arcangeli
2011-01-11 16:31 ` Andrea Arcangeli
2011-01-11 22:59 ` Hugh Dickins [this message]
2011-01-12 2:02 ` Andrea Arcangeli
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=alpine.LSU.2.00.1101111318190.26539@sister.anvils \
--to=hughd@google.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=jeremy@goop.org \
--cc=linux-mm@kvack.org \
/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