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: Thu, 31 May 2012 03:22:24 +0000 [thread overview]
Message-ID: <1338434544.16119.39.camel@pasglop> (raw)
In-Reply-To: <4FC35629.80704@redhat.com>
On Mon, 2012-05-28 at 13:40 +0300, Avi Kivity wrote:
> Depends. How do you detect it exists? Are you detecting kvm, or qemu,
> or the hypercall itself?
>
> I'd hate us to find ourselves in a maze of disconnected documentation
> with no clear guidelines on when a feature is available and when it is not.
At the moment SLOF just "uses it" when using the frame buffer. We could
advertise its presence via the device-tree, there's already stuff there
to expose what hypercalls or set of hypecalls are implemented for PAPR,
we could add qemu specific extensions.
Cheers,
Ben.
next prev parent reply other threads:[~2012-05-31 3:22 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
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 [this message]
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=1338434544.16119.39.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox