From: Marcelo Tosatti <mtosatti@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Chris Wright <chrisw@redhat.com>,
kvm-devel <kvm-devel@lists.sourceforge.net>,
Avi Kivity <avi@qumranet.com>
Subject: Re: QEMU/KVM [RFC]: add support for 128 PCI slots
Date: Fri, 25 Apr 2008 17:39:16 -0300 [thread overview]
Message-ID: <20080425203916.GA9617@dmt> (raw)
In-Reply-To: <3DA29361-81E2-486A-B32B-66A9E280C135@suse.de>
On Fri, Apr 25, 2008 at 11:38:21AM +0200, Alexander Graf wrote:
>
> On Apr 25, 2008, at 3:01 AM, Marcelo Tosatti wrote:
>
> >
> >Add three PCI bridges to support 128 slots. Vendor and device_id have
> >been stolen from my test box.
> >
> >I/O port addresses behind each bridge are statically allocated
> >starting
> >from 0x2000 with 0x1000 length. Once the bridge runs out of I/O space
> >the guest (Linux at least) happily allocates outside of the region.
> >That
> >needs verification.
> >
> >I/O memory addresses are divided between 0xf0000000 -> APIC base.
> >
> >The PCI irq mapping function is also changed, there was the assumption
> >that devices behind the bridge use the IRQ allocated to the bridge
> >device itself, which is weird. Apparently this is how the SPARC ABP
> >PCI
> >host works (only user of the bridge code at the moment).
>
> Is there any reason we're not using the _PIC function and give the OS
> a clue on which APIC pin the device is? Right now everything boils
> down to LNKA - LNKD which it does not have to.
> It might even be a good idea to connect each PCI device to a specific
> APIC pin, so we don't need to share too much, which might become a
> problem with a lot of PCI devices. As far as I know there is no
> limitation on how many pins an APIC may have.
I was not aware of the _PIC function. Will take a look at it.
The number of IRQ's certainly needs to increase.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-25 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 1:01 QEMU/KVM [RFC]: add support for 128 PCI slots Marcelo Tosatti
2008-04-25 9:38 ` Alexander Graf
2008-04-25 20:39 ` Marcelo Tosatti [this message]
2008-04-25 21:19 ` Alexander Graf
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=20080425203916.GA9617@dmt \
--to=mtosatti@redhat.com \
--cc=agraf@suse.de \
--cc=avi@qumranet.com \
--cc=chrisw@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
/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