From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Avi Kivity <avi@redhat.com>
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 21:59:37 +0000 [thread overview]
Message-ID: <1337637577.2779.115.camel@pasglop> (raw)
In-Reply-To: <4FBA493C.1000308@redhat.com>
On Mon, 2012-05-21 at 16:55 +0300, Avi Kivity wrote:
>
> 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.
Well, we have the implementation so in any case the implementation
-will- be an afterthought :-) Anyways, I'll look into adding that to the
patch.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Avi Kivity <avi@redhat.com>
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: Tue, 22 May 2012 07:59:37 +1000 [thread overview]
Message-ID: <1337637577.2779.115.camel@pasglop> (raw)
In-Reply-To: <4FBA493C.1000308@redhat.com>
On Mon, 2012-05-21 at 16:55 +0300, Avi Kivity wrote:
>
> 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.
Well, we have the implementation so in any case the implementation
-will- be an afterthought :-) Anyways, I'll look into adding that to the
patch.
Cheers,
Ben.
next prev parent reply other threads:[~2012-05-21 21:59 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 7:24 [PATCH] spapr: Add "memop" hypercall Benjamin Herrenschmidt
2012-05-21 7:24 ` Benjamin Herrenschmidt
2012-05-21 8:38 ` Alexander Graf
2012-05-21 8:38 ` Alexander Graf
2012-05-21 8:59 ` Benjamin Herrenschmidt
2012-05-21 8:59 ` Benjamin Herrenschmidt
2012-05-21 9:06 ` Alexander Graf
2012-05-21 9:06 ` Alexander Graf
2012-05-21 9:47 ` Avi Kivity
2012-05-21 9:47 ` Avi Kivity
2012-05-21 10:04 ` Benjamin Herrenschmidt
2012-05-21 10:04 ` Benjamin Herrenschmidt
2012-05-21 10:07 ` Avi Kivity
2012-05-21 10:07 ` Avi Kivity
2012-05-21 11:48 ` Benjamin Herrenschmidt
2012-05-21 11:48 ` Benjamin Herrenschmidt
2012-05-21 13:55 ` Avi Kivity
2012-05-21 13:55 ` Avi Kivity
2012-05-21 21:59 ` Benjamin Herrenschmidt [this message]
2012-05-21 21:59 ` Benjamin Herrenschmidt
2012-05-25 3:12 ` Benjamin Herrenschmidt
2012-05-25 3:12 ` Benjamin Herrenschmidt
2012-05-28 10:40 ` Avi Kivity
2012-05-28 10:40 ` Avi Kivity
2012-05-30 8:25 ` Alexander Graf
2012-05-30 8:25 ` Alexander Graf
2012-05-31 3:22 ` Benjamin Herrenschmidt
2012-05-31 3:22 ` Benjamin Herrenschmidt
2012-05-25 3:53 ` [PATCH v2] " Benjamin Herrenschmidt
2012-05-25 3:53 ` [Qemu-devel] " Benjamin Herrenschmidt
2012-05-25 3:53 ` Benjamin Herrenschmidt
2012-05-25 8:30 ` Alexander Graf
2012-05-25 8:30 ` [Qemu-devel] " Alexander Graf
2012-05-25 8:30 ` Alexander Graf
2012-05-25 8:36 ` Benjamin Herrenschmidt
2012-05-25 8:36 ` [Qemu-devel] " Benjamin Herrenschmidt
2012-05-25 8:36 ` Benjamin Herrenschmidt
2012-05-25 8:54 ` Alexander Graf
2012-05-25 8:54 ` [Qemu-devel] " Alexander Graf
2012-05-25 8:54 ` Alexander Graf
2012-05-25 9:24 ` Benjamin Herrenschmidt
2012-05-25 9:24 ` [Qemu-devel] " Benjamin Herrenschmidt
2012-05-25 9:24 ` Benjamin Herrenschmidt
2012-05-25 10:29 ` Alexander Graf
2012-05-25 10:29 ` [Qemu-devel] " Alexander Graf
2012-05-25 10:29 ` Alexander Graf
2012-05-25 12:41 ` Benjamin Herrenschmidt
2012-05-25 12:41 ` [Qemu-devel] " Benjamin Herrenschmidt
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=1337637577.2779.115.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.