From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46269)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mtosatti@redhat.com>) id 1XPyEH-0007ze-3C
	for qemu-devel@nongnu.org; Fri, 05 Sep 2014 14:27:31 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mtosatti@redhat.com>) id 1XPyEA-0005vp-W0
	for qemu-devel@nongnu.org; Fri, 05 Sep 2014 14:27:25 -0400
Received: from mx1.redhat.com ([209.132.183.28]:48207)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mtosatti@redhat.com>) id 1XPyEA-0005vf-PJ
	for qemu-devel@nongnu.org; Fri, 05 Sep 2014 14:27:18 -0400
Date: Fri, 5 Sep 2014 15:26:56 -0300
From: Marcelo Tosatti <mtosatti@redhat.com>
Message-ID: <20140905182656.GA16828@amt.cnet>
References: <20140905135244.104423770@amt.cnet>
	<CABYiri-_bTH2ZTxj1V+9Xb16OkWcmjggGa0KmacKbh+93gtvcg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABYiri-_bTH2ZTxj1V+9Xb16OkWcmjggGa0KmacKbh+93gtvcg@mail.gmail.com>
Subject: Re: [Qemu-devel] [patch 0/3] kvmclock: Ensure time in migration
 never goes backward (v3)
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Andrey Korolyov <andrey@xdel.ru>
Cc: Paolo Bonzini <pbonzini@redhat.com>, Marcin =?iso-8859-1?Q?Gibu=C5?= a <m.gibula@beyond.pl>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

On Fri, Sep 05, 2014 at 10:16:17PM +0400, Andrey Korolyov wrote:
> On Fri, Sep 5, 2014 at 5:52 PM, Marcelo Tosatti <mtosatti@redhat.com> wrote:
> > Regression fix tested with fio and ping-pong migration.
> >
> >
> 
> Thanks, actually this series also introduces regression with average
> live migration time - 42s avg vs 7s avg for the reference VM on
> ping-pong test. Can you please confirm this?

Can't confirm - migration time is similar for me.

What workload are you using?