From: Kevin Wolf <kwolf@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Programmingkid <programmingkidx@gmail.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/3] ui/cocoa.m: Adds device menu items to Machine menu
Date: Mon, 18 May 2015 15:24:55 +0200 [thread overview]
Message-ID: <20150518132455.GE5999@noname.str.redhat.com> (raw)
In-Reply-To: <CAFEAcA9gxKk6vLAJRim6hScVFU=Vsiu39Lbh3bOODrhnNTJdNw@mail.gmail.com>
Am 17.05.2015 um 00:21 hat Peter Maydell geschrieben:
> On 11 May 2015 at 23:16, Programmingkid <programmingkidx@gmail.com> wrote:
> > Adds all removable devices to the Machine menu as a Change and Eject menu
> > item pair.
> > ide-cd0 would have a "Change ide-cd0..." and "Eject ide-cd0" menu items.
> >
> > Signed-off-by: John Arbuckle <programmingkidx@gmail.com>
>
> Kevin -- is there a block layer API for a UI to be informed
> of hotplugged/unplugged block devices so we can update our menu
> entries as removable devices appear or disappear?
I don't think we have that today. Also, I'm not sure if that should be
block device backends or actual block devices. If you mean the former,
then backends that are not connected to a device yet will appear; if you
mean the latter, you should probably ask qdev/QOM rather than the block
layer.
Also, media change is another thing that you may want to be informed of.
The qdev device and the backend stay the same, but the file name
changes. We have notifiers for the device emulation on media change, but
we don't have anything for the UI. (Or can the UI use QMP events?)
If we need something, we can probably add it, though.
Kevin
prev parent reply other threads:[~2015-05-18 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 22:16 [Qemu-devel] [PATCH 2/3] ui/cocoa.m: Adds device menu items to Machine menu Programmingkid
2015-05-16 22:21 ` Peter Maydell
2015-05-18 13:24 ` Kevin Wolf [this message]
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=20150518132455.GE5999@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.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).