From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Sughosh Ganu <sughosh.ganu@linaro.org>,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH 5/6] efi: Use malloc() for the EFI pool
Date: Wed, 31 Jul 2024 11:17:26 -0600 [thread overview]
Message-ID: <20240731171726.GF3794063@bill-the-cat> (raw)
In-Reply-To: <CAFLszThsMiQWfkVJ0POMJAFDyYWErLssG5vsQOG4V2WTWoE=4w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
On Wed, Jul 31, 2024 at 08:39:23AM -0600, Simon Glass wrote:
[snip]
> > > > so that
> > > > step three can be seeing what tweaks may be needed in where things
> > > > allocate memory.
> > >
> > > So my series is step 3?
> >
> > Or at least understanding what the problems may still be, yes.
>
> In that case I would like to clean up EFI's memory management before
> doing step 2, since I believe many of the problems will just go away
> if we can get that right.
Well, I think that's where some of the big points of contention are,
yes. You say "fix" and Ilias and Heinrich say "but the spec".
Perhaps once step one is done it will be easier to find a way to address
your concerns without also breaking "the spec".
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-07-31 17:17 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 13:56 [PATCH 0/6] efi: Start tidying up memory management Simon Glass
2024-07-25 13:56 ` [PATCH 1/6] doc: Show more information in efi index Simon Glass
2024-07-25 16:02 ` Heinrich Schuchardt
2024-07-25 13:56 ` [PATCH 2/6] efi: Convert device_path allocation to use malloc() Simon Glass
2024-07-25 16:13 ` Heinrich Schuchardt
2024-07-25 23:32 ` Simon Glass
2024-07-25 13:56 ` [PATCH 3/6] efi: Allow monitoring of page allocations Simon Glass
2024-07-25 16:20 ` Heinrich Schuchardt
2024-07-25 23:33 ` Simon Glass
2024-07-25 13:56 ` [PATCH 4/6] efi: Avoid pool allocation in efi_get_memory_map_alloc() Simon Glass
2024-07-25 16:38 ` Heinrich Schuchardt
2024-07-31 14:39 ` Simon Glass
2024-07-25 13:56 ` [PATCH 5/6] efi: Use malloc() for the EFI pool Simon Glass
2024-07-25 15:49 ` Heinrich Schuchardt
2024-07-25 23:32 ` Simon Glass
2024-07-26 8:31 ` Ilias Apalodimas
2024-07-26 14:54 ` Simon Glass
2024-07-29 10:01 ` Ilias Apalodimas
2024-07-29 15:28 ` Simon Glass
2024-07-30 8:19 ` Ilias Apalodimas
2024-07-30 14:38 ` Simon Glass
2024-07-30 14:53 ` Mark Kettenis
2024-07-30 15:18 ` Simon Glass
2024-07-30 14:53 ` Ilias Apalodimas
2024-07-30 15:18 ` Simon Glass
2024-07-30 15:24 ` Tom Rini
2024-07-30 19:42 ` Simon Glass
2024-07-30 19:49 ` Tom Rini
2024-07-30 20:05 ` Simon Glass
2024-07-30 20:11 ` Tom Rini
2024-07-30 20:52 ` Simon Glass
2024-07-30 21:20 ` Tom Rini
2024-07-31 14:39 ` Simon Glass
2024-07-31 17:17 ` Tom Rini [this message]
2024-08-01 10:14 ` Ilias Apalodimas
2024-08-01 16:14 ` Simon Glass
2024-08-01 16:22 ` Ilias Apalodimas
2024-08-01 17:43 ` Simon Glass
2024-07-31 7:39 ` Ilias Apalodimas
2024-07-31 14:39 ` Simon Glass
2024-07-25 13:56 ` [PATCH 6/6] efi: Show the location of the bounce buffer Simon Glass
2024-07-25 16:31 ` Heinrich Schuchardt
2024-07-31 14:39 ` Simon Glass
2024-07-25 14:25 ` [PATCH 0/6] efi: Start tidying up memory management Ilias Apalodimas
2024-07-25 15:58 ` Simon Glass
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=20240731171726.GF3794063@bill-the-cat \
--to=trini@konsulko.com \
--cc=ilias.apalodimas@linaro.org \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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