qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH] target-i386: fix losing XCR0 processor state co


From: Paolo Bonzini
Subject: Re: [Qemu-devel] [PATCH] target-i386: fix losing XCR0 processor state component bits
Date: Wed, 28 Sep 2016 17:01:01 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0


On 28/09/2016 16:57, Eduardo Habkost wrote:\
> This can be fixed by adding actual property names to the
> FEAT_XSAVE_COMP_* bits. This way we will be able to report
> meaningful names to management in case GET_SUPPORTED_CPUID says a
> given xsave component is not supported yet, and will ensure we
> correctly treat still-unknown xsave components as unmigratable.

Hmm, right.  Even though XSAVE could be migrated as a blob, QEMU
marshals and unmarshals the registers out and back into the xsave data,
so that unknown features are indeed unmigratable.

But are the property names necessary?  It makes no sense to
enable/disable XSAVE components separately from the other CPUID bits
that enable them.  Could we just mark all unknown features as
unmigratable without giving them names?

Paolo



reply via email to

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