RE: [patch 0/2] tsc/adjust: Cure suspend/resume issues and prevent TSC deadline timer irq storm

2017-01-26 Thread Stanton, Kevin B
On Thurs, 15 Dec 2016, Thomas Gleixner wrote: >See the SDM. It suggests that the deadline is compared to the TSC value. >I don't care how it is implemented, but I very much care about it being >documented in the way it is implemented, which is obviously not the case. The TSC_DEADLINE behavior

RE: [patch 0/2] tsc/adjust: Cure suspend/resume issues and prevent TSC deadline timer irq storm

2017-01-26 Thread Stanton, Kevin B
On Thurs, 15 Dec 2016, Thomas Gleixner wrote: >See the SDM. It suggests that the deadline is compared to the TSC value. >I don't care how it is implemented, but I very much care about it being >documented in the way it is implemented, which is obviously not the case. The TSC_DEADLINE behavior

RE: [PATCH v4 1/4] Produce system time from correlated clocksource

2015-11-03 Thread Stanton, Kevin B
On Wed, 21 Oct 2015, Thomas Gleixner wrote: > On Tue, 20 Oct 2015, John Stultz wrote: >> Being able to have various hardware sharing a time base is quite >> useful, and methods for correlating timestamps together are useful. >> But I don't yet really understand why its important that we can >>

RE: [PATCH v4 1/4] Produce system time from correlated clocksource

2015-11-03 Thread Stanton, Kevin B
On Wed, 21 Oct 2015, Thomas Gleixner wrote: > On Tue, 20 Oct 2015, John Stultz wrote: >> Being able to have various hardware sharing a time base is quite >> useful, and methods for correlating timestamps together are useful. >> But I don't yet really understand why its important that we can >>