From: Oliver Neukum <oneukum@suse.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Tejun Heo <tj@kernel.org>, Alan Stern <stern@rowland.harvard.edu>,
Jan Kara <jack@suse.cz>, Peter Chen <hzpeterchen@gmail.com>,
Florian Mickler <florian@mickler.org>,
Linux-pm mailing list <linux-pm@vger.kernel.org>
Subject: Re: Should suspend plug low-level devices?
Date: Thu, 17 Mar 2016 08:50:28 +0100 [thread overview]
Message-ID: <1458201028.4312.0.camel@suse.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1603170036310.3656@cbobk.fhfr.pm>
On Thu, 2016-03-17 at 00:42 +0100, Jiri Kosina wrote:
> I am (slowly) working towards this goal. First I am trying to make
> sure
> that all the kernel is using the kthread freezing API in a
> well-defined
> way (which is currently not the case at all).
>
> Before this is done, it is more or less impossible to analyse the
> current
> users and make any decisions on top of that.
>
> Once some kind of analysis is possible, I am pretty sure that we'll
> be
> able to get rid of most kthread freezing by introducing fs freezing
> during
> suspend (and fixing a lot of currently existing bugs as a nice
> side-effect), and perhaps eventually ditch the kthread freezer
> altogether.
But what about character devices?
Regards
Oliver
next prev parent reply other threads:[~2016-03-17 8:01 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 3:20 Freezable workqueue blocks non-freezable workqueue during the system resume process Peter Chen
2016-02-23 9:47 ` Peter Chen
2016-02-23 15:34 ` Alan Stern
2016-02-24 7:24 ` Peter Chen
2016-02-25 22:01 ` Tejun Heo
2016-02-26 6:19 ` Peter Chen
2016-03-02 16:00 ` Tejun Heo
2016-03-03 9:33 ` Jan Kara
2016-03-11 17:56 ` Tejun Heo
2016-03-14 7:22 ` Jan Kara
2016-03-14 14:37 ` Alan Stern
2016-03-15 9:25 ` Jan Kara
2016-03-16 15:00 ` Tejun Heo
2016-03-16 15:37 ` Should suspend plug low-level devices? Alan Stern
2016-03-16 16:31 ` Rafael J. Wysocki
2016-03-16 16:35 ` Tejun Heo
2016-03-16 16:39 ` Rafael J. Wysocki
2016-03-16 23:18 ` Jiri Kosina
2016-03-16 23:24 ` Rafael J. Wysocki
2016-03-16 23:42 ` Jiri Kosina
2016-03-16 23:48 ` Rafael J. Wysocki
2016-03-17 7:50 ` Oliver Neukum [this message]
2016-03-17 8:02 ` Jiri Kosina
2016-03-17 8:20 ` Oliver Neukum
2016-03-17 8:35 ` Jiri Kosina
2016-03-17 9:12 ` Oliver Neukum
2016-03-17 10:20 ` Jiri Kosina
2016-03-17 10:29 ` Oliver Neukum
2016-03-17 10:36 ` Jiri Kosina
2016-03-17 18:55 ` Alan Stern
2016-03-18 20:29 ` Tejun Heo
2016-03-17 0:05 ` Tejun Heo
2016-03-17 18:58 ` Alan Stern
2016-03-18 20:25 ` Tejun Heo
2016-03-17 18:53 ` Alan Stern
2016-03-18 20:29 ` Tejun Heo
2016-03-16 16:34 ` Tejun Heo
2016-03-17 18:51 ` Alan Stern
2016-03-18 20:32 ` Tejun Heo
2016-03-18 21:06 ` Alan Stern
2016-03-20 18:29 ` Tejun Heo
2016-03-21 14:38 ` Alan Stern
2016-03-30 17:09 ` 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=1458201028.4312.0.camel@suse.com \
--to=oneukum@suse.com \
--cc=florian@mickler.org \
--cc=hzpeterchen@gmail.com \
--cc=jack@suse.cz \
--cc=jikos@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.