xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>,
	tim@xen.org, stefano.stabellini@citrix.com,
	Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xenproject.org,
	Daniel De Graaf <dgdegra@tycho.nsa.gov>
Subject: Re: [PATCH v2 for 4.5] xen/arm: Add support for GICv3 for domU
Date: Wed, 5 Nov 2014 11:22:55 +0000	[thread overview]
Message-ID: <1415186575.15317.9.camel@citrix.com> (raw)
In-Reply-To: <545A058F.5040603@linaro.org>

On Wed, 2014-11-05 at 11:10 +0000, Julien Grall wrote:
> Hi Ian,
> 
> On 05/11/2014 10:24, Ian Campbell wrote:
> >> @@ -30,6 +32,39 @@ long arch_do_domctl(struct xen_domctl *domctl, struct domain *d,
> >>
> >>           return p2m_cache_flush(d, s, e);
> >>       }
> >> +    case XEN_DOMCTL_arm_configure_domain:
> >> +    {
> >> +        uint8_t gic_version;
> >> +
> >> +        /*
> >> +         * Xen 4.5: The vGIC is emulating the same version of the
> >
> > No need to say "Xen 4.5" here, this comment is true until it is removed.
> > You could say "Currently the vGIC is..." or something if you wanted to
> > indicate that this is temporary.
> 
> Just saying temporary doesn't say anything about when this has been 
> added and will be removed.
> 
> "Xen 4.5" gives explicitly the time and show that we want to remove soon.

Neither of which things belong in the code comment IMHO. Either this
happens soon so it is moot, or it doesn't and we have a strange
misleading comment...

> >
> >> +         * hardware GIC. Only the value XEN_DOMCTL_CONFIG_GIC_DEFAULT
> >> +         * is allowed. The DOMCTL will return the actual version of the
> >> +         * GIC.
> >> +         */
> >> +        if ( domctl->u.configuredomain.gic_version != XEN_DOMCTL_CONFIG_GIC_DEFAULT )
> >> +            return -EOPNOTSUPP;
> 
> > I'm also tempted to suggest that we should accept gic_version == the hw
> > value, i.e. by moping the switch below up and including
> >          && domctl->u.configuredomain.gic_version != gic_version
> > in the condition.
> 
> I consider that explicitly asking for a version of the GIC in Xen 4.5 is 
> invalid. The user should only be able to use the default GIC.
> 
> As the DOMCTL is not set in stone, 

I disagree with your reasoning, but given this I'm not inclined to keep
arguing about it.

Ian.

  reply	other threads:[~2014-11-05 11:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-01 20:10 [PATCH v2 for 4.5] xen/arm: Add support for GICv3 for domU Julien Grall
2014-11-03 11:01 ` Stefano Stabellini
2014-11-03 12:37   ` Vijay Kilari
2014-11-03 16:39     ` Konrad Rzeszutek Wilk
2014-11-04 17:26       ` Julien Grall
2014-11-05 10:25         ` Ian Campbell
2014-11-05 17:15         ` Jan Beulich
2014-11-06  9:45           ` Julien Grall
2014-11-06 10:11             ` Jan Beulich
2014-11-06 10:27               ` Julien Grall
2014-11-07 15:45                 ` Konrad Rzeszutek Wilk
2014-11-08 18:01                   ` Julien Grall
2014-11-08 20:26                     ` Konrad Rzeszutek Wilk
2014-11-10 10:03                       ` Ian Campbell
2014-11-10 11:38                         ` Stefano Stabellini
2014-11-11 16:41                           ` Julien Grall
2014-11-11 16:43                             ` Stefano Stabellini
2014-11-11 17:10                             ` Konrad Rzeszutek Wilk
2014-11-03 22:51 ` Daniel De Graaf
2014-11-05 10:24 ` Ian Campbell
2014-11-05 10:31   ` Stefano Stabellini
2014-11-05 10:56     ` Ian Campbell
2014-11-05 11:02       ` Stefano Stabellini
2014-11-05 11:20         ` Ian Campbell
2014-11-05 11:10   ` Julien Grall
2014-11-05 11:22     ` Ian Campbell [this message]
2014-11-05 11:28       ` Julien Grall

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=1415186575.15317.9.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Vijaya.Kumar@caviumnetworks.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@linaro.org \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --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 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).