From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Maydell Subject: Re: [RFC v2] ARM VM System Specification Date: Mon, 30 Jun 2014 22:14:01 +0100 Message-ID: References: <20140328184517.GA27219@cbox> <20140611065412.GA24286@lvm> <53981043.3010300@redhat.com> <9801429.iblEns5zC3@wuerfel> <53B18E03.4050902@jonmasters.org> <20140630204647.GA19743@cbox> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20140630204647.GA19743@cbox> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Christoffer Dall Cc: Michael Casadevall , Arnd Bergmann , kvm-devel , Rob Herring , "marc.zyngier@arm.com" , "xen-devel@lists.xen.org" , Grant Likely , Christopher Covington , Stefano Stabellini , "cross-distro@lists.linaro.org" , Jon Masters , Paolo Bonzini , "kvmarm@lists.cs.columbia.edu" , arm-mail-list , Ian Campbell List-Id: xen-devel@lists.xenproject.org On 30 June 2014 21:46, Christoffer Dall wrote: > Seems like we should stick a note in there about being UEFI compatible > requires an RTC. We went this far before Peter raised the issue with > noone else realizing it, so it seems like a good idea to me. How about: ===== Guest OSes in the VM image should rely on the UEFI RTC API for real time clock services. (To provide that API, the VM system will likely need to implement some real time clock device, but the details of these are a private implementation issue between it and its associated UEFI implementation.) ===== ? thanks -- PMM