On Wed, 3 Jul 2019 at 22:13, Paolo Bonzini wrote:
>
> On 03/07/19 02:48, Wanpeng Li wrote:
> > Hi Paolo, how about this patchset? Patch 2/2 is easy to take, do you
> > have more concern about patch 1/2?
>
> I don't know. It seems somewhat hard to tune and in cyclictest it only
> happens for preem
On 03/07/19 02:48, Wanpeng Li wrote:
> Hi Paolo, how about this patchset? Patch 2/2 is easy to take, do you
> have more concern about patch 1/2?
I don't know. It seems somewhat hard to tune and in cyclictest it only
happens for preemption_timer=N. Are you using preemption_timer=N
together with t
Hi Paolo, how about this patchset? Patch 2/2 is easy to take, do you
have more concern about patch 1/2?
On Fri, 28 Jun 2019 at 16:29, Wanpeng Li wrote:
>
> ping again,
> On Fri, 21 Jun 2019 at 17:44, Wanpeng Li wrote:
> >
> > ping,
> > On Fri, 14 Jun 2019 at 09:15, Wanpeng Li wrote:
> > >
> > >
ping again,
On Fri, 21 Jun 2019 at 17:44, Wanpeng Li wrote:
>
> ping,
> On Fri, 14 Jun 2019 at 09:15, Wanpeng Li wrote:
> >
> > From: Wanpeng Li
> >
> > Advance lapic timer tries to hidden the hypervisor overhead between the
> > host emulated timer fires and the guest awares the timer is fired.
ping,
On Fri, 14 Jun 2019 at 09:15, Wanpeng Li wrote:
>
> From: Wanpeng Li
>
> Advance lapic timer tries to hidden the hypervisor overhead between the
> host emulated timer fires and the guest awares the timer is fired. However,
> even though after more sustaining optimizations,
> kvm-unit-tests
From: Wanpeng Li
Advance lapic timer tries to hidden the hypervisor overhead between the
host emulated timer fires and the guest awares the timer is fired. However,
even though after more sustaining optimizations,
kvm-unit-tests/tscdeadline_latency
still awares ~1000 cycles latency since we los
6 matches
Mail list logo
