qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch 2/2] qemu: switch pci device init functions to accept devfn
Date: Tue, 14 Apr 2009 00:29:16 -0300	[thread overview]
Message-ID: <20090414032916.GA3349@amt.cnet> (raw)
In-Reply-To: <20090413143445.GB4595@amt.cnet>

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.

  reply	other threads:[~2009-04-14  3:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13  3:53 [Qemu-devel] [patch 0/2] RFC: move PCI device enumeration out of pci drivers Marcelo Tosatti
2009-04-13  3:53 ` [Qemu-devel] [patch 1/2] qemu: move pci devfn "first free" assignment to separate function Marcelo Tosatti
2009-04-13  8:08   ` Avi Kivity
2009-04-13  3:53 ` [Qemu-devel] [patch 2/2] qemu: switch pci device init functions to accept devfn Marcelo Tosatti
2009-04-13 12:27   ` Paul Brook
2009-04-13 13:30     ` Marcelo Tosatti
2009-04-13 13:47       ` Brian Wheeler
2009-04-13 14:34         ` Marcelo Tosatti
2009-04-14  3:29           ` Marcelo Tosatti [this message]
2009-04-14  8:17     ` Marcelo Tosatti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090414032916.GA3349@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).