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] allocate_empty_lowmem_region hypervisor function

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] allocate_empty_lowmem_region hypervisor function
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Tue, 2 Aug 2005 13:48:07 +0100
Cc: cwc22@xxxxxxxxx, Ross C Mcilroy <mcilrorc@xxxxxxxxxxxxx>
Delivery-date: Tue, 02 Aug 2005 12:47:49 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <260002866C8EBA4EA0AD853F467EC11E04ACDB@xxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <260002866C8EBA4EA0AD853F467EC11E04ACDB@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8.2
> Is there a reason that the allocate_empty_lowmem_region() function in
> hypervisor.c is only available in Domain 0.  It is only included if
> CONFIG_XEN_PHYSDEV_ACCESS is defined, however, when I remove this it seems
> to work fine in DomUs.

It's only used in the backend drivers, so I guess the build is trying to omit 
that as dead code as far as a domU is concerned.  IIRC the function is pure 
Linux-isms with no Xen-specifics, so it should be fine to build into a domU 
(or even x86 Linux).


Xen-devel mailing list