All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org, me@clifhouck.com
Cc: Bug 1580459 <1580459@bugs.launchpad.net>
Subject: Re: [Qemu-devel] [Bug 1580459] Re: Windows (10?) guest freezes entire host on shutdown if using PCI passthrough
Date: Thu, 7 Jul 2016 15:03:16 -0600	[thread overview]
Message-ID: <20160707150316.0a715b82@t450s.home> (raw)
In-Reply-To: <20160707203415.17948.81896.malone@wampee.canonical.com>

On Thu, 07 Jul 2016 20:34:15 -0000
Clif Houck <me@clifhouck.com> wrote:

> I was also experiencing the host hard locking when shutting down a
> Windows 10 guest with a Nvidia GPU passed-through, but the issue appears
> to be completely solved after switching the card to MSI mode in the
> Windows guest.
> 
> However, I would be interested in understanding *why* using the card in
> line-interrupt mode in the guest causes the host to lockup when the
> guest relinquishes control of the device. Is it a bug in qemu or vfio,
> or even the Linux kernel?
> 
> I don't know if its relevant, but I've noticed when the card is not
> being used by the guest it is listed as MSI: Enable- by lspci,
> suggesting that vfio is keeping the card in line-interrupt mode when not
> in use.
> 

Interrupts are disabled when the card is not in use.  Can you test
whether the following commit fixes the problem:

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=956b56a984ddf10aa69b25318dc04430101beed6

This was added in v4.7-rc2, so it will also be included in anything
newer.  Thanks,

Alex

  reply	other threads:[~2016-07-07 21:03 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11  6:19 [Qemu-devel] [Bug 1580459] [NEW] Windows (10?) guest freezes entire host on shutdown if using PCI passthrough Jimi
2016-05-19 18:07 ` [Qemu-devel] [Bug 1580459] " kachaffeous
2016-05-19 18:18 ` kachaffeous
2016-05-20  0:11 ` Jimi
2016-05-20 16:43 ` kachaffeous
2016-05-20 16:58 ` Jimi
2016-05-20 16:58 ` Jimi
2016-05-28 16:39 ` Gandalf-The-Red
2016-05-28 17:08 ` Jimi
2016-05-28 17:25 ` Gandalf-The-Red
2016-05-28 18:31 ` Gandalf-The-Red
2016-05-28 19:12 ` Jimi
2016-05-28 19:14 ` Jimi
2016-05-29  1:33 ` Chris McCarron
2016-05-29  1:40 ` Chris McCarron
2016-05-29  1:59 ` Jimi
2016-05-29 17:50 ` Chris McCarron
2016-05-29 17:52 ` Chris McCarron
2016-05-29 17:53 ` Chris McCarron
2016-05-29 17:55 ` Chris McCarron
2016-05-29 17:57 ` Chris McCarron
2016-05-29 18:04 ` Chris McCarron
2016-05-29 18:15 ` Jimi
2016-05-29 18:29 ` Chris McCarron
2016-05-31  6:55 ` James Newman
2016-05-31  7:02 ` James Newman
2016-05-31  7:37 ` Jimi
2016-05-31 23:13 ` Chris McCarron
2016-06-01  1:15 ` Jimi
2016-06-05 23:34 ` jimrif
2016-06-06  0:44 ` Jimi
2016-06-06  5:04 ` jimrif
2016-06-06  5:55 ` Chris McCarron
2016-06-06  8:12 ` Jimi
2016-06-06 22:21 ` Chris McCarron
2016-06-06 22:21 ` Chris McCarron
2016-06-06 22:23 ` Chris McCarron
2016-06-06 23:36 ` James Newman
2016-06-07  1:05 ` Jimi
2016-06-12  9:32 ` Peter Maloney
2016-06-14 19:44 ` Jimi
2016-06-15 14:20 ` kachaffeous
2016-06-23  3:32 ` Jimi
2016-06-23  6:17 ` Jimi
2016-06-23 12:05 ` Chris McCarron
2016-06-23 18:25 ` Jimi
2016-06-24  1:16 ` Chris McCarron
2016-06-25  5:57 ` Jimi
2016-06-25 13:10 ` Chris McCarron
2016-07-07 20:34 ` Clif Houck
2016-07-07 21:03   ` Alex Williamson [this message]
2016-07-07 21:45 ` Jimi
2016-07-07 21:46 ` Jimi
2017-02-25 11:04 ` yanman
2017-12-09 18:44 ` john doe
2017-12-09 20:56 ` Clif Houck
2017-12-09 21:30 ` Jimi
2017-12-18 20:04 ` Benjamin
2021-04-22  5:08 ` Thomas Huth
2021-04-22 10:02 ` Chris McCarron
2021-04-22 12:21 ` Jimi
2021-04-23  4:29 ` Thomas Huth

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=20160707150316.0a715b82@t450s.home \
    --to=alex.williamson@redhat.com \
    --cc=1580459@bugs.launchpad.net \
    --cc=me@clifhouck.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.