linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: j00447129 <jingxiangfeng@huawei.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"the arch/x86 maintainers" <x86@kernel.org>,
	Darren Hart <dvhart@infradead.org>,
	Andy Shevchenko <andy@infradead.org>,
	linux-efi <linux-efi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	<platform-driver-x86@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>,
	"Kefeng Wang" <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH 0/2] arm64: Support to find mirrored memory ranges
Date: Fri, 21 Feb 2020 15:01:29 +0800	[thread overview]
Message-ID: <5E4F8049.9020805@huawei.com> (raw)
In-Reply-To: <CAKv+Gu930691BaDLuoVOU_gz0V8MtfWbfSTKcYuHxDvLz5hAiA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]



On 2020/2/20 17:21, Ard Biesheuvel wrote:
> On Thu, 20 Feb 2020 at 04:43, Jing Xiangfeng <jingxiangfeng@huawei.com> wrote:
>> This series enable finding mirrored memory ranges
>> functionality on arm64 platform. This feature has been
>> implemented on the x86 platform, so we move some
>> functions from x86.
>>
> Hello Jing Xiangfeng,
>
> Could you explain your use case a bit better? Usually, the firmware is
> a better place to make modifications to the EFI memory map.
>
> The reason I am asking is that currently, on ARM and arm64, we never
> make *any* changes to the firmware provided tables (EFI system table,
> EFI memory map, DT/ACPI/SMBIOS tables etc), in order to ensure that
> kexec is idempotent, i.e., it will always see the exact same state as
> far as the firmware is concerned. This is a bit different from x86,
> where the memory map is already modified for various other reasons, so
> using it for fake memory regions is not such a big deal.
     I am not familiar with the firmware specifications. If we want to 
support
     this functionality now, does it mean that the UEFI spec needs to be 
modified?
     kexec related functions also need to be verified under 
synchronization, right?
>
> Do you see a use case for this in production?
     I'm debugging it by fake memory regions.  Our server is expected to 
support it.

         Thanks for your comments
>
>> Jing Xiangfeng (2):
>>    efi: allow EFI_FAKE_MEMMAP on arm64 platform
>>    arm64/efi: support to find mirrored memory ranges
>>
>>   arch/x86/include/asm/efi.h      |  5 -----
>>   arch/x86/platform/efi/efi.c     | 39 ---------------------------------------
>>   drivers/firmware/efi/Kconfig    |  2 +-
>>   drivers/firmware/efi/arm-init.c |  2 ++
>>   drivers/firmware/efi/efi.c      | 23 +++++++++++++++++++++++
>>   drivers/firmware/efi/memmap.c   | 16 ++++++++++++++++
>>   include/linux/efi.h             |  5 +++++
>>   7 files changed, 47 insertions(+), 45 deletions(-)
>>
>> --
>> 1.8.3.1
>>
> .
>


[-- Attachment #2: Type: text/html, Size: 3568 bytes --]

  reply	other threads:[~2020-02-21  7:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 12:52 Jing Xiangfeng
2020-02-20  9:21 ` Ard Biesheuvel
2020-02-21  7:01   ` j00447129 [this message]
2020-02-21 12:52 ` [PATCH 1/2] efi: allow EFI_FAKE_MEMMAP on arm64 platform Jing Xiangfeng
2020-02-21 12:53 ` [PATCH 2/2] arm64/efi: support to find mirrored memory ranges Jing Xiangfeng

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=5E4F8049.9020805@huawei.com \
    --to=jingxiangfeng@huawei.com \
    --cc=andy@infradead.org \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=dvhart@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wangkefeng.wang@huawei.com \
    --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