From: sashiko-bot@kernel.org
To: "Mike Rapoport" <rppt@kernel.org>,
"Shradha Gupta" <shradhagupta@linux.microsoft.com>,
"Pasha Tatashin" <pasha.tatashin@soleen.com>,
"Baoquan He" <baoquan.he@linux.dev>,
"Pratyush Yadav" <pratyush@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>
Cc: "Kees Cook" <kees@kernel.org>, "Mark Brown" <broonie@kernel.org>,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH v3 1/2] kexec: Add helper to report an active kexec reboot
Date: Thu, 01 Oct 2026 13:28:06 +0000 [thread overview]
Message-ID: <20261001132806.91D501F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261001132147.1703600-1-shradhagupta@linux.microsoft.com>
> A shutdown callback in a loadable module may need to distinguish a
> kexec reboot from a normal restart, halt, or poweroff. The Hyper-V
> VMBus driver needs this distinction when moving its kexec cleanup into
> a common syscore shutdown callback.
>
> Add kexec_is_in_progress() and export it to GPL modules so the callback
> can remain guarded when VMBus is built as a module. Provide a false
> inline implementation when CONFIG_KEXEC_CORE is disabled.
>
> The helper reports only the normal kexec reboot path. Crash kexec and
> preserve-context kexec do not set this state.
>
> Signed-off-by: Shradha Gupta <shradhagupta@linux.microsoft.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261001132128.1703511-1-shradhagupta@linux.microsoft.com?part=1
next prev parent reply other threads:[~2026-10-01 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 13:21 [PATCH v3 0/2] hyperv: Run VMBus kexec cleanup from syscore shutdown Shradha Gupta
2026-10-01 13:21 ` [PATCH v3 1/2] kexec: Add helper to report an active kexec reboot Shradha Gupta
2026-10-01 13:28 ` sashiko-bot [this message]
2026-10-01 13:22 ` [PATCH v3 2/2] Drivers: hv: Run VMBus kexec cleanup from syscore shutdown Shradha Gupta
2026-10-01 16:14 ` [PATCH v3 0/2] hyperv: " Michael Kelley
2026-10-01 16:52 ` Bradley Morgan
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=20261001132806.91D501F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baoquan.he@linux.dev \
--cc=broonie@kernel.org \
--cc=kees@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=shradhagupta@linux.microsoft.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
all inboxes | Powered by JetHome®