[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANRm+CyRS883Ne1XEX_dO=GKAN5vZZZ0HDZx4e5rB32c1s8Zow@mail.gmail.com>
Date: Tue, 24 May 2016 10:25:36 +0800
From: Wanpeng Li <kernellwp@...il.com>
To: David Matlack <dmatlack@...gle.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
kvm list <kvm@...r.kernel.org>,
Wanpeng Li <wanpeng.li@...mail.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Radim Krčmář <rkrcmar@...hat.com>,
Christian Borntraeger <borntraeger@...ibm.com>,
Yang Zhang <yang.zhang.wz@...il.com>
Subject: Re: [PATCH v3] KVM: halt-polling: poll if emulated lapic timer will
fire soon
2016-05-24 10:19 GMT+08:00 Wanpeng Li <kernellwp@...il.com>:
> 2016-05-24 2:01 GMT+08:00 David Matlack <dmatlack@...gle.com>:
>> On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li <kernellwp@...il.com> wrote:
>>> From: Wanpeng Li <wanpeng.li@...mail.com>
>>
>> I'm ok with this patch, but I'd like to better understand the target
>> workloads. What type of workloads do you expect to benefit from this?
>
> dynticks guests I think is one of workloads which can get benefit,
> there are lots of upcoming fire timers captured by my feature. Even
> during TCP testing. And also the workload of Yang's.
Do you think I should add an module parameter to enable/disable it
during module insmod or current patch is fine?
Regards,
Wanpeng Li
Powered by blists - more mailing lists