xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: Ian Jackson <Ian.Jackson@citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@citrix.com>,
	"Keir (Xen.org)" <keir@xen.org>, Jan Beulich <jbeulich@suse.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v5 1/3] x86/viridian: Re-purpose the HVM parameter to be a feature mask
Date: Tue, 26 Aug 2014 21:24:00 +0100	[thread overview]
Message-ID: <1409084640.28009.31.camel@citrix.com> (raw)
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD042591F@AMSPEX01CL01.citrite.net>

On Wed, 2014-08-13 at 12:09 +0100, Paul Durrant wrote:
> > -----Original Message-----
> > From: Ian Jackson [mailto:Ian.Jackson@eu.citrix.com]
> > Sent: 12 August 2014 16:26
> > To: Paul Durrant
> > Cc: xen-devel@lists.xen.org; Keir (Xen.org); Jan Beulich; Ian Campbell;
> > Stefano Stabellini
> > Subject: Re: [PATCH v5 1/3] x86/viridian: Re-purpose the HVM parameter to
> > be a feature mask
> > 
> > Paul Durrant writes ("[PATCH v5 1/3] x86/viridian: Re-purpose the HVM
> > parameter to be a feature mask"):
> > > The viridian option in xl.cfg(5) has also been changed to a string list so
> > > that the sets can be individually sepcified. For compatibility, if the
> > > option is specified as a boolean, then a true (1) value will be translated
> > > to a string list containing "base" and "freq".
> > 
> > This is correct, I think.  But the libxl API should be in numbers, not
> > a string list.  Text to string conversion should be done in xl, not
> > libxl.
> > 
> > I think that these flag values ought to be represented in the IDL, so
> > that text-to-string conversion can be done automatically.
> > 
> > I looked at the existing IDL definitions and there don't seem to be
> > any flags of this kind.  So I think this will involve a inventing new
> > kind of IDL type.  It might be possible to adapt Enumeration.  It
> > might be enough simply to provide a way to make an Enumeration whose
> > corresponding typedef is to a uint32_t.
> > 
> > Does this make any kind of sense ?
> > 
> 
> Yes, it does. I guess what we really want is an 'enumeration list'
> then - i.e. strings get translated via enumeration and then
> concatenated into a list.  Is there any precedent for such a thing?

For singleton enums there is, but not for lists of such things. I don't
think.

But isn't what you actually want here a struct viridian-ish thing
containing a bunch of (def)bools, one per fearture? That would seem like
a more natural interface for a libxl app (a list of VIRIDIAN_FEATURE_X,
VIRIDIAN_FEATURE_Y doesn't seem quite right to me).

Ian.

  reply	other threads:[~2014-08-26 20:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 13:07 [PATCH v5 0/3] x86/viridian improvements Paul Durrant
2014-08-05 13:07 ` [PATCH v5 1/3] x86/viridian: Re-purpose the HVM parameter to be a feature mask Paul Durrant
2014-08-12 15:25   ` Ian Jackson
2014-08-13 11:09     ` Paul Durrant
2014-08-26 20:24       ` Ian Campbell [this message]
2014-08-26 20:28   ` Ian Campbell
2014-08-27  8:11     ` Paul Durrant
2014-08-05 13:07 ` [PATCH v5 2/3] x86/viridian: Make logging less verbose Paul Durrant
2014-08-05 13:07 ` [PATCH v5 3/3] x86/viridian: Add partition time reference counter MSR support Paul Durrant
2014-08-12 15:27   ` Ian Jackson
2014-08-13 15:27   ` Egger, Christoph
2014-08-27 14:04     ` Paul Durrant
2014-08-12 10:16 ` [PATCH v5 0/3] x86/viridian improvements Paul Durrant
2014-08-12 10:38   ` Jan Beulich
2014-08-12 11:49     ` Paul Durrant
2014-08-12 12:17       ` Jan Beulich

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=1409084640.28009.31.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@citrix.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=Stefano.Stabellini@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --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).