From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Wen Pu <puwen@hygon.cn>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH RFC] target/i386: Add Intel CPU model versions supporting 'xsaves'
Date: Thu, 08 Apr 2021 15:25:46 +0200 [thread overview]
Message-ID: <875z0w9acl.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <e6500701-19e5-d779-0326-376a110c5514@hygon.cn>
Wen Pu <puwen@hygon.cn> writes:
> On 2021/4/7 23:43, Vitaly Kuznetsov wrote:
>> Hyper-V 2016 refuses to boot on Skylake+ CPU models because they lack
>> 'xsaves'/'vmx-xsaves' features and this diverges from real hardware. The
>> same issue emerges with AMD "EPYC" CPU model prior to version 3 which got
>> 'xsaves' added. EPYC-Rome/EPYC-Milan CPU models have 'xsaves' enabled from
>> the very beginning so the comment blaming KVM to explain why Intel CPUs
>> lack 'xsaves' is likely outdated.
>>
>> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
>> ---
>> The only CPU model where I keep the original comment and don't add
>> a version supporting 'xsaves' is "Hygon Dhyana" as I don't know much
>> about it.
>
> Hi Vitaly,
>
> Hygon Dhyana supports 'xsaves', could you please add a version supporting
> 'xsaves' for Hygon "Dhyana"?
>
Sure, will do! Thanks for the confirmation!
--
Vitaly
prev parent reply other threads:[~2021-04-08 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 15:43 [PATCH RFC] target/i386: Add Intel CPU model versions supporting 'xsaves' Vitaly Kuznetsov
2021-04-08 12:59 ` Wen Pu
2021-04-08 13:25 ` Vitaly Kuznetsov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875z0w9acl.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=puwen@hygon.cn \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).