From: Julien Grall <julien.grall@linaro.org>
To: Andrii Anisov <andrii.anisov@globallogic.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: arm: How DomU access to iomem is implemented
Date: Mon, 10 Jun 2013 11:38:36 +0100 [thread overview]
Message-ID: <51B5ACAC.9050303@linaro.org> (raw)
In-Reply-To: <CAGQvs6hmbmxEQ0DYrQZXjY2YtCaFVLyJiZ=RjVochj4GznR+Gw@mail.gmail.com>
On 06/08/2013 01:49 PM, Andrii Anisov wrote:
> Hello,
Hello,
> Could you please clarify how DomU gets an access to iomem (for ARMv7VE)?
> We traced that iomem configuration of the DomU comes to hypervisor with
> /XEN_DOMCTL_iomem_permission/ domctl. Here iomem space is added to
> domain's /iomem_caps/ ranges. But we did not found how these ranges are
> actually mapped for DomU. Really these configuration looks unused, on
> our board DomU is killed by hypervisor once it tries to access f.e. real
> UART.
You need to use XEN_DOMCTL_memory_mapping. It will give access and map
region in the guest.
This hypercall is still missing on ARM, so you need to implement it.
> Actually we did a workaround by mapping regions using
> /map_mmio_regions() /right here in /XEN_DOMCTL_iomem_permission/
> handling. But it's a real hack, and it would good to know proper way to
> get stuff working.
Your solution with map_mmio_regions looks good for me.
Cheers,
--
Julien
next prev parent reply other threads:[~2013-06-10 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 12:49 arm: How DomU access to iomem is implemented Andrii Anisov
2013-06-10 10:38 ` Julien Grall [this message]
2013-06-10 10:58 ` Andrii Anisov
2013-06-10 11:13 ` Julien Grall
2013-06-10 16:19 ` Stefano Stabellini
2013-06-14 6:41 ` Andrii Anisov
2013-06-10 16:16 ` Stefano Stabellini
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=51B5ACAC.9050303@linaro.org \
--to=julien.grall@linaro.org \
--cc=andrii.anisov@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.