From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [QEMU patch 2/2] kvm: allow configuration of tsc deadline timer
 advancement
Date: Wed, 10 Dec 2014 18:09:19 +0100
Message-ID: <54887E3F.4030904@redhat.com>
References: <20141210162317.370733848@amt.cnet> <20141210162420.218207164@amt.cnet> <54887C61.80008@redhat.com> <20141210170405.GA19952@amt.cnet>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org,
	Luiz Capitulino <lcapitulino@redhat.com>,
	Rik van Riel <riel@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:33292 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S932268AbaLJR3f (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 10 Dec 2014 12:29:35 -0500
In-Reply-To: <20141210170405.GA19952@amt.cnet>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>



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