public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: Jan Richter <jarichte@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Sean Christopherson <seanjc@google.com>
Subject: RE: [PATCH] KVM: selftests: x86: Avoid using SSE/AVX instructions
Date: Tue, 24 Sep 2024 14:04:04 +0200	[thread overview]
Message-ID: <87ikull0ln.fsf@redhat.com> (raw)
In-Reply-To: <2a62086810c14d0e88e38706a06aedde@AcuMS.aculab.com>

David Laight <David.Laight@ACULAB.COM> writes:

> From: Vitaly Kuznetsov <vkuznets@redhat.com>
>> Sent: 20 September 2024 16:44
>> 
>> Some distros switched gcc to '-march=x86-64-v3' by default and while it's
>> hard to find a CPU which doesn't support it today,
>
> I didn't think that any of the Atom based cpu supported AVX.
> I'm pretty sure one we use that are still in production as
> server motherboards don't support it.
>
> Doesn't -v3 also require support for the VEX encoding.
> Which removes a lot of perfectly reasonable cpu?
>

Well, distros making such decision are obviously not very interested in
running on these CPUs then :-) In this particular case, the distro was
Centos Stream 10 and they are very explicit about the decision:
https://developers.redhat.com/articles/2024/01/02/exploring-x86-64-v3-red-hat-enterprise-linux-10#new_cpu_capabilities_in_x86_64_v3

and 'gcc -v' tells me

Configured with: ../configure ... --with-arch_64=x86-64-v3  ...
...
gcc version 14.2.1 20240801 (Red Hat 14.2.1-1) (GCC) 

-- 
Vitaly


  reply	other threads:[~2024-09-24 12:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-20 15:44 [PATCH] KVM: selftests: x86: Avoid using SSE/AVX instructions Vitaly Kuznetsov
2024-09-22 16:17 ` Sean Christopherson
2024-09-23 11:16 ` David Laight
2024-09-24 12:04   ` Vitaly Kuznetsov [this message]
2024-10-21 18:32 ` Mark Brown
2024-10-21 20:33   ` Mark Brown

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=87ikull0ln.fsf@redhat.com \
    --to=vkuznets@redhat.com \
    --cc=David.Laight@ACULAB.COM \
    --cc=jarichte@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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