Re: [PATCH 0/5 V5] Avoid soft lockup message when KVM is stoppedby host

[Avi Kivity]

On 12/16/2011 11:31 AM, Marcelo Tosatti wrote:
> > >
> > > Slow enough that progress of the watchdog thread is unable to keep up
> > > with timer interrupt processing. This is considered a hang and
> > > should be reported.
> > 
> > It's not a guest hang though!
>
> No, but your host system is in such a load state that for the sake of
> system usability you better print out a warning message.

What's the point in printing it in the guest?  The guest can't observe
host conditions.

> I don't see the advantage of preempt notifiers over the simple, paravirt
> solution proposed? Note kvmclock is already paravirt.

Right.

> What do you want to be done in preempt notifiers? Measure what to
> consider setting this flag?

Preemption while TASK_RUNNING or TASK_UNINTERRUPTIBLE.

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/