linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jonathan@jonmasters.org (Jon Masters)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2] ARM VM System Specification
Date: Mon, 30 Jun 2014 12:19:15 -0400	[thread overview]
Message-ID: <53B18E03.4050902@jonmasters.org> (raw)
In-Reply-To: <9801429.iblEns5zC3@wuerfel>

On 6/11/14, 5:06 AM, Arnd Bergmann wrote:
> On Wednesday 11 June 2014 10:16:03 Paolo Bonzini wrote:
>>
>>> If kernels actually do use the UEFI runtime services and have no need
>>> for direct access to an RTC when runing in a UEFI compliant system, then
>>> I agree with not specifying the hardware details.
>>
>> The RTC is not needed for ordinary operation of the kernel and, in the
>> current kernel, the EFI RTC driver is only used for IA64.  However, it
>> seems to be platform independent.  I'll give it a shot (on x86, since
>> that's the only architecture for which I know how to get UEFI firmware).
>
> Using the EFI RTC seems appropriate for ARM, as it's a reasonable
> abstraction that should work with any hypervisor. I suspect the only
> reason we don't use it on x86 is that we know which RTC hardware we
> have and the kernel comes with a mandatory driver already.

(sorry for delay in responding to this thread)

Indeed. We should use the EFI RTC driver in general, rather than push 
for many individual RTC drivers on aarch64 systems that are EFI enabled. 
Within Red Hat, we currently have EFI Runtime Services live in many of 
our labs and are using the EFI RTC. This is the way forward.

Jon.

  reply	other threads:[~2014-06-30 16:19 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
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 [this message]
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=53B18E03.4050902@jonmasters.org \
    --to=jonathan@jonmasters.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).