From: Dario Faggioli <dfaggioli@suse.com>
To: George Dunlap <george.dunlap@citrix.com>,
Andrii Anisov <andrii.anisov@gmail.com>,
xen-devel@lists.xen.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Andrii Anisov <andrii_anisov@epam.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 5/5] formats: print time values as decimals
Date: Wed, 12 Sep 2018 09:54:53 +0200 [thread overview]
Message-ID: <6d9633125b46460c8200c848c81212cba34b9a04.camel@suse.com> (raw)
In-Reply-To: <34420b79-4e2a-6ae4-7838-039e6dd7ee94@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1043 bytes --]
On Tue, 2018-09-11 at 11:33 +0100, George Dunlap wrote:
> On 09/10/2018 05:41 PM, Andrii Anisov wrote:
> > From: Andrii Anisov <andrii_anisov@epam.com>
> >
> > For convinience, print RTDS budget and deadline values as decimals.
> >
I agree, this is a lot better.
> > Signed-off-by: Andrii Anisov <andrii_anisov@epam.com>
>
> Acked-by: George Dunlap <george.dunlap@citrix.com>
>
Not strictly necessary, I now. Still:
Reviewed-by: Dario Faggioli <dfaggioli@suse.com>
Andrii, if you decide to make the patch that turns timestamps into
secs.nsecs, can we also convert these to such format (again, in case we
have MHz)?
Or, in general, what I think would be useful, is to have the timestamps
and the scheduling parameters in the same domain (when possible).
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
next prev parent reply other threads:[~2018-09-12 8:17 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 [this message]
2018-09-12 17:28 ` Andrii Anisov
2018-09-12 17:43 ` Dario Faggioli
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=6d9633125b46460c8200c848c81212cba34b9a04.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).