From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dario Faggioli <dario.faggioli@citrix.com>
Subject: Re: trace IDLE VCPU using xenalyze --scatterplot-pcpu?
Date: Wed, 27 Mar 2013 03:15:32 +0100
Message-ID: <1364350532.3343.49.camel@Solace>
References: <CAPqOm-oG4mvZh-JJdQo=btX5V1rx4zdMw9A1iEXB_E5Yx1_YkA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3275036185353540693=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAPqOm-oG4mvZh-JJdQo=btX5V1rx4zdMw9A1iEXB_E5Yx1_YkA@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Sisu Xi <xisisu@gmail.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

--===============3275036185353540693==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="=-EJDAUS6Y8w1GDQROnrV3"

--=-EJDAUS6Y8w1GDQROnrV3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On mar, 2013-03-26 at 14:12 -0500, Sisu Xi wrote:
> Hi, All:
>=20
Hi Sisu!

> I was following the article here to plot the scheduler execution trace.
> http://blog.xen.org/index.php/2012/09/27/tracing-with-xentrace-and-xenaly=
ze/
>
> I was able to get the trace and plot it,=20
>
EhEh, glad it was helpful! :-P

> however, the trace for IDLE
> VCPU is skipped. This makes it harder to understand the scheduler
> behavior (For example, cap in credit).
>=20
Mmmm... I think I see what you mean.

> Does anyone know how to get the data for the IDLE VCPU when using
> xenalyze --scatterplot-pcpu?
>=20
Well, I double-checked and it is true that, at least here,
--scatterplot-pcpu does not show the vCPUs of the idle domain. One could
probably try to understand when they're scheduled by looking at when
_no_other_ vCPU of any other domain runs on a particular pCPU (and
considering that the idle domain has one vCPU pinned to each pCPU), but
that would be quite unpractical I guess...

Perhaps you can achieve something similar to what you need by looking
for/plotting the runstate changes for the vCPUs of the idle domain
(i.e., 32767vXX from `xenalyze --scatterplot-runstate') ?

George, any other ideas?

Regards,
Dario

--=20
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


--=-EJDAUS6Y8w1GDQROnrV3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)

iEYEABECAAYFAlFSVkQACgkQk4XaBE3IOsTDrACfUOs7+LPrnTBRvqi7i3QLs818
ErUAn38xz0/rowAyzoQEyxo/Rb3uaMJY
=2WEx
-----END PGP SIGNATURE-----

--=-EJDAUS6Y8w1GDQROnrV3--


--===============3275036185353540693==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--===============3275036185353540693==--