This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH 00 of 12] xenpaging fixes for xen-unstable

To: Keir Fraser <keir.xen@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 00 of 12] xenpaging fixes for xen-unstable
From: Olaf Hering <olaf@xxxxxxxxx>
Date: Tue, 7 Jun 2011 15:38:47 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Tue, 07 Jun 2011 06:39:39 -0700
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1307453929; l=2114; s=domk; d=aepfle.de; h=In-Reply-To:Content-Type:MIME-Version:References:Subject:Cc:To:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=mFv1pQms5JeTg0b/XRxlGrwyHnI=; b=l1CVUHJSjt7p05yKLANcHh5D4JOUps36g7ZyDg1k6jdwQF+tko8r3+1HAKgdUNH/RG1 4Roij00pTd29ke77CyUEmIuwsrfgk4ce6KJMj9fIYsuz6i8fSk7PBiLcBENC+WUSxWa1x lyz1GKVHytschZqtc34QT86zzcb6Z4W/R4I=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CA13D7CD.1BB88%keir.xen@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <patchbomb.1307440382@xxxxxxxxxxxx> <CA13D7CD.1BB88%keir.xen@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-12-30)
On Tue, Jun 07, Keir Fraser wrote:

> Once they're in, what is left to do? Do you need help with the in-Xen
> waitqueue stuff? Do you have test cases that fail, a private patch queue,
> etc?


I have no new patches, just returned to xenpaging end of last week.
A few months ago I collected my TODO list below.

One thing that I would need help with is the machine_to_phys_mapping[]
handling, an attempt to fix it was reverted before the 4.1 release. See
the thread in the URL below.

My testcase was a SLES11SP1 pv-on-hvm guest, rebooted in an endless
loop. That catched all of the issues. With the
waitqueue/HVMCOPY_gfn_paged_out issue its best to customize the
xenpaging policy to page the range of gfns were the guest pagetables are

I will send a series of patches to try later.


- implement xl support
- implement stopping of xenpaging
- 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
- 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
- cleanup typeof gfn which is passed around in xenpaging
  unsigned long, uint64_t, xen_pfn_t
- cleanup return types of functions
  some functions return 0 unconditionally, could be void
- remove srand function

Xen-devel mailing list