From: Ryan Harper <ryanh@us.ibm.com>
To: qemu-devel@nongnu.org
Cc: Ryan Harper <ryanh@us.ibm.com>
Subject: [Qemu-devel] [PATCH 0/2] Decouple block device removal from device removal
Date: Mon, 18 Oct 2010 17:17:15 -0500 [thread overview]
Message-ID: <1287440237-14675-1-git-send-email-ryanh@us.ibm.com> (raw)
This patch series decouples the detachment of a block device from the removal
of the backing pci-device. Removal of a hotplugged pci device requires the
guest to respond before qemu tears down the block device. In some cases, the
guest may not respond leaving the guest with continued access to the block
device.
The new monitor command, drive_unplug, will revoke a guests access to the
block device independently of the removal of the pci device.
The first patch adds a new drive find method, the second patch implements the
monitor command and block layer changes.
Signed-off-by: Ryan Harper <ryanh@us.ibm.com>
next reply other threads:[~2010-10-18 22:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 22:17 Ryan Harper [this message]
2010-10-18 22:17 ` [Qemu-devel] [PATCH 1/2] Add drive_get_by_id Ryan Harper
2010-10-19 10:29 ` Stefan Hajnoczi
2010-10-18 22:17 ` [Qemu-devel] [PATCH 2/2] Fix Block Hotplug race with drive_unplug() Ryan Harper
2010-10-19 10:45 ` Stefan Hajnoczi
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=1287440237-14675-1-git-send-email-ryanh@us.ibm.com \
--to=ryanh@us.ibm.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 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).