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] query the page type of a hvm page from within a hvm gues

To: Olaf Hering <olaf@xxxxxxxxx>
Subject: Re: [Xen-devel] query the page type of a hvm page from within a hvm guest
From: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Date: Thu, 7 Apr 2011 12:16:02 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 07 Apr 2011 04:17:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110407101202.GA31553@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: <20110407101202.GA31553@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)

At 11:12 +0100 on 07 Apr (1302174722), Olaf Hering wrote:
> If the crash kernel had a way to ask the hypervisor wether a specific
> guest gfn is ballooned and thus backed by ram, the load issue would not
> happen.  There seems to be no interface to query the type of a guest gfn
> from within the hvm guest.
> Any ideas how to implement that?
> I see HVMOP_set_mem_type, but no HVMOP_get_mem_type.

Feel free to add HVMOP_get_mem_type.  I don't think any great harm can
come from allowing the guest to query its own memory status.


Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>