[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] xen: sched: improve debug dump output.
On 26/01/17 16:52, Dario Faggioli wrote: > Scheduling information debug dump for Credit2 is hard > to read as it contains the same information repeated > multiple time in different ways. > > In fact, in Credit2, CPUs are grouped in runqueus. > Here's the current debug output: > > CPU[00] sibling=00000000,00000003, core=00000000,000000ff > run: [32767.0] flags=0 cpu=0 credit=-1073741824 [w=0] load=0 (~0%) > 1: [0.3] flags=0 cpu=2 credit=3273410 [w=256] load=262144 (~100%) > 2: [0.4] flags=0 cpu=2 credit=2974954 [w=256] load=262144 (~100%) > CPU[01] sibling=00000000,00000003, core=00000000,000000ff > run: [32767.1] flags=0 cpu=1 credit=-1073741824 [w=0] load=0 (~0%) > 1: [0.3] flags=0 cpu=2 credit=3273410 [w=256] load=262144 (~100%) > 2: [0.4] flags=0 cpu=2 credit=2974954 [w=256] load=262144 (~100%) > CPU[02] sibling=00000000,0000000c, core=00000000,000000ff > run: [0.2] flags=2 cpu=2 credit=3556909 [w=256] load=262144 (~100%) > 1: [0.3] flags=0 cpu=2 credit=3273410 [w=256] load=262144 (~100%) > 2: [0.4] flags=0 cpu=2 credit=2974954 [w=256] load=262144 (~100%) > > Here, CPUs 0, 1 and 2, are all part of runqueue 0, > the content of which (which, BTW, is d0v3 and d0v4) > is printed 3 times! It is also not very useful to > see the details of the idle vcpus, as they're always > the same (except for the vCPU ids). > > With this change, we print: > - pCPUs details and, for non idle ones, what vCPU > they're running; > - the runqueue content, once and for all. > > Runqueue 0: > CPU[00] runq=0, sibling=00000000,00000003, core=00000000,000000ff > run: [0.15] flags=2 cpu=0 credit=5804742 [w=256] load=3655 (~1%) > CPU[01] runq=0, sibling=00000000,00000003, core=00000000,000000ff > CPU[02] runq=0, sibling=00000000,0000000c, core=00000000,000000ff > run: [0.3] flags=2 cpu=2 credit=6674856 [w=256] load=262144 (~100%) > CPU[03] runq=0, sibling=00000000,0000000c, core=00000000,000000ff > RUNQ: > 0: [0.1] flags=0 cpu=2 credit=6561215 [w=256] load=262144 (~100%) > 1: [0.2] flags=0 cpu=2 credit=5812356 [w=256] load=262144 (~100%) > > Stop printing details of idle vCPUs also in Credit1 > and RTDS (they're pretty useless in there too). > > Signed-off-by: Dario Faggioli <dario.faggioli@xxxxxxxxxx> Hang on -- how does this relate to the credit2 dumping patch you sent the previous week? I'm all in favor of not saving up a massive queue of patches, but if the patches have conflicts with existing patches, I think it would be better if you re-sent a full series with a new version number, so I wouldn't have to try to figure out what order they needed to be applied in and which ones weren't necessary anymore. There's no problem, I don't think, of sending version n+1 of a series that has no changes other than adding new patches. I've checked in and pushed the three patches that I reviewed today; can you rebase your outstanding changes and send another series? Thanks! And sorry it took so long to get to. -George _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |