From: Paolo Bonzini <pbonzini@redhat.com>
To: Jing Liu <jing2.liu@linux.intel.com>, Wanpeng Li <kernellwp@gmail.com>
Cc: kvm <kvm@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] KVM: x86: expose AVX512_BF16 feature to guest
Date: Mon, 15 Jul 2019 13:56:12 +0200 [thread overview]
Message-ID: <68d07943-c957-7caa-f77c-944cd0d726bf@redhat.com> (raw)
In-Reply-To: <332e8951-e6bb-8394-490d-26c8154712b9@linux.intel.com>
On 15/07/19 13:05, Jing Liu wrote:
>>
>>
> Thanks for the information.
>
> This warning would be fixed by changing to
> entry->eax = min(entry->eax, (u32)1);
>
> @Paolo, sorry for trouble. Would you mind if I re-send?
No need, I can fix it myself (I'd also use 1u instead of the cast).
Paolo
prev parent reply other threads:[~2019-07-15 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 5:49 [PATCH v1] KVM: x86: expose AVX512_BF16 feature to guest Jing Liu
2019-07-13 10:37 ` Paolo Bonzini
2019-07-15 2:46 ` Jing Liu
2019-07-15 6:06 ` Wanpeng Li
2019-07-15 11:05 ` Jing Liu
2019-07-15 11:56 ` Paolo Bonzini [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=68d07943-c957-7caa-f77c-944cd0d726bf@redhat.com \
--to=pbonzini@redhat.com \
--cc=jing2.liu@linux.intel.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).