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

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


  • To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
  • 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
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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


 


Rackspace

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