From: Ard Biesheuvel <ardb@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Wupeng Ma <mawupeng1@huawei.com>,
Jonathan Corbet <corbet@lwn.net>, Will Deacon <will@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
X86 ML <x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
"Paul E. McKenney" <paulmck@kernel.org>,
Kees Cook <keescook@chromium.org>,
songmuchun@bytedance.com, Randy Dunlap <rdunlap@infradead.org>,
damien.lemoal@opensource.wdc.com,
Stephen Boyd <swboyd@chromium.org>, Wei Liu <wei.liu@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
David Hildenbrand <david@redhat.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Zhen Lei <thunder.leizhen@huawei.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
gpiccoli@igalia.com, Huacai Chen <chenhuacai@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
vijayb@linux.microsoft.com,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-efi <linux-efi@vger.kernel.org>,
platform-driver-x86@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v5 1/5] efi: arm64: Introduce ability to find mirrored memory ranges
Date: Wed, 15 Jun 2022 12:03:50 +0200 [thread overview]
Message-ID: <CAMj1kXG+UgWeAVyh8CD5S0M4n2SKFGcP0ayOn41bKmyoVb8QXQ@mail.gmail.com> (raw)
In-Reply-To: <YqmuQIpkY7TJHAh6@arm.com>
On Wed, 15 Jun 2022 at 12:02, Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> On Tue, Jun 14, 2022 at 05:21:52PM +0800, Wupeng Ma wrote:
> > From: Ma Wupeng <mawupeng1@huawei.com>
> >
> > Commit b05b9f5f9dcf ("x86, mirror: x86 enabling - find mirrored memory
> > ranges") introduce the efi_find_mirror() function on x86. In order to reuse
> > the API we make it public.
> >
> > Arm64 can support mirrored memory too, so function efi_find_mirror() is added to
> > efi_init() to this support for arm64.
> >
> > Since efi_init() is shared by ARM, arm64 and riscv, this patch will bring
> > mirror memory support for these architectures, but this support is only tested
> > in arm64.
> >
> > Signed-off-by: Ma Wupeng <mawupeng1@huawei.com>
> > ---
> > arch/x86/include/asm/efi.h | 4 ----
> > arch/x86/platform/efi/efi.c | 23 -----------------------
> > drivers/firmware/efi/efi-init.c | 1 +
> > drivers/firmware/efi/efi.c | 23 +++++++++++++++++++++++
> > include/linux/efi.h | 3 +++
>
> The subject prefix says "efi: arm64: " but it looks like x86 diffstat
> here. You may want to get an ack from the x86 maintainers.
>
This just moves efi code around, and this is going through the EFI
tree, so that should be fine. I'll fix the subject in any case,
though.
next prev parent reply other threads:[~2022-06-15 10:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 9:21 [PATCH v5 0/5] introduce mirrored memory support for arm64 Wupeng Ma
2022-06-14 9:21 ` [PATCH v5 1/5] efi: arm64: Introduce ability to find mirrored memory ranges Wupeng Ma
2022-06-15 10:02 ` Catalin Marinas
2022-06-15 10:03 ` Ard Biesheuvel [this message]
2022-06-14 9:21 ` [PATCH v5 2/5] mm: Ratelimited mirrored memory related warning messages Wupeng Ma
2022-06-14 9:21 ` [PATCH v5 3/5] mm: Limit warning message in vmemmap_verify() to once Wupeng Ma
2022-06-14 9:21 ` [PATCH v5 4/5] arm64: mm: Only remove nomap flag for initrd Wupeng Ma
2022-06-15 10:04 ` Catalin Marinas
2022-06-14 9:21 ` [PATCH v5 5/5] memblock: Disable mirror feature if kernelcore is not specified Wupeng Ma
2022-06-14 10:20 ` Baoquan He
2022-06-14 10:27 ` Ard Biesheuvel
2022-06-14 10:50 ` Baoquan He
2022-06-15 3:52 ` [PATCH v5 0/5] introduce mirrored memory support for arm64 Kefeng Wang
2022-06-15 7:54 ` Mike Rapoport
2022-06-15 10:15 ` Ard Biesheuvel
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=CAMj1kXG+UgWeAVyh8CD5S0M4n2SKFGcP0ayOn41bKmyoVb8QXQ@mail.gmail.com \
--to=ardb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andy@infradead.org \
--cc=anshuman.khandual@arm.com \
--cc=aou@eecs.berkeley.edu \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dvhart@infradead.org \
--cc=geert@linux-m68k.org \
--cc=gpiccoli@igalia.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mawupeng1@huawei.com \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=paulmck@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=robin.murphy@arm.com \
--cc=rppt@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=swboyd@chromium.org \
--cc=tglx@linutronix.de \
--cc=thunder.leizhen@huawei.com \
--cc=vijayb@linux.microsoft.com \
--cc=wangkefeng.wang@huawei.com \
--cc=wei.liu@kernel.org \
--cc=will@kernel.org \
--cc=x86@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 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 NNTP newsgroup(s).