From: Oliver Neukum <oneukum@suse.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Peter Chen <hzpeterchen@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Tejun Heo <tj@kernel.org>, Florian Mickler <florian@mickler.org>,
Alan Stern <stern@rowland.harvard.edu>, Jan Kara <jack@suse.cz>,
Linux-pm mailing list <linux-pm@vger.kernel.org>
Subject: Re: Should suspend plug low-level devices?
Date: Thu, 17 Mar 2016 11:29:26 +0100 [thread overview]
Message-ID: <1458210566.4312.14.camel@suse.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1603171119260.3656@cbobk.fhfr.pm>
On Thu, 2016-03-17 at 11:20 +0100, Jiri Kosina wrote:
> On Thu, 17 Mar 2016, Oliver Neukum wrote:
>
> > Yes, but you are making the assumption that only the kthreads a driver
> > started are causing IO to it. That is a tall one.
> >
> > - logging
> > - network
> > - device discovery on busses
> > - detection of media
> > - knfsd
> >
> > All these things cause IO and I probably forgot some. Defined semantics
> > for the threads a driver starts are a good idea, but it leaves out the
> > really hard cases.
>
> So you named only one specific kthread here (knfsd), so let's focus on
> that one. Where is that one currently being frozen during suspend?
In svc_recv()
That concentration, however, is problematic. We can target anything
specific, but the point is, do we know what is running?
Regards
Oliver
next prev parent reply other threads:[~2016-03-17 10:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160316150053.GG6980@mtj.duckdns.org>
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
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 [this message]
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=1458210566.4312.14.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).