From: Daniel Kiper <dkiper@net-space.pl>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: grub-devel@gnu.org, hbathini@linux.ibm.com, pavrampu@in.ibm.com,
mpe@ellerman.id.au, cpscherr@us.ibm.com, mahesh@linux.ibm.com,
sourabhjain@linux.ibm.com, avnish.chouhan@ibm.com
Subject: Re: [PATCH v8 00/10] ppc64: Restrict memory allocations for kernel and initrd
Date: Fri, 1 Dec 2023 18:04:12 +0100 [thread overview]
Message-ID: <20231201170412.cbhvvn5yqjjjpzuu@tomti.i.net-space.pl> (raw)
In-Reply-To: <20231130141724.1803616-1-stefanb@linux.ibm.com>
On Thu, Nov 30, 2023 at 09:17:14AM -0500, Stefan Berger wrote:
> This series of patches converts the PowerPC ieee1275 memory allocator
> for kernel and initrd to use the (PowerPC) regions_claim memory allocator
> that takes into account memory regions that are not allowed to be used,
> such as the gap between 640MB and 768MB as well as memory regions beyond
> an address in case an fadump is present. Otherwise those two could be
> loaded into restricted memory regions and either cause a crash or
> corruption of the fadump.
>
> I adjusted the kernel and initrd load in loader/powerpc/ieee1275 to use
> the new memory allocator only on PowerVM and PowerKVM since this code is
> shared with other platforms, such as old PowerMACs and i386.
For the patches which do not have my RB Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>...
I will merge these patches next week.
Thanks,
Daniel
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
prev parent reply other threads:[~2023-12-01 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 14:17 [PATCH v8 00/10] ppc64: Restrict memory allocations for kernel and initrd Stefan Berger
2023-11-30 14:17 ` [PATCH v8 01/10] kern/ieee1275/init: ppc64: Introduce a request for regions_claim Stefan Berger
2023-11-30 14:17 ` [PATCH v8 02/10] kern/ieee1275/init: ppc64: Decide by request whether to initialize region Stefan Berger
2023-11-30 14:17 ` [PATCH v8 03/10] kern/ieee1275/init: ppc64: Return allocated address using context Stefan Berger
2023-11-30 14:17 ` [PATCH v8 04/10] kern/ieee1275/init: ppc64: Add support for alignment requirements Stefan Berger
2023-11-30 14:17 ` [PATCH v8 05/10] kern/ieee1275/init: ppc64: Rename regions_claim to grub_regions_claim Stefan Berger
2023-11-30 14:17 ` [PATCH v8 06/10] kern/ieee1275/cmain: ppc64: Introduce flags to identify KVM and Power VM Stefan Berger
2023-11-30 14:17 ` [PATCH v8 07/10] loader/powerpc/ieee1275: Use new allocation function for kernel and initrd Stefan Berger
2023-11-30 14:17 ` [PATCH v8 08/10] kern/ieee1275/ieee1275: debug: Display successful memory claims Stefan Berger
2023-11-30 14:17 ` [PATCH v8 09/10] kern/ieee1275/init: ppc64: Fix a comment Stefan Berger
2023-11-30 14:17 ` [PATCH v8 10/10] kern/ieee1275/init: ppc64: Display upper_mem_limit for debugging Stefan Berger
2023-12-01 17:04 ` Daniel Kiper [this message]
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=20231201170412.cbhvvn5yqjjjpzuu@tomti.i.net-space.pl \
--to=dkiper@net-space.pl \
--cc=avnish.chouhan@ibm.com \
--cc=cpscherr@us.ibm.com \
--cc=grub-devel@gnu.org \
--cc=hbathini@linux.ibm.com \
--cc=mahesh@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=pavrampu@in.ibm.com \
--cc=sourabhjain@linux.ibm.com \
--cc=stefanb@linux.ibm.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).