From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [QEMU patch 2/2] kvm: allow configuration of tsc deadline timer advancement Date: Wed, 10 Dec 2014 18:29:43 +0100 Message-ID: <54888307.6020407@redhat.com> References: <20141210162317.370733848@amt.cnet> <20141210162420.218207164@amt.cnet> <54887C61.80008@redhat.com> <20141210170405.GA19952@amt.cnet> <54887E3F.4030904@redhat.com> <20141210172712.GA20568@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 , Rik van Riel To: Marcelo Tosatti Return-path: Received: from mx1.redhat.com ([209.132.183.28]:40609 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932564AbaLJR3v (ORCPT ); Wed, 10 Dec 2014 12:29:51 -0500 In-Reply-To: <20141210172712.GA20568@amt.cnet> Sender: kvm-owner@vger.kernel.org List-ID: On 10/12/2014 18:27, Marcelo Tosatti wrote: > 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. It's not going to be anyway. Cache line bounces, frequency scaling, presence of higher-priority RT tasks, etc. can cause different response for one CPU over the others. Paolo