scheduler credit capture

scheduler credit capture

[amir masoud noohi]

[-- Attachment #1: Type: text/plain, Size: 162 bytes --]

Hi Everyone,

Today I'm looking for capturing vCPU credit for both credit1 and credit2.
How can I do that?

-- 
*Regards*
*Noohi*
*noohi.org <https://noohi.org>*

[-- Attachment #2: Type: text/html, Size: 935 bytes --]

Re: scheduler credit capture

[George Dunlap]

[-- Attachment #1: Type: text/plain, Size: 317 bytes --]

On Wed, Jan 5, 2022 at 2:45 PM amir masoud noohi <highlimner@gmail.com>
wrote:

> Hi Everyone,
>
> Today I'm looking for capturing vCPU credit for both credit1 and credit2.
> How can I do that?
>

Can you explain what you mean by "capture vCPU credit"?  Do you mean you
want to log or sample changes to it?

 -George

[-- Attachment #2: Type: text/html, Size: 932 bytes --]

Re: scheduler credit capture

[George Dunlap]

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

[Adding back in xen-devel to the cc' list]

On Thu, Jan 6, 2022 at 1:41 PM amir masoud noohi <highlimner@gmail.com>
wrote:

> yes exactly, I want to see the changes of a credit for each vCPU
>

(FYI we respond in-line on the Xen mailing lists rather than top posting.)

Your best bet is to look into xentrace & xenalyze, and the trace or TRACE
calls found in xen.git/xen/common/sched/credit[2].c.  It looks like you can
get the info you want for credit2, but not for credit1 unless you add some
trace points in.

You can find a video introduction to Xen tracing here:
https://vimeo.com/33655967

It's a bit old but that system hasn't changed much.

 -George


>
> On Thu, Jan 6, 2022 at 2:32 PM George Dunlap <dunlapg@umich.edu> wrote:
>
>>
>>
>> On Wed, Jan 5, 2022 at 2:45 PM amir masoud noohi <highlimner@gmail.com>
>> wrote:
>>
>>> Hi Everyone,
>>>
>>> Today I'm looking for capturing vCPU credit for both credit1 and
>>> credit2.
>>> How can I do that?
>>>
>>
>> Can you explain what you mean by "capture vCPU credit"?  Do you mean you
>> want to log or sample changes to it?
>>
>>  -George
>>
>
>
> --
> *Regards*
> *Noohi*
> *noohi.org <https://noohi.org>*
>

[-- Attachment #2: Type: text/html, Size: 3308 bytes --]

Re: scheduler credit capture

[amir masoud noohi]

[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]

>
> It looks like you can get the info you want for credit2


How?

On Thu, Jan 6, 2022 at 6:12 PM George Dunlap <dunlapg@umich.edu> wrote:

> [Adding back in xen-devel to the cc' list]
>
> On Thu, Jan 6, 2022 at 1:41 PM amir masoud noohi <highlimner@gmail.com>
> wrote:
>
>> yes exactly, I want to see the changes of a credit for each vCPU
>>
>
> (FYI we respond in-line on the Xen mailing lists rather than top posting.)
>
> Your best bet is to look into xentrace & xenalyze, and the trace or TRACE
> calls found in xen.git/xen/common/sched/credit[2].c.  It looks like you can
> get the info you want for credit2, but not for credit1 unless you add some
> trace points in.
>
> You can find a video introduction to Xen tracing here:
> https://vimeo.com/33655967
>
> It's a bit old but that system hasn't changed much.
>
>  -George
>
>
>>
>> On Thu, Jan 6, 2022 at 2:32 PM George Dunlap <dunlapg@umich.edu> wrote:
>>
>>>
>>>
>>> On Wed, Jan 5, 2022 at 2:45 PM amir masoud noohi <highlimner@gmail.com>
>>> wrote:
>>>
>>>> Hi Everyone,
>>>>
>>>> Today I'm looking for capturing vCPU credit for both credit1 and
>>>> credit2.
>>>> How can I do that?
>>>>
>>>
>>> Can you explain what you mean by "capture vCPU credit"?  Do you mean you
>>> want to log or sample changes to it?
>>>
>>>  -George
>>>
>>
>>
>> --
>> *Regards*
>> *Noohi*
>> *noohi.org <https://noohi.org>*
>>
>

-- 
*Regards*
*Noohi*
*noohi.org <https://noohi.org>*

[-- Attachment #2: Type: text/html, Size: 4592 bytes --]

Re: scheduler credit capture

[George Dunlap]

[-- Attachment #1: Type: text/plain, Size: 449 bytes --]

On Thu, Jan 6, 2022 at 9:05 PM amir masoud noohi <highlimner@gmail.com>
wrote:

> It looks like you can get the info you want for credit2
>
>
> How?
>

We're happy to help point you in the right direction, but I'm afraid you
will have to actually do some work on your own.  Did you google
"xentrace"?  Did you try running it on your system, and then running
xenalyze to see what it spat out?  Did you look at the TRACE calls in
credit2.c?

 -George

[-- Attachment #2: Type: text/html, Size: 1191 bytes --]