Hi,

this is what remained uncommitted of these other series:

 "Scheduling related tracing improvements"
 v1: http://lists.xenproject.org/archives/html/xen-devel/2016-02/msg01016.html
 v2: http://lists.xenproject.org/archives/html/xen-devel/2016-02/msg02233.html

What is patch 1 here, was there already in v2 of the previous submission, but
it did not got reviewed.

What is patch 2 here, was not there before. George suggested doing it, to do
better what is done in what is patch 3 here (which was there before, in a
slightly different form).

Thanks and Regards,
Dario
---
Dario Faggioli (3):
      xenalyze: handle DOM0 operaions events
      xen: sched RTDS: use uint64_t for tracing time values
      xenalyze: handle RTDS scheduler events

 tools/xentrace/xenalyze.c |   78 +++++++++++++++++++++++++++++++++++++++++++++
 xen/common/sched_rt.c     |   30 ++++++-----------
 2 files changed, 89 insertions(+), 19 deletions(-)
--
<<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)

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

Reply via email to