From: Luiz Capitulino <lcapitulino@redhat.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: Re: [Qemu-devel] Re: [PATCH 0/2] v8 Decouple block device removal from device removal
Date: Tue, 16 Nov 2010 12:36:55 -0200 [thread overview]
Message-ID: <20101116123655.3f906d01@doriath> (raw)
In-Reply-To: <4CE28EA8.6090704@redhat.com>
On Tue, 16 Nov 2010 15:01:12 +0100
Kevin Wolf <kwolf@redhat.com> wrote:
> Am 16.11.2010 14:51, schrieb Luiz Capitulino:
> > On Fri, 12 Nov 2010 18:38:57 +0100
> > Kevin Wolf <kwolf@redhat.com> wrote:
> >
> >> Am 12.11.2010 18:07, schrieb Ryan Harper:
> >>> details, details, v8
> >>>
> >>> 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. Mgmt layer doesn't have a
> >>> reliable method to force a disconnect.
> >>>
> >>> The new monitor command, drive_del, will revoke a guests access to the
> >>> block device independently of the removal of the pci device.
> >>>
> >>> The first patch implements drive_del, the second patch implements the
> >>> qmp version of the monitor command.
> >>>
> >>> Changes since v7:
> >>> - Fixed up doc strings (delete -> drive_del)
> >>> Changes since v6:
> >>> - Updated patch description
> >>> - Dropped bdrv_unplug and inlined in drive_del
> >>> - Explicitly invoke drive_uninit()
> >>> Changes since v5:
> >>> - Removed dangling pointers in guest and host state. This ensures things like
> >>> info block no longer displays the deleted drive; though info pci will
> >>> continue to display the pci device until the guest responds to the removal
> >>> request.
> >>> - Renamed drive_unplug -> drive_del
> >>> Changes since v4:
> >>> - Droppped drive_get_by_id patch and use bdrv_find() instead
> >>> - Added additional details about drive_unplug to hmp/qmp interface
> >>>
> >>> Changes since v3:
> >>> - Moved QMP command for drive_unplug() to separate patch
> >>>
> >>> Changes since v2:
> >>> - Added QMP command for drive_unplug()
> >>>
> >>> Changes since v1:
> >>> - CodingStyle fixes
> >>> - Added qemu_aio_flush() to bdrv_unplug()
> >>>
> >>> Signed-off-by: Ryan Harper <ryanh@us.ibm.com>
> >>
> >> Thanks, applied both to the block branch.
> >
> > I guess the conclusion was that we don't want the new command
> > in QMP?
> >
> > http://lists.gnu.org/archive/html/qemu-devel/2010-11/msg01084.html
>
> If you compare the time of these mails, Markus sent his mail only a few
> minutes after I had applied the patches and posted this.
Oh, didn't notice that.
> Ryan split the patch in two parts only to allow dropping the QMP part if
> we decided so, so I think he'll agree. I'm going to drop the second
> patch from my queue again before I send a pull request.
Ok, thanks.
next prev parent reply other threads:[~2010-11-16 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 17:07 [Qemu-devel] [PATCH 0/2] v8 Decouple block device removal from device removal Ryan Harper
2010-11-12 17:07 ` [Qemu-devel] [PATCH 1/2] Implement drive_del to decouple block " Ryan Harper
2010-11-12 17:07 ` [Qemu-devel] [PATCH 2/2] Add qmp version of drive_del Ryan Harper
2010-11-12 17:38 ` [Qemu-devel] Re: [PATCH 0/2] v8 Decouple block device removal from device removal Kevin Wolf
2010-11-16 13:51 ` Luiz Capitulino
2010-11-16 14:01 ` Kevin Wolf
2010-11-16 14:36 ` Luiz Capitulino [this message]
2010-11-16 14:58 ` Ryan Harper
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=20101116123655.3f906d01@doriath \
--to=lcapitulino@redhat.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=ryanh@us.ibm.com \
--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 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).