From: "Chen, Yu C" <yu.c.chen@intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
<linux-acpi@vger.kernel.org>, "Len Brown" <lenb@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
Peter Zijlstra <peterz@infradead.org>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Andre Eikmeyer <dev@deq.rocks>
Subject: Re: [PATCH] ACPI: x86: Apple T2 systems need early CPU offlining
Date: Tue, 18 Aug 2026 00:27:53 +0800 [thread overview]
Message-ID: <9bc46362-6b3b-48e0-b1a0-0cc7e84fd151@intel.com> (raw)
In-Reply-To: <aoCJGj8HixmJ9oaZ@wunner.de>
Thanks Lukas for bringing this up,
On 8/15/2026 11:43 PM, Lukas Wunner wrote:
> [cc += Chen Yu, start of thread is here:
> https://lore.kernel.org/all/20260812120326.155226-1-dev@deq.rocks/
> ]
>
> On Wed, Aug 12, 2026 at 02:03:26PM +0200, Andre Eikmeyer wrote:
>> Linux reports _OSI("Darwin") on x86 Apple systems. On T2 Macs, the
>> selected firmware suspend path makes secondary CPU startup during early
>> resume take several seconds per CPU.
>
> That's not a T2-specific issue. It occurs on older Intel Macs as well.
>
> Back in 2018, Chen Yu root-caused it to an invalid MTRR upon resume
> from system sleep:
>
> https://lore.kernel.org/all/20180319041843.28218-1-yu.c.chen@intel.com/
>
> I've been using his patch for 8 years to reduce resume time on my
> MacBookPro9,1. Unfortunately it was never applied upstream for
> reasons unknown. It probably just slipped through the cracks.
>
> You may want to test if his patch helps on T2 models as well.
> I think it's a more generic solution to the problem than the one
> you're proposing.
>
Glad it helped! At that time, it seemed that the issue might have
been related to broken Mac platforms, and we were changing the
generic x86 path. Maybe we can wait for Andre's feedback, I
can try again / or assist Andre - or just keep it out-of-tree;
that's also fine.
thanks,
Chenyu
prev parent reply other threads:[~2026-08-17 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 12:03 Andre Eikmeyer
2026-08-15 15:43 ` Lukas Wunner
2026-08-17 16:27 ` Chen, Yu C [this message]
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=9bc46362-6b3b-48e0-b1a0-0cc7e84fd151@intel.com \
--to=yu.c.chen@intel.com \
--cc=dev@deq.rocks \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=tglx@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®