From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, bhelgaas@google.com,
linux@eikelenboom.it
Subject: [PATCH v4] Fixes for PCI backend for 3.19
Date: Fri, 21 Nov 2014 17:17:44 -0500 [thread overview]
Message-ID: <1416608271-18931-1-git-send-email-konrad.wilk@oracle.com> (raw)
Hey,
The last time I posted these patches: https://lkml.org/lkml/2014/7/8/533
was so long ago that I don't even remember most comments. The only
one that stuck in mind was David's recommendation to add a new PCI API
call and use that. See patch #6 and #7.
The original posting (v3) had an extra patch that would do slot and
bus reset using do_flr SysFS attribute. I will revisit that once I am
done with this patchset.
I also seem to have had in my a bunch of 'SoB' from David - which
makes no sense - unless I pulled from his tree. Anyhow wherewere
I saw them I removed them.
Please take a look and comment. If I missed some comment from months
ago hopefully the new version has clarified them.
drivers/pci/pci.c | 5 +--
drivers/xen/xen-pciback/passthrough.c | 14 ++++++--
drivers/xen/xen-pciback/pci_stub.c | 60 ++++++++++++++++++++++-------------
drivers/xen/xen-pciback/pciback.h | 7 ++--
drivers/xen/xen-pciback/vpci.c | 14 ++++++--
drivers/xen/xen-pciback/xenbus.c | 4 +--
include/linux/device.h | 5 +++
include/linux/pci.h | 2 ++
8 files changed, 76 insertions(+), 35 deletions(-)
Konrad Rzeszutek Wilk (7):
xen/pciback: Don't deadlock when unbinding.
driver core: Provide an wrapper around the mutex to do lockdep warnings
xen/pciback: Include the domain id if removing the device whilst still in use
xen/pciback: Print out the domain owning the device.
xen/pciback: Remove tons of dereferences
PCI: Expose pci_load_saved_state for public consumption.
xen/pciback: Restore configuration space when detaching from a guest.
next reply other threads:[~2014-11-21 22:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 22:17 Konrad Rzeszutek Wilk [this message]
2014-11-21 22:17 ` [PATCH v4 1/7] xen/pciback: Don't deadlock when unbinding Konrad Rzeszutek Wilk
2014-11-21 22:17 ` [PATCH v4 2/7] driver core: Provide an wrapper around the mutex to do lockdep warnings Konrad Rzeszutek Wilk
2014-11-21 22:17 ` [PATCH v4 3/7] xen/pciback: Include the domain id if removing the device whilst still in use Konrad Rzeszutek Wilk
2014-11-21 22:17 ` [PATCH v4 4/7] xen/pciback: Print out the domain owning the device Konrad Rzeszutek Wilk
2014-11-21 22:17 ` [PATCH v4 5/7] xen/pciback: Remove tons of dereferences Konrad Rzeszutek Wilk
2014-11-21 22:17 ` [PATCH v4 6/7] PCI: Expose pci_load_saved_state for public consumption Konrad Rzeszutek Wilk
2014-11-21 22:17 ` [PATCH v4 7/7] xen/pciback: Restore configuration space when detaching from a guest Konrad Rzeszutek Wilk
2014-12-01 14:14 ` [Xen-devel] " David Vrabel
2014-12-01 21:59 ` Konrad Rzeszutek Wilk
2014-12-02 23:11 ` Boris Ostrovsky
2014-12-03 15:52 ` Konrad Rzeszutek Wilk
2014-12-02 10:10 ` [Xen-devel] [PATCH v4] Fixes for PCI backend for 3.19 Jan Beulich
2014-12-02 15:05 ` Konrad Rzeszutek Wilk
2014-12-02 15:09 ` Jan Beulich
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=1416608271-18931-1-git-send-email-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xenproject.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).