==Changelog== v2->v3: - reorder patches to add fpu_guest_cfg first and then introduce dynamic kernel feature concept (Dave) - Revise changelog for all patches except the first and the last one (Dave) - Split up patches that do multiple things into separate patches. - collect tags for patch 1 v1->v2: - rebase onto the latest kvm-x86/next - Add performance data to the cover-letter - v1: https://lore.kernel.org/kvm/73802bff-833c-4233-9a5b-88af0d062c82@xxxxxxxxx/ ==Background== This series spins off from CET KVM virtualization enabling series [1]. The purpose is to get these preparation work resolved ahead of KVM part landing. There was a discussion about introducing CET supervisor state support [2] [3]. CET supervisor state, i.e., IA32_PL{0,1,2}_SSP, are xsave-managed MSRs, it can be enabled via IA32_XSS[bit 12]. KVM relies on host side CET supervisor state support to fully enable guest CET MSR contents storage. The benefits are: 1) No need to manually save/restore the 3 MSRs when vCPU fpu context is sched in/out. 2) Omit manually swapping the three MSRs at VM-Exit/VM-Entry for guest/host. 3) Make guest CET user/supervisor states managed in a consistent manner within host kernel FPU framework. ==Solution== This series tries to: 1) Fix existing issue regarding enabling guest supervisor states support. 2) Add CET supervisor state support in core kernel. 3) Introduce new FPU config for guest fpstate setup. With the preparation work landed, for guest fpstate, we have xstate_bv[12] == xcomp_bv[12] == 1 and CET supervisor state is saved/reloaded when xsaves/xrstors executes on guest fpstate. For non-guest/normal fpstate, we have xstate_bv[12] == xcomp_bv[12] == 0, then HW can optimize xsaves/xrstors operations. ==Performance== We measured context-switching performance with the benchmark [4] in following three cases. case 1: the baseline. i.e., this series isn't applied case 2: baseline + this series. CET-S space is allocated for guest fpu only. case 3: baseline + allocate CET-S space for all tasks. Hardware init optimization avoids writing out CET-S space on each XSAVES. the data are as follows case |IA32_XSS[12] | Space | RFBM[12] | Drop% -----+-------------+-------+----------+------ 1 | 0 | None | 0 | 0.0% 2 | 1 | None | 0 | 0.2% 3 | 1 | 24B? | 1 | 0.2% Case 2 and 3 have no difference in performnace. But case 2 is preferred because it can save 24B of CET-S space for all non-vCPU threads with just a one-line change: + fpu_kernel_cfg.default_features &= ~XFEATURE_MASK_KERNEL_DYNAMIC; fpu_guest_cfg has its own merits. Regardless of the approach we take, using different FPU configuration settings for the guest and the kernel improves readability, decouples them from each other, and arguably enhances extensibility. [1]: https://lore.kernel.org/all/20240219074733.122080-1-weijiang.yang@xxxxxxxxx/ [2]: https://lore.kernel.org/all/ZM1jV3UPL0AMpVDI@xxxxxxxxxx/ [3]: https://lore.kernel.org/all/2597a87b-1248-b8ce-ce60-94074bc67ea4@xxxxxxxxx/ [4]: https://github.com/antonblanchard/will-it-scale/blob/master/tests/context_switch1.c Chao Gao (2): x86/fpu/xstate: Drop @perm from guest pseudo FPU container x86/fpu/xstate: Correct xfeatures cache in guest pseudo fpu container Sean Christopherson (1): x86/fpu/xstate: Always preserve non-user xfeatures/flags in __state_perm Yang Weijiang (7): x86/fpu/xstate: Correct guest fpstate size calculation x86/fpu/xstate: Introduce guest FPU configuration x86/fpu/xstate: Initialize guest perm with fpu_guest_cfg x86/fpu/xstate: Initialize guest fpstate with fpu_guest_config x86/fpu/xstate: Add CET supervisor xfeature support x86/fpu/xstate: Introduce XFEATURE_MASK_KERNEL_DYNAMIC xfeature set x86/fpu/xstate: Warn if CET supervisor state is detected in normal fpstate arch/x86/include/asm/fpu/types.h | 31 +++++++++++++++------------ arch/x86/include/asm/fpu/xstate.h | 11 ++++++---- arch/x86/kernel/fpu/core.c | 34 +++++++++++++++++------------- arch/x86/kernel/fpu/xstate.c | 35 ++++++++++++++++++++++++------- arch/x86/kernel/fpu/xstate.h | 2 ++ 5 files changed, 74 insertions(+), 39 deletions(-) -- 2.46.1
