From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: About preemption timer
Date: Wed, 18 Dec 2013 07:58:17 +0100
Message-ID: <52B14789.1000201@siemens.com>
References: <CABpY8M+p5MpgOg4Ggd_Of-YuybwFEeBXKuYrioBzV72pK1H31w@mail.gmail.com>	<52B033BC.90602@siemens.com>	<CABpY8M+1VuvAwKybqm=7Pwv0c83vRsF-0ZL9HcXNwYcToeRkBg@mail.gmail.com>	<52B046DC.90107@siemens.com>	<CABpY8MKcFNeKzsSnkynuEuga3YVLB=SeguKKCnGnbaZEcg23AQ@mail.gmail.com>	<52B06AFF.3070201@siemens.com> <CAF2sySOqdW0SimGpn-N2UH0H8ksce5D39VVcbdX9=FjOhwABQw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Arthur Chunqi Li <yzt356@gmail.com>, kvm <kvm@vger.kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>
To: R <19890121wr@gmail.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from goliath.siemens.de ([192.35.17.28]:21560 "EHLO
	goliath.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753173Ab3LRG6Y (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 18 Dec 2013 01:58:24 -0500
In-Reply-To: <CAF2sySOqdW0SimGpn-N2UH0H8ksce5D39VVcbdX9=FjOhwABQw@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 2013-12-18 04:27, R wrote:
> Hi,
> 
> You must adjust the preemption timer according to the eclipsed time
> when the guest runs.
> 
> And register a hrtimer triggered when a guest exit.
> The timer should be alarmed when the remaining time runs out,

In fact, as we need to register an hrtimer anyway when leaving the
guest, we can simply register it always and stop using the physical
preemption timer. This will also solve the breakage on older Intel CPU,
actually it will add preemption timer support unconditionally.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux