xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: keir@xen.org, JBeulich@suse.com,
	stefano.stabellini@eu.citrix.com, ian.jackson@eu.citrix.com,
	eddie.dong@intel.com, xen-devel@lists.xen.org,
	jun.nakajima@intel.com, andrew.cooper3@citrix.com,
	yang.z.zhang@intel.com
Subject: Re: [PATCH v7 1/3] xen/libxc: Allow changing max number of hypervisor cpuid leaves
Date: Thu, 27 Mar 2014 10:04:29 -0400	[thread overview]
Message-ID: <53342FED.1070208@oracle.com> (raw)
In-Reply-To: <1395926006.22909.128.camel@kazak.uk.xensource.com>

On 03/27/2014 09:13 AM, Ian Campbell wrote:
> On Mon, 2014-03-24 at 19:18 -0400, Boris Ostrovsky wrote:
>> Add support for changing max number of hypervisor leaves from configuration
>> file.
>>
>> This number can be specified using xl's standard 'cpuid' option. Only lowest
>> 8 bits of leaf's 0x4000xx00 eax register are processed, all others are ignored.
> This sounds like it would need a docs update to go along with it, both
> to address this specific constraint and perhaps to give an example of
> the syntax (unless it is already obvious?).

This could to xl.cfg.5[.txt|.html], something in the cpuid option 
description. E.g.

   Note: when specifying CPUID for hypervisor leaves (0x4000xxxx major
   group) only the lowest 8 bits of leaf's 0x4000xx00 EAX register that 
signify
   maximum number of hypervisor leaves are processed, the rest are ignored.

As for example, this uses the same syntax as all other leaves so I am 
not sure
anything more is needed.


> Speaking of obvious syntaxes, does the list in libxl_cpuid_parse_config
> want updating so people can use maxhvleaf=2 instead of whatever the more
> obscure syntax would be?

Yes, I should add this.

Thanks.
-boris

  reply	other threads:[~2014-03-27 14:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24 23:18 [PATCH v7 0/3] Expose HW APIC virtualization support to HVM guests Boris Ostrovsky
2014-03-24 23:18 ` [PATCH v7 1/3] xen/libxc: Allow changing max number of hypervisor cpuid leaves Boris Ostrovsky
2014-03-25  9:42   ` Jan Beulich
2014-03-27 13:13   ` Ian Campbell
2014-03-27 14:04     ` Boris Ostrovsky [this message]
2014-03-27 14:46       ` Ian Campbell
2014-03-24 23:18 ` [PATCH v7 2/3] x86/hvm: Add HVM-specific hypervisor CPUID leaf Boris Ostrovsky
2014-03-25  9:43   ` Jan Beulich
2014-03-24 23:18 ` [PATCH v7 3/3] x86/hvm: Indicate avaliability of HW support of APIC virtualization to HVM guests Boris Ostrovsky
2014-03-25  9:45   ` Jan Beulich
2014-03-25 13:34     ` Boris Ostrovsky
2014-03-26  1:03       ` Zhang, Yang Z
2014-04-01 15:39         ` Boris Ostrovsky
2014-04-02  1:24           ` Zhang, Yang Z

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=53342FED.1070208@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yang.z.zhang@intel.com \
    /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).