Re: [PATCH v2 00/16] Scheduling related tracing improvements

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Fri, Mar 04, 2016 at 07:25:30PM +0100, Dario Faggioli wrote:
> Hello committers, George,
> 
> This is basically a ping for this series, as I think most of it can
> actually go in, unless I've missed something.
> 
> So, let me try to recap:
> 
> On Tue, 2016-02-16 at 19:11 +0100, Dario Faggioli wrote:
> > 
> > Dario Faggioli (16):
> >       xen: sched: __runq_tickle takes a useless cpu parameter
> >       xen: sched: move up the trace record for vcpu_wake and
> > vcpu_sleep
> >       xen: sched: improve domain creation tracing
> >       xen: credit2: pack trace data better for xentrace_format
> >       xen: RTDS: pack trace data better for xentrace_format
> >       xen: sched: tracing: enable TSC tracing for all events
> >
> Until here, it's in already.
> 
> >       xentrace: formats: update format of scheduling events
> >       xentrace: formats: add events from Credit scheduler
> >       xentrace: formats: add events from Credit2 scheduler
> >       xentrace: formats: add events from RTDS scheduler
> >       xentrace: formats: add domain create and destroy events.
> >
> About these, they've got Konrad's Reviewed-by, and George said:
> 
> "I haven't reviewed the formats file changes, but all of them look
> reasonable; so for patches 7-11:
> Acked-by: George Dunlap <george.dunlap@citrix.com>"
> 
> >       xenalyze: handle scheduling events
> >
> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Acked-by: George Dunlap <george.dunlap@citrix.com>
> 
> >       xenalyze: handle Credit1 scheduler events
> >
> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Acked-by: George Dunlap <george.dunlap@citrix.com>
> 
> >       xenalyze: handle Credit2 scheduler events
> >
> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Acked-by: George Dunlap <george.dunlap@citrix.com>
> 
> >       xenalyze: handle RTDS scheduler events
> >
> This should be skipped. In fact, we agreed with George that the plan
> would be:
> 
> "I think most of these patches can be checked in now.  What about
> checking in the other patches, then sending a follow-up series with the
> struct changed in the scheduler, and then this patch with the resulting
> changes?"
> 
> So, just ignore this patch.
> 
> >       xenalyze: handle DOM0 operaions events
> > 
> This one is actually missing Georges's Ack.
> 
> I'd be fine with this being skipped as well, and I will resubmit as
> separate patch, or as part of the followup series mentioned above.
> 
> Or George can Ack it, and it just can go in now.
> 
> But this is not a big deal.
> 
> What I would like, if possible, is for patches until 14 to be checked
> in, so I can submit the follow up (together with other patches that I
> have stacked on top of that).

Could you put them in a git tree please?

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



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