Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Piotr Luc" <piotr.luc@intel.com>,
	x86@kernel.org, "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: Mon, 16 Jan 2017 20:43:38 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1701162041010.3923@nanos> (raw)
In-Reply-To: <bb58b1a6-1e63-61db-da49-2173f7c730e1@redhat.com>

Paolo,

On Tue, 10 Jan 2017, Paolo Bonzini wrote:
> 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.

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/cpufeature

contains that patch now (nothing else for now):

	 06b35d93af0a: x86/cpufeature: Add AVX512_VPOPCNTDQ feature

So you can pull that into your tree as a base for the other one.

Thanks,

	tglx

      parent reply	other threads:[~2017-01-16 19:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 17:34 [PATCH v1 0/2] vpopcntdq support 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-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 ` [PATCH v1 0/2] vpopcntdq support Paolo Bonzini
2017-01-11 13:02   ` Luc, Piotr
2017-01-16 19:43   ` Thomas Gleixner [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=alpine.DEB.2.20.1701162041010.3923@nanos \
    --to=tglx@linutronix.de \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=piotr.luc@intel.com \
    --cc=rkrcmar@redhat.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