From: Alex Williamson <alex.williamson@redhat.com>
To: alex.williamson@redhat.com
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [PATCH 0/2] vfio: Add signal flush and log more verbosely
Date: Tue, 14 Apr 2015 12:14:39 -0600 [thread overview]
Message-ID: <20150414180228.6081.10459.stgit@gimli.home> (raw)
Fix an issue where signals are not flushed causing our interruptible
wait_event to go into a tight loop once a signal is received. Also
add more logging throughout. We have no -EBUSY return path for a
driver remove request and it's confusing to users when tasks get
blocked waiting for the device to release. Provide more clues what's
happening. Thanks,
Alex
---
Alex Williamson (2):
vfio: Flush signals on device request interruption
vfio-pci: Log device requests more verbosely
drivers/vfio/pci/vfio_pci.c | 8 +++++++-
drivers/vfio/vfio.c | 13 ++++++++++---
2 files changed, 17 insertions(+), 4 deletions(-)
next reply other threads:[~2015-04-14 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 18:14 Alex Williamson [this message]
2015-04-14 18:14 ` [PATCH 1/2] vfio: Flush signals on device request interruption Alex Williamson
2015-04-14 18:14 ` [PATCH 2/2] vfio-pci: Log device requests more verbosely 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=20150414180228.6081.10459.stgit@gimli.home \
--to=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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