From: Julien Grall <julien.grall@linaro.org>
To: Arianna Avanzini <avanzini.arianna@gmail.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Cc: paolo.valente@unimore.it, stefano.stabellini@eu.citrix.com,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel@lists.xen.org, julien.grall@citrix.com,
etrudeau@broadcom.com, viktor.kleinik@globallogic.com
Subject: Re: [RFC PATCH 3/3] tools, libxl: handle the iomem parameter with the memory_mapping hcall
Date: Fri, 07 Mar 2014 12:03:30 +0800 [thread overview]
Message-ID: <53194512.9060804@linaro.org> (raw)
In-Reply-To: <53191695.4050301@gmail.com>
Hello Arianna,
On 07/03/14 08:45, Arianna Avanzini wrote:
>>
>> I think Arianna solution's might not work if the 1:1 mapping clash with existing
>> layout. I might help Arianna on this subject because it will be useful to
>> passthrough a device to the guest.
>>
>
> Sorry for the delay and for bothering you with another question. In order to
> ensure that the 1:1 mapping of a new range of I/O memory does not clash with the
> existing layout, we should then check that nothing else has been mapped to that
> address range in the domU's address space?
I think checking is not the right solution, what will you do if the
range is effectively clash to another one?
On a previous mail (see
http://lists.xenproject.org/archives/html/xen-devel/2014-03/msg00036.html),
Ian has proposed to exposed the layout of the host to the guest. That
will allow you to map the memory in 1:1.
I will need this item for device passthrough soon. I can take care of
this item if you want.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-03-07 4:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 0:49 [RFC PATCH 0/3] Implement the XEN_DOMCTL_memory_mapping hypecall for arm32 Arianna Avanzini
2014-03-02 0:49 ` [RFC PATCH 1/3] arch, arm32: add definition of paddr_bits Arianna Avanzini
2014-03-02 8:13 ` Julien Grall
2014-03-07 0:36 ` Arianna Avanzini
2014-03-02 0:49 ` [RFC PATCH 2/3] arch, arm32: add the XEN_DOMCTL_memory_mapping hypercall Arianna Avanzini
2014-03-02 9:56 ` Julien Grall
2014-03-03 11:56 ` Dario Faggioli
2014-03-03 15:20 ` Julien Grall
2014-03-03 15:33 ` Dario Faggioli
2014-03-04 2:42 ` Julien Grall
2014-03-07 0:47 ` Arianna Avanzini
2014-03-03 16:25 ` Eric Trudeau
2014-03-03 16:35 ` Dario Faggioli
2014-03-03 19:04 ` Eric Trudeau
2014-03-05 13:59 ` Arianna Avanzini
2014-03-06 3:41 ` Julien Grall
2014-03-07 0:57 ` Arianna Avanzini
2014-03-03 18:06 ` Eric Trudeau
2014-03-04 3:08 ` Julien Grall
2014-03-07 0:56 ` Arianna Avanzini
2014-03-07 3:41 ` Julien Grall
2014-03-07 19:49 ` Arianna Avanzini
2014-03-02 0:49 ` [RFC PATCH 3/3] tools, libxl: handle the iomem parameter with the memory_mapping hcall Arianna Avanzini
2014-03-02 10:33 ` Julien Grall
2014-03-02 11:27 ` Ian Campbell
2014-03-03 10:32 ` Dario Faggioli
2014-03-03 15:13 ` Julien Grall
2014-03-07 0:45 ` Arianna Avanzini
2014-03-07 4:03 ` Julien Grall [this message]
2014-03-07 19:54 ` Arianna Avanzini
2014-03-03 11:19 ` Dario Faggioli
2014-03-07 4:05 ` Julien Grall
2014-03-02 8:13 ` [RFC PATCH 0/3] Implement the XEN_DOMCTL_memory_mapping hypecall for arm32 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=53194512.9060804@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Jackson@eu.citrix.com \
--cc=avanzini.arianna@gmail.com \
--cc=dario.faggioli@citrix.com \
--cc=etrudeau@broadcom.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=paolo.valente@unimore.it \
--cc=stefano.stabellini@eu.citrix.com \
--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 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.