From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2] ARM VM System Specification
Date: Mon, 31 Mar 2014 10:26:13 -0700 [thread overview]
Message-ID: <20140331172613.GA4756@lvm> (raw)
In-Reply-To: <CAOesGMh7AFfuq73SxOWiiLV0eJNLpA0M5hr0OwRo8=BLWueWwQ@mail.gmail.com>
On Sun, Mar 30, 2014 at 03:10:50PM -0700, Olof Johansson wrote:
> On Fri, Mar 28, 2014 at 11:45 AM, Christoffer Dall
> <christoffer.dall@linaro.org> wrote:
> > ARM VM System Specification
> > ===========================
>
> [not quoting the whole spec here]
>
> This looks very sane to me, and aligns very well with non-virtualized images.
>
> For what it's worth, even though it's not a patch:
>
> Acked-by: Olof Johansson <olof@lixom.net>
Thanks, appreciate it.
>
> What's the plan on how to lock this in? Where's this document going to
> live? In the kernel sources under Documentation/, or external?
>
There were talks during LCA14 about publishing it as a Linaro
white-paper, but I would like it to be hosted by the open-source
projects that relate to it, for example the Linux kernel under
Documentaiton/ to represent both the guest and KVM side, and the Xen
sources too.
However, that may be a pain to update so the preferred method could be
to host it in either its current form (clear-text) or publish some
versioned PDF somewhere and simply point to it from the compliant
software pieces.
Suggestions or input welcome.
-Christoffer
next prev parent reply other threads:[~2014-03-31 17:26 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 [this message]
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
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=20140331172613.GA4756@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).