public inbox for kvm-ppc@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Alexander Graf <agraf@suse.de>,
	kvm@vger.kernel.org, kvm-ppc <kvm-ppc@vger.kernel.org>
Subject: Re: [PATCH] spapr: Add "memop" hypercall
Date: Mon, 21 May 2012 13:55:08 +0000	[thread overview]
Message-ID: <4FBA493C.1000308@redhat.com> (raw)
In-Reply-To: <1337600909.2779.93.camel@pasglop>

On 05/21/2012 02:48 PM, Benjamin Herrenschmidt wrote:
> On Mon, 2012-05-21 at 13:07 +0300, Avi Kivity wrote:
> > > Now I'm adding another one, so yes, it's looking like a trend :-) I'll
> > > look into it, at this stage with only those two, adding some comments in
> > > the header might be plenty enough.
> > 
> > Documentation/virtual/kvm/ppc-pv.txt is a nice central place for these. 
> > It would be even better if you could add them to the spec.
>
> They don't quite fit with the other PV calls in there which use a
> different HV calling mechanism alltogether, but I can certainly add a
> specific section.
>
> As to adding things to PAPR, let's assume for now that this isn't
> possible :-) Besides, those two hypercalls are pretty specific to the
> way things are implemented in qemu and are in both case more or less
> private mechanisms used to communicate between qemu and the SLOF
> firmware we run in inside qemu, they aren't really used by random guest
> SW and aren't meant to be.

Okay.  But let's have a spec, even a kvm-private one, and then an
implementation of that spec, instead of an implementation and some
documentation added as an afterthought (or not).

> It's a bit like if you had private calls between seabios and qemu...

We document those too.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2012-05-21 13:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21  7:24 [PATCH] spapr: Add "memop" hypercall Benjamin Herrenschmidt
2012-05-21  8:38 ` Alexander Graf
2012-05-21  8:59   ` Benjamin Herrenschmidt
2012-05-21  9:06     ` Alexander Graf
2012-05-21  9:47 ` Avi Kivity
2012-05-21 10:04   ` Benjamin Herrenschmidt
2012-05-21 10:07     ` Avi Kivity
2012-05-21 11:48       ` Benjamin Herrenschmidt
2012-05-21 13:55         ` Avi Kivity [this message]
2012-05-21 21:59           ` Benjamin Herrenschmidt
2012-05-25  3:12           ` Benjamin Herrenschmidt
2012-05-28 10:40             ` Avi Kivity
2012-05-30  8:25               ` Alexander Graf
2012-05-31  3:22               ` Benjamin Herrenschmidt
2012-05-25  3:53       ` [PATCH v2] " Benjamin Herrenschmidt
2012-05-25  8:30         ` Alexander Graf
2012-05-25  8:36           ` Benjamin Herrenschmidt
2012-05-25  8:54             ` Alexander Graf
2012-05-25  9:24               ` Benjamin Herrenschmidt
2012-05-25 10:29                 ` Alexander Graf
2012-05-25 12:41                   ` Benjamin Herrenschmidt

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=4FBA493C.1000308@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.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