linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2] ARM VM System Specification
Date: Wed, 2 Jul 2014 03:13:10 -0700	[thread overview]
Message-ID: <20140702101310.GC20104@cbox> (raw)
In-Reply-To: <CAFEAcA9v_xY36iYpCXOt5JTNE4ehiQh7k3LtkyF+=d50LMm=GA@mail.gmail.com>

On Tue, Jul 01, 2014 at 06:10:19PM +0100, Peter Maydell wrote:
> On 1 July 2014 18:03, Stefano Stabellini
> <stefano.stabellini@eu.citrix.com> wrote:
> > On Mon, 30 Jun 2014, Peter Maydell wrote:
> >> How about:
> >> =====
> >> Guest OSes in the VM image should rely on the UEFI RTC API for
> >> real time clock services. (To provide that API, the VM system will
> >> likely need to implement some real time clock device, but the
> >> details of these are a private implementation issue between it
> >> and its associated UEFI implementation.)
> >
> > I don't see why we need to add the text within brackets: it is out of
> > scope for this document.
> 
> The intention is to be an informative note, not normative text
> (I'm happy if we want to format the text to make that clearer,
> with some sort of NOTE: markup). I'd like VM implementors
> reading this spec to make the correct decisions even if they
> don't happen to know inside-out the details of the UEFI
> specification and what exactly UEFI demands of the hardware,
> and I think it's worth adding the occasional clarifying sentence
> even if it doesn't strictly speaking add any extra rules to the
> specification.
> 
That's also the approach we've taken so far elsewhere in the document,
so I think it's useful.

-Christoffer

  reply	other threads:[~2014-07-02 10:13 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 [this message]
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=20140702101310.GC20104@cbox \
    --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).