From: Lukas Wunner <lukas@wunner.de>
To: alan.adamson@oracle.com
Cc: linux-pci@vger.kernel.org, jonathan.derrick@linux.dev
Subject: Re: Spurious DLLSC on a x4x4 NVMe
Date: Sat, 1 Jun 2024 09:27:58 +0200 [thread overview]
Message-ID: <ZlrNfu_PvKkD_4jS@wunner.de> (raw)
In-Reply-To: <c14b0b67-e766-4464-9acb-dc4f6dea0b7e@oracle.com>
On Fri, May 31, 2024 at 02:11:56PM -0700, alan.adamson@oracle.com wrote:
> Back in 2021/2022 there where discussions about issues when hot removing a
> bifurcated x4x4 device from a x8 slot. I could not find any resolution or
> applied fix for this.
>
> https://patchwork.kernel.org/project/linux-pci/patch/20210830155628.130054-1-jonathan.derrick@linux.dev/
>
> Was there ever a resolution?
No, there wasn't.
I proposed a patch in this e-mail:
https://lore.kernel.org/linux-pci/20220924073208.GA26243@wunner.de/
...but it seems nobody actually tested it for the bifurcation use case.
Thanks,
Lukas
prev parent reply other threads:[~2024-06-01 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 21:11 Spurious DLLSC on a x4x4 NVMe alan.adamson
2024-05-31 22:02 ` alan.adamson
2024-06-01 7:27 ` Lukas Wunner [this message]
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=ZlrNfu_PvKkD_4jS@wunner.de \
--to=lukas@wunner.de \
--cc=alan.adamson@oracle.com \
--cc=jonathan.derrick@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox