All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 0/2] backport of ARM / EFI / GICv3 memreserve fix
Date: Wed, 20 Feb 2019 23:04:33 -0500	[thread overview]
Message-ID: <20190221040433.GA10616@sasha-vm> (raw)
In-Reply-To: <20190219190313.2477-1-ard.biesheuvel@linaro.org>

On Tue, Feb 19, 2019 at 08:03:11PM +0100, Ard Biesheuvel wrote:
>This is a backport to v4.20 of the fix for an early memblock reserve issue
>observed on arm64 systems with a GICv3 and many (i.e., hundreds of) CPUs.
>
>Ard Biesheuvel (2):
>  arm64, mm, efi: Account for GICv3 LPI tables in static memblock
>    reserve table
>  efi/arm: Revert "Defer persistent reservations until after
>    paging_init()"
>
> arch/arm64/include/asm/memory.h         | 11 +++++++++++
> arch/arm64/kernel/setup.c               |  1 -
> drivers/firmware/efi/efi.c              |  4 ----
> drivers/firmware/efi/libstub/arm-stub.c |  3 ---
> include/linux/efi.h                     |  7 -------
> include/linux/memblock.h                |  3 ---
> mm/memblock.c                           | 11 +++++++++--
> 7 files changed, 20 insertions(+), 20 deletions(-)

Queued for 4.20, thank you.

--
Thanks,
Sasha

      parent reply	other threads:[~2019-02-21  4:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 19:03 [PATCH 0/2] backport of ARM / EFI / GICv3 memreserve fix Ard Biesheuvel
2019-02-19 19:03 ` [PATCH 1/2] arm64, mm, efi: Account for GICv3 LPI tables in static memblock reserve table Ard Biesheuvel
2019-02-19 19:03 ` [PATCH 2/2] efi/arm: Revert "Defer persistent reservations until after paging_init()" Ard Biesheuvel
2019-02-21  4:04 ` Sasha Levin [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=20190221040433.GA10616@sasha-vm \
    --to=sashal@kernel.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=stable@vger.kernel.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.