From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Sonny Rao <sonny@burdell.org>
Cc: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
Hugh Dickins <hugh@veritas.com>,
Jan Beulich <jbeulich@novell.com>,
Zachary Amsden <zach@vmware.com>,
linux-kernel@vger.kernel.org, anton@samba.org
Subject: Re: [PATCH] i386: PAE entries must have their low word cleared first
Date: Thu, 27 Apr 2006 23:39:54 +1000 [thread overview]
Message-ID: <4450C9AA.8020800@yahoo.com.au> (raw)
In-Reply-To: <20060427102700.GA1299@kevlar.burdell.org>
Sonny Rao wrote:
> On Thu, Apr 27, 2006 at 01:58:42AM +1000, Nick Piggin wrote:
>
>>Keir Fraser wrote:
>>
>>>In more detail the problem is that, since we're still running on the
>>>page tables while clearing them, the CPU may choose to prefetch a
>>>half-cleared pte into its TLB, and then execute speculative memory
>>>accesses based on that mapping (including ones that may write-allocate
>>>cachelines, leading to problems like the AMD AGP GART deadlock Linux had
>>>a year or so back).
>>
>>What do you mean, you're still running on the page tables? The CPU can
>>still walk the pagetables?
>>
>>Because if ptep_get_and_clear_full is passed non zero in the full
>>argument, then that specific translation should never see another
>>access. I didn't know CPUs now actually resolve TLB misses as part of
>>speculative prefetching... does this really happen?
>
>
> For instance, during speculative execution on POWER, we can take a
> TLB miss for a speculative load and start a table-walk.
>
> I'm not sure what "speculative prefetching" means in this case... just
> regular hardware-initiated prefetching (where I suppose one could use the
> modifier "speculative") on POWER will only prefetch to a page-boundary.
speculative prefetching / hardware prefetching...
I believe this bug wouldn't happen as a result of speculative execution,
because a load from this virtual address should never be in the instruction
stream. So it would require some hardware initiated prefetch to establish
the tlb entry.
>
> So, slightly OT, as this is not about x86 CPUs... but thought people
> might be interested.
Thanks!
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-04-27 15:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 13:46 [PATCH] i386: PAE entries must have their low word cleared first Jan Beulich
2006-04-26 14:46 ` Hugh Dickins
2006-04-26 15:06 ` Keir Fraser
2006-04-26 15:44 ` Zachary Amsden
2006-04-26 15:57 ` Hugh Dickins
2006-04-26 16:12 ` Keir Fraser
2006-04-26 15:45 ` Hugh Dickins
2006-04-26 16:06 ` Nick Piggin
2006-04-26 15:58 ` Nick Piggin
2006-04-27 10:27 ` Sonny Rao
2006-04-27 13:39 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-26 22:11 Brunner, Richard
2006-04-26 22:22 ` Zachary Amsden
2006-04-26 22:27 ` Zachary Amsden
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=4450C9AA.8020800@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=anton@samba.org \
--cc=hugh@veritas.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sonny@burdell.org \
--cc=zach@vmware.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).