[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YFy+fdL8PdD2CgOy@unreal>
Date: Thu, 25 Mar 2021 18:46:53 +0200
From: Leon Romanovsky <leon@...nel.org>
To: Amey Narkhede <ameynarkhede03@...il.com>
Cc: info@...ux.net, raphael.norwitz@...anix.com,
alex.williamson@...hat.com, linux-pci@...r.kernel.org,
bhelgaas@...gle.com, linux-kernel@...r.kernel.org,
alay.shah@...anix.com, suresh.gumpula@...anix.com,
shyam.rajendran@...anix.com, felipe@...anix.com
Subject: Re: [PATCH 4/4] PCI/sysfs: Allow userspace to query and set device
reset mechanism
On Thu, Mar 25, 2021 at 09:56:37PM +0530, Amey Narkhede wrote:
> On 21/03/25 10:37AM, Leon Romanovsky wrote:
> > On Wed, Mar 24, 2021 at 11:17:29AM -0600, Alex Williamson wrote:
> > > On Wed, 24 Mar 2021 17:13:56 +0200
> > > Leon Romanovsky <leon@...nel.org> wrote:
<...>
> > I expect that QEMU sets same reset policy for all devices at the same
> > time instead of trying per-device to guess which one works.
> >
> The current reset attribute does the same thing internally you described
> at the end.
> > And yes, you will be able to bypass kernel, but at least this interface
> > will be broader than initial one that serves only SO and workarounds.
> >
> What does it mean by "bypassing" kernel?
> I don't see any problem with SO and workaround if that is the only
> way an user can use their device. Why are you expecting every vendor to
> develop quirk? Also I don't see any point of using linked list to
> unnecessarily complicate a simple thing.
Please reread our conversation with Alex, it has answers to both of your
questions.
Thanks
>
> Thanks,
> Amey
Powered by blists - more mailing lists