* Fwd: Question about the size of VMCOREINFO
[not found] <CAKE-ki_vO=2SXGsX8cjX+89MP09Tku4KyNANPTiEPKUx7y-LpA@mail.gmail.com>
@ 2022-08-10 22:42 ` Donny Xia
2022-08-11 0:45 ` Baoquan He
1 sibling, 0 replies; 2+ messages in thread
From: Donny Xia @ 2022-08-10 22:42 UTC (permalink / raw)
To: kexec
HTML email was blocked. Forward to the email list.
---------- Forwarded message ---------
From: Donny Xia <donnyxia@google.com>
Date: Wed, Aug 10, 2022 at 3:39 PM
Subject: Question about the size of VMCOREINFO
To: <dyoung@redhat.com>
Cc: <bhe@redhat.com>, <vgoyal@redhat.com>, <kexec@lists.infradead.org>
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.
Thanks.
Regards,
Donny Xia
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: Question about the size of VMCOREINFO
[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
1 sibling, 0 replies; 2+ messages in thread
From: Baoquan He @ 2022-08-11 0:45 UTC (permalink / raw)
To: Donny Xia; +Cc: dyoung, vgoyal, kexec
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-08-11 0:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox