From: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
To: "moss@cs.umass.edu" <moss@cs.umass.edu>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>
Cc: "dan.j.williams@intel.com" <dan.j.williams@intel.com>
Subject: Re: nvdimm,pmem: makedumpfile: __vtop4_x86_64: Can't get a valid pte.
Date: Mon, 28 Nov 2022 14:46:15 +0000 [thread overview]
Message-ID: <35997834-f6d2-0fc6-94a1-a7a25559d5ef@fujitsu.com> (raw)
In-Reply-To: <103666d5-3dcf-074c-0057-76b865f012a6@cs.umass.edu>
On 28/11/2022 20:53, Eliot Moss wrote:
> On 11/28/2022 7:04 AM, lizhijian@fujitsu.com wrote:
>> Hi folks,
>>
>> I'm going to make crash coredump support pmem region. So
>> I have modified kexec-tools to add pmem region to PT_LOAD of vmcore.
>>
>> But it failed at makedumpfile, log are as following:
>>
>> In my environment, i found the last 512 pages in pmem region will cause the error.
>
> I wonder if an issue I reported is related: when set up to map
> 2Mb (huge) pages, the last 2Mb of a large region got mapped as
> 4Kb pages, and then later, half of a large region was treated
> that way.
>
Could you share the url/link ? I'd like to take a look
> I've seen no response to the report, but assume folks have
> been busy with other things or perhaps giving this lower
> priority since it does not exactly *fail*, just not work as
> a user might think it should.
>
> Regards - Eliot Moss
next prev parent reply other threads:[~2022-11-28 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 12:04 lizhijian
[not found] ` <103666d5-3dcf-074c-0057-76b865f012a6@cs.umass.edu>
2022-11-28 14:46 ` lizhijian [this message]
2022-11-28 15:03 ` Eliot Moss
2022-11-29 5:16 ` lizhijian
2022-11-29 5:22 ` Eliot Moss
2022-11-30 20:05 ` Dan Williams
2022-12-01 9:42 ` lizhijian
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=35997834-f6d2-0fc6-94a1-a7a25559d5ef@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=dan.j.williams@intel.com \
--cc=kexec@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=moss@cs.umass.edu \
--cc=nvdimm@lists.linux.dev \
/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