From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:34460)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R5Hv7-0003bX-6s
	for qemu-devel@nongnu.org; Sun, 18 Sep 2011 10:00:34 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R5Hv3-0004YK-UT
	for qemu-devel@nongnu.org; Sun, 18 Sep 2011 10:00:33 -0400
Received: from mx1.redhat.com ([209.132.183.28]:23755)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R5Hv3-0004XX-Kd
	for qemu-devel@nongnu.org; Sun, 18 Sep 2011 10:00:29 -0400
Message-ID: <4E75F975.6020504@redhat.com>
Date: Sun, 18 Sep 2011 17:00:21 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <4E70EC90.8000904@us.ibm.com>
	<4E719F7C.10700@redhat.com>	<4E71FD19.6050606@codemonkey.ws>
	<4E725EC9.6060506@redhat.com> <4E726579.7070902@codemonkey.ws>
	<4E75A449.7060602@redhat.com>
In-Reply-To: <4E75A449.7060602@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC] Plan for moving forward with QOM
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: Anthony Liguori <anthony@codemonkey.ws>
Cc: Peter Maydell <peter.maydell@linaro.org>, Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel <qemu-devel@nongnu.org>, Markus Armbruster <armbru@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>, "Edgar E. Iglesias" <edgar.iglesias@gmail.com>, Paolo Bonzini <pbonzini@redhat.com>

On 09/18/2011 10:56 AM, Avi Kivity wrote:
> On 09/15/2011 11:52 PM, Anthony Liguori wrote:
>>> Also, NE2000 methods have to call ISA_NE2000 and PCI_NE2000 methods, 
>>> yes?
>>
>>
>> I don't think so.  The NE2k would export an IRQ and the ISA_NE2K and 
>> PCI_NE2k would have to route that IRQ.  But I think that's the extent 
>> of the communication in that direction.
>>
>> Am I missing something?
>
> I guess for simple devices it's unlikely that anything further is needed.
>
> The most complicated device with a dual interface I can think of is 
> vga, it needs to register memory regions dynamically.  But even that 
> can be done by registering a container on startup, and doing the 
> dynamic stuff within the container.
>

And in fact this exact problem has just hit us with the vga portio_list 
conversion.  And note we can't just use a container, because 
isa_register_portio_list() does more than just register the memory regions.

(problems are in memory/queue, not upstream).

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