mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Salter <msalter@redhat.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: Roy Franz <roy.franz@linaro.org>,
	linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, matt.fleming@intel.com,
	linux@arm.linux.org.uk, leif.lindholm@linaro.org,
	grant.likely@linaro.org, dave.martin@arm.com, patches@linaro.org
Subject: Re: [PATCH V5 2/6] Add shared update_fdt() function for ARM/ARM64
Date: Mon, 02 Dec 2013 09:56:25 -0500	[thread overview]
Message-ID: <1385996185.1861.28.camel@deneb.redhat.com> (raw)
In-Reply-To: <20131129113008.GB11775@console-pimps.org>

On Fri, 2013-11-29 at 11:30 +0000, Matt Fleming wrote:
> >       /*
> >        * Add an additional efi_memory_desc_t because we're doing an
> >        * allocation which may be in a new descriptor region.
> > +      * We allocate as EFI_RUNTIME_SERVICES_DATA since this is what
> > +      * we want for when we pass the memory map to the kernel.  This
> > +      * function is also used to get the memory map for other uses,
> > +      * but is always freed by the stub so the allocation type
> > +      * doesn't matter.
> >        */
> >       *map_size += sizeof(*m);
> >       status = efi_call_phys3(sys_table_arg->boottime->allocate_pool,
> > -                             EFI_LOADER_DATA, *map_size, (void **)&m);
> > +                             EFI_RUNTIME_SERVICES_DATA, *map_size,
> > +                             (void **)&m);
> >       if (status != EFI_SUCCESS)
> >               goto fail;
>   
> 
> OK, this needs a stronger justification. Presumably the reason for this
> change is that you want the allocation to hang around once the kernel is
> running? We have this problem on x86 and it's solved by reserving the
> memory early in the kernel, e.g. memblock_reserve().
> EFI_RUNTIME_SERVICES_DATA is for firmware use, not for kernel data.
> 

Yeah, arm64 reserves it and is okay with it being EFI_LOADER_DATA.

--Mark



  reply	other threads:[~2013-12-02 14:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 23:31 [PATCH V5 0/6] Add ARM EFI stub Roy Franz
2013-11-27 23:31 ` [PATCH V5 1/6] efi-stub.txt updates for ARM Roy Franz
2013-11-29 10:36   ` Matt Fleming
2013-12-05 15:19   ` Grant Likely
2013-11-27 23:31 ` [PATCH V5 2/6] Add shared update_fdt() function for ARM/ARM64 Roy Franz
2013-11-29 11:30   ` Matt Fleming
2013-12-02 14:56     ` Mark Salter [this message]
2013-12-02 23:09       ` Roy Franz
2013-12-05 19:24   ` Grant Likely
2013-12-06  0:58     ` Roy Franz
2013-12-05 19:27   ` Grant Likely
2013-11-27 23:31 ` [PATCH V5 3/6] Add strstr to compressed string.c for ARM Roy Franz
2013-11-27 23:31 ` [PATCH V5 4/6] Add EFI stub " Roy Franz
2013-12-05 20:00   ` Grant Likely
2013-12-06  1:25     ` Roy Franz
2013-11-27 23:31 ` [PATCH V5 5/6] Disable stack protection for decompressor/stub Roy Franz
2013-11-27 23:31 ` [PATCH V5 6/6] Add config EFI_STUB for ARM to Kconfig Roy Franz
2013-12-05 20:04   ` Grant Likely

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=1385996185.1861.28.camel@deneb.redhat.com \
    --to=msalter@redhat.com \
    --cc=dave.martin@arm.com \
    --cc=grant.likely@linaro.org \
    --cc=leif.lindholm@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=matt.fleming@intel.com \
    --cc=matt@console-pimps.org \
    --cc=patches@linaro.org \
    --cc=roy.franz@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome