From: Peter Zijlstra <peterz@infradead.org>
To: Avi Kivity <avi@qumranet.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
shaggy@austin.ibm.com, axboe@kernel.dk, linux-mm@kvack.org,
linux-arch@vger.kernel.org, Clark Williams <williams@redhat.com>,
Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [patch 2/2]: introduce fast_gup
Date: Mon, 21 Apr 2008 16:35:47 +0200 [thread overview]
Message-ID: <1208788547.7115.204.camel@twins> (raw)
In-Reply-To: <480C9619.2050201@qumranet.com>
On Mon, 2008-04-21 at 16:26 +0300, Avi Kivity wrote:
> Peter Zijlstra wrote:
> > On Mon, 2008-04-21 at 15:00 +0300, Avi Kivity wrote:
> >
> >> Linus Torvalds wrote:
> >>
> >>> Finally, I don't think that comment is correct in the first place. It's
> >>> not that simple. The thing is, even *with* the memory barrier in place, we
> >>> may have:
> >>>
> >>> CPU#1 CPU#2
> >>> ===== =====
> >>>
> >>> fast_gup:
> >>> - read low word
> >>>
> >>> native_set_pte_present:
> >>> - set low word to 0
> >>> - set high word to new value
> >>>
> >>> - read high word
> >>>
> >>> - set low word to new value
> >>>
> >>> and so you read a low word that is associated with a *different* high
> >>> word! Notice?
> >>>
> >>> So trivial memory ordering is _not_ enough.
> >>>
> >>> So I think the code literally needs to be something like this
> >>>
> >>> #ifdef CONFIG_X86_PAE
> >>>
> >>> static inline pte_t native_get_pte(pte_t *ptep)
> >>> {
> >>> pte_t pte;
> >>>
> >>> retry:
> >>> pte.pte_low = ptep->pte_low;
> >>> smp_rmb();
> >>> pte.pte_high = ptep->pte_high;
> >>> smp_rmb();
> >>> if (unlikely(pte.pte_low != ptep->pte_low)
> >>> goto retry;
> >>> return pte;
> >>> }
> >>>
> >>>
> >>>
> >> I think this is still broken. Suppose that after reading pte_high
> >> native_set_pte() is called again on another cpu, changing pte_low back
> >> to the original value (but with a different pte_high). You now have
> >> pte_low from second native_set_pte() but pte_high from the first
> >> native_set_pte().
> >>
> >
> > I think the idea was that for user pages we only use set_pte_present()
> > which does the low=0 thing first.
> >
>
> Doesn't matter. The second native_set_pte() (or set_pte_present())
> executes atomically:
>
>
> fast_gup:
> - read low word (l0)
>
> native_set_pte_present:
> - set low word to 0
> - set high word to new value (h1)
> - set low word to new value (l1)
>
>
> - read high word (h1)
>
> native_set_pte_present:
> - set low word to 0
> - set high word to new value (h2)
> - set low word to new value (l2)
>
> - re-read low word (l2)
>
>
> If l2 happens to be equal to l0, then the check succeeds and we have a
> splintered pte h1:l0.
ok, so lets use cmpxchg8.
Index: linux-2.6/arch/x86/mm/gup.c
===================================================================
--- linux-2.6.orig/arch/x86/mm/gup.c
+++ linux-2.6/arch/x86/mm/gup.c
@@ -9,6 +9,19 @@
#include <linux/vmstat.h>
#include <asm/pgtable.h>
+#ifdef CONFIG_X86_PAE
+
+static inline pte_t native_get_pte(pte_t *ptep)
+{
+ return native_make_pte(cmpxchg64((u64 *)ptep, 0ULL, 0ULL));
+}
+
+#else
+
+#define native_get_pte(ptep) (*(ptep))
+
+#endif
+
/*
* The performance critical leaf functions are made noinline otherwise gcc
* inlines everything into a single function which results in too much
@@ -27,16 +40,7 @@ static noinline int gup_pte_range(pmd_t
ptep = pte_offset_map(&pmd, addr);
do {
- /*
- * XXX: careful. On 3-level 32-bit, the pte is 64 bits, and
- * we need to make sure we load the low word first, then the
- * high. This means _PAGE_PRESENT should be clear if the high
- * word was not valid. Currently, the C compiler can issue
- * the loads in any order, and I don't know of a wrapper
- * function that will do this properly, so it is broken on
- * 32-bit 3-level for the moment.
- */
- pte_t pte = *ptep;
+ pte_t pte = native_get_pte(ptep);
struct page *page;
if ((pte_val(pte) & mask) != result)
--
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:[~2008-04-21 14:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 2:54 [patch 0/2]: lockless get_user_pages patchset Nick Piggin
2008-03-28 2:55 ` [patch 1/2]: x86: implement pte_special Nick Piggin
2008-03-28 3:23 ` David Miller, Nick Piggin
2008-03-28 3:31 ` Nick Piggin
2008-03-28 3:44 ` David Miller, Nick Piggin
2008-03-28 4:04 ` Nick Piggin
2008-03-28 4:09 ` David Miller, Nick Piggin
2008-03-28 4:15 ` Nick Piggin
2008-03-28 4:16 ` David Miller, Nick Piggin
2008-03-28 4:19 ` Nick Piggin
2008-03-28 4:17 ` Nick Piggin
2008-03-28 3:00 ` [patch 2/2]: introduce fast_gup Nick Piggin
2008-03-28 10:01 ` Jens Axboe
2008-04-17 15:03 ` Peter Zijlstra
2008-04-17 15:25 ` Linus Torvalds
2008-04-17 16:12 ` Peter Zijlstra
2008-04-17 16:18 ` Linus Torvalds
2008-04-17 16:35 ` Peter Zijlstra
2008-04-17 16:40 ` Linus Torvalds
2008-04-17 17:23 ` Peter Zijlstra
2008-04-17 18:28 ` Linus Torvalds
2008-04-22 3:14 ` Nick Piggin
2008-04-18 6:31 ` Geert Uytterhoeven
2008-04-18 14:40 ` Linus Torvalds
2008-04-18 9:58 ` Jeremy Fitzhardinge
2008-04-21 12:00 ` Avi Kivity
2008-04-21 12:30 ` Peter Zijlstra
2008-04-21 13:26 ` Avi Kivity
2008-04-21 14:35 ` Peter Zijlstra [this message]
2008-04-22 3:23 ` Nick Piggin
2008-04-22 7:19 ` Avi Kivity
2008-04-22 8:07 ` Ingo Molnar
2008-04-22 9:42 ` Peter Zijlstra
2008-04-22 9:46 ` Nick Piggin
2008-05-14 18:33 ` Dave Kleikamp
2008-05-15 1:13 ` Nick Piggin
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=1208788547.7115.204.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=avi@qumranet.com \
--cc=axboe@kernel.dk \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=shaggy@austin.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=williams@redhat.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).