From: Rik van Riel <riel@surriel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Dave Hansen <dave.hansen@intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org, kernel-team@fb.com,
Thomas Gleixner <tglx@linutronix.de>, Dave Jones <dsj@fb.com>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH v2] x86,mm: print likely CPU at segfault time
Date: Thu, 04 Aug 2022 23:01:56 -0400 [thread overview]
Message-ID: <17b83f59efbc568c1fe3154f82a5300f3b4cfe24.camel@surriel.com> (raw)
In-Reply-To: <YuwpQEYCwTl+m6j5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
On Thu, 2022-08-04 at 22:17 +0200, Ingo Molnar wrote:
>
> I've added the tidbit to the changelog that this only gets printed if
> show_unhandled_signals (/proc/sys/kernel/print-fatal-signals) is
The show_unhandled_signals variable seems to be controlled
through /proc/sys/debug/exception-trace, and be on by default.
Enabling print-fatal-signals makes the kernel a lot more
chatty, and does not offer the same value in my experiments :)
> enabled -
> which is off by default. So your patch expands upon a default-off
> debug
> printout in essence - where utility maximization is OK.
>
> Thanks,
>
> Ingo
>
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-08-05 3:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 19:54 [PATCH v2] x86,mm: print likely CPU at segfault time Rik van Riel
2022-08-04 20:17 ` Ingo Molnar
2022-08-05 3:01 ` Rik van Riel [this message]
2022-08-05 7:59 ` Ingo Molnar
2022-08-05 12:54 ` Rik van Riel
2022-08-05 10:08 ` Borislav Petkov
2022-08-05 12:53 ` Rik van Riel
2022-08-05 13:25 ` Borislav Petkov
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=17b83f59efbc568c1fe3154f82a5300f3b4cfe24.camel@surriel.com \
--to=riel@surriel.com \
--cc=dave.hansen@intel.com \
--cc=dsj@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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).