From: "Zhao Forrest" <forrest.zhao@gmail.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] A question about GART aperture unmap
Date: Thu, 10 May 2007 18:00:15 +0800 [thread overview]
Message-ID: <ac8af0be0705100300l91f8b38y288dad4b677bf188@mail.gmail.com> (raw)
In-Reply-To: <20070510094908.GB14898@one.firstfloor.org>
> >
> > As we know that CPU prefetch never cross the page boundary, in this
>
> That only applies to sequential prefetch. But speculative execution can
> prefetch pretty much any address. That is why the clear_kernel_mapping is
> needed.
In BIOS setup, there's "Speculative TLB Reload". Is this "Speculative
TLB Reload" the same as your mentioned speculative execution?
After disabling "Speculative TLB Reload" in BIOS, we could also
experience sync flood and reset when commenting out
clear_kernel_mapping()......
Forrest
next prev parent reply other threads:[~2007-05-10 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 5:59 Zhao Forrest
2007-05-10 9:49 ` [discuss] " Andi Kleen
2007-05-10 10:00 ` Zhao Forrest [this message]
2007-05-10 10:09 ` Zhao Forrest
2007-05-10 10:14 ` Zhao Forrest
2007-05-10 11:06 ` Andi Kleen
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=ac8af0be0705100300l91f8b38y288dad4b677bf188@mail.gmail.com \
--to=forrest.zhao@gmail.com \
--cc=andi@firstfloor.org \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®