From: Ethan Zhao <haifeng.zhao@linux.intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: bhelgaas@google.com, Smita.KoralahalliChannabasappa@amd.com,
ilpo.jarvinen@linux.intel.com,
sathyanarayanan.kuppuswamy@linux.intel.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
kbusch@kernel.org
Subject: Re: [PATCH pci-next] pci/edr: Ignore Surprise Down error on hot removal
Date: Wed, 6 Mar 2024 09:37:01 +0800 [thread overview]
Message-ID: <4908a5ab-dc07-41fa-bdf4-36b1f3f516e2@linux.intel.com> (raw)
In-Reply-To: <20240305092139.GA28325@wunner.de>
On 3/5/2024 5:21 PM, Lukas Wunner wrote:
> On Tue, Mar 05, 2024 at 10:09:20AM +0800, Ethan Zhao wrote:
>> On 3/4/2024 7:58 PM, Lukas Wunner wrote:
>>> On Mon, Mar 04, 2024 at 04:08:19AM -0500, Ethan Zhao wrote:
>>>> -static void dpc_handle_surprise_removal(struct pci_dev *pdev)
>>>> +bool dpc_handle_surprise_removal(struct pci_dev *pdev)
>>>> {
>>>> + if (!dpc_is_surprise_removal(pdev))
>>>> + return false;
>>> This change of moving dpc_is_surprise_removal() into
>>> dpc_handle_surprise_removal() seems unrelated to the problem at hand.
>>>
>>> Please drop it if it's unnecessary to fix the issue.
>> To only export one function dpc_is_surprise_removal()... or I have to
>> export them both.
>> Seems I should keep them intact or refactor them in separated patch ?
> Please keep them intact and make both public. (You're not "exporting"
> the functions, there are no modular users.)
>
> However, I doubt whether you need to respin this patch at all:
>
>
>> Reproduced on "Hardware name: Intel Corporation ArcherCity/ArcherCity,
>> BIOS EGSDCRB1.86B.0107.D20.2310211929 10/21/2023"
> Eagle Stream BIOS, isn't that an Intel-provided BIOS?
>
> Sathya's comments sound like the BIOS is misbehaving. If so,
> then the first thing to do is ask the BIOS team to fix the issue.
> We do not want to pollute the kernel with workarounds for BIOS bugs
> that can be fixed in the field through a BIOS update.
Agree, BIOS writer finally was convinced to fix it in BIOS.
no need to respin.
Thanks,
Ethan
>
> Thanks,
>
> Lukas
next prev parent reply other threads:[~2024-03-06 1:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 9:08 [PATCH pci-next] pci/edr: Ignore Surprise Down error on hot removal Ethan Zhao
2024-03-04 11:58 ` Lukas Wunner
2024-03-04 19:33 ` Smita Koralahalli
2024-03-05 2:19 ` Ethan Zhao
2024-03-05 2:09 ` Ethan Zhao
2024-03-05 9:21 ` Lukas Wunner
2024-03-06 1:37 ` Ethan Zhao [this message]
2024-03-04 20:10 ` Kuppuswamy Sathyanarayanan
2024-03-05 2:29 ` Ethan Zhao
2024-03-05 4:04 ` Kuppuswamy Sathyanarayanan
2024-03-05 5:49 ` Ethan Zhao
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=4908a5ab-dc07-41fa-bdf4-36b1f3f516e2@linux.intel.com \
--to=haifeng.zhao@linux.intel.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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