From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [PATCH] replace rdtsc emulation-vs-native xen boot option with per-domain (hypervisor part) Date: Mon, 28 Sep 2009 16:10:05 -0700 Message-ID: <4AC1424D.8070008@goop.org> References: <7e5859b0-457b-4788-b8c6-6cc3d143bae2@default> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <7e5859b0-457b-4788-b8c6-6cc3d143bae2@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer Cc: "Xen-Devel (E-mail)" , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 09/28/09 15:43, Dan Magenheimer wrote: > PV ones too. An app doesn't have any idea (and doesn't > and shouldn't care) if it is running on a PV or HVM domain. > Well, it shouldn't be enabled by default. That slows down all rdtsc operations for the benefit of very niche applications. The Xen clocksource assumes that rdtsc is fast, unemulated and in need of correction. If someone really needs an artificial tsc, then they can enable the option for themselves. J