From: Andrii Anisov <andrii_anisov@epam.com>
To: Jan Beulich <JBeulich@suse.com>, andrii.anisov@gmail.com
Cc: Tim Deegan <tim@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel@lists.xen.org, Julien Grall <julien.grall@arm.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] perfc: Print a system time in a convenient format
Date: Tue, 11 Sep 2018 11:50:42 +0300 [thread overview]
Message-ID: <d643cde4-a64a-fee0-af57-6d169fd04206@epam.com> (raw)
In-Reply-To: <5B977C7902000078001E70BE@prv1-mh.provo.novell.com>
Hello Jan,
On 11.09.18 11:27, Jan Beulich wrote:
> NAK, for two reasons: I'm not of the opinion that reading a 15 or more
> digit decimal number without any separators is any easier than the
> current format.
It's quite subjective. IMHO timestamps measured in ns easier to
understand in decimals rather than in separated 32-bit hex-es. No matter
how many digital number they have.
Even post processing of perfc output is easier in case of decimal
timestamps. You should not parse hexes and odd separators to calculate
the time elapsed between two samples.
> And then if you/we were to change this, then please
> uniformly everywhere - there's even a second instance right in this
> same file you change, not to speak of similar ones elsewhere
I'll check through this file.
--
*Andrii Anisov*
_______________________________________________
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-11 8:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 6:53 [PATCH] perfc: Print a system time in a convenient format Andrii Anisov
2018-09-11 8:27 ` Jan Beulich
2018-09-11 8:50 ` Andrii Anisov [this message]
2018-09-11 9:10 ` Jan Beulich
2018-09-11 9:15 ` Andrew Cooper
2018-09-11 9:18 ` Jan Beulich
2018-09-11 9:20 ` Andrew Cooper
2018-09-11 9:28 ` Jan Beulich
2018-09-11 9:21 ` Andrii Anisov
2018-09-11 9:30 ` Jan Beulich
2018-09-11 9:49 ` Andrii Anisov
2018-09-11 14:04 ` Andrii Anisov
2018-09-11 14:27 ` George Dunlap
2018-09-11 14:33 ` Jan Beulich
2018-09-11 9:28 ` George Dunlap
2018-09-11 9:37 ` Jan Beulich
2018-09-11 9:19 ` Andrii Anisov
2018-09-11 9:24 ` George Dunlap
2018-09-11 9:33 ` Jan Beulich
2018-09-11 9:50 ` Andrii Anisov
2018-09-11 9:51 ` George Dunlap
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=d643cde4-a64a-fee0-af57-6d169fd04206@epam.com \
--to=andrii_anisov@epam.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=andrii.anisov@gmail.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.