From: Dario Faggioli <dfaggioli@suse.com>
To: Andrii Anisov <andrii_anisov@epam.com>,
Andrii Anisov <andrii.anisov@gmail.com>,
xen-devel@lists.xen.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 5/5] formats: print time values as decimals
Date: Wed, 12 Sep 2018 19:43:21 +0200 [thread overview]
Message-ID: <24ef5f32130e512a8cba4f9abdcd8455cb4ec43d.camel@suse.com> (raw)
In-Reply-To: <48397450-7b3e-35fd-2314-76a4f59bfe6d@epam.com>
[-- Attachment #1.1: Type: text/plain, Size: 1685 bytes --]
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 #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-09-12 17:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 16:41 [PATCH 0/5] Misc changes to xentrace_format Andrii Anisov
2018-09-10 16:41 ` [PATCH 1/5] xentrace_format: print timestamps in nanoseconds Andrii Anisov
2018-09-11 10:15 ` George Dunlap
2018-09-11 10:32 ` Andrii Anisov
2018-09-11 10:44 ` George Dunlap
2018-09-11 10:45 ` George Dunlap
2018-09-11 15:19 ` Andrii Anisov
2018-09-11 15:54 ` George Dunlap
2018-09-12 7:42 ` Dario Faggioli
2018-09-12 16:44 ` Andrii Anisov
2018-09-12 17:16 ` Andrii Anisov
2018-09-10 16:41 ` [PATCH 2/5] xentrace_format: switch mhz option to float Andrii Anisov
2018-09-11 10:21 ` George Dunlap
2018-09-10 16:41 ` [PATCH 3/5] xentrace_format: combine 64-bit LE values from traces Andrii Anisov
2018-09-11 10:48 ` George Dunlap
2018-09-11 12:23 ` Andrii Anisov
2018-09-12 7:47 ` Dario Faggioli
2018-09-10 16:41 ` [PATCH 4/5] formats: allign trace record format to the current code Andrii Anisov
2018-09-11 10:51 ` George Dunlap
2018-09-12 7:49 ` Dario Faggioli
2018-09-10 16:41 ` [PATCH 5/5] formats: print time values as decimals Andrii Anisov
2018-09-11 10:33 ` George Dunlap
2018-09-12 7:54 ` Dario Faggioli
2018-09-12 17:28 ` Andrii Anisov
2018-09-12 17:43 ` Dario Faggioli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24ef5f32130e512a8cba4f9abdcd8455cb4ec43d.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=andrii.anisov@gmail.com \
--cc=andrii_anisov@epam.com \
--cc=george.dunlap@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).