From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: peter.maydell@linaro.org, peter.crosthwaite@xilinx.com,
qemu-devel@nongnu.org, michael@walle.cc,
edgar.iglesias@gmail.com, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH for-2.3 0/3] Contain drive_get() misuse
Date: Tue, 24 Mar 2015 15:50:35 +0100 [thread overview]
Message-ID: <551179BB.4040201@redhat.com> (raw)
In-Reply-To: <877fu68ssm.fsf@blackfin.pond.sub.org>
On 24/03/2015 13:48, Markus Armbruster wrote:
> Use of -drive if=floppy with onboard pc87312 (machine "prep") shouldn't
> be affected. Likewise for connecting onboard m25p80-generic derivatives
> with if=mtd drives, or onboard ssi-sd with if=sd.
Exactly.
> Weird usage similar to the one you caught in time for sdhci-pci (--drive
> if=sd --device sdhci-pci) would break. It's possible when the target
> has the device, and the machine type has a suitable bus.
>
> * pc87312
>
> Depends on CONFIG_PC87312, set in {ppc,ppc64}-softmmu.mak.
>
> Requires an ISA bus. I believe "prep" is the only machine providing
> one.
You can add one with -device i82378. Actually used in
tests/endianness-test.c, hence I guess supported.
> If Andreas agrees, I can set cannot_instantiate_with_device_add_yet
> for pc87312 now.
Could do that, could also decide that "-device i82378 -device pc87312"
is a valid way to add all the legacy crap to a PCI machine. In which
case supporting "-drive if=floppy" is a weird feature but it's also hard
to call it a bug.
The difference with other devices is that you can only add it once.
It's a big difference.
> * ssi-sd
>
> I guess we want to document that --device ssi-sd will at some point
> cease to auto-connect to the next available if=sd drive and require
> the usual drive property instead. Okay?
>
> * m25p80-generic
>
> Document just like ssi-sd.
Ack for these two. Boards can still hook -drive if={sd,mtd} to them,
but (hypothetical) users would have to switch to -drive if=none.
Paolo
> [...]
>> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
>
> Thanks!
>
next prev parent reply other threads:[~2015-03-24 14:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 19:09 [Qemu-devel] [PATCH for-2.3 0/3] Contain drive_get() misuse Markus Armbruster
2015-03-23 19:09 ` [Qemu-devel] [PATCH for-2.3 1/3] hw: Mark devices misusing drive_get(), drive_get_next() FIXME Markus Armbruster
2015-03-23 19:09 ` [Qemu-devel] [PATCH for-2.3 2/3] sdhci: Make device "sdhci-pci" unavailable with -device Markus Armbruster
2015-03-23 19:13 ` Peter Maydell
2015-03-23 20:43 ` Markus Armbruster
2015-03-23 19:09 ` [Qemu-devel] [PATCH for-2.3 3/3] sysbus: Contain drive_get_next() misuse Markus Armbruster
2015-03-24 10:22 ` [Qemu-devel] [PATCH for-2.3 0/3] Contain drive_get() misuse Paolo Bonzini
2015-03-24 12:48 ` Markus Armbruster
2015-03-24 14:50 ` Paolo Bonzini [this message]
2015-03-24 15:18 ` Markus Armbruster
2015-03-24 16:20 ` Paolo Bonzini
2015-03-24 20:03 ` Markus Armbruster
2015-03-24 20:13 ` Paolo Bonzini
2015-03-25 10:23 ` Markus Armbruster
2015-03-25 14:26 ` 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=551179BB.4040201@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=michael@walle.cc \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--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).