public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Christoffer Dall <christoffer.dall@linaro.org>,
	Peter Maydell <peter.maydell@linaro.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	kvm-devel <kvm@vger.kernel.org>,
	Michael Casadevall <Michael.casadevall@linaro.org>,
	"marc.zyngier@arm.com" <marc.zyngier@arm.com>,
	Rob Herring <rob.herring@linaro.org>,
	"cross-distro@lists.linaro.org" <cross-distro@lists.linaro.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	Christopher Covington <cov@codeaurora.org>,
	Grant Likely <grant.likely@linaro.org>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [RFC v2] ARM VM System Specification
Date: Wed, 11 Jun 2014 11:06:45 +0200	[thread overview]
Message-ID: <9801429.iblEns5zC3@wuerfel> (raw)
In-Reply-To: <53981043.3010300@redhat.com>

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.

	Arnd

  reply	other threads:[~2014-06-11  9:07 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 [this message]
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=9801429.iblEns5zC3@wuerfel \
    --to=arnd@arndb.de \
    --cc=Michael.casadevall@linaro.org \
    --cc=christoffer.dall@linaro.org \
    --cc=cov@codeaurora.org \
    --cc=cross-distro@lists.linaro.org \
    --cc=grant.likely@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marc.zyngier@arm.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=rob.herring@linaro.org \
    --cc=stefano.stabellini@citrix.com \
    --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: 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