From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xensource.com
Subject: [PATCH 6/6] xenpaging: document outstanding features
Date: Sun, 16 Jan 2011 17:32:35 +0100 [thread overview]
Message-ID: <20110116163231.352841527@aepfle.de> (raw)
In-Reply-To: 20110116163229.044047464@aepfle.de
[-- Attachment #1: xen-unstable.xenpaging.doc.patch --]
[-- Type: text/plain, Size: 1828 bytes --]
Signed-off-by: Olaf Hering <olaf@aepfle.de>
---
docs/misc/xenpaging.txt | 22 ++++++++++++++++++++--
1 file changed, 20 insertions(+), 2 deletions(-)
--- xen-unstable.hg-4.1.22764.orig/docs/misc/xenpaging.txt
+++ xen-unstable.hg-4.1.22764/docs/misc/xenpaging.txt
@@ -31,7 +31,7 @@ crash because the paged-out memory is no
After a reboot of a guest, its guest_id changes, the current xenpaging
binary has no target anymore. To automate restarting of xenpaging after
-guest reboot, specify the number if pages in the guest configuration
+guest reboot, specify the number of pages in the guest configuration
file /etc/xen/vm/<guest_name>:
xenpaging=32768
@@ -41,8 +41,26 @@ changes.
Todo:
+- implement xl support
- implement stopping of xenpaging
-- implement/test live migration
+- implement live migration
+- implement config option for XENPAGING_DEBUG and XENPAGING_POLICY_MRU_SIZE
+- implement config option for xenpaging_dir
+- implement better starting gfn in xenpaging policy
+ an initial gfn number in the middle of the gfn range may avoid page-ins
+ during BIOS startup
+- fix machine_to_phys_mapping[] array handling during page deallocation
+ the gfn of a released page must be maintained properly in the array
+ http://lists.xensource.com/archives/html/xen-devel/2011-01/msg00824.html
+- fix HVMCOPY_gfn_paged_out handling
+ some callers of __hvm_copy() do not handle HVMCOPY_gfn_paged_out, such
+ as hypercalls and the MMIO emulation
+ the recently added waitqueue feature in Xen 4.1 should be used
+- remove all retry code from gfn_to_mfn() calls
+ use the waitqueue feature to hide page-in from the caller and cover
+ all cases where a retry is currently missing
+- do not bounce p2mt to xenpaging
+ p2m_mem_paging_populate/p2m_mem_paging_resume dont make use of p2mt
# vim: tw=72
next prev parent reply other threads:[~2011-01-16 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 16:32 [PATCH 0/6] xenpaging changes for xen-4.1 Olaf Hering
2011-01-16 16:32 ` [PATCH 1/6] xenpaging: correct dropping pages to avoid full ring buffer Olaf Hering
2011-01-16 16:32 ` [PATCH 2/6] xenpaging: prevent page-out of first 16MB Olaf Hering
2011-01-16 16:32 ` [PATCH 3/6] xenpaging: update machine_to_phys_mapping[] during page deallocation Olaf Hering
2011-01-16 16:32 ` [PATCH 4/6] xenpaging: handle HVMCOPY_gfn_paged_out in copy_from/to_user Olaf Hering
2011-01-16 16:32 ` [PATCH 5/6] xenpaging: start xenpaging via config option Olaf Hering
2011-01-16 16:32 ` Olaf Hering [this message]
2011-01-16 16:50 ` [PATCH 0/6] xenpaging changes for xen-4.1 Keir Fraser
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=20110116163231.352841527@aepfle.de \
--to=olaf@aepfle.de \
--cc=xen-devel@lists.xensource.com \
/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.