From: Alex Williamson <alex.williamson@redhat.com>
To: Mitchell Augustin <mitchell.augustin@canonical.com>
Cc: linux-pci@vger.kernel.org, kvm@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: drivers/pci: (and/or KVM): Slow PCI initialization during VM boot with passthrough of large BAR Nvidia GPUs on DGX H100
Date: Tue, 26 Nov 2024 15:41:45 -0700 [thread overview]
Message-ID: <20241126154145.638dba46.alex.williamson@redhat.com> (raw)
In-Reply-To: <CAHTA-ubXiDePmfgTdPbg144tHmRZR8=2cNshcL5tMkoMXdyn_Q@mail.gmail.com>
On Tue, 26 Nov 2024 16:18:26 -0600
Mitchell Augustin <mitchell.augustin@canonical.com> wrote:
> > The BAR space is walked, faulted, and mapped. I'm sure you're at
> > least experiencing scaling issues of that with 128GB BARs.
>
> The part that is strange to me is that I don't see the initialization
> slowdown at all when the GPUs are hotplugged after boot completes.
> Isn't what you describe here also happening during the hotplugging
> process, or is it different in some way?
The only thing that comes to mind would be if you're using a vIOMMU and
it's configured in non-passthrough mode so the BARs aren't added to the
DMA address space after the vIOMMU is enabled during boot. But your
virt-install command doesn't show a vIOMMU configuration for the VM.
If the slowness is confined to the guest kernel boot, can you share the
log of that boot with timestamps? Thanks,
Alex
next prev parent reply other threads:[~2024-11-26 22:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 22:46 drivers/pci: (and/or KVM): Slow PCI initialization during VM boot with passthrough of large BAR Nvidia GPUs on DGX H100 Mitchell Augustin
2024-11-26 17:34 ` Alex Williamson
2024-11-26 22:18 ` Mitchell Augustin
2024-11-26 22:41 ` Alex Williamson [this message]
2024-11-26 23:08 ` Mitchell Augustin
2024-11-27 0:02 ` Alex Williamson
2024-11-27 1:12 ` Mitchell Augustin
2024-11-27 17:22 ` Alex Williamson
2024-12-02 19:36 ` Mitchell Augustin
2024-12-03 18:34 ` Mitchell Augustin
2024-12-03 19:20 ` Alex Williamson
2024-12-03 20:33 ` Mitchell Augustin
2024-12-03 22:06 ` Alex Williamson
2024-12-03 23:09 ` Mitchell Augustin
2024-12-03 23:30 ` Alex Williamson
2024-12-06 0:09 ` Mitchell Augustin
2025-01-08 23:06 ` Mitchell Augustin
2025-01-13 18:22 ` Alex Williamson
2025-01-13 19:43 ` Mitchell Augustin
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=20241126154145.638dba46.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mitchell.augustin@canonical.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