From: Timothy Miller <miller@techsource.com>
To: Andi Kleen <ak@suse.de>
Cc: "Nakajima, Jun" <jun.nakajima@intel.com>,
richard.brunner@amd.com, linux-kernel@vger.kernel.org
Subject: Re: Intel vs AMD64
Date: Fri, 27 Feb 2004 09:50:09 -0500 [thread overview]
Message-ID: <403F5921.9080008@techsource.com> (raw)
In-Reply-To: <p731xoh61fn.fsf@verdi.suse.de>
Andi Kleen wrote:
> Timothy Miller <miller@techsource.com> writes:
>
[snip]
>
>>Why did Intel decide to do that?
>
>
> Most likely they didn't plan to, but it happened by accident
> and is obscure enough to be not worth fixing. I would agree with
> them that it's not worth fixing.
Yes, I have come to understand that this is merely a case of Intel
documenting that an "undocumented" instruction doesn't behave in a
useful or consistent way.
My apologies for delving into this pointless discussion.
next prev parent reply other threads:[~2004-02-27 14:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7F740D512C7C1046AB53446D37200173EA28A5@scsmsx402.sc.intel.com.suse.lists.linux.kernel>
[not found] ` <403E4681.20603@techsource.com.suse.lists.linux.kernel>
2004-02-26 20:17 ` Intel vs AMD64 Andi Kleen
2004-02-27 14:50 ` Timothy Miller [this message]
2004-02-26 5:32 Nakajima, Jun
2004-02-26 13:39 ` Chris Wedgwood
2004-02-26 14:35 ` Richard B. Johnson
2004-02-26 19:25 ` Timothy Miller
2004-02-26 19:46 ` Richard B. Johnson
2004-02-27 18:44 ` H. Peter Anvin
2004-02-26 19:18 ` Timothy Miller
2004-02-26 19:45 ` Scott Robert Ladd
2004-02-27 14:43 ` Timothy Miller
2004-03-03 17:34 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2004-02-26 4:28 richard.brunner
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=403F5921.9080008@techsource.com \
--to=miller@techsource.com \
--cc=ak@suse.de \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.brunner@amd.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.