From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Maydell Subject: Re: [RFC v2] ARM VM System Specification Date: Wed, 11 Jun 2014 15:14:40 +0100 Message-ID: References: <20140328184517.GA27219@cbox> <53973AA8.9020301@codeaurora.org> <539754E5.3030408@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Grant Likely Cc: arm-mail-list , "cross-distro@lists.linaro.org" , Ian Campbell , kvm-devel , Michael Casadevall , "marc.zyngier@arm.com" , Rob Herring , "xen-devel@lists.xen.org" , Stefano Stabellini , Christopher Covington , Paolo Bonzini , "kvmarm@lists.cs.columbia.edu" , Christoffer Dall List-Id: xen-devel@lists.xenproject.org On 11 June 2014 12:33, Grant Likely wrote: > In practical terms, yes the VM needs to provide an RTC interface, but > I don't think it needs to appear in this spec, even if the kernel > accesses it directly. Portable images should use the UEFI service. I think it might helpful to include some implementation notes to the effect that the VM needs to provide certain things to the associated UEFI implementation but that these aren't part of the specification and the guest OS is expected to use the UEFI interfaces, just for the sake of clarity for people who aren't too familiar with what UEFI requires or provides. thanks -- PMM