From: "H. Peter Anvin" <hpa@zytor.com>
To: "Luck, Tony" <tony.luck@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>
Cc: Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Uros Bizjak <ubizjak@gmail.com>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
Arnd Bergmann <arnd@arndb.de>, Mateusz Guzik <mjguzik@gmail.com>,
Thomas Renninger <trenn@suse.de>,
Greg Kroah-Hartman <gregkh@suse.de>,
Andi Kleen <ak@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>
Subject: RE: [PATCH v2] x86/cpu: Fix x86_match_cpu() to match just X86_VENDOR_INTEL
Date: Mon, 20 May 2024 16:33:27 -0700 [thread overview]
Message-ID: <509BDCB2-5203-460B-8317-043A07CB38B0@zytor.com> (raw)
In-Reply-To: <SJ1PR11MB60835EAF2929D72D9C245ACEFCEE2@SJ1PR11MB6083.namprd11.prod.outlook.com>
On May 17, 2024 1:54:33 PM PDT, "Luck, Tony" <tony.luck@intel.com> wrote:
>>> This is particularly pathetic as there already is a canonical string
>>> representation of the vendor ID!
>>
>> I agree, but that train has left the station long ago,
>
>Is that "GenuineIntel" and "AuthenticAMD"? While canonical, 96-bit values seem less
>easy to use than simple small integers.
>
>-Tony
>
Not for internal use, but for exporting in strings.
next prev parent reply other threads:[~2024-05-20 23:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 16:29 [PATCH v2] x86/cpu: Fix x86_match_cpu() to match just X86_VENDOR_INTEL Tony Luck
2024-05-16 21:27 ` Luck, Tony
2024-05-17 14:43 ` Borislav Petkov
2024-05-17 17:35 ` H. Peter Anvin
2024-05-17 18:17 ` Luck, Tony
2024-05-17 20:42 ` Thomas Gleixner
2024-05-17 20:41 ` Thomas Gleixner
2024-05-17 20:54 ` Luck, Tony
2024-05-20 23:33 ` H. Peter Anvin [this message]
2024-05-22 9:47 ` [tip: x86/urgent] " tip-bot2 for Tony Luck
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=509BDCB2-5203-460B-8317-043A07CB38B0@zytor.com \
--to=hpa@zytor.com \
--cc=ak@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjguzik@gmail.com \
--cc=patches@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=trenn@suse.de \
--cc=ubizjak@gmail.com \
--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 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.