On 30/10/2019 10:39, Jan Beulich wrote: > To fulfill the "protected" in its name, don't let the real hardware > values "shine through". Report a control register value expressing this. > > Signed-off-by: Jan Beulich <jbeul...@suse.com> > --- > TBD: Do we want to permit Dom0 access?
I would recommend reordering the two patches and putting this one first (along with the enumeration details, along with a pair of feature strings in xen-cpuid). This patch at least wants backporting. This would be far more simple if we don't permit dom0 access. Yes, it shares platform responsibility with Xen, but it also can't do anything more with the value than Xen can, which is to simply print it out for #MCEs. Avoiding giving dom0 access would remove the need to attempt to virtualise something which is model specific on the Intel side, and allow all 4 MSRs to be unconditional #GP's. I for one don't want to have to consider the migration implications of letting guests see this. ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
