From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=42422 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Q5NWM-0004Yn-DG
	for qemu-devel@nongnu.org; Thu, 31 Mar 2011 15:27:07 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Q5NWI-0006SM-FX
	for qemu-devel@nongnu.org; Thu, 31 Mar 2011 15:27:06 -0400
Received: from mail-gw0-f45.google.com ([74.125.83.45]:38301)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Q5NWI-0006SA-9j
	for qemu-devel@nongnu.org; Thu, 31 Mar 2011 15:27:02 -0400
Received: by gwb19 with SMTP id 19so1301610gwb.4
	for <qemu-devel@nongnu.org>; Thu, 31 Mar 2011 12:27:01 -0700 (PDT)
Message-ID: <4D94D583.7050203@codemonkey.ws>
Date: Thu, 31 Mar 2011 14:26:59 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH RFC] vga: flag vga ram for notifiers
References: <20110331174328.GA25133@redhat.com>	<4D94C916.6080709@codemonkey.ws>	<20110331184940.GA25688@redhat.com>	<4D94CFA0.3030605@codemonkey.ws>
	<20110331190750.GA25914@redhat.com>
In-Reply-To: <20110331190750.GA25914@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>, qemu-devel@nongnu.org

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?


>> 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