> diff --git a/arch/arm/include/asm/kvm_host.h b/arch/arm/include/asm/kvm_host.h
> index 4cd8732..a5fd858 100644
> --- a/arch/arm/include/asm/kvm_host.h
> +++ b/arch/arm/include/asm/kvm_host.h
> @@ -284,6 +284,10 @@ static inline void kvm_arch_sync_events(struct kvm *kvm)
> {}
> static inline
> diff --git a/arch/arm/include/asm/kvm_host.h b/arch/arm/include/asm/kvm_host.h
> index 4cd8732..a5fd858 100644
> --- a/arch/arm/include/asm/kvm_host.h
> +++ b/arch/arm/include/asm/kvm_host.h
> @@ -284,6 +284,10 @@ static inline void kvm_arch_sync_events(struct kvm *kvm)
> {}
> static inline
2016-05-24 2:01 GMT+08:00 David Matlack :
> On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li wrote:
>> From: Wanpeng Li
>
> I'm ok with this patch, but I'd like to better understand the target
> workloads. What type of workloads do you
2016-05-24 2:01 GMT+08:00 David Matlack :
> On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li wrote:
>> From: Wanpeng Li
>
> 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?
>
In addition, as Paolo great
2016-05-24 14:59 GMT+08:00 Christian Borntraeger :
> On 05/24/2016 04:25 AM, Wanpeng Li wrote:
>> 2016-05-24 10:19 GMT+08:00 Wanpeng Li :
>>> 2016-05-24 2:01 GMT+08:00 David Matlack :
On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li
2016-05-24 14:59 GMT+08:00 Christian Borntraeger :
> On 05/24/2016 04:25 AM, Wanpeng Li wrote:
>> 2016-05-24 10:19 GMT+08:00 Wanpeng Li :
>>> 2016-05-24 2:01 GMT+08:00 David Matlack :
On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li wrote:
> From: Wanpeng Li
I'm ok with this patch,
2016-05-24 14:59 GMT+08:00 Christian Borntraeger :
> On 05/24/2016 04:25 AM, Wanpeng Li wrote:
>> 2016-05-24 10:19 GMT+08:00 Wanpeng Li :
>>> 2016-05-24 2:01 GMT+08:00 David Matlack :
On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li
2016-05-24 14:59 GMT+08:00 Christian Borntraeger :
> On 05/24/2016 04:25 AM, Wanpeng Li wrote:
>> 2016-05-24 10:19 GMT+08:00 Wanpeng Li :
>>> 2016-05-24 2:01 GMT+08:00 David Matlack :
On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li wrote:
> From: Wanpeng Li
I'm ok with this patch,
2016-05-24 10:19 GMT+08:00 Wanpeng Li :
> 2016-05-24 2:01 GMT+08:00 David Matlack :
>> On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li wrote:
>>> From: Wanpeng Li
>>
>> I'm ok with this patch, but I'd like to
2016-05-24 10:19 GMT+08:00 Wanpeng Li :
> 2016-05-24 2:01 GMT+08:00 David Matlack :
>> On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li wrote:
>>> From: Wanpeng Li
>>
>> 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
On 05/24/2016 04:25 AM, Wanpeng Li wrote:
> 2016-05-24 10:19 GMT+08:00 Wanpeng Li :
>> 2016-05-24 2:01 GMT+08:00 David Matlack :
>>> On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li wrote:
From: Wanpeng Li
>>>
On 05/24/2016 04:25 AM, Wanpeng Li wrote:
> 2016-05-24 10:19 GMT+08:00 Wanpeng Li :
>> 2016-05-24 2:01 GMT+08:00 David Matlack :
>>> On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li wrote:
From: Wanpeng Li
>>>
>>> I'm ok with this patch, but I'd like to better understand the target
>>>
2016-05-24 10:19 GMT+08:00 Wanpeng Li :
> 2016-05-24 2:01 GMT+08:00 David Matlack :
>> On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li wrote:
>>> From: Wanpeng Li
>>
>> I'm ok with this patch, but I'd like to
2016-05-24 10:19 GMT+08:00 Wanpeng Li :
> 2016-05-24 2:01 GMT+08:00 David Matlack :
>> On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li wrote:
>>> From: Wanpeng Li
>>
>> 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
2016-05-24 2:01 GMT+08:00 David Matlack :
> On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li wrote:
>> From: Wanpeng Li
>
> I'm ok with this patch, but I'd like to better understand the target
> workloads. What type of workloads do you
2016-05-24 2:01 GMT+08:00 David Matlack :
> On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li wrote:
>> From: Wanpeng Li
>
> 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
On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li wrote:
> From: Wanpeng Li
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?
>
> If an emulated lapic timer will fire
On Sun, May 22, 2016 at 5:42 PM, Wanpeng Li wrote:
> From: Wanpeng Li
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?
>
> If an emulated lapic timer will fire soon(in the scope of 10us the
> base of
From: Wanpeng Li
If an emulated lapic timer will fire soon(in the scope of 10us the
base of dynamic halt-polling, lower-end of message passing workload
latency TCP_RR's poll time < 10us) we can treat it as a short halt,
and poll to wait it fire, the fire callback
From: Wanpeng Li
If an emulated lapic timer will fire soon(in the scope of 10us the
base of dynamic halt-polling, lower-end of message passing workload
latency TCP_RR's poll time < 10us) we can treat it as a short halt,
and poll to wait it fire, the fire callback apic_timer_fn() will set
20 matches
Mail list logo