From: Arianna Avanzini <avanzini.arianna@gmail.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: julien.grall@citrix.com, paolo.valente@unimore.it, keir@xen.org,
stefano.stabellini@eu.citrix.com, tim@xen.org,
dario.faggioli@citrix.com, Ian.Jackson@eu.citrix.com,
xen-devel@lists.xen.org, Ian.Campbell@eu.citrix.com,
etrudeau@broadcom.com, JBeulich@suse.com,
viktor.kleinik@globallogic.com
Subject: Re: [PATCH v3 5/5] tools, libxl: handle the iomem parameter with the memory_mapping hcall
Date: Tue, 18 Mar 2014 17:15:50 +0100 [thread overview]
Message-ID: <53287136.70502@gmail.com> (raw)
In-Reply-To: <5326EBF9.3060004@linaro.org>
On 03/17/2014 01:35 PM, Julien Grall wrote:
> Hello Arianna,
>
> (Adding Mukesh for PVH)
>
> Thanks for the patch.
>
Thank you for your feedback.
> On 03/15/2014 08:11 PM, Arianna Avanzini wrote:
>> diff --git a/tools/libxl/libxl_create.c b/tools/libxl/libxl_create.c
>> index d015cf4..dda4df3 100644
>> --- a/tools/libxl/libxl_create.c
>> +++ b/tools/libxl/libxl_create.c
>> @@ -1107,7 +1107,24 @@ static void domcreate_launch_dm(libxl__egc *egc, libxl__multidev *multidev,
>> "failed give dom%d access to iomem range %"PRIx64"-%"PRIx64,
>> domid, io->start, io->start + io->number - 1);
>> ret = ERROR_FAIL;
>> + continue;
>> }
>> +#if defined(__x86_32__) || defined(__x86_64__)
>> + if (b_info->type != LIBXL_DOMAIN_TYPE_HVM)
>
> Calling xc_domain_memory_memory_mapping might be also useful for PVH.
> AFAIK, on x86 PVH is consider as LIBXL_DOMAIN_TYPE_PV.
>
> The best solution is to check if the domain use auto-translated physmap
> (e.g translation between PFN and MFN is done by Xen). But, after talking
> with Ian C. it's not possible to know it on libxl.
>
> You might need to introduce an architecture helper (libxl_arm.c and
> libxl_x86.c are respectively only compiled on ARM and x86), which check
> if you can call xc_domain_memory_mapping or not.
>
Sorry if I bother you with a question to see if I understood correctly, the
helper should determine whether the guest domain is auto-translated, right?
>> + continue;
>> +#endif /* __x86_32__ || __x86_64__ */
>> +#if defined(__arm__) || defined(__x86_32__) || defined(__x86_64__)
>
> You don't need to ifdef this part. Libxl doesn't support other arch for now.
>
I think it was Jan Beulich who suggested using a whitelist approach here during
the review of the v2 patchset. Is it / is he OK to drop this by now?
> Regards,
>
--
/*
* Arianna Avanzini
* avanzini.arianna@gmail.com
* 73628@studenti.unimore.it
*/
next prev parent reply other threads:[~2014-03-18 16:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 20:11 [PATCH v3 0/5] Implement the XEN_DOMCTL_memory_mapping hypercall for ARM Arianna Avanzini
2014-03-15 20:11 ` [PATCH v3 1/5] arch, arm: domain build: allow access to I/O memory of mapped devices Arianna Avanzini
2014-03-15 21:30 ` Julien Grall
2014-03-15 20:11 ` [PATCH v3 2/5] arch, arm: add consistency checks to REMOVE p2m changes Arianna Avanzini
2014-03-15 22:19 ` Julien Grall
2014-03-15 22:36 ` Arianna Avanzini
2014-03-15 22:42 ` Julien Grall
2014-03-21 10:44 ` Ian Campbell
2014-03-21 11:51 ` Julien Grall
2014-03-21 11:54 ` Ian Campbell
2014-03-21 12:08 ` Julien Grall
2014-03-21 12:32 ` Ian Campbell
2014-03-21 12:45 ` Julien Grall
2014-03-21 14:09 ` Ian Campbell
2014-03-21 14:11 ` Julien Grall
2014-03-15 20:11 ` [PATCH v3 3/5] xen, common: add the XEN_DOMCTL_memory_mapping hypercall Arianna Avanzini
2014-03-15 22:32 ` Julien Grall
2014-03-17 8:01 ` Jan Beulich
2014-03-15 20:11 ` [PATCH v3 4/5] tools, libxl: parse optional start gfn from the iomem config option Arianna Avanzini
2014-03-15 22:35 ` Julien Grall
2014-03-17 10:01 ` Dario Faggioli
2014-03-21 10:47 ` Ian Campbell
2014-03-17 12:24 ` Julien Grall
2014-03-21 10:54 ` Ian Campbell
2014-03-15 20:11 ` [PATCH v3 5/5] tools, libxl: handle the iomem parameter with the memory_mapping hcall Arianna Avanzini
2014-03-17 12:35 ` Julien Grall
2014-03-18 16:15 ` Arianna Avanzini [this message]
2014-03-18 21:01 ` 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=53287136.70502@gmail.com \
--to=avanzini.arianna@gmail.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=dario.faggioli@citrix.com \
--cc=etrudeau@broadcom.com \
--cc=julien.grall@citrix.com \
--cc=julien.grall@linaro.org \
--cc=keir@xen.org \
--cc=paolo.valente@unimore.it \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=viktor.kleinik@globallogic.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 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).