public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Jordan Justen <jordan.l.justen@intel.com>,
	edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Gary Ching-Pang Lin <glin@suse.com>
Subject: Re: [PATCH 2/3] OvmfPkg: introduce FD_SIZE_4MB (mainly) for Windows HCK
Date: Tue, 2 May 2017 16:39:04 +0200	[thread overview]
Message-ID: <c5df3c55-bde6-71d9-9104-5a095f3e820a@redhat.com> (raw)
In-Reply-To: <149368192252.29568.13017173745830665833@jljusten-skl>

On 05/02/17 01:38, Jordan Justen wrote:
> On 2017-05-01 16:07:48, Laszlo Ersek wrote:
>> On 05/01/17 21:20, Jordan Justen wrote:
>>>
>>> At this I'd just like figure out what to do about the 4MB layout, so
>>> can we stop getting worked up over this side show?
>>
>> Thanks for calling it a side show, real friendly.
> 
> Ok, I apologize. The 'side show' comment applies equally to me. Can we
> please just move on? We obviously disagree how to determine how full
> 2MB is, but it doesn't much matter since you'll soon be abandoning it
> entirely. We have too much room in the 4MB fridge to be concerned
> about this.

OK.

I wouldn't mind if we made more room for the varstore in the 2MB build,
even at the expense of FVMAIN_COMPACT, if we also kept the current 2MB
build the default, so that the "new" (incompatible) 2MB build doesn't
come as a surprise to unsuspecting downstreams.

Regarding the 4MB build:
- we can discuss that on top of the above "new" 2MB build,
- we can discuss it instead of the above "new" 2MB build,
- we can postpone it for now, for upstream.

If you do agree that a 4MB build should be offered in upstream, then I'm
proposing my proposal (obviously :) ). If your main focus is the "new"
2MB build, and beause mine is the 4MB build, perhaps we aren't even
disagreeing as much, since this doesn't have to be an either-or. If you
have specific observations for the 4MB structure I proposed, I'd be glad
to hear those as well.

> 
>> The only email (that I can see) in this thread that I haven't reacted to is:
>>
>> http://mid.mail-archive.com/149365894632.25909.11739243410891079091@jljusten-skl
>>
>> where you wrote "I'd rather go with 128k, and I'd also rather stay with
>> 2MB".
> 
> You dropped my ":)" :)
> 
> Ok, me adding that was a poor choice, despite including a smiley. I
> meant to convey was: "Ok, fine, let's figure out the 4MB layout, but I
> still want to whine about it a little more."

I'm sorry that my irony-meter failed (I hope this isn't a poor choice of
words); the downstream deadlines are really close, I'd been working day
and night over the weekend, and I mistook the smiley for "I'll never
agree with you on this, but here's a smiley to take the edge off".

Thanks,
Laszlo


  reply	other threads:[~2017-05-02 14:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-29 20:14 [PATCH 0/3] OvmfPkg: add FD_SIZE_4MB for Windows HCK SB tests, and for future proofing Laszlo Ersek
2017-04-29 20:14 ` [PATCH 1/3] OvmfPkg/OvmfPkg.fdf.inc: extract VARS_LIVE_SIZE and VARS_SPARE_SIZE macros Laszlo Ersek
2017-04-29 20:14 ` [PATCH 2/3] OvmfPkg: introduce FD_SIZE_4MB (mainly) for Windows HCK Laszlo Ersek
2017-04-30  0:48   ` Jordan Justen
2017-04-30 14:42     ` Laszlo Ersek
2017-04-30 21:16       ` Jordan Justen
2017-05-01 10:51         ` Laszlo Ersek
2017-05-01 17:15           ` Jordan Justen
2017-05-01 17:23           ` Jordan Justen
2017-05-01 18:40             ` Laszlo Ersek
2017-05-01 19:20               ` Jordan Justen
2017-05-01 23:07                 ` Laszlo Ersek
2017-05-01 23:38                   ` Jordan Justen
2017-05-02 14:39                     ` Laszlo Ersek [this message]
2017-05-02 18:22                       ` Jordan Justen
2017-05-02 19:31                         ` Laszlo Ersek
2017-05-02 21:45                           ` Jordan Justen
2017-05-03 13:46                             ` Laszlo Ersek
2017-05-01  0:06     ` Laszlo Ersek
2017-04-29 20:15 ` [PATCH 3/3] OvmfPkg: raise max variable size (auth & non-auth) to 33KB for FD_SIZE_4MB 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-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=c5df3c55-bde6-71d9-9104-5a095f3e820a@redhat.com \
    --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