From: Baoquan He <bhe@redhat.com>
To: Donny Xia <donnyxia@google.com>
Cc: dyoung@redhat.com, vgoyal@redhat.com, kexec@lists.infradead.org
Subject: Re: Question about the size of VMCOREINFO
Date: Thu, 11 Aug 2022 08:45:54 +0800 [thread overview]
Message-ID: <20220811004554.GE373960@MiWiFi-R3L-srv> (raw)
In-Reply-To: <CAKE-ki_vO=2SXGsX8cjX+89MP09Tku4KyNANPTiEPKUx7y-LpA@mail.gmail.com>
Hi,
On 08/10/22 at 03:39pm, Donny Xia wrote:
> Hello Kdump Maintainers,
>
> We utilize the kexec and kdump feature heavily to collect the crash dump
> file when the kernel crashes. We write some customized values into
> VMCOREINFO and we find that eventually the size of the data we write
> exceeds the size of VMCOREINFO. I find that the size of VMCOREINFO is one
> page, which I believe is 4k. I am wondering is there any specific reason to
> choose this size? Is it possible to use a bigger number? Any suggestions
> about it would be appreciated.
No specific reason. Just our current usage of vmcoreinfo_data is enough to
cover our need. I don't see why you can't enlarge it to, e.g 2 pages or
more. Have you tried? E.g allocate more pages and change
VMCOREINFO_BYTES to the corresponding value.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2022-08-11 0:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKE-ki_vO=2SXGsX8cjX+89MP09Tku4KyNANPTiEPKUx7y-LpA@mail.gmail.com>
2022-08-10 22:42 ` Fwd: Question about the size of VMCOREINFO Donny Xia
2022-08-11 0:45 ` Baoquan He [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=20220811004554.GE373960@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=donnyxia@google.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--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