From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Paul Durrant <Paul.Durrant@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Keir (Xen.org)" <keir@xen.org>
Subject: Re: [PATCH v3 3/3] x86/hvm: Use white-lists for HVM param guest accessibility checks
Date: Tue, 5 May 2015 15:43:44 +0100 [thread overview]
Message-ID: <5548D720.5000809@citrix.com> (raw)
In-Reply-To: <5548EFDD0200007800076C2F@mail.emea.novell.com>
On 05/05/15 15:29, Jan Beulich wrote:
>>>> On 05.05.15 at 16:09, <Paul.Durrant@citrix.com> wrote:
>>> From: Andrew Cooper [mailto:andrew.cooper3@citrix.com]
>>> Sent: 05 May 2015 11:54
>>> On 05/05/15 11:25, Paul Durrant wrote:
>>>> @@ -5657,21 +5664,11 @@ static int hvm_allow_set_param(struct domain
>>> *d,
>>>> case HVM_PARAM_IDENT_PT:
>>>> case HVM_PARAM_DM_DOMAIN:
>>>> case HVM_PARAM_ACPI_S_STATE:
>>> I think you can safely elide the above cases into default. All that
>>> matters in this case is that none of the whitelisted parameters need to
>>> pause the domain.
>>>
>> I think you and Jan differ there, unless I misunderstood Jan.
> Right, I specifically asked for these to be retained. It's just that
> the comment preceding them is not visible from the patch
> context, so that purpose isn't obvious here.
I would question its usefulness as documentation, given that its
position in the code is now removed from the actual implementation.
However, I am not sufficiently fussed to block an otherwise-good change.
~Andrew
next prev parent reply other threads:[~2015-05-05 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 10:25 [PATCH v3 0/3] x86/hvm: HVMOP_get/set_param improvements Paul Durrant
2015-05-05 10:25 ` [PATCH v3 1/3] x86/hvm: give HVMOP_set_param and HVMOP_get_param their own functions Paul Durrant
2015-05-05 10:25 ` [PATCH v3 2/3] x86/hvm: introduce functions for HVMOP_get/set_param allowance checks Paul Durrant
2015-05-05 10:34 ` Andrew Cooper
2015-05-05 10:25 ` [PATCH v3 3/3] x86/hvm: Use white-lists for HVM param guest accessibility checks Paul Durrant
2015-05-05 10:53 ` Andrew Cooper
2015-05-05 14:09 ` Paul Durrant
2015-05-05 14:29 ` Jan Beulich
2015-05-05 14:43 ` Andrew Cooper [this message]
2015-05-05 15:15 ` Jan Beulich
2015-05-05 14:39 ` Andrew Cooper
2015-05-07 9:46 ` Tim Deegan
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=5548D720.5000809@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xenproject.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.