All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vincent Stehlé" <vincent.stehle@laposte.net>
To: Leif Lindholm <leif@nuviainc.com>
Cc: Daniel Kiper <dkiper@net-space.pl>,
	grub-devel@gnu.org, Grant Likely <grant.likely@arm.com>,
	Peter Jones <pjones@redhat.com>
Subject: Re: [PATCH] arm/efi: fix ram base detection
Date: Tue, 30 Mar 2021 22:01:23 +0200	[thread overview]
Message-ID: <YGODk/UWCg5JJvBR@romuald.bergerie> (raw)
In-Reply-To: <20210322182851.GY1664@vanye>

On Mon, Mar 22, 2021 at 06:28:51PM +0000, Leif Lindholm wrote:
..
> > > diff --git a/grub-core/kern/efi/mm.c b/grub-core/kern/efi/mm.c
> > > index 0cdb063bb..abf8772bc 100644
> > > --- a/grub-core/kern/efi/mm.c
> > > +++ b/grub-core/kern/efi/mm.c
> > > @@ -677,7 +677,8 @@ grub_efi_get_ram_base(grub_addr_t *base_addr)
> > >    for (desc = memory_map, *base_addr = GRUB_EFI_MAX_USABLE_ADDRESS;
> > >         (grub_addr_t) desc < ((grub_addr_t) memory_map + memory_map_size);
> > >         desc = NEXT_MEMORY_DESCRIPTOR (desc, desc_size))
> > > -    if (desc->attribute & GRUB_EFI_MEMORY_WB)
> > > +    if (desc->type == GRUB_EFI_CONVENTIONAL_MEMORY &&
> > > +        desc->attribute & GRUB_EFI_MEMORY_WB)
> 
> Can we safely assume we don't also need to check against
> GRUB_EFI_PERSISTENT_MEMORY? If so, this is fine.

Hi Leif,

Thanks for the review.

This is a good question about persistent memory; I don't know if we should
check it or not.

I am "fighting" with qemu to add an nvdimm above or below the first normal
memory region to see how this behaves. I will let you know when I have
succeeded.

Best regards,
Vincent.


  reply	other threads:[~2021-03-30 20:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12 16:54 [PATCH] arm/efi: fix ram base detection Vincent Stehlé
2021-03-22 16:00 ` Daniel Kiper
2021-03-22 18:28   ` Leif Lindholm
2021-03-30 20:01     ` Vincent Stehlé [this message]
2021-04-12 13:50       ` Daniel Kiper

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=YGODk/UWCg5JJvBR@romuald.bergerie \
    --to=vincent.stehle@laposte.net \
    --cc=dkiper@net-space.pl \
    --cc=grant.likely@arm.com \
    --cc=grub-devel@gnu.org \
    --cc=leif@nuviainc.com \
    --cc=pjones@redhat.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 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.