From: Vadim.Lomovtsev@caviumnetworks.com (Vadim Lomovtsev)
To: linux-arm-kernel@lists.infradead.org
Subject: [v4,0/3] Workaround for bus/slot reset on Cavium cn8xxx root ports
Date: Tue, 12 Sep 2017 02:40:49 -0700 [thread overview]
Message-ID: <20170912094049.GA14111@localhost.localdomain> (raw)
In-Reply-To: <20170908081033.3025-1-jglauber@cavium.com>
Hi all,
Are there any updates on this ?
Comments/objections/acks/nacks ?
WBBR,
Vadim
On Fri, Sep 08, 2017 at 10:10:30AM +0200, Jan Glauber wrote:
> 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.
>
> 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 if bus reset is not possible
>
> drivers/pci/pci.c | 8 ++++++++
> drivers/pci/quirks.c | 8 ++++++++
> 2 files changed, 16 insertions(+)
next prev parent reply other threads:[~2017-09-12 9:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 8:10 [PATCH v4 0/3] Workaround for bus/slot reset on Cavium cn8xxx root ports Jan Glauber
2017-09-08 8:10 ` [PATCH v4 1/3] PCI: Allow PCI_DEV_FLAGS_NO_BUS_RESET to be used on bus device Jan Glauber
2017-09-08 8:10 ` [PATCH v4 2/3] PCI: Avoid bus reset for Cavium cn8xxx root ports Jan Glauber
2017-09-08 8:10 ` [PATCH v4 3/3] PCI: Avoid slot reset if bus reset is not possible Jan Glauber
2017-09-12 9:40 ` Vadim Lomovtsev [this message]
2017-09-20 17:50 ` [v4,0/3] Workaround for bus/slot reset on Cavium cn8xxx root ports Jon Masters
2017-09-20 18:09 ` Alex Williamson
2017-09-21 8:06 ` Jan Glauber
2017-09-26 12:00 ` Jan Glauber
2017-10-11 15:33 ` [PATCH v4 0/3] " Robert Richter
2017-10-11 18:32 ` Bjorn Helgaas
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=20170912094049.GA14111@localhost.localdomain \
--to=vadim.lomovtsev@caviumnetworks.com \
--cc=linux-arm-kernel@lists.infradead.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).