From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: xen-devel@lists.xen.org
Cc: edgar.iglesias@xilinx.com, julien.grall@arm.com, sstabellini@kernel.org
Subject: [RFC for-4.8 0/6] xen/arm: Add support for mapping mmio-sram nodes into dom0
Date: Fri, 20 May 2016 17:51:22 +0200 [thread overview]
Message-ID: <1463759488-11900-1-git-send-email-edgar.iglesias@gmail.com> (raw)
From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
This series adds support for mapping mmio-sram nodes into dom0
as MEMORY, cached and with RWX perms.
Dom0 can then choose to further restrict these mappings if needed.
We only look at the outer mmio-sram region. The sub-area nodes that
describe allocations within the mmio-sram region are only meaningful
to the guest AFAICT.
In an attempt to avoid growing the already fairly large domain_build.c
file, I've tried to implement a distributed way to deal with these kind
of special/custom mapping needs. These can live outside of domain_build.c
and are registerd by means of a .map method in the device_spec.
If this approach is not good, I'm happy to bin it and try something else.
Comments welcome!
Best regards,
Edgar
Edgar E. Iglesias (6):
xen/arm: Add device_get_desc()
xen/arm: Add an optional map function to the device descriptor
xen/arm: Add a DEVICE_MEMORY class
xen/arm: Add helper functions to map RWX memory regions
xen/arm: Add an mmio-sram device
xen/arm: Avoid multiple dev class lookups in handle_node
xen/arch/arm/Makefile | 1 +
xen/arch/arm/device.c | 15 ++++++++
xen/arch/arm/domain_build.c | 19 +++++++--
xen/arch/arm/mmio-sram.c | 92 ++++++++++++++++++++++++++++++++++++++++++++
xen/arch/arm/p2m.c | 26 +++++++++++++
xen/include/asm-arm/device.h | 12 ++++++
xen/include/asm-arm/p2m.h | 10 +++++
7 files changed, 172 insertions(+), 3 deletions(-)
create mode 100644 xen/arch/arm/mmio-sram.c
--
2.5.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-05-20 15:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 15:51 Edgar E. Iglesias [this message]
2016-05-20 15:51 ` [RFC for-4.8 1/6] xen/arm: Add device_get_desc() Edgar E. Iglesias
2016-05-20 15:51 ` [RFC for-4.8 2/6] xen/arm: Add an optional map function to the device descriptor Edgar E. Iglesias
2016-05-20 15:51 ` [RFC for-4.8 3/6] xen/arm: Add a DEVICE_MEMORY class Edgar E. Iglesias
2016-05-20 15:51 ` [RFC for-4.8 4/6] xen/arm: Add helper functions to map RWX memory regions Edgar E. Iglesias
2016-05-23 15:36 ` Julien Grall
2016-05-24 14:14 ` Edgar E. Iglesias
2016-05-20 15:51 ` [RFC for-4.8 5/6] xen/arm: Add an mmio-sram device Edgar E. Iglesias
2016-05-20 15:51 ` [RFC for-4.8 6/6] xen/arm: Avoid multiple dev class lookups in handle_node Edgar E. Iglesias
2016-05-23 10:29 ` [RFC for-4.8 0/6] xen/arm: Add support for mapping mmio-sram nodes into dom0 Julien Grall
2016-05-23 11:56 ` Edgar E. Iglesias
2016-05-23 13:02 ` Julien Grall
2016-05-23 14:02 ` Edgar E. Iglesias
2016-05-23 15:13 ` Julien Grall
2016-05-23 15:42 ` Edgar E. Iglesias
2016-05-24 19:44 ` Julien Grall
2016-05-25 9:43 ` Stefano Stabellini
2016-05-25 9:52 ` Julien Grall
2016-05-25 10:00 ` Stefano Stabellini
2016-05-25 10:35 ` Edgar E. Iglesias
2016-05-25 13:29 ` Edgar E. Iglesias
2016-05-25 14:24 ` Julien Grall
2016-06-03 13:10 ` Edgar E. Iglesias
2016-05-25 9:31 ` 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=1463759488-11900-1-git-send-email-edgar.iglesias@gmail.com \
--to=edgar.iglesias@gmail.com \
--cc=edgar.iglesias@xilinx.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--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).