>>> On 08.06.18 at 20:48, <[email protected]> wrote: > The main purpose of this change is to allow us to set a specific MSR value, > without needing to know whether there is already a load/save list slot for it. > > Previously, callers wanting this property needed to call both vmx_add_*_msr() > and vmx_write_*_msr() to cover both cases, and there are no callers which want > the old behaviour of being a no-op if an entry already existed for the MSR. > > As a result of this API improvement, the default value for guest MSRs need not > be 0, and the default for host MSRs need not be passed via hardware register. > In practice, this cleans up the VPMU allocation logic, and avoids an MSR read > as part of vcpu construction. > > Signed-off-by: Andrew Cooper <[email protected]>
Reviewed-by: Jan Beulich <[email protected]> _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
