[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANRm+CwUOGTHQc+VYfQbUZCFGscyyoqqxBqq-NFLdPP7dTUm6A@mail.gmail.com>
Date: Mon, 6 Nov 2017 18:06:47 +0800
From: Wanpeng Li <kernellwp@...il.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
kvm <kvm@...r.kernel.org>,
Radim Krčmář <rkrcmar@...hat.com>,
Wanpeng Li <wanpeng.li@...mail.com>
Subject: Re: [PATCH] KVM: X86: Fix softlockup when get the current kvmclock timestamp
2017-11-06 17:29 GMT+08:00 Paolo Bonzini <pbonzini@...hat.com>:
> On 06/11/2017 01:55, Wanpeng Li wrote:
>> This can be reproduced when running kvm-unit-tests/hyperv_stimer.flat and
>> cpu-hotplug stress simultaneously. kvm_get_time_scale() takes too long which
>> results in softlockup.
>
> Apart from the pr_debug, kvm_get_time_scale should take less than a
> microsecond. The patch is fine, but can you confirm that pr_debug is
> the culprit?
I can still encounter softlockup after removing the pr_debug.
Regards,
Wanpeng Li
Powered by blists - more mailing lists