From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: [PATCH v3 0/5] Improvements to console timestamps
Date: Thu, 6 Mar 2014 19:28:00 +0000 [thread overview]
Message-ID: <1394134085-22952-1-git-send-email-andrew.cooper3@citrix.com> (raw)
This series aims to improve on the current implementation of console
timestamps in Xen.
Patch 1 is just movement of wallclock_time()s declaration to common code.
Patch 2 changes Xen's idea of when time starts, from when the BSPs TSC was 0,
to when Xen boots.
Patch 3 guesses at AP time calibration earlier during boot, so printk()s using
the new console timestamp have a real stamp, rather than 0s.
Patch 4 is the meat of the series, adding a new timestamp implementation to
printk_start_of_line().
Patch 5 comes as a intermediate suggestion, to retain the old timestamp style,
but to display milliseconds as well.
Finally, from discussion in the office, it has been suggested that the
timestamp mode/format would be better as build-time configuration rather than
boot-time configuration. I am on the fence with this regard, but
comments/thoughts are very welcome.
~Andrew
next reply other threads:[~2014-03-06 19:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 19:28 Andrew Cooper [this message]
2014-03-06 19:28 ` [PATCH v3 1/5] xen/time: Move wallclock_time() declaration into common code Andrew Cooper
2014-03-06 19:28 ` [PATCH v3 2/5] x86/time: Always count s_time from Xen boot Andrew Cooper
2014-03-06 19:28 ` [PATCH v3 3/5] x86/time: Initialise time earlier during start_secondary() Andrew Cooper
2014-03-06 19:28 ` [PATCH v3 4/5] xen/console: Provide timestamps as an offset since boot Andrew Cooper
2014-03-07 9:47 ` Jan Beulich
2014-03-07 10:27 ` Andrew Cooper
2014-03-06 19:28 ` [PATCH v3 5/5] xen/console: Traditional console timestamps including milliseconds Andrew Cooper
2014-03-06 23:54 ` Don Slutz
2014-03-07 0:41 ` Andrew Cooper
2014-03-07 23:33 ` Don Slutz
2014-03-11 10:43 ` Ian Campbell
2014-03-11 11:32 ` Andrew Cooper
2014-03-11 11:39 ` Tim Deegan
2014-03-11 12:47 ` Jan Beulich
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=1394134085-22952-1-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.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).