From: Tejun Heo <tj@kernel.org>
To: Roger Lu <roger.lu@mediatek.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, srv_heupstream@mediatek.com,
Sascha Hauer <kernel@pengutronix.de>,
djkurtz@chromium.org, drinkcat@chromium.org,
fan.chen@mediatek.com, eddie.huang@mediatek.com
Subject: Re: [PATCH] PM / suspend: show workqueues busy name in suspend flow
Date: Tue, 28 Jun 2016 12:56:16 -0400 [thread overview]
Message-ID: <20160628165616.GD5185@htj.duckdns.org> (raw)
In-Reply-To: <1467020645.25092.24.camel@mtksdaap41>
Hello, Roger.
On Mon, Jun 27, 2016 at 05:44:05PM +0800, Roger Lu wrote:
> show_workqueue_state() is a better choice to me. However, only freezable
> workqueue is able to affect suspend flow. So, is there other mailing
> list discussing about showing freezable workqueue state only?? Maybe we
> can use that API in this case. Thanks very much.
>
> freezable workqueue means workqueue is created with flag WQ_FREEZABLE.
It's for debugging anyway and workqueue dumps usually are pretty
short. I don't think it's fine to use the same function. We can add
flags in the printouts but I'm not even sure that'd be necessary.
Thanks.
--
tejun
next prev parent reply other threads:[~2016-06-28 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1466586509-32400-1-git-send-email-roger.lu@mediatek.com>
2016-06-22 15:21 ` [PATCH] PM / suspend: show workqueues busy name in suspend flow Tejun Heo
[not found] ` <1467020645.25092.24.camel@mtksdaap41>
2016-06-28 16:56 ` Tejun Heo [this message]
2016-06-29 3:54 ` Roger Lu
2016-06-29 13:22 ` Tejun Heo
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=20160628165616.GD5185@htj.duckdns.org \
--to=tj@kernel.org \
--cc=djkurtz@chromium.org \
--cc=drinkcat@chromium.org \
--cc=eddie.huang@mediatek.com \
--cc=fan.chen@mediatek.com \
--cc=jiangshanlai@gmail.com \
--cc=kernel@pengutronix.de \
--cc=len.brown@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=roger.lu@mediatek.com \
--cc=srv_heupstream@mediatek.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