The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Christian Ludloff <ludloff@gmail.com>
Cc: Dave Hansen <dave.hansen@intel.com>,
	"Chang S. Bae" <chang.seok.bae@intel.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: Wed, 19 Aug 2026 09:41:35 -0700	[thread overview]
Message-ID: <aoXcv795N-xmtTDl@google.com> (raw)
In-Reply-To: <CAKSQd8UyzWweM15-9ehaCaYYJYw+N8z9pFon2J+3sehqm=Ukbg@mail.gmail.com>

On Tue, Aug 18, 2026, Christian Ludloff wrote:
> On Tue, Aug 18, 2026 at 5:55 PM Dave Hansen <dave.hansen@intel.com> wrote:
> > 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.
> 
> Yes, that terse sentence works.
>   Once for AMX-TRANSPOSE.
>   Once for AMX-TF32.

Maybe use a similar approach as is done for the HYPERVISOR bit (0x1.ECX[31), and
have the "Field Name" entry say Not Used, and then use the "Description" to explain
why?  E.g.

  Register        Field Name      Description                             Domain
  EAX[6]          Not Used        Intel processors always return 0.       Platform
                                  Allocated for backwards compatibility
                                  with software that expects this to
                                  enumerate AMX_TF32.

Or Christian's terse version (I kinda like the terse version).

  Register        Field Name      Description                             Domain
  EAX[6]          Not Used        Intel processors always return 0.       Platform
                                  Once for AMX_TF32.

 
> If you want the back references:
>   TRANSPOSE got dropped from ISE #059 and APX #007.
>   TF32 got dropped from ISE #062.
> 
> In terms of the opcodes, it is like MPX too: no recycling for
> a long time. Luckily there is plenty of remaining space.
> 
> --
> C.

  reply	other threads:[~2026-08-19 16:41 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
2026-08-19  1:48   ` Christian Ludloff
2026-08-19 16:41     ` Sean Christopherson [this message]
  -- 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=aoXcv795N-xmtTDl@google.com \
    --to=seanjc@google.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=chang.seok.bae@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludloff@gmail.com \
    --cc=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox