From: "H. Peter Anvin" <hpa@zytor.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Martin J. Bligh" <mbligh@mbligh.org>
Subject: Re: i386 subarchitectures: boot page table flags
Date: Tue, 30 May 2006 19:49:55 -0700 [thread overview]
Message-ID: <447D0453.5070201@zytor.com> (raw)
In-Reply-To: <1149042065.3545.49.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> On Tue, 2006-05-30 at 18:57 -0700, H. Peter Anvin wrote:
>> Does any of the i386 subarchitectures actually care about the Accessed and Dirty bits in
>> the bootup pagetables (the ones that start at pg0, used before the mm is initialized?) If
>> not, I'd like to speed up booting by setting those bits at initialization time.
>
> Depends what you mean by "care". I do hijack pg0 in
> voyager_memory_detect() to access the clickmap for ascertaining the
> memory layout, but I don't use the accessed or dirty bits.
Okay...
Leaving the A and D bits clear means the CPU has to trap to microcode to
set those bits before it is allowed to load the entry into the TLB.
Furthermore, and this is the real killer on some CPUs, it is not allowed
to load those entries speculatively.
As far as I can tell, this is completely pointless for pg0.
(And no, the Voyager code wouldn't be affected.)
-hpa
prev parent reply other threads:[~2006-05-31 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 1:57 i386 subarchitectures: boot page table flags H. Peter Anvin
2006-05-31 2:21 ` James Bottomley
2006-05-31 2:49 ` H. Peter Anvin [this message]
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=447D0453.5070201@zytor.com \
--to=hpa@zytor.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.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