public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Ran Shalit <ranshalit@gmail.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>,
	linux-pm@vger.kernel.org
Subject: Re: suspend/resume PM criterion for application
Date: Wed, 10 Sep 2014 14:39:38 -0400	[thread overview]
Message-ID: <20227.1410374378@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 10 Sep 2014 21:23:28 +0300." <CAJ2oMhJpTQjgDgEgOqvLVJg7LQjtHg2by71=98uH=vq59zTmDg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]

On Wed, 10 Sep 2014 21:23:28 +0300, Ran Shalit said:

> As far as I understand, suspend/respond PM is not per device, but for
> all system,
> and wakeup source will resume again the whole system.
> I think you mean runtime suspend/resume in the answer.

The original question didn't specify. You said "suspending that application",
not the entire system.

And runtime suspend/resume of devices and even the CPU does fit within
your original question constraints.

If you're looking at system-wide suspend/resume specificially, there's
two basic schemes in use:

1) User hits a button, acpid or similar notices, and does a suspend to
disk/ram/papertape/whatever.

2) User hits a button, closes the lid, or a user inactivity timer expires.
A process notices, and asks all processes which have registered for suspend
notifications "Is it OK if we suspend?", and if nobody says "Nay", it does it.
If a process complains, it is repeatedly polled until it finishes whatever it
was doing and says "OK now".

[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

  reply	other threads:[~2014-09-10 18:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 17:26 suspend/resume PM criterion for application Ran Shalit
2014-09-10 17:59 ` Valdis.Kletnieks
2014-09-10 18:23   ` Ran Shalit
2014-09-10 18:39     ` Valdis.Kletnieks [this message]
2014-09-10 18:58       ` Ran Shalit
2014-09-10 19:25         ` Valdis.Kletnieks
2014-09-10 19:31           ` Ran Shalit
2014-09-11  5:32           ` AYAN KUMAR HALDER
2014-09-11  9:24             ` Ran Shalit
2014-09-14  6:11               ` Ran Shalit
2014-09-17  3:16                 ` Peter Teoh
2014-09-17  3:32                   ` Peter Teoh

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=20227.1410374378@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=ranshalit@gmail.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