From: David Vrabel <david.vrabel@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>, xen-devel@lists.xen.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Keir Fraser <keir@xen.org>,
Ian Campbell <ian.campbell@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v4 1/3] x86/viridian: Re-purpose the HVM parameter to be a feature mask
Date: Tue, 5 Aug 2014 11:16:10 +0100 [thread overview]
Message-ID: <53E0AEEA.4020508@citrix.com> (raw)
In-Reply-To: <1407231886-5031-2-git-send-email-paul.durrant@citrix.com>
On 05/08/14 10:44, Paul Durrant wrote:
>
> This patch grandfathers in the current viridian features set and calls them
> the 'base' plus 'freq' feature set. HVM_PARAM_VIRIDIAN is re-purposed as
> a feature mask. It has only ever been legally set to 0 or 1...
"legally" suggests (to me) that this restriction written as part of a
specification rather than enforced in the code, which would make it
unsafe to repurpose the param as you propose.
But, from the actual code:
case HVM_PARAM_VIRIDIAN:
if ( a.value > 1 )
rc = -EINVAL;
break;
So: "Xen only allowed HVM_PARAM_VIRIDIAN to be set to 0 or 1, setting
other values would fail with -EINVAL." makes it clear that it is okay to
extend this param.
David
next prev parent reply other threads:[~2014-08-05 10:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 9:44 [PATCH v4 0/3] x86/viridian improvements Paul Durrant
2014-08-05 9:44 ` [PATCH v4 1/3] x86/viridian: Re-purpose the HVM parameter to be a feature mask Paul Durrant
2014-08-05 10:16 ` David Vrabel [this message]
2014-08-05 10:33 ` Paul Durrant
2014-08-05 9:44 ` [PATCH v4 2/3] x86/viridian: Make logging less verbose Paul Durrant
2014-08-05 9:53 ` Andrew Cooper
2014-08-05 10:30 ` Paul Durrant
2014-08-05 9:44 ` [PATCH v4 3/3] x86/viridian: Add partition time reference counter MSR support Paul Durrant
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=53E0AEEA.4020508@citrix.com \
--to=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=paul.durrant@citrix.com \
--cc=stefano.stabellini@eu.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.