From: Paolo Bonzini <pbonzini@redhat.com>
To: Piotr Luc <piotr.luc@intel.com>, x86@kernel.org
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] vpopcntdq support
Date: Tue, 10 Jan 2017 18:39:08 +0100 [thread overview]
Message-ID: <bb58b1a6-1e63-61db-da49-2173f7c730e1@redhat.com> (raw)
In-Reply-To: <20170110173403.6010-1-piotr.luc@intel.com>
On 10/01/2017 18:34, Piotr Luc wrote:
> Hi,
>
> This patchset adds the support for new CPUID feature bit that announces the
> vector population count instructions for dwords and qwords.
>
> The path 1/2 adds new feature flags and handles clearing the feature bit in
> case xsave is not enabled.
>
> The patch 2/2 enables passing the feature bit to a kvm/quemu guest.
>
> The patchset is based on v4.10-rc3.
Thanks. I can use a topic branch for patch 1 to apply patch 2.
Regards,
Paolo
> Regards,
> Piotr
>
> Piotr Luc (2):
> x86/cpufeature: Add AVX512_VPOPCNTDQ feature
> kvm: x86: Expose Intel VPOPCNTDQ feature to guest
>
> arch/x86/include/asm/cpufeatures.h | 2 +-
> arch/x86/kernel/fpu/xstate.c | 1 +
> arch/x86/kvm/cpuid.c | 2 +-
> tools/arch/x86/include/asm/cpufeatures.h | 1 +
> 4 files changed, 4 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2017-01-10 17:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 17:34 Piotr Luc
2017-01-10 17:34 ` [PATCH v1 1/2] x86/cpufeature: Add AVX512_VPOPCNTDQ feature Piotr Luc
2017-01-16 17:23 ` Borislav Petkov
2017-01-16 19:43 ` [tip:x86/cpufeature] " tip-bot for Piotr Luc
2017-01-10 17:34 ` [PATCH v1 2/2] kvm: x86: Expose Intel VPOPCNTDQ feature to guest Piotr Luc
2017-01-20 18:00 ` Radim Krčmář
2017-01-10 17:39 ` Paolo Bonzini [this message]
2017-01-11 13:02 ` [PATCH v1 0/2] vpopcntdq support Luc, Piotr
2017-01-16 19:43 ` Thomas Gleixner
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=bb58b1a6-1e63-61db-da49-2173f7c730e1@redhat.com \
--to=pbonzini@redhat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=piotr.luc@intel.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®