Add missing feature bits in EPYC-Milan model
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
linux (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
Confirmed
|
Undecided
|
Unassigned | |||
Kinetic |
Won't Fix
|
Undecided
|
Unassigned | |||
Lunar |
Confirmed
|
Undecided
|
Unassigned | |||
Mantic |
Confirmed
|
Undecided
|
Unassigned | |||
qemu (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
New
|
Undecided
|
Unassigned | |||
Kinetic |
Won't Fix
|
Undecided
|
Unassigned | |||
Lunar |
New
|
Undecided
|
Unassigned | |||
Mantic |
New
|
Undecided
|
Sergio Durigan Junior |
Bug Description
[Impact]
Add the following feature bits for EPYC-Milan model and bump the version.
vaes : Vector VAES(ENC|DEC), VAES(ENC|DEC)LAST instruction support
vpclmulqdq : Vector VPCLMULQDQ instruction support
stibp-always-on : Single Thread Indirect Branch Prediction Mode has enhanced
amd-psfd : Predictive Store Forward Disable
no-
lfence-
null-
[Test Plan]
* First of all we'll (and have in advance) run general regression tests
* Qemu shall show to be aware of the new types
# qemu-system-x86_64 -cpu ? | grep EPYC-Milan
x86 EPYC-Milan (alias configured by machine type)
x86 EPYC-Milan-v1 AMD EPYC-Milan Processor
x86 EPYC-Milan-v2 AMD EPYC-Milan Processor
[Where problems could occur]
* There are two areas to look at
a) compat behavior on old systems - e.g. libvirt would now detect IBRS
on such AMD chips and one might wonder about the change.
E.g. compatibility would exist between old-code/
code; but any action (e.g. suspend resume) from new to old code
might run into trouble (not supported that way but worth to mention
for awareness)
b) Migrations between systems - this should be covered by chip
versioning but still is worth to mention. Versioning will recognize
a formerly started system as v1 and continue to handle it that way.
Only new started guests would become v2 and behave the new and
improved way.
[Other Info]
* n/a
---
https:/
https:/
This patch depends on the definitions that were added as part of the EPYC-Milan patch:
amd-psfd, stibp-always-on:
* https:/
Add feature bits for CPUID_Fn8000002
* https:/
Kernel patches:
https://<email address hidden>/
kvm: Add support for CPUID_80000021_EAX
* https:/
kvm: Add the NO_NESTED_DATA_BP feature
* https:/
kvm: Move X86_FEATURE_
* https:/
kvm: Add the Null Selector Clears Base feature
* https:/
kvm: Add the SMM_CTL MSR not present feature
https:/
And probably this one as well:
KVM: Add common feature flag for AMD's PSFD
https:/
description: | updated |
description: | updated |
description: | updated |
tags: | added: server-triage-discuss |
Changed in qemu (Ubuntu Mantic): | |
assignee: | nobody → Sergio Durigan Junior (sergiodj) |
tags: |
added: server-todo removed: server-triage-discuss |
Changed in linux (Ubuntu Jammy): | |
status: | Incomplete → New |
Changed in linux (Ubuntu Lunar): | |
status: | Incomplete → New |
Changed in linux (Ubuntu Mantic): | |
status: | Incomplete → New |
Changed in qemu (Ubuntu Kinetic): | |
status: | New → Won't Fix |
Changed in linux (Ubuntu): | |
status: | New → Incomplete |
Changed in linux (Ubuntu Jammy): | |
status: | New → Incomplete |
Changed in linux (Ubuntu Lunar): | |
status: | New → Incomplete |
Changed in linux (Ubuntu Jammy): | |
status: | Incomplete → Confirmed |
Changed in linux (Ubuntu Lunar): | |
status: | Incomplete → Confirmed |
Changed in linux (Ubuntu Mantic): | |
status: | Incomplete → Confirmed |
As far as I have researched, the Linux patches pointed by Markus haven't been backported to any of our kernels yet. As such, I am adding a Linux task to this bug so that the kernel team can chime in and provide some feedback as to whether these patches will be backported.
@Kernel team, could you please take a look and let us know? TIA.