xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Don Slutz <dslutz@verizon.com>, Xen-devel <xen-devel@lists.xen.org>
Cc: Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>,
	Keir Fraser <keir@xen.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@citrix.com>
Subject: Re: [PATCH v3 5/5] xen/console: Traditional console timestamps including milliseconds
Date: Fri, 7 Mar 2014 00:41:40 +0000	[thread overview]
Message-ID: <531915C4.6060102@citrix.com> (raw)
In-Reply-To: <53190AB0.4020806@terremark.com>

On 06/03/2014 23:54, Don Slutz wrote:
> On 03/06/14 14:28, Andrew Cooper wrote:
>>
>>   }
>>   -struct tm wallclock_time(void)
>> +struct tm wallclock_time(uint64_t *ns)
>>   {
>
> Adding:
>
>    if ( ns )
>       *ns = 0;
>
> Makes sense here.
>
>>       return (struct tm) { 0 };
>>   }
>> diff --git a/xen/arch/x86/time.c b/xen/arch/x86/time.c
>> index 4f4de22..1156ccc 100644
>> --- a/xen/arch/x86/time.c
>> +++ b/xen/arch/x86/time.c
>> @@ -1646,15 +1646,19 @@ int dom0_pit_access(struct ioreq *ioreq)
>>       return 0;
>>   }
>>   -struct tm wallclock_time(void)
>> +struct tm wallclock_time(uint64_t *ns)
>>   {
>> -    uint64_t seconds;
>> +    uint64_t seconds, nsec;
>>         if ( !wc_sec )
>
> And here.
>
>>           return (struct tm) { 0 };
>>         seconds = NOW() + SECONDS(wc_sec) + wc_nsec;
>> -    do_div(seconds, 1000000000);
>> +    nsec = do_div(seconds, 1000000000);
>> +
>> +    if ( *ns )
>
> This should be just
>
>    if ( ns )

Oops - so it should.

As for the other changes, I am a bit ambivalent.  printk_start_of_line()
is the sole caller of wallclock_time(), which means that tm.tm_day being
0 means *ns will never get looked at.

While it is not exactly a hot codepath, unconditionally clearing it
seems silly, especially as it is not exactly the most likely candidate
to get a new caller in the near future.

~Andrew

  reply	other threads:[~2014-03-07  0:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 19:28 [PATCH v3 0/5] Improvements to console timestamps Andrew Cooper
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 [this message]
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=531915C4.6060102@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=dslutz@verizon.com \
    --cc=ian.campbell@citrix.com \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --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).