xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH for-4.7] docs: Feature Levelling feature document
Date: Wed, 1 Jun 2016 14:11:49 +0100	[thread overview]
Message-ID: <574EDF15.9030908@citrix.com> (raw)
In-Reply-To: <22350.53670.593405.700877@mariner.uk.xensource.com>

On 01/06/16 13:14, Ian Jackson wrote:
> Andrew Cooper writes ("Re: [PATCH for-4.7] docs: Feature Levelling feature document"):
>> On 01/06/16 11:25, Ian Jackson wrote:
>>> I would prefer a wording which was more encouraging to future
>>> improvements.  Shall I suggest something ?
>> I guess there are two different issues here.  (Note: I am specifically
>> distinguishing `xl` as a toolstack itself, from libxl which is a just a
>> library.)
>>
>> Simply exposing the levelling/featureset information in `xl info` is
>> certainly a possible thing to do.  Joao has some plans for surfacing the
>> levelling information in libxl for libvirt to use.
> Right.
>
>> However, without a fundamental redesign of how xl works, it isn't going
>> to gain multi-host knowledge and consideration during domain creation.
> IMO xl ought to have the moving parts necessary to allow an
> administrator to: 1. collect feature information from their hosts;
> 2. combine that information into the desired feature set to expose to
> guests; 3. specify the feature set in their host configuration; 4. do
> all of the above conveniently, without seddery.
>
> We should assume that the administrator has available tools like
> GNU parallel, ansible, or whatever.
>
> I don't want to design this now but I do want the feature levelling
> documentation to welcome suggestions for it, or at least not to seem
> to rule it out.

1) is currently available via the `xen-cpuid` binary introduced,
although I intended it more as a developer tool

Combining is the awkward part, but in the common case, it is just a
bitwise AND of the bitmaps provided by `xen-cpuid`.

3) I don't know what you mean about their host configuration.  Do you
mean guest configuration?

All of this works in combination with the existing cpuid= guest
configuration.

~Andrew

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

  reply	other threads:[~2016-06-01 13:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31 17:05 [PATCH for-4.7] docs: Feature Levelling feature document Andrew Cooper
2016-06-01  9:29 ` Jan Beulich
2016-06-03 15:36   ` Andrew Cooper
2016-06-03 15:42     ` Jan Beulich
2016-06-03 15:53       ` Andrew Cooper
2016-06-01  9:41 ` Wei Liu
2016-06-01 10:25 ` Ian Jackson
2016-06-01 12:05   ` Andrew Cooper
2016-06-01 12:14     ` Ian Jackson
2016-06-01 13:11       ` Andrew Cooper [this message]
2016-06-03 14:59         ` [PATCH v2 " Ian Jackson
2016-06-03 15:35           ` Andrew Cooper

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=574EDF15.9030908@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=wei.liu2@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).