From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Laszlo Ersek <lersek@redhat.com>
Cc: gsomlo@gmail.com, "Gabriel L. Somlo" <somlo@cmu.edu>,
matt.fleming@intel.com, kraxel@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V4 4/4] fw_cfg: insert fw_cfg file blobs via qemu cmdline
Date: Mon, 01 Jun 2015 11:01:23 +0200 [thread overview]
Message-ID: <556C1F63.1090605@redhat.com> (raw)
In-Reply-To: <20150601092645-mutt-send-email-mst@redhat.com>
On 01/06/2015 09:28, Michael S. Tsirkin wrote:
> > I don't feel overly strongly about it; just "mechanism, not policy"
> > looks like a good tradition (well, good excuse anyway).
>
> Most users never see warnings. We ship it, we support it.
> If we don't want to support it, let's not ship it.
Then we should rm -rf half of QEMU. :)
Seriously, I agree wholeheartedly with not baking policy into QEMU. A
lot of QEMU command-line hacking really is just a shortcut to avoid
continuous recompilation. I don't think it's reasonable to expect that
it constitutes a stable API.
Paolo
next prev parent reply other threads:[~2015-06-01 9:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 15:21 [Qemu-devel] [PATCH V4 0/4] fw-cfg: cleanup and user-provided command line blobs Gabriel L. Somlo
2015-04-29 15:21 ` [Qemu-devel] [PATCH V4 1/4] fw_cfg: remove support for guest-side data writes Gabriel L. Somlo
2015-04-29 15:21 ` [Qemu-devel] [PATCH V4 2/4] fw_cfg: prevent selector key conflict Gabriel L. Somlo
2015-04-29 15:21 ` [Qemu-devel] [PATCH V4 3/4] fw_cfg: prohibit insertion of duplicate fw_cfg file names Gabriel L. Somlo
2015-04-29 15:21 ` [Qemu-devel] [PATCH V4 4/4] fw_cfg: insert fw_cfg file blobs via qemu cmdline Gabriel L. Somlo
2015-05-31 18:10 ` Michael S. Tsirkin
2015-06-01 7:06 ` Laszlo Ersek
2015-06-01 7:28 ` Michael S. Tsirkin
2015-06-01 9:01 ` Paolo Bonzini [this message]
2015-06-01 10:23 ` Michael S. Tsirkin
2015-06-01 10:35 ` Laszlo Ersek
2015-06-01 10:42 ` Michael S. Tsirkin
2015-06-01 11:19 ` Laszlo Ersek
2015-06-01 10:43 ` Paolo Bonzini
2015-06-01 10:48 ` Michael S. Tsirkin
2015-06-01 10:50 ` Paolo Bonzini
2015-06-01 11:00 ` Michael S. Tsirkin
2015-06-01 11:18 ` Paolo Bonzini
2015-06-01 11:05 ` Gabriel L. Somlo
2015-06-01 11:20 ` Markus Armbruster
2015-06-01 11:21 ` Paolo Bonzini
2015-06-01 11:26 ` Laszlo Ersek
2015-06-01 12:38 ` Michael S. Tsirkin
2015-06-01 12:39 ` Paolo Bonzini
2015-06-01 12:41 ` Michael S. Tsirkin
2015-06-01 12:43 ` Paolo Bonzini
2015-06-02 7:37 ` Gerd Hoffmann
2015-06-02 8:28 ` Michael S. Tsirkin
2015-06-02 9:43 ` Gerd Hoffmann
2015-06-01 13:21 ` Laszlo Ersek
2015-06-01 11:24 ` Laszlo Ersek
2015-05-18 13:05 ` [Qemu-devel] [PATCH V4 0/4] fw-cfg: cleanup and user-provided command line blobs Gabriel L. Somlo
2015-05-29 12:41 ` Gerd Hoffmann
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=556C1F63.1090605@redhat.com \
--to=pbonzini@redhat.com \
--cc=gsomlo@gmail.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=matt.fleming@intel.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=somlo@cmu.edu \
/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.