All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] monitor: allow device to be ejected if no disk is inserted
Date: Mon, 07 Jun 2010 14:53:37 +0200	[thread overview]
Message-ID: <4C0CEBD1.2050809@redhat.com> (raw)
In-Reply-To: <20100607124345.GV14354@blackpad.lan.raisama.net>

Am 07.06.2010 14:43, schrieb Eduardo Habkost:
> On Mon, Jun 07, 2010 at 02:19:28PM +0200, Markus Armbruster wrote:
>> Kevin Wolf <kwolf@redhat.com> writes:
>>> Am 02.06.2010 00:12, schrieb Eduardo Habkost:
>>>> The first eject command didn't work because the is_inserted() check
>>>> failed.
>>>
>>> But does it really make a difference? The guest should not see a medium
>>> before and it should not see one afterwards.
> 
> It does

How that? Even if the host device is still connected, but no there's no
medium in it, the guest shouldn't see a medium (I mean, which medium
should it see if there is none?)

> as the whole purpose of the "eject" command is to disconnect
> the block device from the host backing file.
> 
> Awful naming, I agree, but that's the expected semantics of the command.

If it's just meant to say "disconnect the image" it's a really bad name.
Luiz, can we please get rid of it before QMP becomes stable?

> If we want to solve the naming confusion, this could be implemented as a
> special case of the "change" command instead, and then the "eject"
> command could be deprecated.

Sounds much better, though it was suggested to deprecate "change"
itself, too. ;-)

Kevin

  reply	other threads:[~2010-06-07 12:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 22:12 [Qemu-devel] [PATCH] monitor: allow device to be ejected if no disk is inserted Eduardo Habkost
2010-06-04 18:01 ` Luiz Capitulino
2010-06-07  6:57   ` Markus Armbruster
2010-06-07 11:18 ` Kevin Wolf
2010-06-07 12:19   ` Markus Armbruster
2010-06-07 12:43     ` Eduardo Habkost
2010-06-07 12:53       ` Kevin Wolf [this message]
2010-06-07 13:18         ` 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=4C0CEBD1.2050809@redhat.com \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=lcapitulino@redhat.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.