From: Baoquan He <bhe@redhat.com>
To: Shijie Huang <shijie@amperemail.onmicrosoft.com>
Cc: Huang Shijie <shijie@os.amperecomputing.com>,
k-hagio-ab@nec.com, lijiang@redhat.com,
akpm@linux-foundation.org, 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: Tue, 28 Nov 2023 11:25:56 +0800 [thread overview]
Message-ID: <ZWVdxAv/PPHY3Ndl@MiWiFi-R3L-srv> (raw)
In-Reply-To: <33021b87-4c6a-45fc-a6ae-265765cfcd78@amperemail.onmicrosoft.com>
On 11/27/23 at 11:18am, Shijie Huang wrote:
>
> 在 2023/11/27 10:51, Baoquan He 写道:
> > Hi,
> >
> > 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.
> > Are there Crash or makedupfile patches posted yet to make use of this?
>
> I have patches for Crash to use the 'vmemmap', but after this patch is
> merged, I will send it out.
>
> (I think Kazu will not merge a crash patch which depends on a kernel patch
> which is not merged.)
Maybe post these userspace patches too so that Kazu can evaluat if those
improvement is necessary?
next prev parent reply other threads:[~2023-11-28 3:26 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 [this message]
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
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=ZWVdxAv/PPHY3Ndl@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dyoung@redhat.com \
--cc=k-hagio-ab@nec.com \
--cc=kexec@lists.infradead.org \
--cc=lijiang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@amperecomputing.com \
--cc=shijie@amperemail.onmicrosoft.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