From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xen.org, Ian.Campbell@citrix.com,
ian.jackson@eu.citrix.com, stefano.stabellini@eu.citrix.com,
wei.liu2@citrix.com, andrew.cooper3@citrix.com
Cc: Juergen Gross <jgross@suse.com>
Subject: [PATCH v4 4/4] libxc: set flag for support of linear p2m list in domain builder
Date: Thu, 7 Jan 2016 13:36:54 +0100 [thread overview]
Message-ID: <1452170214-17821-5-git-send-email-jgross@suse.com> (raw)
In-Reply-To: <1452170214-17821-1-git-send-email-jgross@suse.com>
Set the SIF_VIRT_P2M_4TOOLS flag for pv-domUs in the domain builder
to indicate the Xen tools have full support for the virtual mapped
linear p2m list.
This will enable pv-domUs to drop support of the 3 level p2m tree
and use the linear list only. Without setting this flag some kernels
might limit themselves to 512 GB memory size in order not to break
migration.
Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
---
docs/features/migration.pandoc | 7 ++++---
tools/libxc/xc_dom_compat_linux.c | 2 +-
tools/libxc/xc_dom_core.c | 2 ++
3 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/docs/features/migration.pandoc b/docs/features/migration.pandoc
index 9852a19..151c50d 100644
--- a/docs/features/migration.pandoc
+++ b/docs/features/migration.pandoc
@@ -1,5 +1,5 @@
% Migration
-% Revision 1
+% Revision 2
\clearpage
@@ -95,7 +95,6 @@ scenarios, which will involve starting with VMs from Xen 4.5
# Areas for improvement
* Arm support
-* Linear P2M support for x86 PV
* Live looping parameters
# Known issues
@@ -105,7 +104,8 @@ scenarios, which will involve starting with VMs from Xen 4.5
* x86 HVM with nested-virt (no relevant information included in the
stream)
* x86 PV ballooning (P2M marked dirty, target frame not marked)
-* x86 PV P2M structure changes (not noticed, stale mappings used)
+* x86 PV P2M structure changes (not noticed, stale mappings used) for
+ guests not using the linear p2m layout
# References
@@ -120,4 +120,5 @@ for Migration v2
Date Revision Version Notes
---------- -------- -------- -------------------------------------------
2015-10-24 1 Xen 4.6 Document written
+2015-12-11 2 Xen 4.7 Support of linear p2m list
---------- -------- -------- -------------------------------------------
diff --git a/tools/libxc/xc_dom_compat_linux.c b/tools/libxc/xc_dom_compat_linux.c
index abbc09f..c922c61 100644
--- a/tools/libxc/xc_dom_compat_linux.c
+++ b/tools/libxc/xc_dom_compat_linux.c
@@ -59,7 +59,7 @@ int xc_linux_build(xc_interface *xch, uint32_t domid,
((rc = xc_dom_ramdisk_file(dom, initrd_name)) != 0) )
goto out;
- dom->flags = flags;
+ dom->flags |= flags;
dom->console_evtchn = console_evtchn;
dom->xenstore_evtchn = store_evtchn;
diff --git a/tools/libxc/xc_dom_core.c b/tools/libxc/xc_dom_core.c
index 2061ba6..55c779d 100644
--- a/tools/libxc/xc_dom_core.c
+++ b/tools/libxc/xc_dom_core.c
@@ -777,6 +777,8 @@ struct xc_dom_image *xc_dom_allocate(xc_interface *xch,
dom->parms.elf_paddr_offset = UNSET_ADDR;
dom->parms.p2m_base = UNSET_ADDR;
+ dom->flags = SIF_VIRT_P2M_4TOOLS;
+
dom->alloc_malloc += sizeof(*dom);
return dom;
--
2.6.2
next prev parent reply other threads:[~2016-01-07 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 12:36 [PATCH v4 0/4] support linear p2m list in migrate stream v2 Juergen Gross
2016-01-07 12:36 ` [PATCH v4 1/4] libxc: split mapping p2m leaves into a separate function Juergen Gross
2016-01-07 12:36 ` [PATCH v4 2/4] libxc: support of linear p2m list for migration of pv-domains Juergen Gross
2016-01-07 12:36 ` [PATCH v4 3/4] libxc: stop migration in case of p2m list structural changes Juergen Gross
2016-01-07 12:36 ` Juergen Gross [this message]
2016-01-07 13:23 ` [PATCH v4 0/4] support linear p2m list in migrate stream v2 Ian Campbell
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=1452170214-17821-5-git-send-email-jgross@suse.com \
--to=jgross@suse.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.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.