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] __HYPERVISOR_COMPAT_VIRT_START for HVM guest with PV dri

To: Chuck Anderson <chuck.anderson@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] __HYPERVISOR_COMPAT_VIRT_START for HVM guest with PV drivers
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 20 Aug 2009 17:27:12 +0100
Cc:
Delivery-date: Thu, 20 Aug 2009 09:27:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A8D6C12.90802@xxxxxxxxxx>
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: Acohq0BDNHQDb2mFTT2Bl9oIQWptFgAB9HWE
Thread-topic: [Xen-devel] __HYPERVISOR_COMPAT_VIRT_START for HVM guest with PV drivers
User-agent: Microsoft-Entourage/12.20.0.090605
On 20/08/2009 16:30, "Chuck Anderson" <chuck.anderson@xxxxxxxxxx> wrote:

> Do the guest virtual addresses passed by a hypervisor call on a 32-bit
> HVM with PV drivers guest to a 64-bit hypervisor need to lie below
> __HYPERVISOR_COMPAT_VIRT_START?  Both HVM and PVM domains have their
> hv_compat_vstart set to __HYPERVISOR_COMPAT_VIRT_START.  The
> hypervisor's compat layer is causing the balloon driver's
> HYPERVISOR_memory_op(XENMEM_decrease_reservation, &reservation)
> hypervisor call to error out in xen/common/compat/memory.c
> compat_memory_op(), compat_handle_ok(), because the PVHVM guest's
> extent_start lies above __HYPERVISOR_COMPAT_VIRT_START.  The following
> patch appears to fix the problem but I want to make sure it is fixing
> the real bug:

Yeah, you pretty much have it figured. I may just clean up for style (I
think an extra macro for this is a bit pointless), but the patch is
fundamentally good.

 Thanks,
 Keir



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