From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dario Faggioli <dario.faggioli@citrix.com>
Subject: Re: [PATCH v2 6/8] xenalyze: handle more events in
 sched_process
Date: Tue, 12 May 2015 16:53:44 +0200
Message-ID: <1431442424.2978.53.camel@citrix.com>
References: <1430994944-20471-1-git-send-email-olaf@aepfle.de>
	<1430994944-20471-7-git-send-email-olaf@aepfle.de>
	<CAFLBxZbFbvuJA03HY0ChHk+iap-PTDti99VkEx=mEg9VPs3XtA@mail.gmail.com>
	<554BA0B4.8020008@citrix.com>
	<CAFLBxZbXaLDfjErb+9uyFNYgwepMNv9HrysR5bEhDNLK0MdjUA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0707097585177638009=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAFLBxZbXaLDfjErb+9uyFNYgwepMNv9HrysR5bEhDNLK0MdjUA@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: George Dunlap <dunlapg@umich.edu>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

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

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

On Thu, 2015-05-07 at 18:42 +0100, George Dunlap wrote:
> On Thu, May 7, 2015 at 6:28 PM, Andrew Cooper <andrew.cooper3@citrix.com>=
 wrote:

> > Is it a candidate for dropping from the hypervisor then?  No use keepin=
g
> > useless tracepoints.
>=20
> Well it would have to be replaced with something more informative.
>
Indeed. In fact, if one wants to figure out what happens when changing
some scheduling parameters, it is actually helpful to see the record
about the change in the trace. Provided such record is informative
enough, of course.

> "Someone changed something" is pretty useless, but it's still more
> information than nothing at all. =20
>
Agreed.

> (Presumably the replacement would be
> a per-scheduler tracepoint.)
>=20
Probably, so we can actually print the details of the adjustment being
done.

I'm adding this to my todo list. :-)

Regards,
Dario

--=-YUwy9pNrLTsuQPT9DRnx
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 v2

iEYEABECAAYFAlVSE/gACgkQk4XaBE3IOsTg4gCgrJc6GlfBj9Yq7cWyK7he87wq
KxIAn2zfaMlq37SAyLvvEaNfBhfiNwJ5
=OzMG
-----END PGP SIGNATURE-----

--=-YUwy9pNrLTsuQPT9DRnx--


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

--===============0707097585177638009==--