From: "Michal Prívozník" <mprivozn@redhat.com>
To: Yang Zhong <yang.zhong@intel.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, pkrempa@redhat.com
Subject: Re: [PATCH] x86/amx: compatible with older kernel release
Date: Fri, 18 Mar 2022 15:31:20 +0100 [thread overview]
Message-ID: <eb0d5aaf-940a-30fb-19dd-4d730bec30d6@redhat.com> (raw)
In-Reply-To: <20220318115529.4850-1-yang.zhong@intel.com>
On 3/18/22 12:55, Yang Zhong wrote:
> The AMX KVM introduced one new ARCH_GET_XCOMP_SUPP system attribute
> API to get host side supported_xcr0 and latest Qemu can decide if it
> can request dynamically enabled XSAVE features permission. But this
> implementation(19db68ca68) did not consider older kernel release.
> This patch can avoid to read this new KVM_GET_DEVICE_ATTR ioctl.
>
> Signed-off-by: Yang Zhong <yang.zhong@intel.com>
> ---
> target/i386/kvm/kvm.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
Tested-by: Michal Privoznik <mprivozn@redhat.com>
Thank you.
Michal
prev parent reply other threads:[~2022-03-18 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 11:55 [PATCH] x86/amx: compatible with older kernel release Yang Zhong
2022-03-18 14:31 ` Michal Prívozník [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=eb0d5aaf-940a-30fb-19dd-4d730bec30d6@redhat.com \
--to=mprivozn@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yang.zhong@intel.com \
/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).