c3498942a5
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
71 lines
2.9 KiB
C
71 lines
2.9 KiB
C
/*-
|
|
* Copyright (c) 2011 NetApp, Inc.
|
|
* All rights reserved.
|
|
*
|
|
* Redistribution and use in source and binary forms, with or without
|
|
* modification, are permitted provided that the following conditions
|
|
* are met:
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
* notice, this list of conditions and the following disclaimer.
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
* documentation and/or other materials provided with the distribution.
|
|
*
|
|
* THIS SOFTWARE IS PROVIDED BY NETAPP, INC ``AS IS'' AND
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL NETAPP, INC OR CONTRIBUTORS BE LIABLE
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
* SUCH DAMAGE.
|
|
*
|
|
* $FreeBSD$
|
|
*/
|
|
|
|
#ifndef _VMX_MSR_H_
|
|
#define _VMX_MSR_H_
|
|
|
|
struct vmx;
|
|
|
|
void vmx_msr_init(void);
|
|
void vmx_msr_guest_init(struct vmx *vmx, int vcpuid);
|
|
void vmx_msr_guest_enter(struct vmx *vmx, int vcpuid);
|
|
void vmx_msr_guest_exit(struct vmx *vmx, int vcpuid);
|
|
int vmx_rdmsr(struct vmx *, int vcpuid, u_int num, uint64_t *val, bool *retu);
|
|
int vmx_wrmsr(struct vmx *, int vcpuid, u_int num, uint64_t val, bool *retu);
|
|
|
|
uint32_t vmx_revision(void);
|
|
|
|
int vmx_set_ctlreg(int ctl_reg, int true_ctl_reg, uint32_t ones_mask,
|
|
uint32_t zeros_mask, uint32_t *retval);
|
|
|
|
/*
|
|
* According to Section 21.10.4 "Software Access to Related Structures",
|
|
* changes to data structures pointed to by the VMCS must be made only when
|
|
* there is no logical processor with a current VMCS that points to the
|
|
* data structure.
|
|
*
|
|
* This pretty much limits us to configuring the MSR bitmap before VMCS
|
|
* initialization for SMP VMs. Unless of course we do it the hard way - which
|
|
* would involve some form of synchronization between the vcpus to vmclear
|
|
* all VMCSs' that point to the bitmap.
|
|
*/
|
|
#define MSR_BITMAP_ACCESS_NONE 0x0
|
|
#define MSR_BITMAP_ACCESS_READ 0x1
|
|
#define MSR_BITMAP_ACCESS_WRITE 0x2
|
|
#define MSR_BITMAP_ACCESS_RW (MSR_BITMAP_ACCESS_READ|MSR_BITMAP_ACCESS_WRITE)
|
|
void msr_bitmap_initialize(char *bitmap);
|
|
int msr_bitmap_change_access(char *bitmap, u_int msr, int access);
|
|
|
|
#define guest_msr_rw(vmx, msr) \
|
|
msr_bitmap_change_access((vmx)->msr_bitmap, (msr), MSR_BITMAP_ACCESS_RW)
|
|
|
|
#define guest_msr_ro(vmx, msr) \
|
|
msr_bitmap_change_access((vmx)->msr_bitmap, (msr), MSR_BITMAP_ACCESS_READ)
|
|
|
|
#endif
|