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] [PATCH] hvm: Use main memory for video memory. [Was: xen

To: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] hvm: Use main memory for video memory. [Was: xend, 8MB video memory and ballooning]
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 31 Jul 2008 14:39:59 +0100
Cc:
Delivery-date: Thu, 31 Jul 2008 06:41:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080731131850.GI4678@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjzEuztK42G/l8GEd2L3gAX8io7RQ==
Thread-topic: [Xen-devel] [PATCH] hvm: Use main memory for video memory. [Was: xend, 8MB video memory and ballooning]
User-agent: Microsoft-Entourage/11.4.0.080122
On 31/7/08 14:18, "Samuel Thibault" <samuel.thibault@xxxxxxxxxxxxx> wrote:

> diff -r 83b3a8a2a4f3 tools/libxc/xc_domain_save.c
> --- a/tools/libxc/xc_domain_save.c Thu Jul 31 12:58:07 2008 +0100
> +++ b/tools/libxc/xc_domain_save.c Thu Jul 31 13:20:02 2008 +0100
> @@ -1112,9 +1112,7 @@ int xc_domain_save(int xc_handle, int io
>                      continue;
>  
>                  /* Skip PFNs that aren't really there */
> -                if ( hvm && ((n >= 0xa0 && n < 0xc0) /* VGA hole */
> -                             || (n >= (HVM_BELOW_4G_MMIO_START >> PAGE_SHIFT)
> -                                 && n < (1ULL<<32) >> PAGE_SHIFT)) /* MMIO */
> )
> +                if ( hvm && n == shared_info_frame )
>                      continue;

What happens if you don't special-case shared_info_frame? I'd've hoped it
would just work... does the extra page of allocation during restore fail?

I'm thinking that the grant tables will be mapped in the I/O hole too, and
that is from 'Xen heap' just like shared_info is. So special-casing one and
not the other sure is odd.

 -- Keir



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