From: Matthew Ruffell <matthew.ruffell@canonical.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-pci@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org,
nathan.langford@xcelesunifiedtechnologies.com
Subject: Re: [PROBLEM] Frequently get "irq 31: nobody cared" when passing through 2x GPUs that share same pci switch via vfio
Date: Tue, 5 Oct 2021 18:02:24 +1300 [thread overview]
Message-ID: <2fadf33d-8487-94c2-4460-2a20fdb2ea12@canonical.com> (raw)
In-Reply-To: <20210915103235.097202d2.alex.williamson@redhat.com>
Hi Alex,
Have you had an opportunity to have a look at this a bit deeper?
On 16/09/21 4:32 am, Alex Williamson wrote:
>
> Adding debugging to the vfio-pci interrupt handler, it's correctly
> deferring the interrupt as the GPU device is not identifying itself as
> the source of the interrupt via the status register. In fact, setting
> the disable INTx bit in the GPU command register while the interrupt
> storm occurs does not stop the interrupts.
>
> The interrupt storm does seem to be related to the bus resets, but I
> can't figure out yet how multiple devices per switch factors into the
> issue. Serializing all bus resets via a mutex doesn't seem to change
> the behavior.
>
> I'm still investigating, but if anyone knows how to get access to the
> Broadcom datasheet or errata for this switch, please let me know.
We have managed to obtain a recent errata for this switch, and it
doesn't
mention any interrupt storms with nested switches. What would
I be looking for
in the errata? I cannot share our copy, sorry.
Is there anything that we can do to help?
Thanks,
Matthew
next prev parent reply other threads:[~2021-10-05 5:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d4084296-9d36-64ec-8a79-77d82ac6d31c@canonical.com>
2021-09-14 16:43 ` [PROBLEM] Frequently get "irq 31: nobody cared" when passing through 2x GPUs that share same pci switch via vfio Alex Williamson
2021-09-15 4:44 ` Matthew Ruffell
2021-09-15 16:32 ` Alex Williamson
2021-09-16 5:13 ` Matthew Ruffell
2021-10-05 5:02 ` Matthew Ruffell [this message]
2021-10-05 23:13 ` Alex Williamson
2021-10-12 4:58 ` Matthew Ruffell
2021-10-12 20:05 ` Alex Williamson
2021-10-12 22:35 ` Matthew Ruffell
2021-11-01 4:35 ` Matthew Ruffell
2021-11-04 22:05 ` Alex Williamson
2021-11-24 5:52 ` Matthew Ruffell
2021-11-29 17:56 ` 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=2fadf33d-8487-94c2-4460-2a20fdb2ea12@canonical.com \
--to=matthew.ruffell@canonical.com \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nathan.langford@xcelesunifiedtechnologies.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