From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alessandro Zummo <alessandro.zummo@towertech.it>
Cc: rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [rtc-linux] [PATCH 2/2] rtc: Add boot_timesource sysfs attribute
Date: Fri, 4 Sep 2009 17:30:29 +0100 [thread overview]
Message-ID: <20090904163029.GA25239@srcf.ucam.org> (raw)
In-Reply-To: <20090904182528.591dbd29@i1501.lan.towertech.it>
On Fri, Sep 04, 2009 at 06:25:28PM +0200, Alessandro Zummo wrote:
> This feature is meant to be in addition of the regular
> hwclock call to read the system time.
>
> Have you tested if there are drawbacks by not reading it? Like
> TZ, DST and similar?
Current util-linux has a hwclock that can just set the timezone without
performing a full read. However, there's no way of knowing whether it's
safe to do this without knowing that the kernel config option was set
and used. We'd prefer to avoid always doing --hctosys because it's a
noticable performance hit on boot if the work's already been done by the
kernel.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-09-04 16:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 16:26 [PATCH 1/2] rtc: Document the sysfs interface Matthew Garrett
2009-09-04 16:26 ` [PATCH 2/2] rtc: Add boot_timesource sysfs attribute Matthew Garrett
2009-09-04 16:25 ` [rtc-linux] " Alessandro Zummo
2009-09-04 16:30 ` Matthew Garrett [this message]
2009-09-04 16:38 ` [rtc-linux] " Alessandro Zummo
2009-09-04 16:41 ` Matthew Garrett
2009-09-04 16:52 ` Alessandro Zummo
2009-09-04 16:55 ` Matthew Garrett
2009-09-04 17:03 ` Alessandro Zummo
2009-09-04 17:09 ` Matthew Garrett
2009-09-05 21:11 ` Alessandro Zummo
2009-09-06 1:34 ` Mark Brown
2009-09-14 22:59 ` Karel Zak
2009-09-04 16:26 ` [rtc-linux] [PATCH 1/2] rtc: Document the sysfs interface Alessandro Zummo
2009-09-04 16:35 ` Mark Brown
2009-09-04 16:39 ` Matthew Garrett
2009-09-04 16:52 ` [rtc-linux] " Mark Brown
2009-09-04 23:23 ` Andrew Morton
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=20090904163029.GA25239@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=alessandro.zummo@towertech.it \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
/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