xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Meng Xu <xumengpanda@gmail.com>, Wei Liu <wei.liu2@citrix.com>
Subject: [PATCH 0/3] xen: more scheduler tracing improvement
Date: Sat, 12 Mar 2016 12:33:48 +0100	[thread overview]
Message-ID: <20160312112621.14480.21747.stgit@Solace.station> (raw)

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	other threads:[~2016-03-12 11:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-12 11:33 Dario Faggioli [this message]
2016-03-12 11:33 ` [PATCH 1/3] xenalyze: handle DOM0 operaions events Dario Faggioli
2016-03-12 14:35   ` Wei Liu
2016-03-14 14:06   ` Konrad Rzeszutek Wilk
2016-03-14 14:11     ` Dario Faggioli
2016-03-16 16:37   ` [PATCH 1/3 v2] xenalyze: handle DOM0 operations events Dario Faggioli
2016-03-23 12:35   ` [PATCH 1/3] xenalyze: handle DOM0 operaions events George Dunlap
2016-03-25 13:29     ` Konrad Rzeszutek Wilk
2016-04-01 12:13       ` git branch for checking-in leftover patches [was: Re: [PATCH 1/3] xenalyze: handle DOM0 operaions events] Dario Faggioli
2016-04-01 14:00         ` Ian Jackson
2016-03-12 11:34 ` [PATCH 2/3] xen: sched RTDS: use uint64_t for tracing time values Dario Faggioli
2016-03-12 15:05   ` Meng Xu
2016-03-14  9:07   ` Jan Beulich
2016-03-16 16:38     ` Dario Faggioli
2016-03-12 11:34 ` [PATCH 3/3] xenalyze: handle RTDS scheduler events Dario Faggioli
2016-03-12 15:14   ` Meng Xu
2016-03-23 12:36   ` George Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160312112621.14480.21747.stgit@Solace.station \
    --to=dario.faggioli@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xumengpanda@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).