From: Jan Glauber <jglauber@cavium.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org,
Alex Williamson <alex.williamson@redhat.com>,
linux-kernel@vger.kernel.org, david.daney@cavium.com,
Jon Masters <jcm@redhat.com>,
Robert Richter <robert.richter@cavium.com>,
linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
Jan Glauber <jglauber@cavium.com>
Subject: [PATCH v3 0/3] Workaround for bus/slot reset on Cavium cn8xxx root ports
Date: Wed, 30 Aug 2017 16:24:51 +0200 [thread overview]
Message-ID: <20170830142454.10971-1-jglauber@cavium.com> (raw)
Using vfio-pci on a combination of cn8xxx and some PCI devices results in
a kernel panic. This is triggered by issuing a bus or a slot reset
on the PCI device.
The solution is to prevent the reset. I've dropped the vfio patch from the
previous series as vfio-pci already checks in the reset path for
pci_bus_resetable() and pci_slot_resetable().
With this series both checks indicate that the reset is not possible
preventing the kernel panic.
David Daney (2):
PCI: Allow PCI_DEV_FLAGS_NO_BUS_RESET to be used on bus device
PCI: Avoid bus reset for Cavium cn8xxx root ports
Jan Glauber (1):
PCI: Avoid slot reset for Cavium cn8xxx root ports
drivers/pci/pci.c | 4 ++++
drivers/pci/quirks.c | 24 ++++++++++++++++++++++++
2 files changed, 28 insertions(+)
--
2.9.0.rc0.21.g7777322
next reply other threads:[~2017-08-30 14:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 14:24 Jan Glauber [this message]
2017-08-30 14:24 ` [PATCH v3 1/3] PCI: Allow PCI_DEV_FLAGS_NO_BUS_RESET to be used on bus device Jan Glauber
2017-08-30 14:24 ` [PATCH v3 2/3] PCI: Avoid bus reset for Cavium cn8xxx root ports Jan Glauber
2017-08-30 14:24 ` [PATCH v3 3/3] PCI: Avoid slot " Jan Glauber
2017-08-30 14:40 ` Alex Williamson
2017-08-31 9:40 ` Jan Glauber
2017-08-31 16:01 ` Alex Williamson
2017-09-07 7:40 ` Jan Glauber
2017-09-07 7:49 ` Jan Glauber
2017-09-07 16:52 ` Alex Williamson
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=20170830142454.10971-1-jglauber@cavium.com \
--to=jglauber@cavium.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=david.daney@cavium.com \
--cc=jcm@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robert.richter@cavium.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;
as well as URLs for NNTP newsgroup(s).