From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Tejus GK <tejus.gk@nutanix.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com, marcel.apfelbaum@gmail.com
Subject: Re: pcie-root-port limits for q35?
Date: Tue, 8 Oct 2024 11:40:55 +0100 [thread overview]
Message-ID: <ZwUMN6P40sVwcmm-@redhat.com> (raw)
In-Reply-To: <9d0e5db9-aaf9-4536-ad9f-2f5c86523627@nutanix.com>
On Tue, Oct 08, 2024 at 03:44:33PM +0530, Tejus GK wrote:
> Hi, recently I was trying to play with the PCIe limits on the q35 machine
> type. I see that docs/pcie.txt mentions:
>
> > The IO space is very limited, to 65536 byte-wide IO ports, and may
> > even be fragmented by fixed IO ports owned by platform devices
> > resulting in at most 10 PCI Express Root Ports or PCI Express
> > Downstream Ports per system if devices with IO BARs are used in the
> > PCI Express hierarchy
>
> But in my own experimental setup, I was able to successfully create and
> power on a VM with 232 pcie-root-ports, with each root port hosting a
> virtio-net device on it. The root ports, and the network devices end up
> appearing inside the VM's PCI enumeration as well. So I'm left wondering
> where this limit exactly come from? And I'm not sure if I am missing
> something here, since I'm able to go way above the limit mentioned above.
Note the very last part of the text you quoted:
..if devices with IO BARs are used..
^^
AFAIK, the virtio devices (at least in modern mode) don't use IO BARs,
thus avoiding the mentioned limit.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2024-10-08 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 10:14 pcie-root-port limits for q35? Tejus GK
2024-10-08 10:40 ` Daniel P. Berrangé [this message]
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=ZwUMN6P40sVwcmm-@redhat.com \
--to=berrange@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tejus.gk@nutanix.com \
/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).