qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: [PATCH v3 12/21] kvm: x86: Drop MCE MSRs write back res


From: Jan Kiszka
Subject: [Qemu-devel] Re: [PATCH v3 12/21] kvm: x86: Drop MCE MSRs write back restrictions
Date: Wed, 05 Jan 2011 09:07:36 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666

Am 05.01.2011 07:42, Huang Ying wrote:
> On Tue, 2011-01-04 at 16:32 +0800, Jan Kiszka wrote:
>> From: Jan Kiszka <address@hidden>
>>
>> There is no need to restrict writing back MCE MSRs to reset or full
>> state updates as setting their values has no side effects.
> 
> Sorry for late.

Don't worry.

> 
> The MCE MSRs contents is sticky for warm reset except MCG_STATUS, so
> their content should be kept.  And the following sequence may set
> uncorrected value in MCE registers.
> 
> savevm -> loadvm -> (OS clear MCE registers) -> reset -> (MCE registers
> has new (uncorrected) value)

Sorry, I can't follow. Unless I miss some subtle detail, the question is
not when we transfer the mcg_* CPUState fields to the kernel, but when
and how we manipulate them in user space, e.g. on reset. Where are those
fields touched incorrectly between get and put msrs so that we cannot
write them back?

Jan

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]