From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>, xen-devel@lists.xenproject.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH v2 03/16] xen: sched: improve domain creation tracing
Date: Wed, 24 Feb 2016 12:21:41 +0100 [thread overview]
Message-ID: <1456312901.17312.21.camel@citrix.com> (raw)
In-Reply-To: <56C5A551.4050303@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1603 bytes --]
On Thu, 2016-02-18 at 11:04 +0000, George Dunlap wrote:
> On 16/02/16 18:11, Dario Faggioli wrote:
> > by doing the following two things:
> >
> > - move TRC_SCHED_DOM_{ADD,REM}, into the functions
> > that do the actual scheduling-related domain
> > initialization;
> >
> > - add two 'generic' DOM_{ADD,REM} events. They're
> > made part of the TRC_DOM0 tracing class, as Dom0
> > is, usually, from where domains are created and
> > destroyed.
> >
> > Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com>
>
> Reviewed-by: George Dunlap <george.dunlap@citrix.com>
>
> Since this changes domain.c, I guess this would need an ack from "The
> Rest" -- probably either from Jan or Ian, since they're somewhat
> familiar with this code...?
>
Ping (Ian, Jan)?
Also, George, I haven't seen any comment from you on patch 16 ("PATCH
v2 16/16] xenalyze: handle DOM0 operaions events",
<20160216181331.27876.31120.stgit@Solace.station> )... Is that because
you want to see others' opinion on this patch first?
As far as I can tell, these two patches (i.e., 03/16 and 16/16) is all
that is preventing this series to be checked in (with the exception of
patch 15, which I'll resend as part of another, follow-up, series, as
agreed with George).
Thanks and Regards,
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: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-24 11:21 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 18:11 [PATCH v2 00/16] Scheduling related tracing improvements Dario Faggioli
2016-02-16 18:11 ` [PATCH v2 01/16] xen: sched: __runq_tickle takes a useless cpu parameter Dario Faggioli
2016-02-18 10:33 ` George Dunlap
2016-02-16 18:11 ` [PATCH v2 02/16] xen: sched: move up the trace record for vcpu_wake and vcpu_sleep Dario Faggioli
2016-02-18 10:34 ` George Dunlap
2016-02-16 18:11 ` [PATCH v2 03/16] xen: sched: improve domain creation tracing Dario Faggioli
2016-02-18 11:04 ` George Dunlap
2016-02-24 11:21 ` Dario Faggioli [this message]
2016-02-24 11:52 ` Jan Beulich
2016-02-24 13:20 ` Dario Faggioli
2016-02-16 18:11 ` [PATCH v2 04/16] xen: credit2: pack trace data better for xentrace_format Dario Faggioli
2016-02-18 11:10 ` George Dunlap
2016-02-18 13:42 ` Dario Faggioli
2016-02-16 18:11 ` [PATCH v2 05/16] xen: RTDS: " Dario Faggioli
2016-02-18 11:12 ` George Dunlap
2016-02-18 14:43 ` Meng Xu
2016-02-16 18:11 ` [PATCH v2 06/16] xen: sched: tracing: enable TSC tracing for all events Dario Faggioli
2016-02-16 18:21 ` Meng Xu
2016-02-17 9:52 ` Dario Faggioli
2016-02-17 15:26 ` Meng Xu
2016-02-18 11:43 ` George Dunlap
2016-02-18 16:52 ` Dario Faggioli
2016-02-22 11:02 ` George Dunlap
2016-02-16 18:12 ` [PATCH v2 07/16] xentrace: formats: update format of scheduling events Dario Faggioli
2016-02-18 12:28 ` George Dunlap
2016-02-16 18:12 ` [PATCH v2 08/16] xentrace: formats: add events from Credit scheduler Dario Faggioli
2016-02-16 18:12 ` [PATCH v2 09/16] xentrace: formats: add events from Credit2 scheduler Dario Faggioli
2016-02-16 18:12 ` [PATCH v2 10/16] xentrace: formats: add events from RTDS scheduler Dario Faggioli
2016-02-16 18:12 ` [PATCH v2 11/16] xentrace: formats: add domain create and destroy events Dario Faggioli
2016-02-16 18:12 ` [PATCH v2 12/16] xenalyze: handle scheduling events Dario Faggioli
2016-02-18 15:18 ` George Dunlap
2016-02-16 18:12 ` [PATCH v2 13/16] xenalyze: handle Credit1 scheduler events Dario Faggioli
2016-02-18 15:28 ` George Dunlap
2016-02-18 15:31 ` George Dunlap
2016-02-18 16:58 ` Dario Faggioli
2016-02-16 18:13 ` [PATCH v2 14/16] xenalyze: handle Credit2 " Dario Faggioli
2016-02-18 15:17 ` George Dunlap
2016-02-16 18:13 ` [PATCH v2 15/16] xenalyze: handle RTDS " Dario Faggioli
2016-02-18 15:28 ` George Dunlap
2016-02-18 17:02 ` Dario Faggioli
2016-02-18 17:06 ` George Dunlap
2016-02-18 17:10 ` Dario Faggioli
2016-02-16 18:13 ` [PATCH v2 16/16] xenalyze: handle DOM0 operaions events Dario Faggioli
2016-03-04 18:25 ` [PATCH v2 00/16] Scheduling related tracing improvements Dario Faggioli
2016-03-04 19:52 ` Konrad Rzeszutek Wilk
2016-03-07 10:50 ` Jan Beulich
2016-03-07 10:54 ` Wei Liu
2016-03-07 11:21 ` Jan Beulich
2016-03-07 11:27 ` Wei Liu
2016-03-07 14:21 ` Dario Faggioli
2016-03-07 15:36 ` Konrad Rzeszutek Wilk
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=1456312901.17312.21.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.com \
--cc=george.dunlap@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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).