From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:37907)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1QN2g6-0002pa-2d
	for qemu-devel@nongnu.org; Thu, 19 May 2011 08:50:10 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1QN2g5-0006zx-3W
	for qemu-devel@nongnu.org; Thu, 19 May 2011 08:50:10 -0400
Received: from mx1.redhat.com ([209.132.183.28]:64045)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1QN2g4-0006zm-Sc
	for qemu-devel@nongnu.org; Thu, 19 May 2011 08:50:09 -0400
Message-ID: <4DD511FB.3080901@redhat.com>
Date: Thu, 19 May 2011 15:50:03 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <4DD3D236.90708@siemens.com> <4DD3D95E.2060105@redhat.com>
	<4DD3E1B3.3020405@siemens.com> <4DD3E47F.9060104@redhat.com>
	<4DD3E782.8090208@siemens.com> <4DD3E8D6.6090807@redhat.com>
	<20110519090851.GD28399@redhat.com> <4DD4DE8E.8030402@redhat.com>
	<20110519091404.GE28399@redhat.com> <4DD5029D.6000700@redhat.com>
	<20110519115405.GG28399@redhat.com>
	<4DD505C4.6010604@redhat.com> <4DD50B17.7000205@siemens.com>
In-Reply-To: <4DD50B17.7000205@siemens.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC] Memory API
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/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: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Gleb Natapov <gleb@redhat.com>

On 05/19/2011 03:20 PM, Jan Kiszka wrote:
> >
> >  An example is ne2000-isa and ne2000-pci.  There's no getting around some
> >  glue logic, but I think this API minimizes it (you can declare
> >  everything about your memory region in common code, the only thing that
> >  is different is registration).
>
> If devices register against the corresponding qbus (I expect we'll have
> multiple ones in the future), not even that need to be different.

Eventually we may make the memory API a sub-API of qdev.  I don't want 
to start with that however, the change is large enough already.

-- 
error compiling committee.c: too many arguments to function