From: Arnd Bergmann <arnd@arndb.de>
To: kvm-devel@lists.sourceforge.net
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Eric Van Hensbergen <ericvanhensbergen@us.ibm.com>,
kvm-devel@lists.sourceforge.net, lguest <lguest@ozlabs.org>,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org
Subject: Re: [kvm-devel] [PATCH 3/3] virtio PCI device
Date: Tue, 27 Nov 2007 10:25:59 +0100 [thread overview]
Message-ID: <200711271026.00084.arnd@arndb.de> (raw)
In-Reply-To: <474BDD28.7050801@qumranet.com>
On Tuesday 27 November 2007, Avi Kivity wrote:
> > :-) Do you know if there is a hard limit on the number of devices on
> > a PCI bus? My concern was that it was limited by something stupid
> > like an 8-bit identifier.
>
> IIRC pci slots are 8-bit, but you can have multiple buses, so
> effectively 16 bits of device address space (discounting functions which
> are likely not hot-pluggable).
You have an 8 bit bus number and an 8 bit device/function number.
The function number is 3 bits, so if you want to use only function 0
for everything, you are limited to a little under 8192 (2^(8+5)) devices
per PCI domain. PC style hardware cannot easily address multiple PCI
domains, but I think you can have them if you assume that the guest is
using mmconfig.
For using multiple buses, the easiest way could be to have every
device/function on bus 0 be a bridge by itself, so you end up with a
flat number space for the actual devices,
$ lspci -t
[0000:00]-+-00.0-[0000:01]--+-00.0
| +-01.0
| +-02.0
| + ...
| \-3f.0
+-00.1-[0000:02]--+-00.0
| +-01.0
| +-02.0
| + ...
| \-3f.0
+ ...
|
+-3f.6-[0000:ff]--+-00.0
+-01.0
+-02.0
+ ...
\-3f.0
Arnd <><
next prev parent reply other threads:[~2007-11-27 9:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 2:46 [PATCH 0/3] virtio PCI driver Anthony Liguori
2007-11-08 2:46 ` [PATCH 1/3] Export vring functions for modules to use Anthony Liguori
2007-11-08 2:46 ` [PATCH 2/3] Put the virtio under the virtualization menu Anthony Liguori
2007-11-08 2:46 ` [PATCH 3/3] virtio PCI device Anthony Liguori
2007-11-08 6:12 ` [kvm-devel] " Avi Kivity
2007-11-08 13:54 ` Anthony Liguori
2007-11-08 14:37 ` Avi Kivity
2007-11-08 15:06 ` Anthony Liguori
2007-11-08 15:13 ` Avi Kivity
2007-11-08 23:43 ` Dor Laor
2007-11-08 17:46 ` Arnd Bergmann
2007-11-08 19:04 ` Anthony Liguori
2007-11-09 11:03 ` Arnd Bergmann
2007-11-09 0:39 ` Dor Laor
2007-11-09 2:17 ` Anthony Liguori
2007-11-20 15:01 ` Avi Kivity
2007-11-20 15:43 ` Anthony Liguori
2007-11-20 16:12 ` Avi Kivity
2007-11-20 22:16 ` Anthony Liguori
2007-11-21 7:13 ` Avi Kivity
2007-11-21 18:22 ` Zachary Amsden
2007-11-22 7:32 ` Avi Kivity
2007-11-23 16:51 ` Anthony Liguori
2007-11-23 17:47 ` Avi Kivity
2007-11-26 19:18 ` Anthony Liguori
2007-11-27 9:02 ` Avi Kivity
2007-11-27 9:09 ` Carsten Otte
2007-11-27 9:27 ` Avi Kivity
2007-11-27 10:12 ` Carsten Otte
2007-11-27 10:19 ` Avi Kivity
2007-11-27 10:28 ` Carsten Otte
2007-11-27 9:25 ` Arnd Bergmann [this message]
2007-11-08 6:49 ` [kvm-devel] [PATCH 2/3] Put the virtio under the virtualization menu Avi Kivity
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=200711271026.00084.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=aliguori@us.ibm.com \
--cc=ericvanhensbergen@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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