On Fri, Sep 30, 2016 at 10:21 AM, Dario Faggioli <[email protected]> wrote: > As far as {csched, csched2, rt}_schedule() are concerned, > an "empty" event, would already make it easier to read and > understand a trace. > > But while there, add a few useful information, like > if the cpu that is going through the scheduler has > been tickled or not, if it is currently idle, etc > (they vary, on a per-scheduler basis). > > For Credit1 and Credit2, add a record about when > rate-limiting kicks in too. > > Signed-off-by: Dario Faggioli <[email protected]> > --- > Cc: George Dunlap <[email protected]> > Cc: Meng Xu <[email protected]> > Cc: Anshul Makkar <[email protected]> > --- > Changes from v1: > * corrected the schedule record for sched_rt.c, as pointed out during review; > * pack the Credit1 records as well, as requested during review. > --- > xen/common/sched_credit.c | 32 ++++++++++++++++++++++++++++++++ > xen/common/sched_credit2.c | 38 +++++++++++++++++++++++++++++++++++++- > xen/common/sched_rt.c | 15 +++++++++++++++ > 3 files changed, 84 insertions(+), 1 deletion(-)
As to xen/common/sched_rt.c, Reviewed-by: Meng Xu <[email protected]> Thanks, Meng -- ------------ Meng Xu PhD Student in Computer and Information Science University of Pennsylvania http://www.cis.upenn.edu/~mengxu/ _______________________________________________ Xen-devel mailing list [email protected] https://lists.xen.org/xen-devel
