All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "McMillan, Erich" <erich.mcmillan@hp.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: "mst@redhat.com" <mst@redhat.com>,
	"qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
	"Markus Armbruster" <armbru@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: PATCH: Increase System Firmware Max Size
Date: Fri, 11 Sep 2020 18:11:33 +0200	[thread overview]
Message-ID: <ad584cb7-3fb6-1f1f-62af-61aa3a071fb0@redhat.com> (raw)
In-Reply-To: <CS1PR8401MB03273F105DE3FA773E2DB2F5F3240@CS1PR8401MB0327.NAMPRD84.PROD.OUTLOOK.COM>

On 09/11/20 17:22, McMillan, Erich wrote:

> I agree that fw has become the vendor OS, but at this point there's no
> going back.
> Utilizing a virtual platform allows us to greatly increase the security
> of our code,
> could we make this change a Qemu experimental flag, so that fw vendors could
> use it at their own risk?

That would make me feel more comfortable, yes.

Daniel proposed "firmware-max-size" (I've now taken the liberty to
replace "_" with "-"; I believe that's the current rule for property names).

If we called it "x-firmware-max-size" and kept the default value
unchanged, I'd feel way safer. (Because then any feature request for
upstream OVMF that were based on changing "x-firmware-max-size" could be
refuted immediately with: "that property name starts with x-, sorry".)

Thanks,
Laszlo



  reply	other threads:[~2020-09-11 16:13 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 [this message]
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é
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=ad584cb7-3fb6-1f1f-62af-61aa3a071fb0@redhat.com \
    --to=lersek@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=erich.mcmillan@hp.com \
    --cc=mst@redhat.com \
    --cc=philmd@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.