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

[Xen-devel] CONFIG_CPU_FREQ change

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] CONFIG_CPU_FREQ change
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Mon, 20 Feb 2006 16:43:46 +0100
Delivery-date: Mon, 20 Feb 2006 15:56:08 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
To my surprise, c/s 8888 enables CPU_FREQ for x86-64 rather than disabling it 
for i386. Did anyone at your end actually
test that if enabled this at least builds properly now? Not to mention that of 
course this also should work... If I
remember right, the main reason for posting a patch to disable it on 32-bits 
(similar to how it was on 64-bits before)
was that there were some missing symbols, and I don't think I saw any 
changesets addressing this. Also, from previous
discussion I seem to recall that it was generally agreed that there is little 
point in allowing a single domain (even
dom0) to decide whether/what power management actions should be taken without 
knowing about the requirements of the rest
of the system...

Thanks, Jan

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

<Prev in Thread] Current Thread [Next in Thread>