[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v4 1/3] x86/msr: Dispatch Xen and Viridian MSRs from guest_{wr, rd}msr()
On Wed, 2018-09-12 at 13:00 +0100, Andrew Cooper wrote: > Despite the complicated diff in {svm,vmx}_msr_write_intercept(), it is just > the 0 case losing one level of indentation, as part of removing the call to > wrmsr_hypervisor_regs(). > > The case blocks in guest_{wr,rd}msr() use raw numbers, partly for consistency > with the CPUID side of things, but mainly because this is clearer code to > follow. In particular, the Xen block may overlap with the Viridian block if > Viridian is not enabled for the domain, and trying to express this with named > literals caused more confusion that it solved. > > Future changes with clean up the individual APIs, including allowing these > MSRs to be usable for vcpus other than current (no callers exist with v != > current). > > Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> > Reviewed-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> > Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx> > Reviewed-by: Paul Durrant <paul.durrant@xxxxxxxxxx> > --- > CC: Jan Beulich <JBeulich@xxxxxxxx> > CC: Wei Liu <wei.liu2@xxxxxxxxxx> > CC: Roger Pau Monné <roger.pau@xxxxxxxxxx> > CC: Sergey Dyasli <sergey.dyasli@xxxxxxxxxx> > > v3: > * Split out of previous series. Retain appropriate R-by's > v4: > * Retain switch() for interpreting the result of wrmsr_hypervisor_regs() > --- > xen/arch/x86/hvm/svm/svm.c | 27 +++----------------------- > xen/arch/x86/hvm/vmx/vmx.c | 28 ++++----------------------- > xen/arch/x86/msr.c | 43 > ++++++++++++++++++++++++++++++++++++++---- > xen/arch/x86/pv/emul-priv-op.c | 6 ------ > 4 files changed, 46 insertions(+), 58 deletions(-) Reviewed-by: Sergey Dyasli <sergey.dyasli@xxxxxxxxxx> -- Thanks, Sergey _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |