From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47919)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mtosatti@redhat.com>) id 1Xyl31-0003yt-GJ
	for qemu-devel@nongnu.org; Wed, 10 Dec 2014 12:27:41 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mtosatti@redhat.com>) id 1Xyl2v-0004E8-Bz
	for qemu-devel@nongnu.org; Wed, 10 Dec 2014 12:27:35 -0500
Received: from mx1.redhat.com ([209.132.183.28]:60329)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mtosatti@redhat.com>) id 1Xyl2v-0004E2-4j
	for qemu-devel@nongnu.org; Wed, 10 Dec 2014 12:27:29 -0500
Date: Wed, 10 Dec 2014 15:27:12 -0200
From: Marcelo Tosatti <mtosatti@redhat.com>
Message-ID: <20141210172712.GA20568@amt.cnet>
References: <20141210162317.370733848@amt.cnet>
	<20141210162420.218207164@amt.cnet> <54887C61.80008@redhat.com>
	<20141210170405.GA19952@amt.cnet> <54887E3F.4030904@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54887E3F.4030904@redhat.com>
Subject: Re: [Qemu-devel] [QEMU patch 2/2] kvm: allow configuration of tsc
 deadline timer advancement
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: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, Luiz Capitulino <lcapitulino@redhat.com>

On Wed, Dec 10, 2014 at 06:09:19PM +0100, Paolo Bonzini wrote:
> 
> 
> On 10/12/2014 18:04, Marcelo Tosatti wrote:
> >> Please add an object property to the x86 CPU object.  It can then be
> >> configured with "-global" on the command line.
> > 
> > Don't want to allow individual values for different CPUs. 
> > It is a per-VM property.
> 
> Why?  It can cause busy waiting, it would make sense to make it stricter
> for realtime CPUs and leave 0 for non-realtime CPUs.
> 
> Paolo

HW timer behaviour should be consistent across CPUs, IMO.