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

Re: [Xen-devel] [PATCH][cpufreq] Xen support for the ondemand governor [1/2] (hypervisor code)


  • To: "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Wed, 24 Oct 2007 14:50:10 +0100
  • Delivery-date: Wed, 24 Oct 2007 06:50:59 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcgWDB15XAW5MIH/EdyyOQAWy6hiGQAOAaWQAAApvpg=
  • Thread-topic: [Xen-devel] [PATCH][cpufreq] Xen support for the ondemand governor [1/2] (hypervisor code)

On 24/10/07 14:46, "Langsdorf, Mark" <mark.langsdorf@xxxxxxx> wrote:

>> You can already work out total 'ticks' (actually nanoseconds
>> since boot) via data stored in shared_info. There's code in
>> arch/i386/kernel/time-xen.c to
>> do so. Use that rather than modify this hypercall.
> 
> Excellent.  I wasn't aware of that, and wasn't wild
> about having to modify the hypercall.
> 
> Since you were planning on modifying it to use the
> cpumask, are you also going to add the shared_info
> code?  If not, can you send me a pointer to the
> changeset so I know what to work from for my
> modifications?

Actually I checked in Kevin Tian's patch (slightly modified, of course ;-).
So go take a look in xen-unstable staging. You'll see that we do return the
current system time, since it is easy to do and is probably convenient for
the caller. But we return it as a single value, not a per-cpu value!

 -- Keir



_______________________________________________
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®.