From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2] ARM VM System Specification
Date: Wed, 11 Jun 2014 14:04:52 +0200 [thread overview]
Message-ID: <20140611120452.GE24286@lvm> (raw)
In-Reply-To: <CACxGe6vzGrNxqdanhUX3G-dvN-jVrX9YQyOA==h0Vnv_sf-aTA@mail.gmail.com>
On Wed, Jun 11, 2014 at 12:28:40PM +0100, Grant Likely wrote:
> On Wed, Jun 11, 2014 at 10:55 AM, Christoffer Dall
> <christoffer.dall@linaro.org> wrote:
> > Agree with what Stefano says, and I strongly recommend you reconsider
> > your position on FDT vs. ACPI for ARM VMs, but it's completely up to
> > you of course :)
>
> Not entirely.
of course it's up to them what they want to do.
> The plan right now is to only support ACPI when booting
> with UEFI. If they don't use UEFI, then ACPI will not be available. If
> OSv only supports ACPI, then it is forced to use the UEFI boot path.
>
The plan right now is to not support ACPI in VMs at all, as per the last
discussion at LCA14. If an when someone wants to add that, fine, but
the spec mandates FDT describing the full system.
If OSv wants to hack a KVM implementation or provide a static ACPI blob
coupled to OSv that happens to describe the KVM/ARM/QEMU system model,
then they can do that. Crazy, it sounds to me, but as I said, up to the
OSv guys.
-Christoffer
next prev parent reply other threads:[~2014-06-11 12: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
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 [this message]
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=20140611120452.GE24286@lvm \
--to=christoffer.dall@linaro.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).