All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Ruben <rubenbryon@gmail.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	Alex Williamson <alex.williamson@redhat.com>,
	linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [question]: BAR allocation failing
Date: Thu, 15 Jul 2021 14:50:02 -0700	[thread overview]
Message-ID: <20210715215002.GA1839645@dhcp-10-100-145-180.wdc.com> (raw)
In-Reply-To: <CALdZjm6iDnCR7OWzfCuKOALAtN-FoVvTdxUB=XcAFqHg5Aumpw@mail.gmail.com>

On Thu, Jul 15, 2021 at 11:39:54PM +0300, Ruben wrote:
> Thanks for the response, here's a link to the entire dmesg log:
> https://drive.google.com/file/d/1Uau0cgd2ymYGDXNr1mA9X_UdLoMH_Azn/view
> 
> Some entries that might be of interest:
> 
> [    0.378712] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
> [    0.378712] pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffffff]
> [    0.378712] pci_bus 0000:00: root bus resource [bus 00-ff]

I have not seen anything like that before. Usually you get non-zero
offset windows for memory resources separating 32-bit non-prefetchable
from the prefetchable.

Assuming what you're showing is fine, this says you've 1TB memory
addressable space available to the root bus. Each of your device's
memory requires 128GB and 32MB, both 64-bit non-prefetchable BARs. Due
to alignment requirements, your GPUs should need at least 2TB of IO
memory space to satisfy their memory request.

That's probably not very helpful information, though. I'll look if
there's something creating a 1TB limit in qemu, but I'm honestly not
very familiar enough in that particular area.

  reply	other threads:[~2021-07-15 21:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 21:32 [question]: BAR allocation failing Ruben
2021-07-14 22:03 ` Alex Williamson
2021-07-14 22:43   ` Ruben
2021-07-15 14:49     ` Bjorn Helgaas
2021-07-15 20:39       ` Ruben
2021-07-15 21:50         ` Keith Busch [this message]
2021-07-15 23:05         ` Bjorn Helgaas
2021-07-15 23:08           ` Alex Williamson
2021-07-16  6:14             ` Ruben

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=20210715215002.GA1839645@dhcp-10-100-145-180.wdc.com \
    --to=kbusch@kernel.org \
    --cc=alex.williamson@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rubenbryon@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.