Skip to contentSkip to conversation

i386 subarchitectures: boot page table flags

DISCUSSION H. Peter Anvin 2 participants 3 messages May 31, 2006

lore
Share & tools
lore
#0 lore raw

Hi all,

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.

-hpa

#1 lore raw
Quoted 3 lines · H. Peter Anvin

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.

James

#2 lore raw
Quoted 6 lines · James Bottomley
Quoted 1 line · H. Peter Anvin

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