From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] 1/2: cpufreq/PowerNow! in Xen: Time and platform changes Date: Thu, 30 Aug 2007 11:12:28 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Tian, Kevin" , Mark Langsdorf , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 30/8/07 10:45, "Tian, Kevin" wrote: > Sure, some experiment can be done later to compare dom0 userspace > and in-xen governor. Agree that in-kernel dom0 approach is not > charming because anyway it needs help from either user-level or xen > for global view. > > Actually finally we may take both. Xen takes simple heuristic policy > with user-level governor to adjust with more complex and flexible > policies based on domain behaviors. :-) There is the problem, though, that most modern CPUs will need cpufreq info to be parsed out of the ACPI DSDT. And Xen can't do that itself unaided. Pushing down some form of cpufreq info table to Xen *is* an option though, but we'd need more custom dom0 kernel code to do that. Or we'd need to do it from a userspace program. -- Keir