All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: grwhyte@linux.microsoft.com
Cc: linux-pci@vger.kernel.org, shyamsaini@linux.microsoft.com,
	code@tyhicks.com, Okaya@kernel.org, bhelgaas@google.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PCI: Reduce delay after FLR of Microsoft MANA devices
Date: Thu, 29 May 2025 12:34:36 +0200	[thread overview]
Message-ID: <aDg4PE4Zbzwps71E@wunner.de> (raw)
In-Reply-To: <20250528181047.1748794-1-grwhyte@linux.microsoft.com>

On Wed, May 28, 2025 at 06:10:47PM +0000, grwhyte@linux.microsoft.com wrote:
> Add a device-specific reset for Microsoft MANA devices with the FLR
> delay reduced from 100ms to 10ms. While this is not compliant with the pci
> spec, these devices safely complete the FLR much quicker than 100ms and
> this can be reduced to optimize certain scenarios

How often do you reset these devices that 90 msec makes a difference?
What are these "certain scenarios"?

There are already "d3hot_delay" and "d3cold_delay" members in
struct pci_dev.  I'm wondering if it would make sense to add
another one, say, "flr_delay".  That would allow other devices
to reduce or lengthen the delay without each of them having to
duplicate pcie_flr().  The code duplication makes this difficult
to maintain long-term.

Thanks,

Lukas

  reply	other threads:[~2025-05-29 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 18:10 [PATCH v2] PCI: Reduce delay after FLR of Microsoft MANA devices grwhyte
2025-05-29 10:34 ` Lukas Wunner [this message]
2025-05-30 16:26   ` Graham Whyte
2025-05-31 14:09     ` Lukas Wunner

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=aDg4PE4Zbzwps71E@wunner.de \
    --to=lukas@wunner.de \
    --cc=Okaya@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=code@tyhicks.com \
    --cc=grwhyte@linux.microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=shyamsaini@linux.microsoft.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.