[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47146df8-b4e1-595d-9664-3830d770eecf@codeaurora.org>
Date: Wed, 25 Oct 2017 17:42:24 -0400
From: Sinan Kaya <okaya@...eaurora.org>
To: Alex Williamson <alex.williamson@...hat.com>,
Bjorn Helgaas <helgaas@...nel.org>
Cc: linux-pci@...r.kernel.org, timur@...eaurora.org,
linux-arm-msm@...r.kernel.org, Bjorn Helgaas <bhelgaas@...gle.com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] PCI: rework error checking in the reset path
On 10/25/2017 5:28 PM, Alex Williamson wrote:
>> Previously, we only tried the next reset method if one method failed
>> with -ENOTTY. With this patch, we'll try the next reset method if one
>> method fails for any reason, not just -ENOTTY.
> Hmm, I thought the return codes were pretty consistent. -ENOTTY means
> that the reset callback doesn't handle the device, move on. Many
> ioctls use the same return code to indicate an unknown ioctl. This
> allows us to differentiate success vs error vs unhandled. In the code
> below we lose the ability to, for instance, have a device specific
> reset that returns -EINVAL to prevent the PCI core for triggering
> further reset mechanisms which might be broken on the device. So, I
> don't see that this patch specifically fixes anything, but it does
> remove what seems like useful functionality... I'd veto it. Thanks,
>
OK, It was not obvious how the EINVAL and ENOTTY used by code inspection.
Thank your very much for the clarification. I'm dropping the patch unless
Bjorn has another idea.
> Alex
>
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
Powered by blists - more mailing lists