Linux Watchdog driver development
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mrungta@google.com
Cc: Mayank Rungta via B4 Relay
	<devnull+mrungta.google.com@kernel.org>,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Tzung-Bi Shih <tzungbi@kernel.org>,
	Douglas Anderson <dianders@chromium.org>,
	linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 1/2] nmi: Export CPU backtrace APIs for loadable modules
Date: Thu, 6 Aug 2026 16:44:04 -0700	[thread overview]
Message-ID: <20260806164404.aca27fe3593bb5c95828807d@linux-foundation.org> (raw)
In-Reply-To: <20260730-export-cpu-backtrace-apis-v1-1-bace8e1cb817@google.com>

On Thu, 30 Jul 2026 15:00:21 -0700 Mayank Rungta via B4 Relay <devnull+mrungta.google.com@kernel.org> wrote:

> From: Mayank Rungta <mrungta@google.com>
> 
> Currently, CPU backtrace functions cannot be called from loadable
> modules because the underlying helper arch_trigger_cpumask_backtrace()
> is not exported.
> 
> Instead of exporting arch_trigger_cpumask_backtrace() individually
> across every supported architecture, introduce and export a common
> helper, cpumask_backtrace(), in lib/nmi_backtrace.c. Update the four
> inline CPU backtrace macros in include/linux/nmi.h to route through this
> centralized helper.

Reviewed-by: Andrew Morton <akpm@linux-foundation.org>


  parent reply	other threads:[~2026-08-06 23:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 22:00 [PATCH 0/2] watchdog: pretimeout: Allow building dump governor as module Mayank Rungta via B4 Relay
2026-07-30 22:00 ` [PATCH 1/2] nmi: Export CPU backtrace APIs for loadable modules Mayank Rungta via B4 Relay
2026-07-31  1:54   ` Doug Anderson
2026-08-06 21:40   ` Guenter Roeck
2026-08-06 23:44   ` Andrew Morton [this message]
2026-08-07  3:50   ` Guenter Roeck
2026-07-30 22:00 ` [PATCH 2/2] watchdog: pretimeout: Convert dump pretimeout governor to tristate Mayank Rungta via B4 Relay
2026-07-31  1:55   ` Doug Anderson
2026-08-01 12:38   ` Tzung-Bi Shih
2026-08-06 21:41   ` Guenter Roeck
2026-08-06 23:44   ` Andrew Morton
2026-08-07  3:50   ` Guenter Roeck
2026-07-30 22:50 ` [PATCH 0/2] watchdog: pretimeout: Allow building dump governor as module Andrew Morton
2026-07-30 23:39   ` Mayank Rungta
2026-07-31 21:01     ` Andrew Morton
2026-07-31 21:19       ` Guenter Roeck

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=20260806164404.aca27fe3593bb5c95828807d@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=devnull+mrungta.google.com@kernel.org \
    --cc=dianders@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mrungta@google.com \
    --cc=tzungbi@kernel.org \
    --cc=wim@linux-watchdog.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