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

[Wei Liu <wei.liu2@citrix.com>]

On Mon, Mar 07, 2016 at 04:21:22AM -0700, Jan Beulich wrote:
> >>> On 07.03.16 at 11:54, <wei.liu2@citrix.com> wrote:
> > On Mon, Mar 07, 2016 at 03:50:20AM -0700, Jan Beulich wrote:
> >> >>> On 04.03.16 at 19:25, <dario.faggioli@citrix.com> 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.
> >> 
> >> And that's the part I could reasonably take care of. I generally avoid
> >> committing larger chunks of tools/ stuff, with the expectation that
> >> Ian would take deal with those.
> >> 
> > 
> > Ian is away this week. To avoid having no tools stuff committed this
> > whole week, I can prepare a branch for you to pull if you think that's
> > OK.
> 
> Well, if these were urgent I'd say yes. But I don't think they are,
> so I'd leave it to either Konrad (who has basically asked for what
> you offer) if he wants to deal with it, of wait for Ian's return.
> 

It's not urgent, but I would like to avoid wasting any test cycle. No
matter how innocent a patch looks, there is always risk that it breaks
something.

Konrad, your call.

Wei.

> Jan
> 

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