From: "H. Peter Anvin" <hpa@zytor.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Christian Ludloff <ludloff@gmail.com>
Subject: Re: Code archaeology - 3DNow vs Pending Break Enable
Date: Tue, 25 Nov 2025 18:03:32 -0800 [thread overview]
Message-ID: <4D5BE8C1-04C9-470C-AB4D-F9DAEF5AD8E4@zytor.com> (raw)
In-Reply-To: <800773c2-40c5-4c8b-87d5-e327db46985a@citrix.com>
It was simply a matter of having two bits for the same thing, and the possibility (at the time) that Intel might allocate bit 31 for something.
prev parent reply other threads:[~2025-11-26 2:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 22:40 Andrew Cooper
2025-11-25 23:07 ` Andrew Cooper
2025-11-26 2:03 ` H. Peter Anvin [this message]
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=4D5BE8C1-04C9-470C-AB4D-F9DAEF5AD8E4@zytor.com \
--to=hpa@zytor.com \
--cc=andrew.cooper3@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ludloff@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®