[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
  • 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
  • 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=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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

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


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.