Re: [Xen-users] Grant iomem access and map IRQs to a domU guest in Xen for ARM targets

["Kapania, Ashish" <akapania@xxxxxx>]

> -----Original Message-----
> From: Arianna Avanzini [mailto:avanzini.arianna@xxxxxxxxx]
> Sent: Wednesday, June 11, 2014 4:01 AM
> To: Dario Faggioli; Kapania, Ashish
> Cc: Ian Campbell; xen-users@xxxxxxxxxxxxx
> Subject: Re: [Xen-users] Grant iomem access and map IRQs to a domU
> guest in Xen for ARM targets
> 
> On 06/11/2014 10:29 AM, Dario Faggioli wrote:
> > [Adding Arianna]
> >
> > On mar, 2014-06-10 at 01:37 +0000, Kapania, Ashish wrote:
> >>> From: Ian Campbell [mailto:Ian.Campbell@xxxxxxxxxx]
> >>>
> >>> I'm not sure how people have been triggering these extra mappings.
> I
> >>> suppose you could either do it statically for each domid==N e.g. in
> >>> arch_domain_create (but then you can't easily restart the guests)
> or
> >>> you could add a custom domctl and add a call in the toolstack, or a
> >>> new DOMCRF_ flag (which gets passed to arch_domain_create).
> >>>
> >>
> >> Thanks Ian, this helps. I think I am going to go ahead with your
> >> Suggestion to create a custom domctl op for now and add a call to it
> >> in the xen toolstack. This should allow me to specify the desired
> >> mappings in the domU.cfg file.
> >>
> > What Xen version are we talking about? If that is not a constraint,
> > and you can use a fairly recent one --even better work with the git
> > master branch
> > directly-- I think I'd dare suggesting to give Arianna's (and
> > Julien's) series a look, trying to apply the latest versions of them,
> > and see whether they work for you.
> >
> > At least for Arianna's one (so "iomem="), there should be no need to
> > wait for it to be upstreamed (although, that looks pretty imminent).
> I
> > mean, if you just take the series and apply it, it's already working!
> > Things can change in the implementation, but I think I personally
> > would prefer this approach as, as soon as the patches will be merged,
> > you'll be all set, your RTOS will work with Xen upstream, without the
> > need to change anything, nor in the code neither in the config file.
> I
> > don't know whether or not this is important for your use case,
> though.
> >
> > AFAIUI, Arianna's series also allows you to specify the mapping in
> the
> > config file, via "iomem=", as you seem to need.
> >
> > What RTOS, if I can ask?
> >
> > Arianna, what's the best version of your series you suggest to apply,
> > in order to have something working, and close enough to the final
> > version that will land upstream (at least from the interface point of
> view)?
> >
> 
> I would suggest trying the latest version of the series, that has been
> proposed to the mailing list (that is v8 [1]). The patch adding the
> iomem option to libxl has been already acked by both Ian Campbell and
> Julien Grall, so, at least from that point of view, it should be
> somewhat stable and the interface should not change in the next
> version(s).
> 
> 
> Thank you,
> Arianna
> 
> 
> [1] http://markmail.org/thread/wtevxxizyxjhvmg2
> 

Thanks!

> > Regards, Dario
> >
> 
> 
> --
> /*
>  * Arianna Avanzini
>  * avanzini.arianna@xxxxxxxxx
>  * 73628@xxxxxxxxxxxxxxxxxxx
>  */
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users