linux-kernel - Re: [PATCH 1/2] x86/xen: sync the CMOS RTC as well as the Xen wallclock

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]

Date:	Tue, 28 May 2013 15:05:30 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	John Stultz <john.stultz@...aro.org>
Cc:	David Vrabel <david.vrabel@...rix.com>, xen-devel@...ts.xen.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] x86/xen: sync the CMOS RTC as well as the Xen
 wallclock

On Tue, May 28, 2013 at 12:01:57PM -0700, John Stultz wrote:
> On 05/28/2013 11:22 AM, David Vrabel wrote:
> >From: David Vrabel <david.vrabel@...rix.com>
> >
> >Adjustments to Xen's persistent_clock via update_persistent_clock()
> >don't actually persist, as the xen_set_walltime() just notifies other
> >domN guests that it has been updated, and does not modify the
> >underlying CMOS clock.
> >
> >Thus, this patch modifies xen_set_wallclock() so it will set the
> >underlying CMOS clock when called from dom0, ensuring the
> >persistent_clock will be correct on the next hardware boot.
> >
> >Dom0 does not support accessing EFI runtime services and Xen does not
> >run on Moorsetown platforms so the CMOS RTC is the only supported
> >hardware clock.
> >
> >Signed-off-by: David Vrabel <david.vrabel@...rix.com>
> >Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
> 
> Ok, I've queued this for 3.11.

Thanks.
> 
> thanks
> -john
> 
--
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/