On 16.04.2024 08:18, Sergiy Kibrik wrote: > This series aims to continue what Xenia started a year ago: > > https://lore.kernel.org/xen-devel/20230213145751.1047236-1-burzalod...@gmail.com/ > > Here's an attempt to provide a means to render the cpu virtualization > technology support in Xen configurable. > Currently, irrespectively of the target platform, both AMD-V and Intel VT-x > drivers are built. > The series adds two new Kconfig controls, SVM and VMX, that can be > used to switch to a finer-grained configuration for a given platform, and > reduce dead code. > > The code separation is done using the new config guards. > > Since the initial RFC series felt rather welcomed, I took a courage naming > it v1 and continuing from there. New changes are: > > v1: > * changed Kconfig options naming > * use IS_ENABLED() instead of #ifdef where possible > * move altp2m code apart from p2m & hide under VMX option > * introduce helper in cpu_has_vmx_* macros > * and address other comments from Jan > > Sergiy Kibrik (6): > x86/monitor: guard altp2m usage > x86/p2m: guard altp2m init/teardown > x86/p2m: move altp2m-related code to separate file > x86/p2m: guard altp2m code with CONFIG_VMX option > x86/vpmu: separate amd/intel vPMU code > x86/vmx: introduce helper function for vmcs macro > > Xenia Ragiadakou (9): > x86: introduce AMD-V and Intel VT-x Kconfig options > x86/hvm: guard AMD-V and Intel VT-x hvm_function_table initializers > x86/p2m: guard vmx specific ept functions with CONFIG_VMX > x86/traps: guard vmx specific functions with CONFIG_VMX > x86/domain: guard svm specific functions with CONFIG_SVM > x86/oprofile: guard svm specific symbols with CONFIG_SVM > x86: wire cpu_has_{svm/vmx}_* to false when svm/vmx not enabled > x86/ioreq: guard VIO_realmode_completion with CONFIG_VMX > x86/hvm: make AMD-V and Intel VT-x support configurable
Going forward, can you please make sure you send patch series as threads (i.e. individual patches with Reply-to: referencing the cover letter)? Jan
