From: "Moger, Babu" <babu.moger@amd.com>
To: "Dr. David Alan Gilbert" <dave@treblig.org>
Cc: pbonzini@redhat.com, zhao1.liu@intel.com, qemu-devel@nongnu.org,
kvm@vger.kernel.org, davydov-max@yandex-team.ru
Subject: Re: [PATCH v7 4/6] target/i386: Add couple of feature bits in CPUID_Fn80000021_EAX
Date: Mon, 16 Jun 2025 13:09:01 -0500 [thread overview]
Message-ID: <e7cdab23-de40-457d-aa69-f0e210206c16@amd.com> (raw)
In-Reply-To: <aELfPr7snDmIirNk@gallifrey>
Hi Dave,
On 6/6/25 07:29, Dr. David Alan Gilbert wrote:
> * Babu Moger (babu.moger@amd.com) wrote:
>> Add CPUID bit indicates that a WRMSR to MSR_FS_BASE, MSR_GS_BASE, or
>> MSR_KERNEL_GS_BASE is non-serializing amd PREFETCHI that the indicates
>> support for IC prefetch.
>>
>> CPUID_Fn80000021_EAX
>> Bit Feature description
>> 20 Indicates support for IC prefetch.
>> 1 FsGsKernelGsBaseNonSerializing.
>
> I'm curious about this:
> a) Is this new CPUs are non-serialising on that write?
> b) If so, what happens if you run existing kernels/firmware on them?
> c) Bonus migration question; what happens if you live migrate from a host
> that claims to be serialising to one that has the extra non-serialising
> flag but is disabled in the emulated CPU model.
Good question. After looking at the AMD64 Architecture Programmer’s Manual
again, these writes have always been non-serializing. Behavior has not
changed. We're just reporting it through CPUID now. This information
likely isn’t being used anywhere. Let me know if you have any questions.
--
Thanks
Babu Moger
next prev parent reply other threads:[~2025-06-16 18:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 19:57 [PATCH v7 0/6] target/i386: Update EPYC CPU models for Cache property, RAS, SVM feature and add EPYC-Turin CPU model Babu Moger
2025-05-08 19:57 ` [PATCH v7 1/6] target/i386: Update EPYC CPU model for Cache property, RAS, SVM feature bits Babu Moger
2025-05-08 19:58 ` [PATCH v7 2/6] target/i386: Update EPYC-Rome " Babu Moger
2025-05-08 19:58 ` [PATCH v7 3/6] target/i386: Update EPYC-Milan " Babu Moger
2025-05-08 19:58 ` [PATCH v7 4/6] target/i386: Add couple of feature bits in CPUID_Fn80000021_EAX Babu Moger
2025-06-06 12:29 ` Dr. David Alan Gilbert
2025-06-16 18:09 ` Moger, Babu [this message]
2025-06-16 23:33 ` Dr. David Alan Gilbert
2025-05-08 19:58 ` [PATCH v7 5/6] target/i386: Update EPYC-Genoa for Cache property, perfmon-v2, RAS and SVM feature bits Babu Moger
2025-05-08 19:58 ` [PATCH v7 6/6] target/i386: Add support for EPYC-Turin model Babu Moger
2025-05-27 15:22 ` [PATCH v7 0/6] target/i386: Update EPYC CPU models for Cache property, RAS, SVM feature and add EPYC-Turin CPU model Jon Kohler
2025-05-27 15:42 ` Paolo Bonzini
2025-05-27 22:43 ` Moger, Babu
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=e7cdab23-de40-457d-aa69-f0e210206c16@amd.com \
--to=babu.moger@amd.com \
--cc=dave@treblig.org \
--cc=davydov-max@yandex-team.ru \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).