>>> On 15.03.18 at 12:21, wrote:
> On 15/03/18 11:13, Jan Beulich wrote:
> On 15.03.18 at 12:03, wrote:
>>> On 15/03/18 10:40, Jan Beulich wrote:
>> @@ -200,6 +202,16 @@ int guest_wrmsr(struct vcpu *v, uint32_t
>> /*
On 15/03/18 11:13, Jan Beulich wrote:
On 15.03.18 at 12:03, wrote:
>> On 15/03/18 10:40, Jan Beulich wrote:
> @@ -200,6 +202,16 @@ int guest_wrmsr(struct vcpu *v, uint32_t
> /* Read-only */
> goto gp_fault;
>
> +case
>>> On 15.03.18 at 12:03, wrote:
> On 15/03/18 10:40, Jan Beulich wrote:
>>
@@ -200,6 +202,16 @@ int guest_wrmsr(struct vcpu *v, uint32_t
/* Read-only */
goto gp_fault;
+case MSR_AMD_PATCHLOADER:
+if (
>>> On 13.03.18 at 11:36, wrote:
> On 13/03/2018 10:13, Jan Beulich wrote:
>> The respective MSRs are write-only, and hence attempts by guests to
>> write to these are - as of 1f1d183d49 ("x86/HVM: don't give the wrong
>> impression of WRMSR succeeding") no longer
On 13/03/2018 10:13, Jan Beulich wrote:
> The respective MSRs are write-only, and hence attempts by guests to
> write to these are - as of 1f1d183d49 ("x86/HVM: don't give the wrong
> impression of WRMSR succeeding") no longer ignored. Restore original
> behavior for the two affected MSRs.
>
>