From: Adrian Hunter <adrian.hunter@intel.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
James Clark <james.clark@linaro.org>,
"Thomas Gleixner" <tglx@kernel.org>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Pavel Machek <pavel@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Danilo Krummrich" <dakr@kernel.org>,
Johan Hovold <johan@kernel.org>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
Jiayuan Chen <jiayuan.chen@linux.dev>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>,
"Vineeth Pillai (Google)" <vineeth@bitbyteword.org>,
Frederic Weisbecker <frederic@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
<linux-perf-users@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>,
<driver-core@lists.linux.dev>
Subject: Re: [PATCH 1/6] irq_work: Re-raise pending irq_work after system resume
Date: Tue, 3 Nov 2026 17:46:32 +0200 [thread overview]
Message-ID: <2d6105b4-bd75-41b5-a7b2-da91bda31350@intel.com> (raw)
In-Reply-To: <20261102163937.KwllF-Pg@linutronix.de>
On 02/11/2026 18:39, Sebastian Andrzej Siewior wrote:
> On 2026-11-02 12:54:22 [+0200], Adrian Hunter wrote:
>>
>> Yes CPUs remain online for suspend2idle, but currently the choice between
>> suspend2idle and "deep" (S3) suspend is a user space choice,
>> refer /sys/power/mem_sleep. Many modern systems do not support S3
>> anymore, but it has not gone away.
>>
>>>
>>> Anyway, I'm torn; I would much rather make this trigger a WARN and have
>>
>> AI now also identifies ftrace, BPF, GHES NMI, and #MC as possible causes,
>> not just perf. I haven't tried to confirm any of those.
>>
>> And, belatedly, AI is now saying an irq_work raised before lapic_resume()
>> might result in #GP if the APIC is left in xAPIC mode at resume. Also
>> not confirmed.
>
> Could we flush this before similarly to what happens during CPU-hotplug.
> The question is if this event can stay enqueued during suspend (and
> handled on resume) or should be taken care before entering suspend.
WRT "might result in #GP if the APIC is left in xAPIC mode at resume",
the systems I have checked restore the APIC in x2APIC mode, so the
issue is theoretical at this point, although I can get "unchecked MSR
access error: WRMSR to 0x83f" if I deliberately add code to change
x2APIC to xAPIC early in S3 wake (in x86_acpi_suspend_lowlevel()),
and then do:
perf record -e power:suspend_resume --filter 'action == "machine_suspend" && start == 0' --no-buffering -C 0 -o /tmp/x.data &
rtcwake -m mem -s 10
The error can be avoided with:
diff --git a/arch/x86/include/asm/apic.h b/arch/x86/include/asm/apic.h
index 08c9aa176c33..41f93586f22c 100644
--- a/arch/x86/include/asm/apic.h
+++ b/arch/x86/include/asm/apic.h
@@ -63,6 +63,7 @@ extern int apic_verbosity;
extern int local_apic_timer_c2_ok;
extern bool apic_is_disabled;
+extern bool lapic_suspended;
extern unsigned int lapic_timer_period;
extern enum apic_intr_mode_id apic_intr_mode;
diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
index 40fa7bc7fb97..187cbfad0d76 100644
--- a/arch/x86/kernel/apic/apic.c
+++ b/arch/x86/kernel/apic/apic.c
@@ -2385,6 +2385,8 @@ void __init up_late_init(void)
}
#endif
+bool lapic_suspended;
+
/*
* Power management
*/
@@ -2454,6 +2456,8 @@ static int lapic_suspend(void *data)
*/
mask_ioapic_entries();
+ WRITE_ONCE(lapic_suspended, true);
+
disable_local_APIC();
irq_remapping_disable();
@@ -2534,6 +2538,8 @@ static void lapic_resume(void *data)
irq_remapping_reenable(x2apic_mode);
+ WRITE_ONCE(lapic_suspended, false);
+
local_irq_restore(flags);
}
diff --git a/arch/x86/kernel/irq_work.c b/arch/x86/kernel/irq_work.c
index 308c62411ff4..32386b7cf84e 100644
--- a/arch/x86/kernel/irq_work.c
+++ b/arch/x86/kernel/irq_work.c
@@ -25,7 +25,7 @@ DEFINE_IDTENTRY_SYSVEC(sysvec_irq_work)
void arch_irq_work_raise(void)
{
- if (!arch_irq_work_has_interrupt())
+ if (!arch_irq_work_has_interrupt() || READ_ONCE(lapic_suspended))
return;
__apic_send_IPI_self(IRQ_WORK_VECTOR);
next prev parent reply other threads:[~2026-11-03 15:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 7:40 [PATCH 0/6] perf/x86/intel/pt: Fix tracing across kexec, kdump and suspend Adrian Hunter
2026-11-02 7:40 ` [PATCH 1/6] irq_work: Re-raise pending irq_work after system resume Adrian Hunter
2026-11-02 9:06 ` Peter Zijlstra
2026-11-02 10:54 ` Adrian Hunter
2026-11-02 16:39 ` Sebastian Andrzej Siewior
2026-11-03 15:46 ` Adrian Hunter [this message]
2026-11-02 7:40 ` [PATCH 2/6] perf/x86/intel/pt: Stop tracing if VMXON has not yet happened Adrian Hunter
2026-11-02 9:57 ` Peter Zijlstra
2026-11-02 11:04 ` Adrian Hunter
2026-11-02 11:07 ` Peter Zijlstra
2026-11-02 7:40 ` [PATCH 3/6] perf/x86/intel/pt: Stop tracing at syscore shutdown Adrian Hunter
2026-11-02 10:04 ` Peter Zijlstra
2026-11-02 10:23 ` Adrian Hunter
2026-11-02 11:01 ` Peter Zijlstra
2026-11-02 16:15 ` Andi Kleen
2026-11-02 16:27 ` Adrian Hunter
2026-11-02 17:45 ` Andi Kleen
2026-11-02 18:13 ` Adrian Hunter
2026-11-02 7:40 ` [PATCH 4/6] perf/x86/intel/pt: Clear TraceEn in hardware in cpu_emergency_stop_pt() Adrian Hunter
2026-11-02 10:07 ` Peter Zijlstra
2026-11-02 18:41 ` Adrian Hunter
2026-11-02 7:40 ` [PATCH 5/6] perf/x86/intel/pt: Reset stale MSR state on CPU start and resume Adrian Hunter
2026-11-02 7:40 ` [PATCH 6/6] perf/x86/intel/pt: Stop tracing across system suspend Adrian Hunter
2026-11-02 10:10 ` [PATCH 0/6] perf/x86/intel/pt: Fix tracing across kexec, kdump and suspend Peter Zijlstra
2026-11-02 12:22 ` Adrian Hunter
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=2d6105b4-bd75-41b5-a7b2-da91bda31350@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=dakr@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=driver-core@lists.linux.dev \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jiayuan.chen@linux.dev \
--cc=johan@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=pavel@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@kernel.org \
--cc=vineeth@bitbyteword.org \
--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
all inboxes | Powered by JetHome®