On 06/06/2016 16:22, Rik van Riel wrote:
>> Sorry for being late---again, I'd like to give a shot to a fix in KVM
>> guest code.
>
> This is in the guest code.
The key word is "KVM" guest code, :) i.e. not in kernel/sched/cputime.c
but in arch/x86/kernel/kvm.c.
Thanks,
Paolo
> Do you mean a
On Mon, 2016-06-06 at 15:44 +0200, Paolo Bonzini wrote:
>
> On 03/06/2016 15:10, Rik van Riel wrote:
> >
> > On Fri, 2016-06-03 at 13:21 +0800, Wanpeng Li wrote:
> > >
> > > From: Wanpeng Li
> > >
> > > I observed that sometimes st is 100% instantaneous, then idle is
> > > 100%
> > > even if
On 03/06/2016 15:10, Rik van Riel wrote:
> On Fri, 2016-06-03 at 13:21 +0800, Wanpeng Li wrote:
>> From: Wanpeng Li
>>
>> I observed that sometimes st is 100% instantaneous, then idle is
>> 100%
>> even if there is a cpu hog on the guest cpu after the cpu hotplug
>> comes
>> back(N.B. this can
On Fri, 2016-06-03 at 13:21 +0800, Wanpeng Li wrote:
> From: Wanpeng Li
>
> I observed that sometimes st is 100% instantaneous, then idle is
> 100%
> even if there is a cpu hog on the guest cpu after the cpu hotplug
> comes
> back(N.B. this can not always be readily reproduced). I add trace to
From: Wanpeng Li
I observed that sometimes st is 100% instantaneous, then idle is 100%
even if there is a cpu hog on the guest cpu after the cpu hotplug comes
back(N.B. this can not always be readily reproduced). I add trace to
capture it as below:
cpuhp/1-12[001] d.h1 167.461657: accou
5 matches
Mail list logo
