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-introspect] Status Update

To: Steve Brueckner <steve@xxxxxxxxxxxxxx>, "'xen-introspect@xxxxxxxxxxxxxxxxxxx'" <xen-introspect@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-introspect] Status Update
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Date: Wed, 3 Jun 2009 15:37:12 +0100
Accept-language: en-US
Acceptlanguage: en-US
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Delivery-date: Thu, 04 Jun 2009 02:56:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <60D45469A1AAD311A04C009027B6BF680691D899@SERVER20>
List-archive: <http://lists.xensource.com/archives/html/xen-introspect>
List-help: <mailto:xen-introspect-request@lists.xensource.com?subject=help>
List-id: xen-introspect.lists.xensource.com
List-post: <mailto:xen-introspect@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-introspect>, <mailto:xen-introspect-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-introspect>, <mailto:xen-introspect-request@lists.xensource.com?subject=unsubscribe>
References: <60D45469A1AAD311A04C009027B6BF680691D899@SERVER20>
Sender: xen-introspect-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acnjl8AIj1VoL3LcQbulamQeJtXiyAAvVI7w
Thread-topic: [Xen-introspect] Status Update
> The second problem is the difficulty in altering the hypervisor for
> those of us unfamiliar with it.  For example, we spent about a hundred 
> man-hours
> trying to implement "memory trigger" functionality, but had to abandon
> the effort.  I think the group needs some level of dedicated support from
> XenSource or Citrix to answer questions.

I think you'll find that folks like Tim Deegan and Gianluca Guida would be very 
helpful in reviewing design proposals and commenting on patches. 

I'd very much like to see the ability to add type-codes to pages that enable 
synchronous and asynchronous triggers[*] to be delivered to a "monitor 
application" when pages are accessed, written, or executed[**]. These events 
can be captured through a fairly simple modification to the HAP and shadow 
code, and then delivered to the  nominated monitor application in a manner very 
similar to the mechanism used for delivering IO and MMIO events to qemu-dm.

[*] Synchronous triggers block the VCPU until a response from the monitor 
application is received, whereas asynchronous triggers may be queued until the 
queue fills. 
[**] I'd also add a special fast-path page-type that marks a page as 
executable-but-read-only, but allows it to automatically revert to the 
writeable-but-not-executable page type without requiring a synchronous trigger 
to manually changing the page type. 

Xen-introspect mailing list

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