From: Yuchen <yu.chen@h3c.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "rth@twiddle.net" <rth@twiddle.net>,
"ehabkost@redhat.com" <ehabkost@redhat.com>,
Dongli Zhang <dongli.zhang@oracle.com>
Subject: 回复: 回复: [PATCH] target/i386: Clear xsave pkru bit when KVM XCR0 not support
Date: Sat, 20 May 2023 01:57:58 +0000 [thread overview]
Message-ID: <26ad17ab26ea43d1a5ef97c0a4c8c7bd@h3c.com> (raw)
In-Reply-To: <e7c5d527-2461-332e-638f-38c95ff2602d@redhat.com>
Paolo, thanks,
The kernel patch can solve this problem. But it is difficult to upgrade the kernel in some production environments,
and upgrading qemu is easy. This patch is just to sync qemu with kvm XSAVE features, no negative impact.
At the same time, it increases the compatibility of qemu to kernel and improves the robustness of qemu.
> -----邮件原件-----
> 发件人: Paolo Bonzini <pbonzini@redhat.com>
> 发送时间: 2023年5月20日 1:37
> 收件人: yuchen (Cloud) <yu.chen@h3c.com>
> 主题: Re: 回复: [PATCH] target/i386: Clear xsave pkru bit when KVM
> XCR0 not support
>
> On 5/18/23 14:37, Yuchen wrote:
> > Yes, because x86_cpu_xsave_all_areas() can get the correct XSAVE
> features.
>
> If you tested it, I can post the patch as a workaround. However, the
> kernel bug has been fixed too.
>
> Paolo
>
> >> -----邮件原件-----
> >> 发件人: Paolo Bonzini <pbonzini@redhat.com>
> >> 发送时间: 2023年5月18日 1:08
> >> 收件人: yuchen (Cloud) <yu.chen@h3c.com>;
> qemu-devel@nongnu.org
> >> 抄送: rth@twiddle.net; ehabkost@redhat.com; chengchiwen (Cloud)
> >> <chengchiwen@h3c.com>
> >> 主题: Re: [PATCH] target/i386: Clear xsave pkru bit when KVM XCR0
> not
> >> support
> >>
> >> On 5/17/23 12:55, Yuchen wrote:
> >>> Migrating guest from Intel new CPU (as Gold 6230) to old CPU (as
> >>> E5-2650 v4) will pause on the destination host. Because old CPU not
> >>> support xsave pkru feature, and KVM KVM_SET_XSAVE ioctl return
> >> EINVAL.
> >>>
> >>> This kernel commit introduces the problem:
> >>>
> >>> ea4d6938d4c0 x86/fpu: Replace KVMs home brewed FPU copy from
> >> user
> >>>
> >>> Signed-off-by: YuChen <yu.chen@h3c.com>
> >>
> >> Would this work instead?
> >>
> >> diff --git a/target/i386/xsave_helper.c b/target/i386/xsave_helper.c
> >> index 996e9f3bfef5..d3e5edad2ecd 100644
> >> --- a/target/i386/xsave_helper.c
> >> +++ b/target/i386/xsave_helper.c
> >> @@ -47,7 +47,7 @@ void x86_cpu_xsave_all_areas(X86CPU *cpu,
> void
> >> *buf, uint32_t buflen)
> >> stq_p(xmm + 8, env->xmm_regs[i].ZMM_Q(1));
> >> }
> >>
> >> - header->xstate_bv = env->xstate_bv;
> >> + header->xstate_bv = env->xstate_bv &
> >> + x86_cpu_xsave_xcr0_components(cpu);
> >>
> >> e = &x86_ext_save_areas[XSTATE_YMM_BIT];
> >> if (e->size && e->offset) {
> >>
> >> Paolo
> >
> > ----------------------------------------------------------------------
> > ---------------------------------------------------------------
> > 本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址
> 中列出
> > 的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部
> 或部分地泄露、复制、
> > 或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮
> 件通知发件人并删除本
> > 邮件!
> > This e-mail and its attachments contain confidential information from
> > New H3C, which is intended only for the person or entity whose address
> > is listed above. Any use of the information contained herein in any
> > way (including, but not limited to, total or partial disclosure,
> > reproduction, or dissemination) by persons other than the intended
> > recipient(s) is prohibited. If you receive this e-mail in error,
> > please notify the sender by phone or email immediately and delete it!
next prev parent reply other threads:[~2023-05-20 1:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 10:55 [PATCH] target/i386: Clear xsave pkru bit when KVM XCR0 not support Yuchen
2023-05-17 17:08 ` Paolo Bonzini
[not found] ` <6c64f1b84cbf4dd1a75301fc4615f351@h3c.com>
[not found] ` <e7c5d527-2461-332e-638f-38c95ff2602d@redhat.com>
2023-05-20 1:57 ` Yuchen [this message]
2023-05-20 6:21 ` 回复: 回复: " Yuchen
2023-05-17 17:17 ` Dongli Zhang
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=26ad17ab26ea43d1a5ef97c0a4c8c7bd@h3c.com \
--to=yu.chen@h3c.com \
--cc=dongli.zhang@oracle.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).