From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=45682 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Q5O5S-0001UL-TE
	for qemu-devel@nongnu.org; Thu, 31 Mar 2011 16:03:23 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1Q5O5S-0004yi-0t
	for qemu-devel@nongnu.org; Thu, 31 Mar 2011 16:03:22 -0400
Received: from mx1.redhat.com ([209.132.183.28]:17801)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1Q5O5R-0004ya-ML
	for qemu-devel@nongnu.org; Thu, 31 Mar 2011 16:03:21 -0400
Date: Thu, 31 Mar 2011 22:03:00 +0200
From: "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC] vga: flag vga ram for notifiers
Message-ID: <20110331200300.GA26170@redhat.com>
References: <20110331174328.GA25133@redhat.com>
	<4D94C916.6080709@codemonkey.ws>
	<20110331184940.GA25688@redhat.com>
	<4D94CFA0.3030605@codemonkey.ws>
	<20110331190750.GA25914@redhat.com>
	<4D94D583.7050203@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D94D583.7050203@codemonkey.ws>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Alex Williamson <alex.williamson@redhat.com>, qemu-devel@nongnu.org

On Thu, Mar 31, 2011 at 02:26:59PM -0500, Anthony Liguori wrote:
> On 03/31/2011 02:07 PM, Michael S. Tsirkin wrote:
> >>Just needs some love.
> >>
> >>VGA is just another device.  It happens to be that we treat VGA
> >>device memory as something that behaves like ram occassionally but
> >>that does not make it RAM.
> >If we agree on that, will a pair of functions for this work?
> >How about device_register_ram / device_unregister_ram ?
> 
> To register normal RAM or to register stuff that isn't RAM but looks
> and tastes like RAM?

The later.

> >>Something like vhost doesn't need to see anything but RAM.  If we
> >>have a mechanism to identify RAM as RAM, then vhost can only look at
> >>RAM memory and not worry about things like VGA.
> >>
> >>I thought Alex had gotten a mini-version of RamAPI in but I can't
> >>seem to figure out what that included.
> >Me neither.
> >
> >>  At any rate, the point is
> >>still that registering things that you want to exclude in vhost is
> >>the wrong approach, you want to explicitly mark the things you want
> >>to include.
> >>
> >>Regards,
> >>
> >>Anthony Liguori
> >vhost just wants RAM.
> 
> Right, so mark RAM, and call it a day :-)
> 
> Regards,
> 
> Anthony Liguori
>