linux-kernel - Re: [PATCH] x86-64: use EFI to deal with platform wall clock

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <4FBFC1A3020000780008638F@nat28.tlf.novell.com>
Date:	Fri, 25 May 2012 16:30:11 +0100
From:	"Jan Beulich" <JBeulich@...e.com>
To:	"Matthew Garrett" <mjg59@...f.ucam.org>
Cc:	<mingo@...e.hu>, <tglx@...utronix.de>,
	<matt.fleming@...ux.intel.com>, <linux-kernel@...r.kernel.org>,
	<hpa@...or.com>
Subject: Re: [PATCH] x86-64: use EFI to deal with platform wall clock

>>> On 25.05.12 at 17:24, Matthew Garrett <mjg59@...f.ucam.org> wrote:
> On Fri, May 25, 2012 at 04:20:31PM +0100, Jan Beulich wrote:
> 
>> Also make the two EFI functions in question here static - they're not
>> being referenced elsewhere.
> 
> Looks good, but should we also be changing get_time to return in UTC? 

Imo that would be a separate change though.

> What are the expected semantics for get_wallclock?

Not sure - I think both are permitted (just like for the legacy RTC),
with the expectation that early user mode would tell the kernel.

Jan

--
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/