On Wed, 2017-02-01 at 14:59 +, George Dunlap wrote:
> 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.
> >
> > [..]
> >
> > Signed-off-by: Dario
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]
On Thu, Jan 26, 2017 at 11:52 AM, 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
>
> > > TBH, what I don't especially like in the output above is, within
> > > the
> > > vCPU info being printed:
> > > - the spaces inside '[' ']';
> > > - the big numbers;
> > > - the fact that last_start is rather useless (it's more tracing
> > > info
> > >than debug dump info, IMO);
> >
On Fri, 2017-01-27 at 12:05 -0500, Meng Xu wrote:
> On Thu, Jan 26, 2017 at 5:08 PM, Dario Faggioli
> wrote:
> > "Runqueue 0" tells that what follow is information about the pCPUs
> > and
> > the vCPUs of that runqueue (it's the same label used above for,
> > showing
>
On Thu, Jan 26, 2017 at 5:08 PM, Dario Faggioli
wrote:
> On Thu, 2017-01-26 at 13:59 -0500, Meng Xu wrote:
>> Hi Dario,
>>
> Hi,
>
>> On Thu, Jan 26, 2017 at 11:52 AM, Dario Faggioli
>> wrote:
>> >
>> > Runqueue 0:
>> > CPU[00] runq=0,
On Thu, 2017-01-26 at 13:59 -0500, Meng Xu wrote:
> Hi Dario,
>
Hi,
> On Thu, Jan 26, 2017 at 11:52 AM, Dario Faggioli
> wrote:
> >
> > Runqueue 0:
> > CPU[00] runq=0, sibling=,0003, core=,00ff
> > run: [0.15] flags=2 cpu=0 credit=5804742
Hi Dario,
I'm commenting on the rtds part.
On Thu, Jan 26, 2017 at 11:52 AM, 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
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=,0003, core=,00ff
run: