linux-kernel - Re: [rtc-linux] Re: [PATCH 2/2] rtc: Add boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090914225928.GB29406@nb.net.home>
Date:	Tue, 15 Sep 2009 00:59:28 +0200
From:	Karel Zak <kzak@...hat.com>
To:	rtc-linux@...glegroups.com
Cc:	Matthew Garrett <mjg59@...f.ucam.org>, linux-kernel@...r.kernel.org
Subject: Re: [rtc-linux] Re: [PATCH 2/2] rtc: Add boot_timesource sysfs
	attribute

On Fri, Sep 04, 2009 at 06:52:43PM +0200, Alessandro Zummo wrote:
> 
> On Fri, 4 Sep 2009 17:41:27 +0100
> Matthew Garrett <mjg59@...f.ucam.org> wrote:
> 
> > >  it shouldn't. maybe your hwclock is waiting for the tick
> > >  or something similar. I'd check it.  
> > 
> > I'm just going by what our userspace people are saying. They'd prefer 
> > not to have to run --hctosys if the time's already been set - 
> > https://bugzilla.redhat.com/show_bug.cgi?id=489494 has the discussion.
> > 
> 
>  that's ok, but nonetheless there's a problem in hwclock
>  if it takes 3 secs to read the time.

 IMHO 3 seconds is nonsense. It's usually 0.5 - 1 second.
 
 Anyway, the "hwclock --hctosys" in userspace is a mystical voodoo and
 it's definitely better to move this thing to kernel.

    Karel

-- 
 Karel Zak  <kzak@...hat.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/