Skip to contentSkip to conversation

Athlon Prefetch workaround for 2.6.0test6

PATCH Andi Kleen 1 participant 1 message Sep 30, 2003 5 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): 20030929170323.GC21798@mail.jlokier.co.uk.suse.lists.linux.kernel

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): 20030929200820.GA23444@mail.jlokier.co.uk.suse.lists.linux.kernel

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#5 lore raw
Quoted 9 lines · Gabriel Paubert
Quoted 4 lines · Jamie Lokier

Btw, you assume that regs->xcs is a valid segment value. I think that the upper 16 bits are not guaranteed to be zero in general on the IA32, although they clearly are zero for the majority of IA-32 chips. Are they guaranteed to be zero on AMD's processors?

At least for pushes of segment registers a 486 decrements the stack pointer by 4 but only writes the 2 least significant bytes, leaving garbage in the upper half.

The code only runs on newer AMD CPUs (K7/K8)

-Andi