From: Ian Campbell <Ian.Campbell@citrix.com> To: Peter Maydell <peter.maydell@linaro.org> Cc: Christoffer Dall <christoffer.dall@linaro.org>, "cross-distro@lists.linaro.org" <cross-distro@lists.linaro.org>, arm-mail-list <linux-arm-kernel@lists.infradead.org>, "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>, kvm-devel <kvm@vger.kernel.org>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org> Subject: Re: [RFC v2] ARM VM System Specification Date: Tue, 10 Jun 2014 16:03:20 +0100 [thread overview] Message-ID: <1402412600.20641.25.camel@kazak.uk.xensource.com> (raw) In-Reply-To: <CAFEAcA-isiLax0UASTMkedwGXWOaBdR7N1t2o87XYDkj5nt5ig@mail.gmail.com> On Tue, 2014-06-10 at 15:42 +0100, Peter Maydell wrote: > On 28 March 2014 18:45, Christoffer Dall <christoffer.dall@linaro.org> wrote: > > ARM VM System Specification > > =========================== > > > > > The virtual hardware platform must provide a number of mandatory > > peripherals: > > > > Serial console: The platform should provide a console, > > based on an emulated pl011, a virtio-console, or a Xen PV console. > > > > An ARM Generic Interrupt Controller v2 (GICv2) [3] or newer. GICv2 > > limits the the number of virtual CPUs to 8 cores, newer GIC versions > > removes this limitation. > > > > The ARM virtual timer and counter should be available to the VM as > > per the ARM Generic Timers specification in the ARM ARM [1]. > > I just noticed that this doesn't mandate that the platform > provides an RTC. As I understand it, the UEFI spec mandates > that there's an RTC (could somebody more familiar with UEFI > than me confirm/deny that?) so we should probably put one here. Isn't that already done transitively via the requirement to provide a UEFI environment? I thought the RTC was exposed via UEFI Runtime Service, in which case it's mostly a hypervisor internal issue how time is provided to the (hypervisor provided) UEFI implementation, the guest OS just uses the runtime services interfaces. Given that do we also need to standardise on a guest OS visible clock device too? I'm not sure if we do or not, but if yes then I have a couple of comments on the suggested wording (you can probably guess what they are going to be...): > Suggested wording: > > RTC: The platform should provide a real time clock, based > on an emulated pl031 or mc146818. We would need to include the Xen PV wallclock here too. > and in the guest-support section later: > > The guest OS must include support for pl031 and mc146818 RTC. and here. Ian.
WARNING: multiple messages have this Message-ID (diff)
From: Ian.Campbell@citrix.com (Ian Campbell) To: linux-arm-kernel@lists.infradead.org Subject: [RFC v2] ARM VM System Specification Date: Tue, 10 Jun 2014 16:03:20 +0100 [thread overview] Message-ID: <1402412600.20641.25.camel@kazak.uk.xensource.com> (raw) In-Reply-To: <CAFEAcA-isiLax0UASTMkedwGXWOaBdR7N1t2o87XYDkj5nt5ig@mail.gmail.com> On Tue, 2014-06-10 at 15:42 +0100, Peter Maydell wrote: > On 28 March 2014 18:45, Christoffer Dall <christoffer.dall@linaro.org> wrote: > > ARM VM System Specification > > =========================== > > > > > The virtual hardware platform must provide a number of mandatory > > peripherals: > > > > Serial console: The platform should provide a console, > > based on an emulated pl011, a virtio-console, or a Xen PV console. > > > > An ARM Generic Interrupt Controller v2 (GICv2) [3] or newer. GICv2 > > limits the the number of virtual CPUs to 8 cores, newer GIC versions > > removes this limitation. > > > > The ARM virtual timer and counter should be available to the VM as > > per the ARM Generic Timers specification in the ARM ARM [1]. > > I just noticed that this doesn't mandate that the platform > provides an RTC. As I understand it, the UEFI spec mandates > that there's an RTC (could somebody more familiar with UEFI > than me confirm/deny that?) so we should probably put one here. Isn't that already done transitively via the requirement to provide a UEFI environment? I thought the RTC was exposed via UEFI Runtime Service, in which case it's mostly a hypervisor internal issue how time is provided to the (hypervisor provided) UEFI implementation, the guest OS just uses the runtime services interfaces. Given that do we also need to standardise on a guest OS visible clock device too? I'm not sure if we do or not, but if yes then I have a couple of comments on the suggested wording (you can probably guess what they are going to be...): > Suggested wording: > > RTC: The platform should provide a real time clock, based > on an emulated pl031 or mc146818. We would need to include the Xen PV wallclock here too. > and in the guest-support section later: > > The guest OS must include support for pl031 and mc146818 RTC. and here. Ian.
next prev parent reply other threads:[~2014-06-10 15:03 UTC|newest] Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-03-28 18:45 [RFC v2] ARM VM System Specification Christoffer Dall 2014-03-28 18:45 ` Christoffer Dall 2014-03-30 22:10 ` Olof Johansson 2014-03-30 22:10 ` Olof Johansson 2014-03-30 22:10 ` Olof Johansson 2014-03-31 17:26 ` Christoffer Dall 2014-03-31 17:26 ` Christoffer Dall 2014-03-31 17:26 ` Christoffer Dall 2014-04-01 9:49 ` Ian Campbell 2014-04-01 9:49 ` Ian Campbell 2014-04-01 9:49 ` Ian Campbell 2014-04-01 9:57 ` Michael Casadevall 2014-04-01 9:57 ` Michael Casadevall 2014-04-01 9:57 ` Michael Casadevall 2014-04-01 10:16 ` Grant Likely 2014-04-01 10:16 ` Grant Likely 2014-04-01 10:16 ` Grant Likely 2014-04-29 14:42 ` Christoffer Dall 2014-04-29 14:42 ` Christoffer Dall 2014-04-29 14:42 ` Christoffer Dall 2014-04-30 8:14 ` Grant Likely 2014-04-30 8:14 ` Grant Likely 2014-04-30 8:14 ` Grant Likely 2014-06-10 14:42 ` Peter Maydell 2014-06-10 14:42 ` Peter Maydell 2014-06-10 14:42 ` Peter Maydell 2014-06-10 15:03 ` Ian Campbell [this message] 2014-06-10 15:03 ` Ian Campbell 2014-06-10 15:03 ` Ian Campbell 2014-06-10 17:00 ` Paolo Bonzini 2014-06-10 17:00 ` Paolo Bonzini 2014-06-10 17:00 ` Paolo Bonzini 2014-06-10 17:04 ` Christopher Covington 2014-06-10 17:04 ` Christopher Covington 2014-06-10 17:04 ` Christopher Covington 2014-06-10 18:08 ` Peter Maydell 2014-06-10 18:08 ` Peter Maydell 2014-06-10 18:08 ` Peter Maydell 2014-06-10 18:56 ` Paolo Bonzini 2014-06-10 18:56 ` Paolo Bonzini 2014-06-10 18:56 ` Paolo Bonzini 2014-06-10 19:18 ` Paolo Bonzini 2014-06-10 19:18 ` Paolo Bonzini 2014-06-10 19:18 ` Paolo Bonzini 2014-06-10 19:18 ` Paolo Bonzini 2014-06-10 19:18 ` Paolo Bonzini 2014-06-10 19:18 ` Paolo Bonzini 2014-06-11 6:54 ` Christoffer Dall 2014-06-11 6:54 ` Christoffer Dall 2014-06-11 6:54 ` Christoffer Dall 2014-06-11 8:16 ` Paolo Bonzini 2014-06-11 8:16 ` Paolo Bonzini 2014-06-11 8:16 ` Paolo Bonzini 2014-06-11 9:06 ` Arnd Bergmann 2014-06-11 9:06 ` Arnd Bergmann 2014-06-11 9:06 ` Arnd Bergmann 2014-06-30 16:19 ` Jon Masters 2014-06-30 16:19 ` Jon Masters 2014-06-30 16:19 ` Jon Masters 2014-06-30 20:46 ` Christoffer Dall 2014-06-30 20:46 ` Christoffer Dall 2014-06-30 21:14 ` Peter Maydell 2014-06-30 21:14 ` Peter Maydell 2014-06-30 21:14 ` Peter Maydell 2014-07-01 17:03 ` Stefano Stabellini 2014-07-01 17:03 ` Stefano Stabellini 2014-07-01 17:10 ` Peter Maydell 2014-07-01 17:10 ` Peter Maydell 2014-07-01 17:10 ` Peter Maydell 2014-07-02 10:13 ` Christoffer Dall 2014-07-02 10:13 ` Christoffer Dall 2014-07-02 10:13 ` Christoffer Dall 2014-07-01 17:03 ` Stefano Stabellini 2014-06-30 20:46 ` Christoffer Dall 2014-06-11 11:33 ` Grant Likely 2014-06-11 11:33 ` Grant Likely 2014-06-11 11:58 ` Arnd Bergmann 2014-06-11 11:58 ` Arnd Bergmann 2014-06-11 11:58 ` Arnd Bergmann 2014-06-11 12:02 ` Grant Likely 2014-06-11 12:02 ` Grant Likely 2014-06-11 12:02 ` Grant Likely 2014-06-11 14:14 ` Peter Maydell 2014-06-11 14:14 ` Peter Maydell 2014-06-11 14:14 ` Peter Maydell 2014-06-11 11:33 ` Grant Likely 2014-06-10 16:44 ` Claudio Fontana 2014-06-10 16:44 ` Claudio Fontana 2014-06-10 16:44 ` Claudio Fontana 2014-06-10 19:21 ` Arnd Bergmann 2014-06-10 19:21 ` Arnd Bergmann 2014-06-10 19:21 ` Arnd Bergmann 2014-06-11 9:50 ` Stefano Stabellini 2014-06-11 9:50 ` Stefano Stabellini 2014-06-11 9:50 ` Stefano Stabellini 2014-06-11 9:55 ` Christoffer Dall 2014-06-11 9:55 ` Christoffer Dall 2014-06-11 11:28 ` Grant Likely 2014-06-11 11:28 ` Grant Likely 2014-06-11 11:28 ` Grant Likely 2014-06-11 12:04 ` Christoffer Dall 2014-06-11 12:04 ` Christoffer Dall 2014-06-11 12:04 ` Christoffer Dall 2014-06-11 9:55 ` Christoffer Dall 2014-06-11 10:27 ` Arnd Bergmann 2014-06-11 10:27 ` Arnd Bergmann 2014-06-11 10:27 ` Arnd Bergmann 2014-06-11 11:22 ` Grant Likely 2014-06-11 11:22 ` Grant Likely 2014-06-11 11:22 ` Grant Likely 2014-03-28 18:45 Christoffer Dall
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1402412600.20641.25.camel@kazak.uk.xensource.com \ --to=ian.campbell@citrix.com \ --cc=christoffer.dall@linaro.org \ --cc=cross-distro@lists.linaro.org \ --cc=kvm@vger.kernel.org \ --cc=kvmarm@lists.cs.columbia.edu \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=peter.maydell@linaro.org \ --cc=xen-devel@lists.xen.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.