From: Shijie Huang <shijie@amperemail.onmicrosoft.com>
To: Baoquan He <bhe@redhat.com>,
Huang Shijie <shijie@os.amperecomputing.com>,
akpm@linux-foundation.org
Cc: vgoyal@redhat.com, dyoung@redhat.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, patches@amperecomputing.com
Subject: Re: [PATCH] crash_core: export vmemmap when CONFIG_SPARSEMEM_VMEMMAP is enabled
Date: Wed, 17 Jan 2024 09:32:35 +0800 [thread overview]
Message-ID: <2414bcf0-d7d6-485e-ba68-8d13a28da8b5@amperemail.onmicrosoft.com> (raw)
In-Reply-To: <ZYO7MvpT9yWWfjO7@MiWiFi-R3L-srv>
Hi Andrew,
在 2023/12/21 12:12, Baoquan He 写道:
> On 11/27/23 at 10:07am, Huang Shijie wrote:
>> In memory_model.h, if CONFIG_SPARSEMEM_VMEMMAP is configed,
>> kernel will use vmemmap to do the __pfn_to_page/page_to_pfn,
>> and kernel will not use the "classic sparse" to do the
>> __pfn_to_page/page_to_pfn.
>>
>> So export the vmemmap when CONFIG_SPARSEMEM_VMEMMAP is configed.
>> This makes the user applications (crash, etc) get faster
>> pfn_to_page/page_to_pfn operations too.
>>
>> Signed-off-by: Huang Shijie <shijie@os.amperecomputing.com>
>> ---
>> kernel/crash_core.c | 3 +++
>> 1 file changed, 3 insertions(+)
> Ack this one as it's needed by crash utility patches.
>
> Acked-by: Baoquan He <bhe@redhat.com>
Could you please merge this patch?
Thanks
Huang Shijie
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2024-01-17 1:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 2:07 [PATCH] crash_core: export vmemmap when CONFIG_SPARSEMEM_VMEMMAP is enabled Huang Shijie
2023-11-27 2:51 ` Baoquan He
2023-11-27 3:18 ` Shijie Huang
2023-11-28 3:25 ` Baoquan He
2023-11-28 3:31 ` Shijie Huang
2023-11-28 7:34 ` Baoquan He
2023-12-21 3:11 ` Shijie Huang
2023-12-21 4:12 ` Baoquan He
2024-01-17 1:32 ` Shijie Huang [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=2414bcf0-d7d6-485e-ba68-8d13a28da8b5@amperemail.onmicrosoft.com \
--to=shijie@amperemail.onmicrosoft.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@amperecomputing.com \
--cc=shijie@os.amperecomputing.com \
--cc=vgoyal@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).