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

Re: [Xen-devel] [PATCH 4 of 5 v3] xen: tracing: introduce per-scheduler trace event IDs

On Mon, Dec 17, 2012 at 10:29 PM, Dario Faggioli
<dario.faggioli@xxxxxxxxxx> wrote:
> So that it becomes possible to create scheduler specific trace records,
> within each scheduler, without worrying about the overlapping, and also
> without giving up being able to recognise them univocally. The latter
> is deemed as useful, since we can have more than one scheduler running
> at the same time, thanks to cpupools.
> The event ID is 12 bits, and this change uses the upper 3 of them for
> the 'scheduler ID'. This means we're limited to 8 schedulers and to
> 512 scheduler specific tracing events. Both seem reasonable limitations
> as of now.
> This also converts the existing credit2 tracing (the only scheduler
> generating tracing events up to now) to the new system.

Dario, do you have xenalyze patches for this changeset somewhere?


Xen-devel mailing list



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