From: Ryan Harper <ryanh@us.ibm.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Anthony Liguori <aliguori@linux.vnet.ibm.com>,
Ryan Harper <ryanh@us.ibm.com>,
Stefan Hajnoczi <stefan.hajnoczi@uk.ibm.com>
Subject: [Qemu-devel] Re: [PATCH 1/2] Implement drive_del to decouple block removal from device removal
Date: Fri, 12 Nov 2010 10:45:00 -0600 [thread overview]
Message-ID: <20101112164500.GP22381@us.ibm.com> (raw)
In-Reply-To: <4CDD6DC6.2050107@redhat.com>
* Kevin Wolf <kwolf@redhat.com> [2010-11-12 10:43]:
> Am 12.11.2010 16:38, schrieb Ryan Harper:
> > Currently device hotplug removal code is tied to device removal via
> > ACPI. All pci devices that are removable via device_del() require the
> > guest to respond to the request. In some cases the guest may not
> > respond leaving the device still accessible to the guest. The management
> > layer doesn't currently have a reliable way to revoke access to host
> > resource in the presence of an uncooperative guest.
> >
> > This patch implements a new monitor command, drive_del, which
> > provides an explicit command to revoke access to a host block device.
> >
> > drive_del first quiesces the block device (qemu_aio_flush;
> > bdrv_flush() and bdrv_close()). This prevents further IO from being
> > submitted against the host device. Finally, drive_del cleans up
> > pointers between the drive object (host resource) and the device
> > object (guest resource).
> >
> > Signed-off-by: Ryan Harper <ryanh@us.ibm.com>
> > ---
> > blockdev.c | 39 +++++++++++++++++++++++++++++++++++++++
> > blockdev.h | 1 +
> > hmp-commands.hx | 18 ++++++++++++++++++
> > 3 files changed, 58 insertions(+), 0 deletions(-)
> >
> > diff --git a/blockdev.c b/blockdev.c
> > index 6cb179a..f6ac439 100644
> > --- a/blockdev.c
> > +++ b/blockdev.c
> > @@ -14,6 +14,8 @@
> > #include "qemu-option.h"
> > #include "qemu-config.h"
> > #include "sysemu.h"
> > +#include "hw/qdev.h"
> > +#include "block_int.h"
> >
> > static QTAILQ_HEAD(drivelist, DriveInfo) drives = QTAILQ_HEAD_INITIALIZER(drives);
> >
> > @@ -597,3 +599,40 @@ int do_change_block(Monitor *mon, const char *device,
> > }
> > return monitor_read_bdrv_key_start(mon, bs, NULL, NULL);
> > }
> > +
> > +int do_drive_del(Monitor *mon, const QDict *qdict, QObject **ret_data)
> > +{
> > + const char *id = qdict_get_str(qdict, "id");
> > + BlockDriverState *bs;
> > + BlockDriverState **ptr;
> > + Property *prop;
> > +
> > + bs = bdrv_find(id);
> > + if (!bs) {
> > + qerror_report(QERR_DEVICE_NOT_FOUND, id);
> > + return -1;
> > + }
> > +
> > + /* quiesce block driver; prevent further io */
> > + qemu_aio_flush();
> > + bdrv_flush(bs);
> > + bdrv_close(bs);
> > +
> > + /* clean up guest state from pointing to host resource by
> > + * finding and removing DeviceState "drive" property */
> > + for (prop = bs->peer->info->props; prop && prop->name; prop++) {
> > + if (prop->info->type == PROP_TYPE_DRIVE) {
> > + ptr = qdev_get_prop_ptr(bs->peer, prop);
> > + if ((*ptr) == bs) {
> > + bdrv_detach(bs, bs->peer);
> > + *ptr = NULL;
> > + break;
> > + }
> > + }
> > + }
> > +
> > + /* clean up host side */
> > + drive_uninit(drive_get_by_blockdev(bs));
> > +
> > + return 0;
> > +}
> > diff --git a/blockdev.h b/blockdev.h
> > index 653affc..2a0559e 100644
> > --- a/blockdev.h
> > +++ b/blockdev.h
> > @@ -51,5 +51,6 @@ int do_eject(Monitor *mon, const QDict *qdict, QObject **ret_data);
> > int do_block_set_passwd(Monitor *mon, const QDict *qdict, QObject **ret_data);
> > int do_change_block(Monitor *mon, const char *device,
> > const char *filename, const char *fmt);
> > +int do_drive_del(Monitor *mon, const QDict *qdict, QObject **ret_data);
> >
> > #endif
> > diff --git a/hmp-commands.hx b/hmp-commands.hx
> > index e5585ba..d6dc18c 100644
> > --- a/hmp-commands.hx
> > +++ b/hmp-commands.hx
> > @@ -68,6 +68,24 @@ Eject a removable medium (use -f to force it).
> > ETEXI
> >
> > {
> > + .name = "drive_del",
> > + .args_type = "id:s",
> > + .params = "device",
> > + .help = "remove host block device",
> > + .user_print = monitor_user_noop,
> > + .mhandler.cmd_new = do_drive_del,
> > + },
> > +
> > +STEXI
> > +@item delete @var{device}
> > +@findex delete
>
> I think this should be @item drive_del and @findex drive_del.
Yep.
>
> Kevin
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com
next prev parent reply other threads:[~2010-11-12 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 15:38 [Qemu-devel] [PATCH 0/2] v7 Decouple block device removal from device removal Ryan Harper
2010-11-12 15:38 ` [Qemu-devel] [PATCH 1/2] Implement drive_del to decouple block " Ryan Harper
2010-11-12 16:27 ` Markus Armbruster
2010-11-12 16:39 ` [Qemu-devel] " Kevin Wolf
2010-11-12 16:45 ` Ryan Harper [this message]
2010-11-12 15:38 ` [Qemu-devel] [PATCH 2/2] Add qmp version of drive_del Ryan Harper
2010-11-12 16:28 ` [Qemu-devel] [PATCH 0/2] v7 Decouple block device removal from device removal Markus Armbruster
2010-11-12 16:46 ` Kevin Wolf
2010-11-12 17:41 ` Markus Armbruster
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=20101112164500.GP22381@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefan.hajnoczi@uk.ibm.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 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.