On 12/10/18 6:52 AM, Andrew Cooper wrote:
> The intention of this patch was to remove the calls to nsvm_{rd,wr}msr() from
> the default cases of svm_msr_{read,write}_intercept(), but it has turned into
> a more corrective patch than just code motion.
>
> First, collect the VM_CR bit definitions next to the main define, and simplify
> the naming. The SVM MSRs should be entirely unavailable when SVM isn't
> enumerated in CPUID.
>
> When SVM is available, Xen only supports the "Enabled" mode as described in
> the BKGD/PPRs, which means VM_CR.LOCK should be set. This in turn means the
> MSR_SVM_LOCK_KEY should be implemented. It is read-as-0/write-discard as Xen
> doesn't implement the "disabled with user supplied key" mode.
What about bits 0-2? I am not sure what a guest can do with them but
they are writable.
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
