From: Andi Kleen <ak@suse.de>
To: Gabriel Paubert <paubert@iram.es>
Cc: jamie@shareable.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Athlon Prefetch workaround for 2.6.0test6
Date: 30 Sep 2003 11:50:53 +0200 [thread overview]
Message-ID: <p73fziey58i.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <20030930093556.GB12970@iram.es.suse.lists.linux.kernel>
Gabriel Paubert <paubert@iram.es> writes:
> On Mon, Sep 29, 2003 at 09:08:20PM +0100, Jamie Lokier wrote:
> > 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
next parent reply other threads:[~2003-09-30 9:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030929125629.GA1746@averell.suse.lists.linux.kernel>
[not found] ` <20030929170323.GC21798@mail.jlokier.co.uk.suse.lists.linux.kernel>
[not found] ` <20030929174910.GA90905@colin2.muc.de.suse.lists.linux.kernel>
[not found] ` <20030929200820.GA23444@mail.jlokier.co.uk.suse.lists.linux.kernel>
[not found] ` <20030930093556.GB12970@iram.es.suse.lists.linux.kernel>
2003-09-30 9:50 ` Andi Kleen [this message]
2003-09-29 12:56 Andi Kleen
2003-09-29 17:03 ` Jamie Lokier
2003-09-29 17:49 ` Andi Kleen
2003-09-29 20:08 ` Jamie Lokier
2003-09-30 5:50 ` Andi Kleen
2003-09-30 9:35 ` Gabriel Paubert
2003-09-29 22:13 ` Jamie Lokier
2003-09-30 5:38 ` Andi Kleen
2003-09-30 0:19 ` Jamie Lokier
2003-09-29 21:02 ` bill davidsen
2003-09-30 0:50 ` Nick Piggin
2003-09-30 13:27 ` Dave Jones
2003-09-30 15:36 ` Bill Davidsen
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=p73fziey58i.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paubert@iram.es \
/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®