From: "Luck, Tony" <tony.luck@intel.com>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"anton@enomsg.org" <anton@enomsg.org>,
"ccross@android.com" <ccross@android.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
"Guilherme G. Piccoli" <kernel@gpiccoli.net>
Subject: RE: pstore/ramoops - why only collect a partial dmesg?
Date: Tue, 4 Jan 2022 18:46:01 +0000 [thread overview]
Message-ID: <8675f69c1643451b91f797b114dfc311@intel.com> (raw)
In-Reply-To: <c5a04638-90c2-8ec0-4573-a0e5d2e24b6b@igalia.com>
> There lies the issue: if I set panic_print to dump all backtraces, task
> info and memory state in a panic event, that information + the
> panic/oops and some previous relevant stuff, does it all fit in the 2M
> chunk? Likely so, but *if it doesn't fit*, we may lose _exactly_ the
> most important piece, which is the panic cause.
That does change things ... I wonder how many megabytes you need
for a big system (hundreds of cores, thousands of tasks)!
This use case does look like it could use multiple chunks in ramoops.
-Tony
next prev parent reply other threads:[~2022-01-04 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 14:43 pstore/ramoops - why only collect a partial dmesg? Guilherme G. Piccoli
2022-01-03 23:31 ` Luck, Tony
2022-01-04 12:17 ` Guilherme G. Piccoli
2022-01-04 17:00 ` Luck, Tony
2022-01-04 18:03 ` Guilherme G. Piccoli
2022-01-04 18:46 ` Luck, Tony [this message]
2022-01-04 19:36 ` Guilherme G. Piccoli
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=8675f69c1643451b91f797b114dfc311@intel.com \
--to=tony.luck@intel.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=kernel@gpiccoli.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 NNTP newsgroup(s).