From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LtZLF-00044p-3O
	for qemu-devel@nongnu.org; Mon, 13 Apr 2009 23:29:45 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LtZL9-00044d-JF
	for qemu-devel@nongnu.org; Mon, 13 Apr 2009 23:29:43 -0400
Received: from [199.232.76.173] (port=43003 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LtZL9-00044a-EE
	for qemu-devel@nongnu.org; Mon, 13 Apr 2009 23:29:39 -0400
Received: from mx2.redhat.com ([66.187.237.31]:57461)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <mtosatti@redhat.com>) id 1LtZL8-0002RK-0S
	for qemu-devel@nongnu.org; Mon, 13 Apr 2009 23:29:39 -0400
Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26])
	by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n3E3TYJi011164
	for <qemu-devel@nongnu.org>; Mon, 13 Apr 2009 23:29:35 -0400
Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199])
	by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n3E3TXJb029311
	for <qemu-devel@nongnu.org>; Mon, 13 Apr 2009 23:29:34 -0400
Received: from amt.cnet (vpn-10-15.str.redhat.com [10.32.10.15])
	by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n3E3TWk3016923
	for <qemu-devel@nongnu.org>; Mon, 13 Apr 2009 23:29:33 -0400
Received: from amt.cnet (amt.cnet [127.0.0.1])
	by amt.cnet (Postfix) with ESMTP id 04364274003
	for <qemu-devel@nongnu.org>; Tue, 14 Apr 2009 00:29:17 -0300 (BRT)
Received: (from marcelo@localhost)
	by amt.cnet (8.14.3/8.14.3/Submit) id n3E3TGN9003568
	for qemu-devel@nongnu.org; Tue, 14 Apr 2009 00:29:16 -0300
Date: Tue, 14 Apr 2009 00:29:16 -0300
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [Qemu-devel] [patch 2/2] qemu: switch pci device init
	functions to accept devfn
Message-ID: <20090414032916.GA3349@amt.cnet>
References: <20090413035311.009617911@amt.cnet>
	<20090413035340.296329700@amt.cnet>
	<200904131327.35201.paul@codesourcery.com>
	<20090413133021.GA1065@amt.cnet>
	<1239630459.27750.3.camel@nibbler.dlib.indiana.edu>
	<20090413143445.GB4595@amt.cnet>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090413143445.GB4595@amt.cnet>
Reply-To: qemu-devel@nongnu.org
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.gnu.org/pipermail/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: qemu-devel@nongnu.org

On Mon, Apr 13, 2009 at 11:34:46AM -0300, Marcelo Tosatti wrote:
> On Mon, Apr 13, 2009 at 09:47:39AM -0400, Brian Wheeler wrote:
> > Does this mean that there would be a mechanism for a platform to map the
> > pci memory address to a platform specific linear address?  Alpha uses 
> > 
> > 0x8000000000 + (0x20000000 * bus) + address
> > 
> > to determine where the pci memory is mapped in the cpu address space...
> 
> I think so yes. 

Actually, no.

> The use case in mind for us is interrupt mapping from
> (device address + PCI interrupt specifier) -> platform interrupt
> specifier.

Note: the discussion here is about _pci device address_:
bus,device,function.