On Wed, Sep 09, 2015 at 11:51:43AM +0200, Thomas Gleixner wrote:
> On Tue, 8 Sep 2015, Shaohua Li wrote:
> > On Tue, Sep 08, 2015 at 05:08:03PM +0200, Thomas Gleixner wrote:
> > > For non paravirt kernels which can read the TSC directly, we'd need a
> > > way to transport that information. A simple
On Tue, 8 Sep 2015, Shaohua Li wrote:
> On Tue, Sep 08, 2015 at 05:08:03PM +0200, Thomas Gleixner wrote:
> > For non paravirt kernels which can read the TSC directly, we'd need a
> > way to transport that information. A simple mechanism would be to
> > query an emulated MSR from the watchdog which
On Tue, Sep 08, 2015 at 05:08:03PM +0200, Thomas Gleixner wrote:
> On Tue, 8 Sep 2015, Mathieu Desnoyers wrote:
> > Introduce WATCHDOG_RETRY to bound the number of retry (in the
> > unlikely event of a bogus clock source for wdnow). If the
> > number of retry has been reached, disable the watchdog
On Tue, 8 Sep 2015, Mathieu Desnoyers wrote:
> Introduce WATCHDOG_RETRY to bound the number of retry (in the
> unlikely event of a bogus clock source for wdnow). If the
> number of retry has been reached, disable the watchdog timer.
This does not make any sense at all. Why would the clocksource be
I have been getting those warnings across a range of guest
kernels in my development virtual machines. The host is a
3.13 Ubuntu kernel. The latest guest on which I reproduced
this is a 4.2 kernel (akpm's tree).
[ 126.902240] clocksource: timekeeping watchdog: Marking clocksource 'tsc' as
unstab
5 matches
Mail list logo
