From: Stefano Stabellini <sstabellini@kernel.org>
To: xen-devel@lists.xenproject.org
Cc: julien.grall@arm.com, sstabellini@kernel.org, Volodymyr_Babchuk@epam.com
Subject: [Xen-devel] [PATCH v7 0/8] reserved-memory in dom0
Date: Mon, 19 Aug 2019 10:43:13 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1908191011060.20094@sstabellini-ThinkPad-T480s> (raw)
Hi all,
This patch series introduces partial reserved-memory support for dom0
only (no domU support for reserved-memory yet.)
The following changes since commit 762b9a2d990bba1f3aefe660cff0c37ad2e375bc:
xen/page_alloc: Keep away MFN 0 from the buddy allocator (2019-08-09 11:12:55 -0700)
are available in the Git repository at:
http://xenbits.xenproject.org/git-http/people/sstabellini/xen-unstable.git reserved-mem-7
for you to fetch changes up to 794790f98d9bba4e34ea689049bf29899c6f1b2b:
xen/arm: add reserved-memory regions to the dom0 memory node (2019-08-19 10:08:56 -0700)
----------------------------------------------------------------
Stefano Stabellini (8):
xen/arm: pass node to device_tree_for_each_node
xen/arm: make process_memory_node a device_tree_node_func
xen/arm: keep track of reserved-memory regions
xen/arm: fix indentation in early_print_info
xen/arm: early_print_info print reserved_mem
xen/arm: handle reserved-memory in consider_modules and dt_unreserved_regions
xen/arm: don't iomem_permit_access for reserved-memory regions
xen/arm: add reserved-memory regions to the dom0 memory node
xen/arch/arm/acpi/boot.c | 8 ++-
xen/arch/arm/bootfdt.c | 128 +++++++++++++++++++++++++++++-------------
xen/arch/arm/domain_build.c | 47 +++++++++++-----
xen/arch/arm/setup.c | 53 ++++++++++++++++-
xen/include/asm-arm/setup.h | 1 +
xen/include/xen/device_tree.h | 6 +-
6 files changed, 181 insertions(+), 62 deletions(-)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-08-19 17:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 17:43 Stefano Stabellini [this message]
2019-08-19 17:43 ` [Xen-devel] [PATCH v7 1/8] xen/arm: pass node to device_tree_for_each_node Stefano Stabellini
2019-08-19 17:56 ` Julien Grall
2019-08-19 17:43 ` [Xen-devel] [PATCH v7 2/8] xen/arm: make process_memory_node a device_tree_node_func Stefano Stabellini
2019-08-19 18:03 ` Julien Grall
2019-08-19 17:43 ` [Xen-devel] [PATCH v7 3/8] xen/arm: keep track of reserved-memory regions Stefano Stabellini
2019-08-19 17:43 ` [Xen-devel] [PATCH v7 4/8] xen/arm: fix indentation in early_print_info Stefano Stabellini
2019-08-19 17:43 ` [Xen-devel] [PATCH v7 5/8] xen/arm: early_print_info print reserved_mem Stefano Stabellini
2019-08-19 17:43 ` [Xen-devel] [PATCH v7 6/8] xen/arm: handle reserved-memory in consider_modules and dt_unreserved_regions Stefano Stabellini
2019-08-19 17:43 ` [Xen-devel] [PATCH v7 7/8] xen/arm: don't iomem_permit_access for reserved-memory regions Stefano Stabellini
2019-08-19 18:38 ` Julien Grall
2019-08-19 17:43 ` [Xen-devel] [PATCH v7 8/8] xen/arm: add reserved-memory regions to the dom0 memory node Stefano Stabellini
2019-08-20 15:28 ` Oleksandr
2019-08-20 17:49 ` 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=alpine.DEB.2.21.1908191011060.20094@sstabellini-ThinkPad-T480s \
--to=sstabellini@kernel.org \
--cc=Volodymyr_Babchuk@epam.com \
--cc=julien.grall@arm.com \
--cc=xen-devel@lists.xenproject.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).