From: Paolo Bonzini <pbonzini@redhat.com>
To: Kyung Min Park <kyung.min.park@intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
hpa@zytor.com, sean.j.christopherson@intel.com,
jmattson@google.com, joro@8bytes.org, vkuznets@redhat.com,
wanpengli@tencent.com, cathy.zhang@intel.com
Subject: Re: [PATCH 0/2] Enumerate and expose AVX512_FP16 feature
Date: Sat, 12 Dec 2020 00:42:29 +0100 [thread overview]
Message-ID: <a10c6b11-9e70-23ac-cdb2-141bb913de3d@redhat.com> (raw)
In-Reply-To: <20201208033441.28207-1-kyung.min.park@intel.com>
On 08/12/20 04:34, Kyung Min Park wrote:
> Introduce AVX512_FP16 feature and expose it to KVM CPUID for processors
> that support it. KVM reports this information and guests can make use
> of it.
>
> Detailed information on the instruction and CPUID feature flag can be found
> in the latest "extensions" manual [1].
>
> Reference:
> [1]. https://software.intel.com/content/www/us/en/develop/download/intel-architecture-instruction-set-extensions-programming-reference.html
>
> Cathy Zhang (1):
> x86: Expose AVX512_FP16 for supported CPUID
>
> Kyung Min Park (1):
> Enumerate AVX512 FP16 CPUID feature flag
>
> arch/x86/include/asm/cpufeatures.h | 1 +
> arch/x86/kernel/cpu/cpuid-deps.c | 1 +
> arch/x86/kvm/cpuid.c | 2 +-
> 3 files changed, 3 insertions(+), 1 deletion(-)
>
Queued, with adjusted commit message according to Sean's review.
Paolo
next prev parent reply other threads:[~2020-12-11 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 3:34 [PATCH 0/2] Enumerate and expose AVX512_FP16 feature Kyung Min Park
2020-12-08 3:34 ` [PATCH 1/2] Enumerate AVX512 FP16 CPUID feature flag Kyung Min Park
2020-12-08 9:28 ` Borislav Petkov
2020-12-08 3:34 ` [PATCH 2/2] x86: Expose AVX512_FP16 for supported CPUID Kyung Min Park
2020-12-11 1:03 ` Sean Christopherson
2020-12-11 23:42 ` Paolo Bonzini [this message]
2020-12-15 1:43 ` [PATCH 0/2] Enumerate and expose AVX512_FP16 feature Zhang, Cathy
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=a10c6b11-9e70-23ac-cdb2-141bb913de3d@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=cathy.zhang@intel.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=kyung.min.park@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@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