Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, Apr 26, 2018 at 10:51 AM, Thomas Gleixner wrote: > On Thu, 26 Apr 2018, Rafael J. Wysocki wrote: > >> On Thu, Apr 26, 2018 at 9:42 AM, Thomas Gleixner wrote: >> > On Thu, 26 Apr 2018, Mike Galbraith wrote: >> >> On Wed, 2018-04-25 at 15:03 +0200,

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, Apr 26, 2018 at 10:51 AM, Thomas Gleixner wrote: > On Thu, 26 Apr 2018, Rafael J. Wysocki wrote: > >> On Thu, Apr 26, 2018 at 9:42 AM, Thomas Gleixner wrote: >> > On Thu, 26 Apr 2018, Mike Galbraith wrote: >> >> On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote: >> >> > Right, it

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, 26 Apr 2018, Rafael J. Wysocki wrote: > On Thu, Apr 26, 2018 at 9:42 AM, Thomas Gleixner wrote: > > On Thu, 26 Apr 2018, Mike Galbraith wrote: > >> On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote: > >> > Right, it does not matter. The real interesting one is

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, 26 Apr 2018, Rafael J. Wysocki wrote: > On Thu, Apr 26, 2018 at 9:42 AM, Thomas Gleixner wrote: > > On Thu, 26 Apr 2018, Mike Galbraith wrote: > >> On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote: > >> > Right, it does not matter. The real interesting one is d6ed449afdb3. > >> >

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, Apr 26, 2018 at 9:42 AM, Thomas Gleixner wrote: > On Thu, 26 Apr 2018, Mike Galbraith wrote: >> On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote: >> > Right, it does not matter. The real interesting one is d6ed449afdb3. >> >> FWIW, three boxen here

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, Apr 26, 2018 at 9:42 AM, Thomas Gleixner wrote: > On Thu, 26 Apr 2018, Mike Galbraith wrote: >> On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote: >> > Right, it does not matter. The real interesting one is d6ed449afdb3. >> >> FWIW, three boxen here suspend/resume fine, but

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, 26 Apr 2018, Mike Galbraith wrote: > On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote: > > Right, it does not matter. The real interesting one is d6ed449afdb3. > > FWIW, three boxen here suspend/resume fine, but repeatably exhibit the > below after a very few minute suspend, and a

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, 26 Apr 2018, Mike Galbraith wrote: > On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote: > > Right, it does not matter. The real interesting one is d6ed449afdb3. > > FWIW, three boxen here suspend/resume fine, but repeatably exhibit the > below after a very few minute suspend, and a

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote: > Right, it does not matter. The real interesting one is d6ed449afdb3. FWIW, three boxen here suspend/resume fine, but repeatably exhibit the below after a very few minute suspend, and a short bisect fingered your suspect. Distro is

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote: > Right, it does not matter. The real interesting one is d6ed449afdb3. FWIW, three boxen here suspend/resume fine, but repeatably exhibit the below after a very few minute suspend, and a short bisect fingered your suspect. Distro is

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Wed, 25 Apr 2018, Rafael J. Wysocki wrote: > On Wednesday, April 25, 2018 10:52:18 AM CEST Rafael J. Wysocki wrote: > > On Tuesday, April 24, 2018 10:09:28 AM CEST Thomas Gleixner wrote: > > > On Mon, 23 Apr 2018, John Stultz wrote: > > > > > > > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Wed, 25 Apr 2018, Rafael J. Wysocki wrote: > On Wednesday, April 25, 2018 10:52:18 AM CEST Rafael J. Wysocki wrote: > > On Tuesday, April 24, 2018 10:09:28 AM CEST Thomas Gleixner wrote: > > > On Mon, 23 Apr 2018, John Stultz wrote: > > > > > > > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Wednesday, April 25, 2018 10:52:18 AM CEST Rafael J. Wysocki wrote: > On Tuesday, April 24, 2018 10:09:28 AM CEST Thomas Gleixner wrote: > > On Mon, 23 Apr 2018, John Stultz wrote: > > > > > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote: > > > > Quoting Genki Sky (2018/04/23

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Wednesday, April 25, 2018 10:52:18 AM CEST Rafael J. Wysocki wrote: > On Tuesday, April 24, 2018 10:09:28 AM CEST Thomas Gleixner wrote: > > On Mon, 23 Apr 2018, John Stultz wrote: > > > > > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote: > > > > Quoting Genki Sky (2018/04/23 20:40:36

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Wednesday, April 25, 2018 8:50:15 AM CEST Pavel Machek wrote: > > --ReaqsoxgOBHFXBhH > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Tue 2018-04-24 10:09:28, Thomas Gleixner wrote: > > On Mon, 23 Apr 2018, John

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Wednesday, April 25, 2018 8:50:15 AM CEST Pavel Machek wrote: > > --ReaqsoxgOBHFXBhH > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Tue 2018-04-24 10:09:28, Thomas Gleixner wrote: > > On Mon, 23 Apr 2018, John

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Tuesday, April 24, 2018 10:09:28 AM CEST Thomas Gleixner wrote: > On Mon, 23 Apr 2018, John Stultz wrote: > > > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote: > > > Quoting Genki Sky (2018/04/23 20:40:36 -0400) > > >> I came across this thread for same reason as [0]: Daemons

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Tuesday, April 24, 2018 10:09:28 AM CEST Thomas Gleixner wrote: > On Mon, 23 Apr 2018, John Stultz wrote: > > > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote: > > > Quoting Genki Sky (2018/04/23 20:40:36 -0400) > > >> I came across this thread for same reason as [0]: Daemons getting > > >>

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Tue 2018-04-24 10:09:28, Thomas Gleixner wrote: > On Mon, 23 Apr 2018, John Stultz wrote: > > > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote: > > > Quoting Genki Sky (2018/04/23 20:40:36 -0400) > > >> I came across this thread for same reason as [0]: Daemons getting > > >>

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Tue 2018-04-24 10:09:28, Thomas Gleixner wrote: > On Mon, 23 Apr 2018, John Stultz wrote: > > > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote: > > > Quoting Genki Sky (2018/04/23 20:40:36 -0400) > > >> I came across this thread for same reason as [0]: Daemons getting > > >> killed by

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Tue, 24 Apr 2018, Genki Sky wrote: > Sorry to have been the bearer of bad news :(. No problem. We're not shooting the messengers > Again, I just have my user hat on here. It does seem like this unifying > would have been nice to have. And even, more compliant with the POSIX > definition of

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Tue, 24 Apr 2018, Genki Sky wrote: > Sorry to have been the bearer of bad news :(. No problem. We're not shooting the messengers > Again, I just have my user hat on here. It does seem like this unifying > would have been nice to have. And even, more compliant with the POSIX > definition of

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

Sorry to have been the bearer of bad news :(. Again, I just have my user hat on here. It does seem like this unifying would have been nice to have. And even, more compliant with the POSIX definition of MONOTONIC... On that note, maybe it is still worth introducing MONOTONIC_ACTIVE, but just as an

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

Sorry to have been the bearer of bad news :(. Again, I just have my user hat on here. It does seem like this unifying would have been nice to have. And even, more compliant with the POSIX definition of MONOTONIC... On that note, maybe it is still worth introducing MONOTONIC_ACTIVE, but just as an

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Mon, 23 Apr 2018, John Stultz wrote: > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote: > > Quoting Genki Sky (2018/04/23 20:40:36 -0400) > >> I came across this thread for same reason as [0]: Daemons getting > >> killed by systemd on resume (after >WatchdogSec seconds of > >>

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Mon, 23 Apr 2018, John Stultz wrote: > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote: > > Quoting Genki Sky (2018/04/23 20:40:36 -0400) > >> I came across this thread for same reason as [0]: Daemons getting > >> killed by systemd on resume (after >WatchdogSec seconds of > >> suspending).

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote: > Quoting Genki Sky (2018/04/23 20:40:36 -0400) >> I came across this thread for same reason as [0]: Daemons getting >> killed by systemd on resume (after >WatchdogSec seconds of >> suspending). I'm using master branch of systemd

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote: > Quoting Genki Sky (2018/04/23 20:40:36 -0400) >> I came across this thread for same reason as [0]: Daemons getting >> killed by systemd on resume (after >WatchdogSec seconds of >> suspending). I'm using master branch of systemd and the kernel.

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

Quoting Genki Sky (2018/04/23 20:40:36 -0400) > I came across this thread for same reason as [0]: Daemons getting > killed by systemd on resume (after >WatchdogSec seconds of > suspending). I'm using master branch of systemd and the kernel. As > mentioned, systemd uses CLOCK_MONOTONIC, originally

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

Quoting Genki Sky (2018/04/23 20:40:36 -0400) > I came across this thread for same reason as [0]: Daemons getting > killed by systemd on resume (after >WatchdogSec seconds of > suspending). I'm using master branch of systemd and the kernel. As > mentioned, systemd uses CLOCK_MONOTONIC, originally

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

Hello, I came across this thread for same reason as [0]: Daemons getting killed by systemd on resume (after >WatchdogSec seconds of suspending). I'm using master branch of systemd and the kernel. As mentioned, systemd uses CLOCK_MONOTONIC, originally expecting it to not include suspend time.

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

Hello, I came across this thread for same reason as [0]: Daemons getting killed by systemd on resume (after >WatchdogSec seconds of suspending). I'm using master branch of systemd and the kernel. As mentioned, systemd uses CLOCK_MONOTONIC, originally expecting it to not include suspend time.

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

Hi On Fri, Apr 20, 2018 at 7:44 AM, Sergey Senozhatsky wrote: > On (04/20/18 06:37), David Herrmann wrote: >> >> I get lots of timer-errors on Arch-Linux booting current master, after >> a suspend/resume cycle. Just a selection of errors I see on resume: > >

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

Hi On Fri, Apr 20, 2018 at 7:44 AM, Sergey Senozhatsky wrote: > On (04/20/18 06:37), David Herrmann wrote: >> >> I get lots of timer-errors on Arch-Linux booting current master, after >> a suspend/resume cycle. Just a selection of errors I see on resume: > > Hello David, > Any chance you can

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On (04/20/18 06:37), David Herrmann wrote: > > I get lots of timer-errors on Arch-Linux booting current master, after > a suspend/resume cycle. Just a selection of errors I see on resume: Hello David, Any chance you can revert the patches in question and test? I'm running ARCH

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On (04/20/18 06:37), David Herrmann wrote: > > I get lots of timer-errors on Arch-Linux booting current master, after > a suspend/resume cycle. Just a selection of errors I see on resume: Hello David, Any chance you can revert the patches in question and test? I'm running ARCH

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

Hey On Tue, Mar 13, 2018 at 7:11 PM, John Stultz wrote: > On Mon, Mar 12, 2018 at 11:36 PM, Ingo Molnar wrote: >> Ok, I have edited all the changelogs accordingly (and also flipped around the >> 'clock MONOTONIC' language to the more readable 'the

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

Hey On Tue, Mar 13, 2018 at 7:11 PM, John Stultz wrote: > On Mon, Mar 12, 2018 at 11:36 PM, Ingo Molnar wrote: >> Ok, I have edited all the changelogs accordingly (and also flipped around the >> 'clock MONOTONIC' language to the more readable 'the MONOTONIC clock' >> variant), >> the resulting

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Mon, Mar 12, 2018 at 11:36 PM, Ingo Molnar wrote: > > * Linus Torvalds wrote: > >> On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote: >> > >> > This really needs lot of testing, documentation updates and more input from

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Mon, Mar 12, 2018 at 11:36 PM, Ingo Molnar wrote: > > * Linus Torvalds wrote: > >> On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote: >> > >> > This really needs lot of testing, documentation updates and more input from >> > userspace folks to make a final decision. >> >> Honestly, I

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

* Linus Torvalds wrote: > On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote: > > > > This really needs lot of testing, documentation updates and more input from > > userspace folks to make a final decision. > > Honestly, I don't think

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

* Linus Torvalds wrote: > On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote: > > > > This really needs lot of testing, documentation updates and more input from > > userspace folks to make a final decision. > > Honestly, I don't think we'd get the testing this kind of change needs >

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, 1 Mar 2018, Thomas Gleixner wrote: > On Thu, 1 Mar 2018, Linus Torvalds wrote: > > On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote: > > > > > > This really needs lot of testing, documentation updates and more input > > > from > > > userspace folks to make a

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, 1 Mar 2018, Thomas Gleixner wrote: > On Thu, 1 Mar 2018, Linus Torvalds wrote: > > On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote: > > > > > > This really needs lot of testing, documentation updates and more input > > > from > > > userspace folks to make a final decision. > > > >

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, 1 Mar 2018 19:41:35 +0100 (CET) Thomas Gleixner wrote: > I'm old enough to have learned that conflate means unify or combine, but > I'm still not old enough to be stubborn about it :) You need to watch more American Cable News channels to know what "conflate" means

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, 1 Mar 2018 19:41:35 +0100 (CET) Thomas Gleixner wrote: > I'm old enough to have learned that conflate means unify or combine, but > I'm still not old enough to be stubborn about it :) You need to watch more American Cable News channels to know what "conflate" means today. -- Steve

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, 1 Mar 2018, Linus Torvalds wrote: > On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote: > > > > This really needs lot of testing, documentation updates and more input from > > userspace folks to make a final decision. > > Honestly, I don't think we'd get the

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, 1 Mar 2018, Linus Torvalds wrote: > On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote: > > > > This really needs lot of testing, documentation updates and more input from > > userspace folks to make a final decision. > > Honestly, I don't think we'd get the testing this kind of

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote: > > This really needs lot of testing, documentation updates and more input from > userspace folks to make a final decision. Honestly, I don't think we'd get the testing this kind of change needs except by just trying it.

Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote: > > This really needs lot of testing, documentation updates and more input from > userspace folks to make a final decision. Honestly, I don't think we'd get the testing this kind of change needs except by just trying it. I'm willing to

[RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

While working through the melted spectrum induced backlog I found that last years discussion about unifying clock MONOTONIC and clock BOOTTIME has died out and obviously nobody had time to do testing on that half baken RFC patch:

[RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME

While working through the melted spectrum induced backlog I found that last years discussion about unifying clock MONOTONIC and clock BOOTTIME has died out and obviously nobody had time to do testing on that half baken RFC patch: