From: Julien Grall <julien.grall@linaro.org>
To: Arianna Avanzini <avanzini.arianna@gmail.com>, xen-devel@lists.xen.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,
Ian.Campbell@eu.citrix.com, etrudeau@broadcom.com,
JBeulich@suse.com, viktor.kleinik@globallogic.com
Subject: Re: [PATCH v3 1/5] arch, arm: domain build: allow access to I/O memory of mapped devices
Date: Sat, 15 Mar 2014 21:30:04 +0000 [thread overview]
Message-ID: <5324C65C.6040201@linaro.org> (raw)
In-Reply-To: <1394914286-29713-2-git-send-email-avanzini.arianna@gmail.com>
Hello Arianna,
Thanks for the patch.
On 15/03/14 20:11, Arianna Avanzini wrote:
> Currently, a domain is allowed access to the I/O memory ranges
> used to access devices exposed to it, but doesn't have those
> ranges in its iomem_caps. This commit attempts to implement the
> correct bookkeeping, adding the ranges to the domain's iomem_caps.
Sorry to ask you another change in the commit message. You remove every
reference to dom0. Is it normal? IHMO, even if the function is generic,
for now this patch is dom0 related for now.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-03-15 21:30 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 [this message]
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
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=5324C65C.6040201@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=avanzini.arianna@gmail.com \
--cc=dario.faggioli@citrix.com \
--cc=etrudeau@broadcom.com \
--cc=julien.grall@citrix.com \
--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).