xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH v6 00/21] x86: Improvements to cpuid handling for guests
Date: Fri, 8 Apr 2016 20:04:40 -0400	[thread overview]
Message-ID: <20160409000440.GE2926@char.us.oracle.com> (raw)
In-Reply-To: <1460147517-11706-1-git-send-email-andrew.cooper3@citrix.com>

On Fri, Apr 08, 2016 at 09:31:36PM +0100, Andrew Cooper wrote:
> This series is available in git form at:
>   http://xenbits.xen.org/git-http/people/andrewcoop/xen.git levelling-v6

And in 'for-staging'.
> 
> Very few changes from v5:
>  * Change the PKU feature depdendency from PAE to LM
>  * Bugfix for HVM CPUID.0xd[1].ebx when %xcr0 is empty
>  * Tweak command line parsing in xen-cpuid to avoid a backwards goto
>  * Misc comment improvements
> 
> Most importantly, a complete set of Reviews and Acks.
> 
> Andrew Cooper (21):
>   xen/x86: Annotate VM applicability in featureset
>   xen/x86: Calculate maximum host and guest featuresets
>   xen/x86: Generate deep dependencies of features
>   xen/x86: Clear dependent features when clearing a cpu cap
>   xen/x86: Improve disabling of features which have dependencies
>   xen/x86: Improvements to in-hypervisor cpuid sanity checks
>   x86/cpu: Move set_cpumask() calls into c_early_init()
>   x86/cpu: Sysctl and common infrastructure for levelling context
>     switching
>   x86/cpu: Rework AMD masking MSR setup
>   x86/cpu: Rework Intel masking/faulting setup
>   x86/cpu: Context switch cpuid masks and faulting state in
>     context_switch()
>   x86/pv: Provide custom cpumasks for PV domains
>   x86/domctl: Update PV domain cpumasks when setting cpuid policy
>   xen+tools: Export maximum host and guest cpu featuresets via SYSCTL
>   tools/libxc: Modify bitmap operations to take void pointers
>   tools/libxc: Use public/featureset.h for cpuid policy generation
>   tools/libxc: Expose the automatically generated cpu featuremask
>     information
>   tools: Utility for dealing with featuresets
>   tools/libxc: Wire a featureset through to cpuid policy logic
>   tools/libxc: Use featuresets rather than guesswork
>   tools/libxc: Calculate xstate cpuid leaf from guest information

Applied from your 'for-staging' branch which top commit id
is 75f9455e9263289864b7b3e55579133807995de6

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

      parent reply	other threads:[~2016-04-09  0:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08 20:31 [PATCH v6 00/21] x86: Improvements to cpuid handling for guests Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 01/21] xen/x86: Annotate VM applicability in featureset Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 02/21] xen/x86: Calculate maximum host and guest featuresets Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 03/21] xen/x86: Generate deep dependencies of features Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 04/21] xen/x86: Clear dependent features when clearing a cpu cap Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 05/21] xen/x86: Improve disabling of features which have dependencies Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 06/21] xen/x86: Improvements to in-hypervisor cpuid sanity checks Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 07/21] x86/cpu: Move set_cpumask() calls into c_early_init() Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 08/21] x86/cpu: Sysctl and common infrastructure for levelling context switching Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 09/21] x86/cpu: Rework AMD masking MSR setup Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 10/21] x86/cpu: Rework Intel masking/faulting setup Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 11/21] x86/cpu: Context switch cpuid masks and faulting state in context_switch() Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 12/21] x86/pv: Provide custom cpumasks for PV domains Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 13/21] x86/domctl: Update PV domain cpumasks when setting cpuid policy Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 14/21] xen+tools: Export maximum host and guest cpu featuresets via SYSCTL Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 15/21] tools/libxc: Modify bitmap operations to take void pointers Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 16/21] tools/libxc: Use public/featureset.h for cpuid policy generation Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 17/21] tools/libxc: Expose the automatically generated cpu featuremask information Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 18/21] tools: Utility for dealing with featuresets Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 19/21] tools/libxc: Wire a featureset through to cpuid policy logic Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 20/21] tools/libxc: Use featuresets rather than guesswork Andrew Cooper
2016-04-08 20:31 ` [PATCH v6 21/21] tools/libxc: Calculate xstate cpuid leaf from guest information Andrew Cooper
2016-04-09  0:04 ` Konrad Rzeszutek Wilk [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=20160409000440.GE2926@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=andrew.cooper3@citrix.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).