From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:51702)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1QMn7f-0004j4-59
	for qemu-devel@nongnu.org; Wed, 18 May 2011 16:13:35 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1QMn7e-0004fT-9k
	for qemu-devel@nongnu.org; Wed, 18 May 2011 16:13:35 -0400
Received: from mail-pz0-f45.google.com ([209.85.210.45]:48787)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1QMn7e-0004fI-07
	for qemu-devel@nongnu.org; Wed, 18 May 2011 16:13:34 -0400
Received: by pzk30 with SMTP id 30so1092156pzk.4
	for <qemu-devel@nongnu.org>; Wed, 18 May 2011 13:13:32 -0700 (PDT)
Sender: Richard Henderson <rth7680@gmail.com>
Message-ID: <4DD4286A.2030408@twiddle.net>
Date: Wed, 18 May 2011 13:13:30 -0700
From: Richard Henderson <rth@twiddle.net>
MIME-Version: 1.0
References: <4DD3C5B9.1080908@redhat.com>	<4DD3D236.90708@siemens.com>	<4DD3D95E.2060105@redhat.com>	<4DD3E1B3.3020405@siemens.com>	<4DD3E47F.9060104@redhat.com>	<4DD3E782.8090208@siemens.com>	<4DD3E8D6.6090807@redhat.com>	<4DD3ED22.6080005@siemens.com>
	<4DD3F055.6000905@redhat.com>	<4DD3F626.7060500@siemens.com>
	<4DD3F83E.4090700@redhat.com>
In-Reply-To: <4DD3F83E.4090700@redhat.com>
Content-Type: text/plain; charset=UTF-8
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: Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel <qemu-devel@nongnu.org>

On 05/18/2011 09:47 AM, Avi Kivity wrote:
> Yes.  We'd change pci_register_bar() to accept a MemoryRegion.

Surely this detail would be hidden on the pci_dev->bus?

>> However, we are yet in troubles if we want to change that because
>> devices can only be on one bus - at least so far.
> 
> Nothing prohibits a device from calling pci_register_bar() for one region and some other API for another.

Sure, but the majority of PCI devices are plain pci, and 
that sort of complexity should be hidden by default.


r~