All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sinan Kaya <Okaya@kernel.org>
To: Christoph Hellwig <hch@infradead.org>, linux-pci@vger.kernel.org
Subject: Re: reprobing BAR sizes and capabilities after a FLR?
Date: Tue, 9 Jul 2019 12:27:45 -0400	[thread overview]
Message-ID: <28402a5d-713e-93d4-560d-197605233ca6@kernel.org> (raw)
In-Reply-To: <20190709154019.GA30673@infradead.org>

On 7/9/2019 11:40 AM, Christoph Hellwig wrote:
> Hi all,
> 
> I've just been talking to some firmware developers that were a little
> surprised that Linux does not reprobe BAR sizes after a FLR.  I looked
> at our code and we do not reprobe anything at all after a FLR.  Is it
> a good assumption that a devices comes back in exactly the same state
> after an FLR?
> 

What's the use case for BAR size changing? I do remember that code was
saving the assigned BAR values.

I don't think FLR can be treated as a full enumeration.

  reply	other threads:[~2019-07-09 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-09 15:40 reprobing BAR sizes and capabilities after a FLR? Christoph Hellwig
2019-07-09 16:27 ` Sinan Kaya [this message]
2019-07-10 14:14 ` Bjorn Helgaas

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=28402a5d-713e-93d4-560d-197605233ca6@kernel.org \
    --to=okaya@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-pci@vger.kernel.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 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.