WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [Xen-users] About profiling xen

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-users] About profiling xen
From: Marco Tizzoni <marco.tizzoni@xxxxxxxxx>
Date: Wed, 30 Sep 2009 16:48:01 +0200
Cc: xen <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 30 Sep 2009 07:48:48 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type; bh=Id7+m9TAGKWQv+6+oKJyAUlRv4tozOFruzEB/cGrcCc=; b=JrqYAWkGaXWJ4uYpvwYkpzU9g/rGlKJWIQ2V/nC4EdV0U+8PgVcsEQMkydVWHCZA9t dJMgu/OcYWGROPdlflMo2dEiJAEUlonR7ty/ff824wHLbWUBb1Xt7cuj4InkIK5a/zMQ xYohGg1J16ucH5iUUV9xCrANeseLvRKEBeW/Y=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=T+9+T9yxlkeeoxhQHQVJFqiCx4hrgV8jvZVwUHvfz+rV8DI+05b8JIEXSx8DAZt2Rs 7xAIUwAuemMk5UWis2yL4jqtQHEgMryCpzCgUzc+gKdfQ5Er9JHPNqo8QqcAwiqUWUtc B4aDhWDsGNQNp821+vIYjIX1gh/6JO2Gt0k3I=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <66dbb9d4-c820-4297-b14b-34922b2d14f1@default>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <f9611b0f0909300206v53577d1cw300ff6092b8ffede@xxxxxxxxxxxxxx> <66dbb9d4-c820-4297-b14b-34922b2d14f1@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Sep 30, 2009 at 4:21 PM, Dan Magenheimer
<dan.magenheimer@xxxxxxxxxx> wrote:

> Because of save/restore and migrate, no hardware timer is
> suitable for a pv domain.  The code that is handling the
> clock is the paravirtualized clock code (aka pvclock).
> Nobody ever changed the sysfs reporting mechanism in
> pv versions of released Red Hat kernels, so clocksource
> gets reported as "jiffies", and even though "pit"
> appears to be available, it is not (since it wouldn't
> work).  I suspect this is also the case for other
> distros' pv kernels.

How can I get a different, and I hope better, clocksource? In time.c I
found acpi and hpet are available.

m-

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel