xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
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>
Subject: Re: [PATCH 4 of 5 v3] xen: tracing: introduce per-scheduler trace event IDs
Date: Mon, 11 Mar 2013 20:10:17 +0100	[thread overview]
Message-ID: <1363029017.3685.10.camel@Abyss> (raw)
In-Reply-To: <513DB895.9050902@eu.citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1233 bytes --]

On lun, 2013-03-11 at 10:57 +0000, George Dunlap wrote:
> On 09/03/13 10:40, Dario Faggioli wrote:
> > TBH, I haven't done any xenalyze modification, corresponding to this.
> > However, I'm not really sure it's necessary.
> 
> It does change the trace records slightly, by adding in the extra 
> scheduler ID at the top.  It just requires propagating the changes in 
> trace.h from the xen tree to xenalyze -- not hard to do; 
>
Oh, I see... Then I guess I just failed to spot anything like that was
needed, perhaps because everything was JustWorking^TM, at least to my
inexperienced eyes. :-)

> I jut wanted to 
> know if you happened to have the patch lying around so I wouldn't have 
> to go through and do it.  No worries. :-)
> 
Ok, so, I think we should go for a "whoever gets to it first tell it to
the other (e.g., by Cc-ing him to the patch ;-P), to avoid duplicating
the (although small) effort" policy... Is that fine with you?

Dario

-- 
<<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)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

  reply	other threads:[~2013-03-11 19:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 22:28 [PATCH 0 of 5 v3] xen: sched_credit: fix picking and tickling and add some tracing Dario Faggioli
2012-12-17 22:28 ` [PATCH 1 of 5 v3] xen: sched_credit: define and use curr_on_cpu(cpu) Dario Faggioli
2012-12-18 12:10   ` George Dunlap
2012-12-17 22:28 ` [PATCH 2 of 5 v3] xen: sched_credit: improve picking up the idle CPU for a VCPU Dario Faggioli
2012-12-18 12:12   ` George Dunlap
2012-12-17 22:29 ` [PATCH 3 of 5 v3] xen: sched_credit: improve tickling of idle CPUs Dario Faggioli
2012-12-17 22:29 ` [PATCH 4 of 5 v3] xen: tracing: introduce per-scheduler trace event IDs Dario Faggioli
2013-03-08 16:08   ` George Dunlap
2013-03-09 10:40     ` Dario Faggioli
2013-03-11 10:57       ` George Dunlap
2013-03-11 19:10         ` Dario Faggioli [this message]
2012-12-17 22:29 ` [PATCH 5 of 5 v3] xen: sched_credit: add some tracing Dario Faggioli
2012-12-18 12:15   ` George Dunlap
2012-12-18 12:16 ` [PATCH 0 of 5 v3] xen: sched_credit: fix picking and tickling and " George Dunlap
2012-12-18 14:16   ` Dario Faggioli

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=1363029017.3685.10.camel@Abyss \
    --to=dario.faggioli@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xensource.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).