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

Re: [Xen-devel] Problems with enabling hypervisor C and P-state control

To: "Yu, Ke" <ke.yu@xxxxxxxxx>
Subject: Re: [Xen-devel] Problems with enabling hypervisor C and P-state control
From: "Niraj Tolia" <ntolia@xxxxxxxxx>
Date: Mon, 27 Oct 2008 11:01:04 -0700
Cc: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>, Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 27 Oct 2008 11:01:28 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=g7H5DwmT19x561yKmobQQ4j2vT2eHzVFTFNfiYsl/I0=; b=PgzRDFu5WbbH/FBiZAXHe3UsrfQCiPszcK6agHi/1pivVjrcH3c2B87SHhlstTOijE 3QCR9jdN7DB1rANGiw8Rw5XmdgIsc6ygS/eW7xyzSyYdU4O0wEkCDWYd1Sm6B7SrBfnA kXPWvf2AN2hjWYIAp7lRc+FF3xd2orG4T3Mb8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=cTVA3W4jYiEQhPCmZsy9UDiY7BhzWa8+ReDvqlU3V4o0d87xX7QFIL8kslwCtjCPJA d9pFAFmkNpIVdAU9IEYw3YaYsE2XvouTPB6E3GnwBQ2NDEOZ9QjRzxcx9RVdx8Ju/K63 pujc7lW4tQ7q56p/wQ9RCu7Q78QNrRxZ+uVoM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49582C73AC36CC4C8C6C42390304E81C0927508EC9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <7e45e2ac0810220057w26b1ab45l8410c54346211d3f@xxxxxxxxxxxxxx> <49582C73AC36CC4C8C6C42390304E81C092722CF78@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <7e45e2ac0810231649o7fd82c81ha09912cfa6a92b76@xxxxxxxxxxxxxx> <49582C73AC36CC4C8C6C42390304E81C092722D967@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <7e45e2ac0810232145ob5f84bcs5c2aeb3e0b5de695@xxxxxxxxxxxxxx> <49582C73AC36CC4C8C6C42390304E81C0927508EC9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Oct 23, 2008 at 10:59 PM, Yu, Ke <ke.yu@xxxxxxxxx> wrote:
> After discussing with Jinsong, we got the root cause. You are right, this is 
> xen pm statistics logic issue. when the coordination type is SW_ANY, we only 
> record the first CPU cpufreq change, the other 3 cores within the same 
> dependency domain is ignored, so you only see one core changes every 
> dependency domain.
>
> The attached patch fix  this issue. could you please have a try? If it works 
> in your platform, we will send out for applying in upstream.

I just applied the patch and while xenpm might be doing the right
thing, I am not completely sure. For example, if I launch a single
VCPU VM, pin it to a core, and launch a CPU intensive task on it, ALL
four cores on the socket are reported to switch into P0. However, from
what I understand about this processor (Xeon E7330), only two of them
should. Like vanilla Linux, the other two should be able to operate at
independent voltage/frequency settings. Once again, I am not sure if
this is xenpm's fault or if the underlying frequency control code
isn't able to determine what  CPUs need to switch frequency at the
same time.

Cheers,
Niraj

-- 
Niraj Tolia, Researcher, HP Labs
http://www.hpl.hp.com/personal/Niraj_Tolia/

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

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