xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	ian.jackson@eu.citrix.com, Luwei Kang <luwei.kang@intel.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] tools/libxc: Add xstate cpuid leaf of avx512
Date: Fri, 4 Nov 2016 14:24:55 +0000	[thread overview]
Message-ID: <20161104142455.GH30231@citrix.com> (raw)
In-Reply-To: <20161104134020.GE28847@char.us.oracle.com>

On Fri, Nov 04, 2016 at 09:40:20AM -0400, Konrad Rzeszutek Wilk wrote:
> On Fri, Nov 04, 2016 at 11:00:16AM +0000, Wei Liu wrote:
> > On Fri, Nov 04, 2016 at 10:20:24AM +0000, Andrew Cooper wrote:
> > > On 04/11/16 08:29, Luwei Kang wrote:
> > > > Enable get xstate cpuid leaf information regarding avx512 in guest.
> > > >
> > > > Signed-off-by: Luwei Kang <luwei.kang@intel.com>
> > > 
> > > Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
> > > 
> > 
> > Oops, should have read all the entire thread.
> > 
> > I think we can sneak this in for 4.8 if we have some free cycles,
> > otherwise I will queue it up for -next.
> 
> It would be good to get it in as it provides some nice performance
> benefits for guests.
> 

Given that the queue is empty at the moment, I've pushed this patch.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-11-04 14:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04  8:29 [PATCH] tools/libxc: Add xstate cpuid leaf of avx512 Luwei Kang
2016-11-04 10:20 ` Andrew Cooper
2016-11-04 11:00   ` Wei Liu
2016-11-04 13:40     ` Konrad Rzeszutek Wilk
2016-11-04 14:24       ` Wei Liu [this message]
2016-11-04 10:57 ` Wei Liu

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=20161104142455.GH30231@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=luwei.kang@intel.com \
    --cc=xen-devel@lists.xen.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).