From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dario Faggioli <dario.faggioli@citrix.com>
Subject: Re: [PATCH 4 of 6 v2] xen: tracing: report where a VCPU
 wakes up
Date: Mon, 17 Dec 2012 15:43:20 +0100
Message-ID: <1355755400.5931.16.camel@Abyss>
References: <patchbomb.1355280770@Solace>
	<7a199dea34425e890b31.1355280774@Solace>
	<50CB84A1.1060205@eu.citrix.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5860694473982927584=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <50CB84A1.1060205@eu.citrix.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: George Dunlap <george.dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Keir
	(Xen.org)" <keir@xen.org>, Ian Campbell <Ian.Campbell@citrix.com>
List-Id: xen-devel@lists.xenproject.org

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

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

On Fri, 2012-12-14 at 19:57 +0000, George Dunlap wrote:=20
> On 12/12/12 02:52, Dario Faggioli wrote:
> > When looking at traces, it turns out to be useful to know where a
> > waking-up VCPU is being queued. Yes, that is always the CPU where
> > it ran last, but that information can well be lost in past trace
> > records!
>=20
> When you say "lost in past trace records", do you primarily mean that=20
> the records themselves have been lost (due to the per-cpu trace buffers=
=20
> filling up), or do you mean that it may be way way back and you don't=20
> want to go back and find it?
>=20
The latter... I'm quite lazy when looking at traces! :-P

> If the latter, I think the best thing to do would be to just augment=20
> xenalyze to keep track of that information and print it when it sees the=
=20
> wake record.
>=20
I agree, I'll kill this patch for now, and investigate further solution
along the line you suggested in the future.

Thanks and Regards,
Dario

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



--=-lAl3P5FNUVonLZdAjFEr
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.12 (GNU/Linux)

iEYEABECAAYFAlDPL4gACgkQk4XaBE3IOsTOqQCff6AuQlgxk7vR7uVhDuozQZ6A
1B0An2frFkafjgAEsqgNSv1qqyGd5o34
=n7sj
-----END PGP SIGNATURE-----

--=-lAl3P5FNUVonLZdAjFEr--


--===============5860694473982927584==
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

--===============5860694473982927584==--