Re: [PATCH] kvm: x86: make lapic hrtimer pinned

2016-04-22 21:12 GMT+08:00 Luiz Capitulino : > On Fri, 22 Apr 2016 07:12:51 +0800 > Wanpeng Li wrote: > >> 2016-04-05 20:40 GMT+08:00 Luiz Capitulino : >> > On Tue, 5 Apr 2016 14:18:01 +0800 >> > Yang Zhang

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

2016-04-22 21:12 GMT+08:00 Luiz Capitulino : > On Fri, 22 Apr 2016 07:12:51 +0800 > Wanpeng Li wrote: > >> 2016-04-05 20:40 GMT+08:00 Luiz Capitulino : >> > On Tue, 5 Apr 2016 14:18:01 +0800 >> > Yang Zhang wrote: >> > >> >> On 2016/4/5 5:00, Rik van Riel wrote: >> >> > On Mon, 2016-04-04 at

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

On Fri, 22 Apr 2016 07:12:51 +0800 Wanpeng Li wrote: > 2016-04-05 20:40 GMT+08:00 Luiz Capitulino : > > On Tue, 5 Apr 2016 14:18:01 +0800 > > Yang Zhang wrote: > > > >> On 2016/4/5 5:00, Rik van Riel wrote: > >> > On Mon,

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

On Fri, 22 Apr 2016 07:12:51 +0800 Wanpeng Li wrote: > 2016-04-05 20:40 GMT+08:00 Luiz Capitulino : > > On Tue, 5 Apr 2016 14:18:01 +0800 > > Yang Zhang wrote: > > > >> On 2016/4/5 5:00, Rik van Riel wrote: > >> > On Mon, 2016-04-04 at 16:46 -0400, Luiz Capitulino wrote: > >> >> When a

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

2016-04-05 20:40 GMT+08:00 Luiz Capitulino : > On Tue, 5 Apr 2016 14:18:01 +0800 > Yang Zhang wrote: > >> On 2016/4/5 5:00, Rik van Riel wrote: >> > On Mon, 2016-04-04 at 16:46 -0400, Luiz Capitulino wrote: >> >> When a vCPU runs on a nohz_full

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

2016-04-05 20:40 GMT+08:00 Luiz Capitulino : > On Tue, 5 Apr 2016 14:18:01 +0800 > Yang Zhang wrote: > >> On 2016/4/5 5:00, Rik van Riel wrote: >> > On Mon, 2016-04-04 at 16:46 -0400, Luiz Capitulino wrote: >> >> When a vCPU runs on a nohz_full core, the hrtimer used by >> >> the lapic emulation

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

On 2016/4/5 23:54, Radim Krčmář wrote: 2016-04-05 14:18+0800, Yang Zhang: On 2016/4/5 5:00, Rik van Riel wrote: Given that delivering a timer to a guest seems to involve trapping from the guest to the host, anyway, I don't see a downside to your patch. If that is ever changed (eg. allowing

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

On 2016/4/5 23:54, Radim Krčmář wrote: 2016-04-05 14:18+0800, Yang Zhang: On 2016/4/5 5:00, Rik van Riel wrote: Given that delivering a timer to a guest seems to involve trapping from the guest to the host, anyway, I don't see a downside to your patch. If that is ever changed (eg. allowing

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

2016-04-05 14:18+0800, Yang Zhang: > On 2016/4/5 5:00, Rik van Riel wrote: >>Given that delivering a timer to a guest seems to >>involve trapping from the guest to the host, anyway, >>I don't see a downside to your patch. >> >>If that is ever changed (eg. allowing delivery of >>a timer interrupt

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

2016-04-05 14:18+0800, Yang Zhang: > On 2016/4/5 5:00, Rik van Riel wrote: >>Given that delivering a timer to a guest seems to >>involve trapping from the guest to the host, anyway, >>I don't see a downside to your patch. >> >>If that is ever changed (eg. allowing delivery of >>a timer interrupt

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

On Tue, 5 Apr 2016 14:18:01 +0800 Yang Zhang wrote: > On 2016/4/5 5:00, Rik van Riel wrote: > > On Mon, 2016-04-04 at 16:46 -0400, Luiz Capitulino wrote: > >> When a vCPU runs on a nohz_full core, the hrtimer used by > >> the lapic emulation code can be migrated to

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

On Tue, 5 Apr 2016 14:18:01 +0800 Yang Zhang wrote: > On 2016/4/5 5:00, Rik van Riel wrote: > > On Mon, 2016-04-04 at 16:46 -0400, Luiz Capitulino wrote: > >> When a vCPU runs on a nohz_full core, the hrtimer used by > >> the lapic emulation code can be migrated to another core. > >> When this

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

On 04/04/2016 22:46, Luiz Capitulino wrote: > When a vCPU runs on a nohz_full core, the hrtimer used by > the lapic emulation code can be migrated to another core. > When this happens, it's possible to observe milisecond > latency when delivering timer IRQs to KVM guests. > > The huge latency is

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

On 04/04/2016 22:46, Luiz Capitulino wrote: > When a vCPU runs on a nohz_full core, the hrtimer used by > the lapic emulation code can be migrated to another core. > When this happens, it's possible to observe milisecond > latency when delivering timer IRQs to KVM guests. > > The huge latency is

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

On 2016/4/5 5:00, Rik van Riel wrote: On Mon, 2016-04-04 at 16:46 -0400, Luiz Capitulino wrote: When a vCPU runs on a nohz_full core, the hrtimer used by the lapic emulation code can be migrated to another core. When this happens, it's possible to observe milisecond latency when delivering

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

On 2016/4/5 5:00, Rik van Riel wrote: On Mon, 2016-04-04 at 16:46 -0400, Luiz Capitulino wrote: When a vCPU runs on a nohz_full core, the hrtimer used by the lapic emulation code can be migrated to another core. When this happens, it's possible to observe milisecond latency when delivering

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

On Mon, 2016-04-04 at 16:46 -0400, Luiz Capitulino wrote: > When a vCPU runs on a nohz_full core, the hrtimer used by > the lapic emulation code can be migrated to another core. > When this happens, it's possible to observe milisecond > latency when delivering timer IRQs to KVM guests. > > The

Re: [PATCH] kvm: x86: make lapic hrtimer pinned

On Mon, 2016-04-04 at 16:46 -0400, Luiz Capitulino wrote: > When a vCPU runs on a nohz_full core, the hrtimer used by > the lapic emulation code can be migrated to another core. > When this happens, it's possible to observe milisecond > latency when delivering timer IRQs to KVM guests. > > The

[PATCH] kvm: x86: make lapic hrtimer pinned

When a vCPU runs on a nohz_full core, the hrtimer used by the lapic emulation code can be migrated to another core. When this happens, it's possible to observe milisecond latency when delivering timer IRQs to KVM guests. The huge latency is mainly due to the fact that apic_timer_fn() expects to

[PATCH] kvm: x86: make lapic hrtimer pinned

When a vCPU runs on a nohz_full core, the hrtimer used by the lapic emulation code can be migrated to another core. When this happens, it's possible to observe milisecond latency when delivering timer IRQs to KVM guests. The huge latency is mainly due to the fact that apic_timer_fn() expects to