All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "mst@redhat.com" <mst@redhat.com>,
	"qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"McMillan, Erich" <erich.mcmillan@hp.com>,
	Igor Mammedov <imammedo@redhat.com>
Subject: Re: PATCH: Increase System Firmware Max Size
Date: Wed, 16 Sep 2020 12:43:46 +0100	[thread overview]
Message-ID: <20200916114346.GK1535709@redhat.com> (raw)
In-Reply-To: <712696ed-8f23-d8e6-f765-df7aa68f1013@redhat.com>

On Wed, Sep 16, 2020 at 01:31:05PM +0200, Laszlo Ersek wrote:
> On 09/16/20 11:56, Daniel P. Berrangé wrote:
> > On Wed, Sep 16, 2020 at 11:52:41AM +0200, Laszlo Ersek wrote:
> >> (5) In my opinion (which could be wrong of course), we shouldn't
> >> introduce a new command line option for this, but a new PC machine type
> >> property called "x-firmware-max-size".
> > 
> > Yeah, we definitely do not want a new top level CLI arg, just a
> > machine type property.  We don't need any "x-" prefix on it
> > though, just a plain "firmware-max-size" prop is fine.
> 
> According to the previous discussion, I'd like to request that we add
> the x- prefix (showing that either the property is experimental, or that
> it is intended in support of experimental use cases).
> 
> If you disagree, I'll accept that though.

I don't see a reason to call the property itself experimental unless
someone is proposing that there's likely to be a better way to enlarge
the max firmware size that will replace it later.

The use case is definitely not something I'd call experimental either.
The user providing their own arbirary firmware is not going to be common,
but when they do I'd consider it a valid supported use case. QEMU is
agnostic about what firmware impl is used, as long as the firmware can
support the expected services/interfaces.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2020-09-16 11:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11  1:45 PATCH: Increase System Firmware Max Size McMillan, Erich
2020-09-11  7:55 ` Laszlo Ersek
2020-09-11  8:34   ` Dr. David Alan Gilbert
2020-09-11 14:53     ` Laszlo Ersek
2020-09-11 15:06       ` Dr. David Alan Gilbert
2020-09-11 15:22         ` McMillan, Erich via
2020-09-11 16:11           ` Laszlo Ersek
2020-09-11 15:23         ` Daniel P. Berrangé
2020-09-11 16:06           ` Laszlo Ersek
2020-09-11 16:21             ` Daniel P. Berrangé
2020-09-11 16:45               ` Laszlo Ersek
2020-09-11 15:57         ` Laszlo Ersek
2020-09-11 16:22           ` Dr. David Alan Gilbert
2020-09-11 16:53             ` Laszlo Ersek
2020-09-11 16:59               ` Dr. David Alan Gilbert
2020-09-11 17:51                 ` McMillan, Erich via
2020-09-15 19:09 ` McMillan, Erich
2020-09-15 19:10   ` McMillan, Erich via
2020-09-16  9:52     ` Laszlo Ersek
2020-09-16  9:56       ` Daniel P. Berrangé
2020-09-16 11:31         ` Laszlo Ersek
2020-09-16 11:43           ` Daniel P. Berrangé [this message]
2020-09-16 10:00       ` Laszlo Ersek

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=20200916114346.GK1535709@redhat.com \
    --to=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=erich.mcmillan@hp.com \
    --cc=imammedo@redhat.com \
    --cc=lersek@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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 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.