Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Maverickk 78 <maverickk1778@gmail.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: Problem with kernel rescan and realloc BAR resource for endponts
Date: Thu, 24 Apr 2025 12:13:37 -0500	[thread overview]
Message-ID: <20250424171337.GA492527@bhelgaas> (raw)
In-Reply-To: <CALfBBTsD40J3PAv4LXit6oTmJmeZOVjN+FG-PN2Aj2+KyPFahA@mail.gmail.com>

On Thu, Apr 24, 2025 at 10:19:44PM +0530, Maverickk 78 wrote:
> Hello,
> 
> The command line parameter
> 
> pciehp.pciehp_force=1 pciehp.pciehp_debug=1 pcie_ports=native
> pci=nocrs pci=hpmemsize=256M,realloc pci=noacpi pci=realloc=on
> pci=nobios
> 
> 
> There are a couple of endpoints connected to downstream ports on a
> switch, and the endpoints are not visible during the BIOS (seabios)
> enumeration, but they are brought out of reset just before kernel
> starts pci scan.
> 
> Even though the kernel enumerates the endpoint with proper bdf and is
> able to read the config space but its not able to properly program the
> BAR register, the lspci lists as
> 
> 
> Region 0: Memory at <unassigned> (32-bit, non-prefetchable) [disabled]
> [size=32M]
> 
> 
> This is an emulation platform.

Can't really give any suggestions without seeing a complete dmesg log 
and output of "sudo lspci -vv".  This will give insight into how much
space the devices require and what space is available.

Bjorn

  reply	other threads:[~2025-04-24 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 16:49 Problem with kernel rescan and realloc BAR resource for endponts Maverickk 78
2025-04-24 17:13 ` Bjorn Helgaas [this message]
2025-04-25  4:19   ` Maverickk 78

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=20250424171337.GA492527@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=maverickk1778@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox