diff options
| author | Yosry Ahmed <yosry@kernel.org> | 2026-07-13 18:10:18 +0000 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2026-07-22 13:41:54 -0700 |
| commit | a4b8acd428ba3f03952ef309d7f438dbc357557b (patch) | |
| tree | 5a44d13cbbae9648893b0b631e4423f26db1a89a /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | e62392bf39ebfdf60d1d082799397fe1cbf8dfc5 (diff) | |
KVM: x86: Always initialize EFER reserved bits on vendor initialization
EFER reserved bits are statically initialized, and do not reset if a
vendor module is re-loaded. For example, loading kvm_amd with nested=1
removes EFER.SVME (and potentially EFER.LMSLE) from the reserved bits.
Reloading kvm_amd with nested=0 does not add them back, allowing
userspace to set EFER.SVME with nested=0.
Re-initializing EFER reserved bits before configuring them on vendor
initialization.
Cc: stable@vger.kernel.org
Signed-off-by: Yosry Ahmed <yosry@kernel.org>
Link: https://patch.msgid.link/20260713181020.2735367-4-yosry@kernel.org
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
