From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2] ARM VM System Specification
Date: Tue, 10 Jun 2014 13:04:40 -0400 [thread overview]
Message-ID: <53973AA8.9020301@codeaurora.org> (raw)
In-Reply-To: <CAFEAcA-isiLax0UASTMkedwGXWOaBdR7N1t2o87XYDkj5nt5ig@mail.gmail.com>
Hi Peter,
On 06/10/2014 10:42 AM, 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.
Pardon my ignorance, but what exactly disqualifies Generic Timer
implementations from being used as Real Time Clocks?
Thanks,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-06-10 17:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 18:45 [RFC v2] ARM VM System Specification Christoffer Dall
2014-03-30 22:10 ` Olof Johansson
2014-03-31 17:26 ` Christoffer Dall
2014-04-01 9:49 ` Ian Campbell
2014-04-01 9:57 ` Michael Casadevall
2014-04-01 10:16 ` Grant Likely
2014-04-29 14:42 ` Christoffer Dall
2014-04-30 8:14 ` Grant Likely
2014-06-10 14:42 ` Peter Maydell
2014-06-10 15:03 ` Ian Campbell
2014-06-10 17:00 ` Paolo Bonzini
2014-06-10 17:04 ` Christopher Covington [this message]
2014-06-10 18:08 ` Peter Maydell
2014-06-10 18:56 ` 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 8:16 ` Paolo Bonzini
2014-06-11 9:06 ` Arnd Bergmann
2014-06-30 16:19 ` Jon Masters
2014-06-30 20:46 ` Christoffer Dall
2014-06-30 21:14 ` Peter Maydell
2014-07-01 17:03 ` Stefano Stabellini
2014-07-01 17:10 ` Peter Maydell
2014-07-02 10:13 ` Christoffer Dall
2014-06-11 11:33 ` Grant Likely
2014-06-11 11:58 ` Arnd Bergmann
2014-06-11 12:02 ` Grant Likely
2014-06-11 14:14 ` Peter Maydell
2014-06-10 16:44 ` Claudio Fontana
2014-06-10 19:21 ` Arnd Bergmann
2014-06-11 9:50 ` Stefano Stabellini
2014-06-11 9:55 ` Christoffer Dall
2014-06-11 11:28 ` Grant Likely
2014-06-11 12:04 ` Christoffer Dall
2014-06-11 10:27 ` Arnd Bergmann
2014-06-11 11:22 ` Grant Likely
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=53973AA8.9020301@codeaurora.org \
--to=cov@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).