All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] tools/libxc: Fix the reported max_leaf values for PV guests
Date: Wed, 11 Jan 2017 14:32:47 +0000	[thread overview]
Message-ID: <20170111143247.GN1100@citrix.com> (raw)
In-Reply-To: <1484138681-24805-1-git-send-email-andrew.cooper3@citrix.com>

On Wed, Jan 11, 2017 at 12:44:41PM +0000, Andrew Cooper wrote:
> When iterating through CPUID leaves to generating a policy, libxc will clip
> itself at the hardcoded maxima, meaning that no data outside of the hardcoded
> maxima are provided to Xen (in turn, causing Xen to return zeros if these
> leaves are requested.)
> 
> The HVM code also clips the max_leaf data reported to the guest, but the PV
> side didn't.
> 
> This results in a PV guest using the emulated CPUID, or via Xen using CPUID
> faulting, to observe a max_leaf higher than the toolstack wants, although with
> zeros being returned in the intervening leaves.
> 
> Fix the PV side to behave like the HVM side, and clip the max_leaf values in
> leaf 0 and 0x80000000.
> 
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>

Acked-by: Wei Liu <wei.liu2@citrix.com>

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

      parent reply	other threads:[~2017-01-11 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 12:44 [PATCH] tools/libxc: Fix the reported max_leaf values for PV guests Andrew Cooper
2017-01-11 13:41 ` Jan Beulich
2017-01-11 14:32 ` Wei Liu [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=20170111143247.GN1100@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.