From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
xen-devel@lists.xenproject.org,
Dario Faggioli <dario.faggioli@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH 1/3] xenalyze: handle DOM0 operaions events
Date: Fri, 25 Mar 2016 09:29:34 -0400 [thread overview]
Message-ID: <20160325132934.GB29603@char.us.oracle.com> (raw)
In-Reply-To: <56F28D98.6070904@citrix.com>
On Wed, Mar 23, 2016 at 12:35:36PM +0000, George Dunlap wrote:
> On 12/03/16 11:33, Dario Faggioli wrote:
> > (i.e., domain creation and destruction) so the
> > trace will show properly decoded info, rather
> > than just a bunch of hex codes.
> > ---
>
> For some reason git won't apply your 'v2', complaining: 'corrupt patch
> at line 14'.
/me nods. Same here. I tried to check it in but couldn't.
Dariof could you make a git branch to pull in the Acked patches please?
>
> But re the content (i.e., this patch with the SoB and the title fixed)
>
> Acked-by: George Dunlap <george.dunlap@citrix.com>
>
> Sorry it took so long to get to this.
>
>
> > Cc: George Dunlap <george.dunlap@eu.citrix.com>
> > Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> > Cc: Wei Liu <wei.liu2@citrix.com>
> > Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> > ---
> > Changes from v1:
> > * new patch in the series.
> > ---
> > tools/xentrace/xenalyze.c | 26 ++++++++++++++++++++++++++
> > 1 file changed, 26 insertions(+)
> >
> > diff --git a/tools/xentrace/xenalyze.c b/tools/xentrace/xenalyze.c
> > index d4a5b0c..353bed7 100644
> > --- a/tools/xentrace/xenalyze.c
> > +++ b/tools/xentrace/xenalyze.c
> > @@ -8388,6 +8388,30 @@ void hw_process(struct pcpu_info *p)
> > }
> >
> > }
> > +
> > +#define TRC_DOM0_SUB_DOMOPS 1
> > +void dom0_process(struct pcpu_info *p)
> > +{
> > + struct record_info *ri = &p->ri;
> > +
> > + switch(ri->evt.sub)
> > + {
> > + case TRC_DOM0_SUB_DOMOPS:
> > + if(opt.dump_all) {
> > + struct {
> > + unsigned int domid;
> > + } *r = (typeof(r))ri->d;
> > +
> > + printf(" %s %s domain d%u\n", ri->dump_header,
> > + ri->event == TRC_DOM0_DOM_ADD ? "creating" : "destroying",
> > + r->domid);
> > + }
> > + break;
> > + default:
> > + process_generic(&p->ri);
> > + }
> > +}
> > +
> > /* ---- Base ----- */
> > void dump_generic(FILE * f, struct record_info *ri)
> > {
> > @@ -9224,6 +9248,8 @@ void process_record(struct pcpu_info *p) {
> > hw_process(p);
> > break;
> > case TRC_DOM0OP_MAIN:
> > + dom0_process(p);
> > + break;
> > default:
> > process_generic(ri);
> > }
> >
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-25 13:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 11:33 [PATCH 0/3] xen: more scheduler tracing improvement Dario Faggioli
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 [this message]
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=20160325132934.GB29603@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=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 \
/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).