From: Julien Grall <julien.grall@linaro.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: wei.liu2@citrix.com, ian.campbell@citrix.com,
vijay.kilari@gmail.com, stefano.stabellini@eu.citrix.com,
tim@xen.org, Vijaya.Kumar@caviumnetworks.com,
ian.jackson@eu.citrix.com, stefano.stabellini@citrix.com,
xen-devel@lists.xenproject.org, dgdegra@tycho.nsa.gov
Subject: Re: [PATCH v2 for 4.5] xen/arm: Add support for GICv3 for domU
Date: Thu, 06 Nov 2014 10:27:41 +0000 [thread overview]
Message-ID: <545B4D1D.4090000@linaro.org> (raw)
In-Reply-To: <545B577D0200007800045407@mail.emea.novell.com>
On 06/11/2014 10:11, Jan Beulich wrote:
>>>> On 06.11.14 at 10:45, <julien.grall@linaro.org> wrote:
>> Hi Jan,
>>
>> On 05/11/2014 17:15, Jan Beulich wrote:
>>>>>> Julien Grall <julien.grall@linaro.org> 11/04/14 6:27 PM >>>
>>>> On 11/03/2014 04:39 PM, Konrad Rzeszutek Wilk wrote:
>>>>> It also needs Acks from Daniel and Jan.
>>>>
>>>> This patch doesn't modify the x86 part. So I'm not sure if Jan ack is
>>>> required. Would Ian C. ack be enough?
>>>
>>> Yes, it would.
>>>
>>>> Anyway, Jan do you have any objection on this patch?
>>>
>>> As said previously, I'm not particularly happy about it, but I also don't
>> strongly
>>> mind it going in in the current shape.
>>
>> May I ask what is wrong with the new approach to the a DOMCTL in this patch?
>>
>> The DOMCTL has been clearly identify as arm specific (there is "arm" in
>> the name). Therefore it doesn't seem necessary to expose it for other
>> architecture than ARM32 and ARM64.
>
> I didn't say there's anything actively wrong with it, all I said is that
> I'm not particularly happy about it: Irrespective of its name it doesn't
> look to be really arch-specific in the long run, plus it feels like the
> data being set here should rather be specified right at domain
> creation, or via a mechanism similar to x86'es HVM parameters (iirc
> the value set here can't be changed once the domain got first
> unpaused).
TBH I choose this solution because I though you would be disagree with
extending the domain create hypercall.
In long run, there will be more parameters such as the number of spis.
All will be required at the same time. So the HVM parameters solution
won't really help here.
However, I could give a look to extending the domain creation hypercall
(xen_domctl_createdomain) to add arch specific field.
But I don't think it's Xen 4.5 material. So I would prefer to stay on
this approach for this release because we'd like to have GICv3 guest
support on Xen. Though I could rename the DOMCTL to DOMCTL_get_gic_version.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-11-06 10:27 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 [this message]
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
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=545B4D1D.4090000@linaro.org \
--to=julien.grall@linaro.org \
--cc=JBeulich@suse.com \
--cc=Vijaya.Kumar@caviumnetworks.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=vijay.kilari@gmail.com \
--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).