From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Thomas Huth <thuth@redhat.com>,
Qemu-block <qemu-block@nongnu.org>,
Bin Meng <bin.meng@windriver.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Hao Wu <wuhaotsh@google.com>,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: does drive_get_next(IF_NONE) make sense?
Date: Mon, 15 Nov 2021 16:28:39 +0100 [thread overview]
Message-ID: <874k8digk8.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAFEAcA_N6r81-0K6Y-qCdzyx67jzsSZnh-R8vYh2ZGZtAHpAAQ@mail.gmail.com> (Peter Maydell's message of "Mon, 15 Nov 2021 13:31:52 +0000")
Peter Maydell <peter.maydell@linaro.org> writes:
> On Mon, 15 Nov 2021 at 13:24, Kevin Wolf <kwolf@redhat.com> wrote:
>> Same question as for Hao Wu's series: Wouldn't the proper solution be to
>> add a drive property to the machine type?
>>
>> If you can't use -blockdev, it's not done right.
>
> Is there an example of "doing it right" for built-in-to-the-machine
> devices?
>
> (My experience with the new-style options is that almost
> always they're designed for x86 where the device they're attached
> to is also created on the command line, and then handling of boards
> where the device is builtin is either an afterthought or forgotten.
> See also -netdev, where it took forever for built-in-ethernet to
> be usable.)
I'm afraid the situation for onboard block devices is far worse than it
ever was for NICs. See my reply "On configuring onboard block devices
with -blockdev" to Kevin's other message on the topic.
To be fair, improving onboard device configuration is *hard*. Our
general device configuration interface doesn't cover them, and we've so
far failed finding a general solution. Without one, we're drowning in
the sheer number of boards and onboard devices. Which is ever growing.
prev parent reply other threads:[~2021-11-15 15:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 15:14 does drive_get_next(IF_NONE) make sense? Peter Maydell
2021-11-02 15:28 ` Philippe Mathieu-Daudé
2021-11-03 8:41 ` Markus Armbruster
2021-11-03 9:19 ` Thomas Huth
2021-11-12 13:33 ` Markus Armbruster
2021-11-14 17:16 ` Peter Maydell
2021-11-15 5:31 ` Markus Armbruster
2021-11-15 7:12 ` Alistair Francis
2021-11-15 16:09 ` Thomas Huth
2021-11-18 13:03 ` Alistair Francis
2021-11-18 13:20 ` Peter Maydell
2021-11-15 13:24 ` Kevin Wolf
2021-11-15 13:31 ` Peter Maydell
2021-11-15 15:13 ` Kevin Wolf
2021-11-15 15:28 ` Markus Armbruster [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=874k8digk8.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wuhaotsh@google.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 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.