qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: BALATON Zoltan <balaton@eik.bme.hu>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-ppc <qemu-ppc@nongnu.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Multiple pci buses
Date: Mon, 17 Mar 2014 23:14:05 +0100 (CET)	[thread overview]
Message-ID: <alpine.LMD.2.02.1403172250220.23807@jedlik.phy.bme.hu> (raw)
In-Reply-To: <53272822.8000502@suse.de>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2166 bytes --]

On Mon, 17 Mar 2014, Andreas Färber wrote:
> In earlier times QEMU did not properly support multiple PCI bus domains.
> Some code in
> http://git.qemu.org/?p=qemu.git;a=blob;f=hw/pci-host/uninorth.c;h=e72fe2a70b954bf5675ad0c8735fea6bad665be6;hb=HEAD
> is #if 0'ed out that you should take a look at.

I've seen these #if 0'ed parts but just enabling them does not seem to be 
enough. I don't know enough about how should all this work and found no 
documentation or examples to follow so I hope someone can explain what it 
takes to create two pci buses (so devices added to the first get 
0:dev:func and those added to the second get 1:dev:func addresses) and 
these busses have their Cfg/IO/MMIO space mapped to different addresses. 
The patch I came up with so far did not work. The pci buses and memory map 
from the dumps I've seen should look like this:

0000:00:0b.0 Host bridge [0600]: Apple Computer Inc. UniNorth AGP [106b:0020]
0000:00:10.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon R200 QL [Radeon 8500 LE] [1002:514c]

0001:10:0b.0 Host bridge [0600]: Apple Computer Inc. UniNorth PCI [106b:001f]
0001:10:0d.0 PCI bridge [0604]: Digital Equipment Corporation DECchip 21154 [1011:0026] (rev 05)
0001:11:07.0 Unassigned class [ff00]: Apple Computer Inc. KeyLargo Mac I/O [106b:0022] (rev 02)

corresponding to this openfirmware tree:

ff8721c0: /pci@f0000000
ff898cd0:   /uni-north-agp@b
ff898f40:   /ATY,Rage128Ps@10
ff873268: /pci@f2000000
ff8742d8:   /pci-bridge@d
ff876368:     /mac-io@7

and the memory mapping is:

80000000-8fffffff : /pci@f2000000
    80000000-800fffff : PCI Bus 0001:11
      80000000-8007ffff : 0001:11:07.0
        80000000-8007ffff : 0.80000000:mac-io

90000000-9fffffff : /pci@f0000000
    90000000-9000ffff : 0000:00:10.0
      90000000-9000ffff : radeonfb mmio

f1000000-f1ffffff : /pci@f0000000
f3000000-f3ffffff : /pci@f2000000

> I had investigated that some time ago based on a G4 in our office and
> might be able to revive some patches... Please keep me CC'ed.

If you have any info/patches for this they are very welcome.

Regards,
BALATON Zoltan

  reply	other threads:[~2014-03-17 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-15 21:21 [Qemu-devel] Multiple pci buses BALATON Zoltan
2014-03-16 17:06 ` BALATON Zoltan
2014-03-17  2:09 ` Alexey Kardashevskiy
2014-03-17 16:51 ` Andreas Färber
2014-03-17 22:14   ` BALATON Zoltan [this message]
2014-03-19 22:36     ` Andreas Färber
2014-03-20  9:42       ` BALATON Zoltan

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=alpine.LMD.2.02.1403172250220.23807@jedlik.phy.bme.hu \
    --to=balaton@eik.bme.hu \
    --cc=afaerber@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).