From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:49565) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RdiBd-0004jr-Sx for qemu-devel@nongnu.org; Thu, 22 Dec 2011 07:56:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RdiBS-0006fh-Gh for qemu-devel@nongnu.org; Thu, 22 Dec 2011 07:55:53 -0500 Received: from mx1.redhat.com ([209.132.183.28]:22378) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RdiBR-0006bS-FU for qemu-devel@nongnu.org; Thu, 22 Dec 2011 07:55:41 -0500 Date: Thu, 22 Dec 2011 14:57:35 +0200 From: "Michael S. Tsirkin" Message-ID: <20111222125734.GC25538@redhat.com> References: <1324304024-11220-1-git-send-email-avi@redhat.com> <1324304024-11220-15-git-send-email-avi@redhat.com> <20111222125016.GB25538@redhat.com> <4EF32793.30108@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EF32793.30108@redhat.com> Subject: Re: [Qemu-devel] [PATCH 14/23] vhost: convert to MemoryListener API List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org, kvm@vger.kernel.org, Stefano Stabellini On Thu, Dec 22, 2011 at 02:50:27PM +0200, Avi Kivity wrote: > On 12/22/2011 02:50 PM, Michael S. Tsirkin wrote: > > On Mon, Dec 19, 2011 at 04:13:35PM +0200, Avi Kivity wrote: > > > +static void vhost_log_start(MemoryListener *listener, > > > + MemoryRegionSection *section) > > > +{ > > > + /* FIXME: implement */ > > > +} > > > + > > > +static void vhost_log_stop(MemoryListener *listener, > > > + MemoryRegionSection *section) > > > +{ > > > + /* FIXME: implement */ > > > +} > > > + > > > > What exactly do we need to fix here? > > Tell vhost to start tracking those regions? > > I guess you don't often read packets into the framebuffer, or we'd have > a lot of bug reports. Yes, we currently simply don't pass these regions to vhost. It currently signals an error if such is observed, so we could handle framebuffer in userspace if we wanted to. > -- > error compiling committee.c: too many arguments to function