From: Andrew Jones <ajones@ventanamicro.com>
To: Andrew Jones <andrew.jones@linux.dev>
Cc: kvm-riscv@lists.infradead.org
Subject: Re: [kvm-unit-tests PATCH] riscv: efi: Bump number of memregions
Date: Wed, 29 Jan 2025 18:14:02 +0100 [thread overview]
Message-ID: <20250129-a3d20dcf21f54ad5650d284c@orel> (raw)
In-Reply-To: <20250129165131.163433-2-andrew.jones@linux.dev>
On Wed, Jan 29, 2025 at 05:51:32PM +0100, Andrew Jones wrote:
> There may be a bunch of EFI memory regions in the EFI memory map,
> which we convert to k-u-t memregions. Bump the number we allow to
> ensure we don't hit the assert in memregions_add().
>
> Signed-off-by: Andrew Jones <andrew.jones@linux.dev>
> ---
>
> I noticed that the gitlab CI started failing the riscv EFI tests. It
> looks like the edk2 used by CI has been updated to a version later than
> what I was using locally and the newer one has several more memory
> regions.
>
> lib/riscv/setup.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/lib/riscv/setup.c b/lib/riscv/setup.c
> index 211945448b0f..a30aa0c4cb80 100644
> --- a/lib/riscv/setup.c
> +++ b/lib/riscv/setup.c
> @@ -31,7 +31,11 @@
> #endif
>
> #define MAX_DT_MEM_REGIONS 16
> +#ifdef CONFIG_EFI
> +#define NR_MEM_REGIONS (MAX_DT_MEM_REGIONS + 128)
> +#else
> #define NR_MEM_REGIONS (MAX_DT_MEM_REGIONS + 16)
> +#endif
>
> extern unsigned long _etext;
>
> --
> 2.48.1
>
Merged.
--
kvm-riscv mailing list
kvm-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kvm-riscv
prev parent reply other threads:[~2025-01-29 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 16:51 [kvm-unit-tests PATCH] riscv: efi: Bump number of memregions Andrew Jones
2025-01-29 17:14 ` Andrew Jones [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=20250129-a3d20dcf21f54ad5650d284c@orel \
--to=ajones@ventanamicro.com \
--cc=andrew.jones@linux.dev \
--cc=kvm-riscv@lists.infradead.org \
/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.