[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v2 6/8] xenalyze: handle more events in sched_process

On Thu, May 7, 2015 at 6:28 PM, Andrew Cooper <andrew.cooper3@xxxxxxxxxx> wrote:
> On 07/05/15 18:13, George Dunlap wrote:
>>> +        case TRC_SCHED_ADJDOM:
>>> > +            printf(" %s sched_adjdom domid d%u\n",
>>> > +                   ri->dump_header, ri->d[0]);
>>> > +            break;
>> <aside>Wow, this has got to be one of the most useless trace points
>> ever...</aside>
> Is it a candidate for dropping from the hypervisor then?  No use keeping
> useless tracepoints.

Well it would have to be replaced with something more informative.
"Someone changed something" is pretty useless, but it's still more
information than nothing at all.  (Presumably the replacement would be
a per-scheduler tracepoint.)


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.