From c3498942a588dda8ae4e7bd9d03d53baa2cbf39a Mon Sep 17 00:00:00 2001 From: Neel Natu Date: Sat, 20 Sep 2014 02:35:21 +0000 Subject: Restructure the MSR handling so it is entirely handled by processor-specific code. There are only a handful of MSRs common between the two so there isn't too much duplicate functionality. The VT-x code has the following types of MSRs: - MSRs that are unconditionally saved/restored on every guest/host context switch (e.g., MSR_GSBASE). - MSRs that are restored to guest values on entry to vmx_run() and saved before returning. This is an optimization for MSRs that are not used in host kernel context (e.g., MSR_KGSBASE). - MSRs that are emulated and every access by the guest causes a trap into the hypervisor (e.g., MSR_IA32_MISC_ENABLE). Reviewed by: grehan --- sys/modules/vmm/Makefile | 1 - 1 file changed, 1 deletion(-) (limited to 'sys/modules/vmm') diff --git a/sys/modules/vmm/Makefile b/sys/modules/vmm/Makefile index 76f9364433fb..702587bb72c1 100644 --- a/sys/modules/vmm/Makefile +++ b/sys/modules/vmm/Makefile @@ -19,7 +19,6 @@ SRCS+= vmm.c \ vmm_ipi.c \ vmm_lapic.c \ vmm_mem.c \ - vmm_msr.c \ vmm_stat.c \ vmm_util.c \ x86.c \ -- cgit v1.3