From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Maresca Subject: Re: Hypervisor to dom0 communication Date: Thu, 15 Nov 2012 09:26:56 -0500 Message-ID: References: <50A16639.2090209@gmail.com> <1352800791.7491.21.camel@zakaz.uk.xensource.com> <50A22044.6060608@gmail.com> <1352802973.7491.40.camel@zakaz.uk.xensource.com> <50A225CA.2080705@gmail.com> <1352805173.7491.57.camel@zakaz.uk.xensource.com> <50A22DD7.7020901@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <50A22DD7.7020901@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Razvan Cojocaru Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Tue, Nov 13, 2012 at 6:24 AM, Razvan Cojocaru wrote: >> Perhaps it would be useful to build on the vmitools (previously >> xenaccess)? http://code.google.com/p/vmitools/ > > > Indeed, but LibVMI does not offer event-based access, and polling is not > really a solution. > > >> In general we prefer not to put stuff in the hypervisor unless >> absolutely required. > > > Me too :) > > Thanks, > Razvan FYI, vmitools (LibVMI) does have support for memory events, just not in the main branch. The events branch works properly for 4.1.x; I have updated it to support 4.2, but due to other more pressing matters, I have not had time to commit it to the main branch. If you're interested in using the memory event facilities abstracted via LibVMI, please let me know. Steve