From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106111] [GPU Passthrough]GPU (Polaris) not reinitialized with Linux VM (Reset bug)
Date: Tue, 17 Apr 2018 22:55:23 +0000 [thread overview]
Message-ID: <bug-106111-502-jnBFzeJHJI@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106111-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1876 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106111
--- Comment #2 from Alex Williamson <alex.williamson@redhat.com> ---
The IOMMU looks to be unhappy first:
[ 40.201258] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x19@0x270
[ 40.201271] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x1b@0x2d0
[ 40.201279] vfio_ecap_init: 0000:0a:00.0 hiding ecap 0x1e@0x370
[ 159.958402] AMD-Vi: Completion-Wait loop timed out
[ 160.118777] AMD-Vi: Completion-Wait loop timed out
[ 160.799864] AMD-Vi: Event logged [
[ 160.799868] IOTLB_INV_TIMEOUT device=0a:00.0 address=0x000000043e8e8550]
[ 160.799872] AMD-Vi: Event logged [
[ 160.799874] IOTLB_INV_TIMEOUT device=0a:00.0 address=0x000000043e8e8570]
[ 160.799876] AMD-Vi: Event logged [
[ 160.799878] IOTLB_INV_TIMEOUT device=0a:00.0 address=0x000000043e8e8590]
[ 161.801729] AMD-Vi: Event logged [
[ 161.801732] IOTLB_INV_TIMEOUT device=0a:00.0 address=0x000000043e8e85e0]
[ 180.096365] AMD-Vi: Completion-Wait loop timed out
[ 180.256758] AMD-Vi: Completion-Wait loop timed out
[ 180.417182] AMD-Vi: Completion-Wait loop timed out
[ 180.577636] AMD-Vi: Completion-Wait loop timed out
Can you try a v4.17-rc1 kernel? Specifically, these two updates:
6bd06f5a486c vfio/type1: Adopt fast IOTLB flush interface when unmap IOVAs
eb5ecd1a40e2 iommu/amd: Add support for fast IOTLB flushing
Something about AMD GPUs get unhappy if the IOMMU sends out too many
invalidations and the above two patches can reduce the number of those
invalidations by up to a factor of 512.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6bd06f5a486c06023a618a86e8153b91d26f75f4
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb5ecd1a40e2098f805fb63cb07817ac48826e40
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2997 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-17 22:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 22:29 [Bug 106111] [GPU Passthrough]GPU (Polaris) not reinitialized with Linux VM (Reset bug) bugzilla-daemon
2018-04-17 22:30 ` bugzilla-daemon
2018-04-17 22:55 ` bugzilla-daemon [this message]
2018-04-18 6:11 ` bugzilla-daemon
2018-04-18 16:13 ` bugzilla-daemon
2018-04-18 16:33 ` bugzilla-daemon
2018-08-18 8:31 ` bugzilla-daemon
2018-09-14 10:30 ` bugzilla-daemon
2019-11-19 8:35 ` bugzilla-daemon
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=bug-106111-502-jnBFzeJHJI@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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