Re: [Xen-devel] [PATCH 5/5] formats: print time values as decimals

[Dario Faggioli <dfaggioli@xxxxxxxx>]

On Wed, 2018-09-12 at 20:28 +0300, Andrii Anisov wrote:
> On 12.09.18 10:54, Dario Faggioli wrote:
> > 
> > Or, in general, what I think would be useful, is to have the
> > timestamps
> > and the scheduling parameters in the same domain (when possible).
> 
> As I understand, now we do have among scheduling parameters:
>      - credit's tsclice in ms, rlimit in us, migration delay in us
>      - rtds'es period and budget in us.
> 
> I do not think it worth to add more zeros to those parameters for 
> converting them to ns.
> 
We're still speaking only about printing right? IAC, you're right, me
saying "scheduling parameters" was a bit too generic.

What I care is to be able to, when looking at a trace, compare/relate
the time at which a particular event occurred (i.e., the timestamps)
with budget and absolute deadlines --as far as RTDS is concern-- and
with credits --as far as Credit 1 and 2 are concerned (and also with
remaining cap budget, for Credit2).

In fact, that is what you need to fiddle with, in order to understand
whether events are occurring when they are supposed to.

Those other global and (almost) never changing parameters you're
mentioning, are less of a concern, and we can print it in whatever time
unit we want (as far as it's possible to tell which one).

> IMHO trimming timestamps from ns would not be accepted, as well.
> 
No, let's _not_ do that! :-D

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel