On Fri, Jan 09, 2015 at 02:15:00PM +1100, Cyril Bur wrote:
> >
> > I am not too familar with it, but the kernel/watchdog.c code has calls to
> > kvm_check_and_clear_guest_paused(), which is probably a good place to
> > start.
> >
> Ah yes that, I did initially have a look at what it does when I
>
On Tue, 2015-01-06 at 10:01 -0500, Don Zickus wrote:
> On Tue, Jan 06, 2015 at 10:53:35AM +1100, Cyril Bur wrote:
> > On Mon, 2015-01-05 at 11:50 -0500, Don Zickus wrote:
> > > cc'ing Marcelo
> > >
> > > On Mon, Dec 22, 2014 at 04:06:02PM +1100, Cyril Bur wrote:
> > > > When the hypervisor pauses
On Tue, Jan 06, 2015 at 10:53:35AM +1100, Cyril Bur wrote:
> On Mon, 2015-01-05 at 11:50 -0500, Don Zickus wrote:
> > cc'ing Marcelo
> >
> > On Mon, Dec 22, 2014 at 04:06:02PM +1100, Cyril Bur wrote:
> > > When the hypervisor pauses a virtualised kernel the kernel will observe a
> > > jump
> > >
On Mon, 2015-01-05 at 14:09 -0800, Andrew Morton wrote:
> On Mon, 22 Dec 2014 16:06:02 +1100 Cyril Bur wrote:
>
> > When the hypervisor pauses a virtualised kernel the kernel will observe a
> > jump
> > in timebase, this can cause spurious messages from the softlockup detector.
> >
> > Whilst t
On Mon, 2015-01-05 at 11:50 -0500, Don Zickus wrote:
> cc'ing Marcelo
>
> On Mon, Dec 22, 2014 at 04:06:02PM +1100, Cyril Bur wrote:
> > When the hypervisor pauses a virtualised kernel the kernel will observe a
> > jump
> > in timebase, this can cause spurious messages from the softlockup detecto
On Mon, 22 Dec 2014 16:06:02 +1100 Cyril Bur wrote:
> When the hypervisor pauses a virtualised kernel the kernel will observe a jump
> in timebase, this can cause spurious messages from the softlockup detector.
>
> Whilst these messages are harmless, they are accompanied with a stack trace
> whi
cc'ing Marcelo
On Mon, Dec 22, 2014 at 04:06:02PM +1100, Cyril Bur wrote:
> When the hypervisor pauses a virtualised kernel the kernel will observe a jump
> in timebase, this can cause spurious messages from the softlockup detector.
>
> Whilst these messages are harmless, they are accompanied wit
When the hypervisor pauses a virtualised kernel the kernel will observe a jump
in timebase, this can cause spurious messages from the softlockup detector.
Whilst these messages are harmless, they are accompanied with a stack trace
which causes undue concern and more problematically the stack trace
When the hypervisor pauses a virtualised kernel the kernel will observe a jump
in timebase, this can cause spurious messages from the softlockup detector.
Whilst these messages are harmless, they are accompanied with a stack trace
which causes undue concern and more problematically the stack trace
9 matches
Mail list logo
