All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: tglx@linutronix.de, dmitry.torokhov@gmail.com,
	torvalds@linux-foundation.org,
	kernel list <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>
Subject: Re: CLOCK_MONOTONIC, BOOTTIME, suspend and screensaver regression
Date: Tue, 24 Apr 2018 14:08:06 +0200	[thread overview]
Message-ID: <20180424120806.GA14523@amd> (raw)
In-Reply-To: <20180424120659.GA14411@amd>

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

On Tue 2018-04-24 14:06:59, Pavel Machek wrote:
> Hi!
> 
> In 4.17-rc1 I have weird problems with network manager... and I also
> have screensaver kicking just after resume.
> 
> Searching the git logs:
> 
>        - The most interesting change is the consolidation of clock
>          MONOTONIC
> 	          and clock BOOTTIME.
> 
>          Clock MONOTONIC behaves now exactly like clock BOOTTIME and
>          does
> 	          not longer ignore the time spent in suspend. A new
>          clock
> 	          MONOTONIC_ACTIVE is provived which behaves like
>          clock MONOTONIC in
> 	          kernels before this change. This allows applications
>          to
> 	          programmatically check for the clock MONOTONIC
>          behaviour.
> 
>          As discussed in the review thread, this has the potential of
> 	          breaking user space and we might have to revert
> 	          this. Knock on wood
> 		           that we can avoid that exercise.
> 
> 
> ...I believe you are breaking userspace for me. How can we check that?

And actually... how is it supposed to work? If monotonic behaves same
way as boottime, we'll have nasty thundering herd problem after
resume, riight?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

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

  reply	other threads:[~2018-04-24 12:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 12:07 CLOCK_MONOTONIC, BOOTTIME, suspend and screensaver regression Pavel Machek
2018-04-24 12:08 ` Pavel Machek [this message]
2018-04-24 22:13 ` Rafael J. Wysocki

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=20180424120806.GA14523@amd \
    --to=pavel@ucw.cz \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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.