From: Sinan Kaya <okaya@kernel.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Dennis Dalessandro <dennis.dalessandro@intel.com>,
Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: RFC on PCI Device Lock
Date: Tue, 4 Sep 2018 18:12:16 -0700 [thread overview]
Message-ID: <17720f56-2caa-2d2e-b655-867debf55934@kernel.org> (raw)
In-Reply-To: <20180904165202.4e5bb59d@t450s.home>
On 9/4/2018 3:52 PM, Alex Williamson wrote:
> I won't deny that we're getting a little sloppy with some of the reset
> interfaces and I'd love to solve the device lock issue more generally,
> but trying to abstract slot vs bus and hide the lower level interfaces
> from drivers doesn't seem like it's really working here. Thanks,
Counter argument is that drivers need to know about bus/slot distinction
and call two different API for hotplug capable systems. I think that's
too much to ask.
The motivation for original patch was that hotplug information was leaking
and we could do a better job about it. But, you are right; I partially
covered VFIO needs as it seemed to be doing more work than a simple
reset due to ownership dependencies.
next prev parent reply other threads:[~2018-09-05 5:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 23:03 RFC on PCI Device Lock Sinan Kaya
2018-09-04 22:52 ` Alex Williamson
2018-09-05 1:12 ` Sinan Kaya [this message]
2018-09-05 2:46 ` Alex Williamson
2018-09-05 3:09 ` Sinan Kaya
2018-09-05 3:41 ` Sinan Kaya
2018-09-05 4:13 ` Alex Williamson
2018-09-05 14:26 ` Sinan Kaya
2018-09-05 17:37 ` Alex Williamson
2018-09-05 17:50 ` Sinan Kaya
2018-09-05 2:59 ` Dennis Dalessandro
2018-09-05 3:10 ` Sinan Kaya
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=17720f56-2caa-2d2e-b655-867debf55934@kernel.org \
--to=okaya@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=dennis.dalessandro@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).