From: Stefan Berger <stefanb@linux.ibm.com>
To: Daniel Kiper <dkiper@net-space.pl>, Daniel Axtens <dja@axtens.net>
Cc: grub-devel@gnu.org, leif@nuviainc.com, ps@pks.im
Subject: Re: [PATCH v2 00/15] Dynamic allocation of memory regions and IBM vTPM v2
Date: Wed, 18 May 2022 11:24:48 -0400 [thread overview]
Message-ID: <33330aa2-abfd-d26d-7f33-800adbcce6ae@linux.ibm.com> (raw)
In-Reply-To: <20220414153018.7ojgxpwpgq4ii6ej@tomti.i.net-space.pl>
On 4/14/22 11:30, Daniel Kiper wrote:
> On Thu, Apr 07, 2022 at 04:41:04PM +0200, Daniel Kiper wrote:
>> On Mon, Mar 28, 2022 at 05:22:25PM +1100, Daniel Axtens wrote:
>>> Hi all,
>>>
>>> This is, at long last, an updated version of my series extending Patrick's
>>> dynamic memory regions to ieee1275.
>>>
>>> Noteworthy changes:
>>>
>>> - reworked debug prints as grub_dprintfs. Folded the ieee1275 ones into the
>>> ieee1275 patches.
>>>
>>> - reworked the ieee1275 runtime memory claiming to be more resilient and better
>>> documented.
>>>
>>> - fixed comment style and hopefully addressed all other change requests.
>>>
>>> - grub will now try asking for contiguous memory and then, if that fails, for
>>> discontiguous memory - in case region merging with the discontiguous memory
>>> is sufficient to allow the eventual allocation to succeed.
>>
>> Patrick, all mm and EFI code got my RB. Could you test it with your
>> Argon changes? If these changes pass your tests I will merge them.
>
> Patrick, ping?
>
> To be more precise, I am thinking about the patches up to #10.
>
> Daniel
Any way we can make progress with this series before it gets all
forgotten about?
Stefan
next prev parent reply other threads:[~2022-05-18 15:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 6:22 [PATCH v2 00/15] Dynamic allocation of memory regions and IBM vTPM v2 Daniel Axtens
2022-03-28 6:22 ` [PATCH v2 01/15] grub-shell: only pass SeaBIOS fw_opt in for x86 BIOS platforms Daniel Axtens
2022-04-06 17:18 ` Daniel Kiper
2022-03-28 6:22 ` [PATCH v2 02/15] mm: assert that we preserve header vs region alignment Daniel Axtens
2022-04-06 17:20 ` Daniel Kiper
2022-03-28 6:22 ` [PATCH v2 03/15] mm: when adding a region, merge with region after as well as before Daniel Axtens
2022-04-07 13:55 ` Daniel Kiper
2022-03-28 6:22 ` [PATCH v2 04/15] mm: debug support for region operations Daniel Axtens
2022-04-07 13:57 ` Daniel Kiper
2022-03-28 6:22 ` [PATCH v2 05/15] mm: Drop unused unloading of modules on OOM Daniel Axtens
2022-03-28 6:22 ` [PATCH v2 06/15] mm: Allow dynamically requesting additional memory regions Daniel Axtens
2022-04-07 14:02 ` Daniel Kiper
2022-03-28 6:22 ` [PATCH v2 07/15] efi: mm: Always request a fixed number of pages on init Daniel Axtens
2022-03-28 6:22 ` [PATCH v2 08/15] efi: mm: Extract function to add memory regions Daniel Axtens
2022-04-07 14:08 ` Daniel Kiper
2022-03-28 6:22 ` [PATCH v2 09/15] efi: mm: Pass up errors from `add_memory_regions ()` Daniel Axtens
2022-04-07 14:15 ` Daniel Kiper
2022-03-28 6:22 ` [PATCH v2 10/15] efi: mm: Implement runtime addition of pages Daniel Axtens
2022-03-28 6:22 ` [PATCH v2 11/15] ieee1275: request memory with ibm, client-architecture-support Daniel Axtens
2022-03-28 6:22 ` [PATCH v2 12/15] ieee1275: drop len -= 1 quirk in heap_init Daniel Axtens
2022-03-28 6:22 ` [PATCH v2 13/15] ieee1275: support runtime memory claiming Daniel Axtens
2022-03-28 6:22 ` [PATCH v2 14/15] [RFC] Add memtool module with memory allocation stress-test Daniel Axtens
2022-03-28 6:22 ` [PATCH v2 15/15] ibmvtpm: Add support for trusted boot using a vTPM 2.0 Daniel Axtens
2022-04-07 14:41 ` [PATCH v2 00/15] Dynamic allocation of memory regions and IBM vTPM v2 Daniel Kiper
2022-04-14 15:30 ` Daniel Kiper
2022-05-18 15:24 ` Stefan Berger [this message]
2022-05-19 16:34 ` Daniel Kiper
2022-05-29 5:55 ` Patrick Steinhardt
2022-06-23 17:16 ` Daniel Kiper
2022-06-24 6:16 ` Patrick Steinhardt
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=33330aa2-abfd-d26d-7f33-800adbcce6ae@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=dja@axtens.net \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
--cc=leif@nuviainc.com \
--cc=ps@pks.im \
/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.