From: Dave Hansen <dave.hansen@intel.com>
To: ludloff@gmail.com, "Chang S. Bae" <chang.seok.bae@intel.com>
Cc: Sean Christopherson <seanjc@google.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
pbonzini@redhat.com, stable@vger.kernel.org,
Zhao Liu <zhao1.liu@intel.com>,
Binbin Wu <binbin.wu@linux.intel.com>
Subject: Re: [PATCH v2] KVM: x86: Remove AMX-TF32 enumeration
Date: Tue, 18 Aug 2026 17:55:22 -0700 [thread overview]
Message-ID: <abe4535e-c72b-4df2-99be-064479b685ec@intel.com> (raw)
In-Reply-To: <CAKSQd8V=wfVrUxeU+fDRgKJBLdiyCkkY2SRY+OoRBNE68LFnCg@mail.gmail.com>
On 7/24/26 08:37, Christian Ludloff wrote:
>> My understanding is that the revert was considered because TF32 never
>> reached any implementation. If that's incorrect, I'd certainly welcome a
>> correction.
> Both TF32 and TRANSPOSE made it into a product that shipped.
>
> Not from Intel... but.
>
> So their CPUID feature flags and their opcodes aren't reclaimable
> and efforts to rip out their software support are counterproductive.
What would folks' preference be on how Intel should document this going
forward? Just leave it as it as enumerating TF32?
There are notes in the SDM like:
Intel® MPX has been deprecated and will not be available on any
future processors.
There could be a note like that for the TF32, I would imagine.
next prev parent reply other threads:[~2026-08-19 0:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 15:37 [PATCH v2] KVM: x86: Remove AMX-TF32 enumeration Christian Ludloff
2026-08-19 0:55 ` Dave Hansen [this message]
2026-08-19 1:48 ` Christian Ludloff
2026-08-19 16:41 ` Sean Christopherson
-- strict thread matches above, loose matches on Subject: below --
2026-07-20 20:52 Chang S. Bae
2026-07-21 0:37 ` Xiaoyao Li
2026-07-23 18:04 ` Sean Christopherson
2026-07-23 19:44 ` Chang S. Bae
2026-07-27 15:27 ` Sean Christopherson
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=abe4535e-c72b-4df2-99be-064479b685ec@intel.com \
--to=dave.hansen@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=chang.seok.bae@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludloff@gmail.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=zhao1.liu@intel.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.