WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] slow xp hibernation revisited

To: "Keir Fraser" <keir.xen@xxxxxxxxx>, "Tim Deegan" <Tim.Deegan@xxxxxxxxxx>
Subject: RE: [Xen-devel] slow xp hibernation revisited
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Sat, 4 Jun 2011 18:05:57 +1000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 04 Jun 2011 01:08:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CA0FA2A9.1B9B2%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: <AEC6C66638C05B468B556EA548C1A77D01D57760@trantor> <CA0FA2A9.1B9B2%keir.xen@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcwiBQi9TTmL+VIUTGmHL1mgnlOPmgAak8qgAADdoAAAA9fn5AABgqJAAAEDCUwAACdjUA==
Thread-topic: [Xen-devel] slow xp hibernation revisited
> 
> On 04/06/2011 08:38, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
wrote:
> 
> > Looking past the test_bit call, the next statement does another test
and
> > sets last_address_index to 0 and returns NULL. Is this just to
ensure
> > that the next access isn't just trivially accepted?
> 
> Yes, first test is on a potentially stale bucket. Second test is on a
fresh
> bucket.
> 

How about the following patch? Is munmap the correct way to unmap or is
an IOCTL required too?

The exit condition is what would happen anyway after the remap is done
and the page is still invalid.

diff --git a/hw/xen_machine_fv.c b/hw/xen_machine_fv.c
index d02e23f..1ff80bb 100644
--- a/hw/xen_machine_fv.c
+++ b/hw/xen_machine_fv.c
@@ -151,6 +151,24 @@ uint8_t *qemu_map_cache(target_phys_addr_t
phys_addr, uint8_t lock)
         pentry->next = entry;
         qemu_remap_bucket(entry, address_index);
     } else if (!entry->lock) {
+        if (entry->vaddr_base && entry->paddr_index == address_index &&
!test_bit(address_offset>>XC_PAGE_SHIFT, entry->valid_mapping))
+        {
+            /* The page was invalid previously. Test if it is valid now
and only remap if so */
+            xen_pfn_t pfn;
+            int err;
+            void *tmp_vaddr;
+
+            pfn = phys_addr >> XC_PAGE_SHIFT;
+            tmp_vaddr = xc_map_foreign_bulk(xc_handle, domid,
PROT_READ|PROT_WRITE, &pfn, &err, 1);
+            if (tmp_vaddr)
+                munmap(tmp_vaddr, PAGE_SIZE);
+
+            if (!tmp_vaddr || err)
+            {
+                last_address_index = ~0UL;
+                return NULL;
+            }
+        }
         if (!entry->vaddr_base || entry->paddr_index != address_index
|| !test_bit(address_offset>>XC_PAGE_SHIFT, entry->valid_mapping))
             qemu_remap_bucket(entry, address_index);
     }


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel