From: "Daniel P. Berrange" <berrange@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: aliguori@us.ibm.com, hpoussin@reactos.org,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 2/2] Split fdd devices off the floppy controller
Date: Mon, 14 May 2012 09:50:41 +0100 [thread overview]
Message-ID: <20120514085041.GC9942@redhat.com> (raw)
In-Reply-To: <4FB0C6A7.2040308@redhat.com>
On Mon, May 14, 2012 at 10:47:35AM +0200, Kevin Wolf wrote:
> Am 11.05.2012 17:22, schrieb Markus Armbruster:
> > For historical reasons, and unlike other block devices, our floppy
> > devices isa-fdc, sysbus-fdc and SUNW,fdtwo integrate the controller
> > and the drive(s) in a single qdev. This makes them weird: we need
> > -global to set up floppy drives, unlike every other optional device.
>
> I like the idea of splitting the drives from the controller. In fact, I
> think we could even try to split them into a separate hw/fdd.c
>
> > Unfortunately, eliding the qbus means I can't make the floppy disk a
> > qdev (sub-class of TYPE_DEVICE), because qdevs can only connect to a
> > qbus. Anthony tells me that restriction is gone in his latest QOM
> > series.
> >
> > Since it's not a qdev, -device fdd does not work. Pity, because it
> > defeats the stated purpose of making floppy disk drives work like
> > other existing optional devices.
>
> As long as this is true, committing a patch like this doesn't help a
> lot, so I hope Anthony's patches will go in before this is ready.
>
> > Note: I *break* -global isa-fdc.driveA=... The properties are simply
> > gone. Fixable if we need backwards compatibility there.
>
> We might need it, I seem to remember that libvirt uses it.
Yes, since we had no other way to configure floppys, we used the -global
options. I welcome a move to bring floppys into line with other disks,
but would like us to have a little bit of overlap where -global still
works, before finally being removed in a later release.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2012-05-14 8:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 15:22 [Qemu-devel] [RFC PATCH 0/2] Split fdd devices off the floppy controller Markus Armbruster
2012-05-11 15:22 ` [Qemu-devel] [RFC PATCH 1/2] Un-inline fdctrl_init_isa() Markus Armbruster
2012-05-14 13:32 ` Anthony Liguori
2012-05-14 13:45 ` Kevin Wolf
2012-05-11 15:22 ` [Qemu-devel] [RFC PATCH 2/2] Split fdd devices off the floppy controller Markus Armbruster
2012-05-14 8:47 ` Kevin Wolf
2012-05-14 8:50 ` Daniel P. Berrange [this message]
2012-05-14 11:58 ` Andreas Färber
2012-05-14 12:09 ` Kevin Wolf
2012-05-16 20:09 ` Markus Armbruster
2012-05-14 13:42 ` Anthony Liguori
2012-05-16 20:30 ` Markus Armbruster
2012-05-24 16:36 ` Markus Armbruster
2012-05-11 15:24 ` [Qemu-devel] [RFC PATCH 0/2] " 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=20120514085041.GC9942@redhat.com \
--to=berrange@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=hpoussin@reactos.org \
--cc=kwolf@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 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).