On Wed, 2018-07-11 at 05:51 -0700, Paul E. McKenney wrote:
> Interesting.  (I am assuming that the guest is printing these messages,
> not the host, but please let me know if my assumption is incorrect.)

No, this is all in the host. When the VMM (qemu, etc.) opens more files
and has to expand its fd_table, the threads which are currently in
KVM's vcpu_run() are making synchronize_sched() take multiple seconds.

> Are the CPUs saturated?  If so, could you please try booting with
> rcutree.kthread_prio=2?  If that prevents the messages from happening,
> then I need to put some work into guaranteeing forward progress.
> Otherwise, I need to figure out why the setting of rcu_urgent_qs is
> being ignored.

The CPUs shouldn't be saturated. The guest is fairly much idle. I can
best reproduce this by starting up the guest and then assigning a new
PCI device. At that point fairly much nothing is happening at all.

> I will assume the latter for the moment and see if I can spot the
> problem.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to