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-users

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

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-users] About profiling xen
From: Marco Tizzoni <marco.tizzoni@xxxxxxxxx>
Date: Thu, 1 Oct 2009 09:35:55 +0200
Cc: "Fajar A." <fajar@xxxxxxxxx>, Fasiha Ashraf <feehapk@xxxxxxxxxxx>, xen <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 01 Oct 2009 00:36:59 -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=2ws/VtKHMIeGXQr6gMPZ4wCIIWn5Zzn++DmdYFftsPE=; b=KczUnyrFB8eK+xFxUVcjyGtlUfVoOUmg+YPsEJgkipIqHEC5+7B+QpPTx6nba7z+4H 12jOqZ+I2emvf57KovITMZijDMKrS4CNGmEXdNp91ujEgaRn80XNj4GiIXmVnH6sfHLn 7//ZuvJs7Y2lDp97EXp0kbop6fFoJIJnS7tO4=
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=QKbwozU51d5M/7Cft62e4bGd0c8XQ38PsaV8kmWnsCAO9al0WwqsbZOHcrTETU+/bB dWycqL6SsgV2ij/Tvn0wFTZXuFMKmOA1JEGvQi/7smby7wws7OaY15F3q5DBxvONM1ez 13jffdY9Qgq2Y9tXZx3sRyPV1jiuGMJl7/eSo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AC3E889.6060407@xxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <196324.1267.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <f9611b0f0909292333r7da0c616rbe53ca73a6ea512d@xxxxxxxxxxxxxx> <20090930063747.GG1434@xxxxxxxxxxx> <f9611b0f0909292340o6a53326aobcd87334d7cfaa6b@xxxxxxxxxxxxxx> <f9611b0f0909300045o55e22378xea270e9873471f1d@xxxxxxxxxxxxxx> <f9611b0f0909300206v53577d1cw300ff6092b8ffede@xxxxxxxxxxxxxx> <4AC3E889.6060407@xxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Oct 1, 2009 at 1:23 AM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> Your clocksource is "xen", which is the best possible for a PV xen guest.
>
> However, a clocksource is for measuring elapsed time, not triggering
> timers.

Why? How would you solve the problem of raising events at a fixed rate?

> Unfortunately there doesn't seem to be a /sys file to show the
> current clockevent source in use, but if you have "xen" clocksource it's
> almost certainly the xen clockevent.
>
> However, this is only relevent if you have CONFIG_NO_HZ and
> CONFIG_HIGHRES_TIMERS enabled.

I've tried both set/unset but nothing change.

m-

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