From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [RFC v2] ARM VM System Specification
Date: Mon, 31 Mar 2014 10:26:13 -0700
Message-ID: <20140331172613.GA4756@lvm>
References: <20140328184517.GA27219@cbox>
 <CAOesGMh7AFfuq73SxOWiiLV0eJNLpA0M5hr0OwRo8=BLWueWwQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: cross-distro@lists.linaro.org,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	xen-devel@lists.xen.org, Peter Maydell <peter.maydell@linaro.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	Michael Casadevall <Michael.casadevall@linaro.org>,
	"marc.zyngier@arm.com" <marc.zyngier@arm.com>,
	Rob Herring <rob.herring@linaro.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	Grant Likely <grant.likely@linaro.org>
To: Olof Johansson <olof@lixom.net>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail-pb0-f54.google.com ([209.85.160.54]:59366 "EHLO
	mail-pb0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752932AbaCaR0J (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 31 Mar 2014 13:26:09 -0400
Received: by mail-pb0-f54.google.com with SMTP id ma3so8580702pbc.27
        for <kvm@vger.kernel.org>; Mon, 31 Mar 2014 10:26:08 -0700 (PDT)
Content-Disposition: inline
In-Reply-To: <CAOesGMh7AFfuq73SxOWiiLV0eJNLpA0M5hr0OwRo8=BLWueWwQ@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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