public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Devon Bautista" <dbautista@newmexicoconsortium.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: devel@edk2.groups.io, Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Jiewen Yao <jiewen.yao@intel.com>,
	Jordan Justen <jordan.l.justen@intel.com>
Subject: Re: [PATCH v2 1/1] OvmfPkg: Introduce 16MiB flash size for (primarily) Linuxboot
Date: Mon, 6 Sep 2021 17:55:20 -0700	[thread overview]
Message-ID: <9250555d-d8a8-60d9-dcea-1e2146ec58ce@newmexicoconsortium.org> (raw)
In-Reply-To: <20210906083725.vbkudl3qqxrtbaqo@sirius.home.kraxel.org>

> So DXEFV needs more space then.  I'm wondering that the size doesn't
> change according to the commit message.  Looking at the fdf files it
> seems PEIFV and DXEFV don't have a fixed size, seems everything is
> fine as long as the compressed image fits into FVMAIN_COMPACT.
> 
> take care,
>   Gerd
> 
DXEFV would indeed need more space, but I recall that in the first
version of this patch, Laszlo commented:

> (2) [FD.MEMFD] should immediately benefit from this change, even if
> your downstream populates FVMAIN_COMPACT with something else than
> PEIFV and DXEFV. First, we're almost out of (uncompressed) DXEFV space
> again.
> Second, especially the confidential computing technologies have been
> gobbling up the nice, low, free space in FD.MEMFD the way a kid with a
> sweet tooth empties a cookie jar. This change is already compat
> breaking, so I'd like to see *some* proposal (separate patches) for
> enlarging *and pushing up* PEIFV and DXEFV.

For the latter point, I figured that it might be beneficial to expand
FVMAIN_COMPACT as a whole to allow for the possibility of growing either
DXEFV _or_ PEIFV, or both.

Best,
Devon


  reply	other threads:[~2021-09-07  0:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03  5:26 [PATCH v2 0/1] OVMF: Introduce 16MiB Flash Size Devon Bautista
2021-09-03  5:26 ` [PATCH v2 1/1] OvmfPkg: Introduce 16MiB flash size for (primarily) Linuxboot Devon Bautista
2021-09-03  7:17   ` Gerd Hoffmann
2021-09-03 19:35     ` Devon Bautista
2021-09-06  8:37       ` Gerd Hoffmann
2021-09-07  0:55         ` Devon Bautista [this message]
2021-09-09  9:09   ` [edk2-devel] " Philippe Mathieu-Daudé
2021-09-09 12:10     ` Gerd Hoffmann
2021-10-19 23:03     ` Devon Bautista

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-list 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=9250555d-d8a8-60d9-dcea-1e2146ec58ce@newmexicoconsortium.org \
    --to=devel@edk2.groups.io \
    /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