From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 216352] [BISECTED] 250 ms system suspend performance regression
Date: Thu, 11 Aug 2022 21:03:22 +0000 [thread overview]
Message-ID: <bug-216352-62941-agImlnZFPi@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216352-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216352
--- Comment #4 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
(In reply to Len Brown from comment #3)
> Comparing the attached sleepgraph output of 5.19 to 5.19-rc8...
>
> acpi_ps_execute_method(PCI.XHC._PS0) plus
> msleep 120
> msleep 40
> msleep 40
> msleep 10
>
> have, as a group, shifted left from the suspend phase,
> where they used to overlap with other tasks,
> into the suspend_prepare phase, where they are the
> slowest operation.
We can probably return to the way it was if we detect the event mask needs
updating or not by checking if there is any connections, anyway if you attempt
to suspend while there is a bluetooth connection this extra latency would
probably reappear since in that case we need to update the event mask in order
to not wakeup the system by events such Disconnect Complete, not sure if this
is acceptable or perhaps the root cause is that notifiers are serialized so
while these commands are pending it prevents other notifiers to be run?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-08-11 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 0:47 [Bug 216352] New: [BISECTED] 250 ms system suspend performance regression bugzilla-daemon
2022-08-11 3:51 ` [Bug 216352] " bugzilla-daemon
2022-08-11 3:59 ` bugzilla-daemon
2022-08-11 4:01 ` bugzilla-daemon
2022-08-11 4:10 ` bugzilla-daemon
2022-08-11 21:03 ` bugzilla-daemon [this message]
2022-08-11 21:23 ` bugzilla-daemon
2022-08-12 18:10 ` bugzilla-daemon
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=bug-216352-62941-agImlnZFPi@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.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