From: Gabriel Paubert <paubert@iram.es>
To: Jamie Lokier <jamie@shareable.org>
Cc: Andi Kleen <ak@colin2.muc.de>, Andi Kleen <ak@muc.de>,
torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
richard.brunner@amd.com
Subject: Re: [PATCH] Athlon Prefetch workaround for 2.6.0test6
Date: Tue, 30 Sep 2003 11:35:56 +0200 [thread overview]
Message-ID: <20030930093556.GB12970@iram.es> (raw)
In-Reply-To: <20030929200820.GA23444@mail.jlokier.co.uk>
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.
That's documented in the list of differences between 486 and Pentium.
It may be different for the frame pushed on the stack during interrupt
entry; my take on it is that it is inherently dangerous to rely
on the upper 16 bits being zero.
Just my 2 cents,
Regards,
Gabriel
next prev parent reply other threads:[~2003-09-30 9:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 12:56 [PATCH] Athlon Prefetch workaround for 2.6.0test6 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 [this message]
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
[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
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=20030930093556.GB12970@iram.es \
--to=paubert@iram.es \
--cc=ak@colin2.muc.de \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.brunner@amd.com \
--cc=torvalds@osdl.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