diff options
| author | Yosry Ahmed <yosry@kernel.org> | 2026-07-13 18:10:20 +0000 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2026-07-22 13:41:55 -0700 |
| commit | 92b2af2b6d2c9f53097e48614ea9b9e3aa1dfd43 (patch) | |
| tree | 791243a72c91c70e2dcde198a5d0616c84cf9f8e /scripts | |
| parent | 37352c4fbdd7921c032ab7e0eb7a0fec960924ec (diff) | |
| download | linux-92b2af2b6d2c9f53097e48614ea9b9e3aa1dfd43.tar.gz linux-92b2af2b6d2c9f53097e48614ea9b9e3aa1dfd43.zip | |
KVM: x86: Move supported EFER bits to kvm_caps
Supported EFER bits naturally fits into kvm_caps because it gets
recomputed during vendor initialization (e.g. to account for EFER.SVME
being allowed/disallowed based on nested being enabled/disabled). Move
efer_supported_bits into kvm_caps as supported_efer_bits (for naming
consistency).
As the bitmask is now globally visible as part of kvm_caps, there's
little use for helpers to enable/disable specific bits, so drop them and
open-code updates to kvm_caps.supported_efer_bits.
No functional change intended.
Suggested-by: Sean Christopherson <seanjc@google.com>
Reviewed-by: Nikolay Borisov <nik.borisov@suse.com>
Signed-off-by: Yosry Ahmed <yosry@kernel.org>
Link: https://patch.msgid.link/20260713181020.2735367-6-yosry@kernel.org
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions