From mboxrd@z Thu Jan 1 00:00:00 1970 From: Razvan Cojocaru Subject: Re: Hypervisor to dom0 communication Date: Thu, 15 Nov 2012 16:37:43 +0200 Message-ID: <50A4FE37.4040809@gmail.com> 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"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Steven Maresca Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org > 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. I am. I've already pulled the events branch from your git server to try out (on an up-to-date 64bit Arch Linux machine), but it didn't compile: make[3]: Entering directory `vmitools/libvmi' /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -fvisibility=hidden -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g -O2 -MT driver/libvmi_la-interface.lo -MD -MP -MF driver/.deps/libvmi_la-interface.Tpo -c -o driver/libvmi_la-interface.lo `test -f 'driver/interface.c' || echo './'`driver/interface.c [...] In file included from ./driver/xen.h:29:0, from driver/interface.c:29: ./driver/xen_events.h:66:5: error: unknown type name 'mem_event_shared_page_t' Maybe I missed some ./configure flag? Thanks, Razvan