linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Yoder Stuart <stuart.yoder@freescale.com>,
	kvm-ppc <kvm-ppc@vger.kernel.org>,
	ppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 2/4] kvmppc: add hypercall infrastructure - guest part
Date: Fri, 22 Aug 2008 09:00:49 -0500	[thread overview]
Message-ID: <200808220900.50611.hollisb@us.ibm.com> (raw)
In-Reply-To: <0AFFA88B-E4B4-4B27-8B6F-8BA0463D7245@kernel.crashing.org>

On Friday 22 August 2008 05:38:54 Kumar Gala wrote:
> 
> On Aug 19, 2008, at 5:36 AM, ehrhardt@linux.vnet.ibm.com wrote:
> 
> > From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
> >
> > This adds the guest portion of the hypercall infrastructure,  
> > basically an
> > illegal instruction with a defined layout.
> > See http://kvm.qumranet.com/kvmwiki/PowerPC_Hypercall_ABI for more  
> > detail
> > on the hypercall ABI for powerpc.
> >
> > Signed-off-by: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
> > ---
> >
> > [diffstat]
> > kvm_para.h |   33 +++++++++++++++++++++++++++++++++
> > 1 file changed, 33 insertions(+)
> >
> > [diff]
> 
> Can we make this more generic (naming) and location.  I believe there  
> is some interesting in using the same ABI on the Freescale HV so it  
> seems like have the wrappers be a bit more generic saves us.

Agreed. Maybe something like epapr_hcalls.h .

-- 
Hollis Blanchard
IBM Linux Technology Center

  reply	other threads:[~2008-08-22 14:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 10:36 [PATCH 0/4][RFC] kvmppc: paravirtualization interface - guest part v2 ehrhardt
2008-08-19 10:36 ` [PATCH 1/4] kvmppc: read device tree hypervisor node infrastructure ehrhardt
2008-08-19 11:52   ` Josh Boyer
2008-08-19 11:56     ` Josh Boyer
2008-08-19 10:36 ` [PATCH 2/4] kvmppc: add hypercall infrastructure - guest part ehrhardt
2008-08-19 11:28   ` Arnd Bergmann
2008-08-20 12:41     ` Christian Ehrhardt
2008-08-21 22:25     ` Hollis Blanchard
2008-08-22 10:38   ` Kumar Gala
2008-08-22 14:00     ` Hollis Blanchard [this message]
2008-08-19 10:36 ` [PATCH 3/4] kvmppc: magic page paravirtualization " ehrhardt
2008-08-20  2:29   ` Tony Breeds
2008-08-19 10:36 ` [PATCH 4/4] kvmppc: convert wrteei to wrtee as kvm guest optimization ehrhardt
2008-08-19 11:42   ` Arnd Bergmann
2008-08-20 12:53     ` Christian Ehrhardt
2008-08-20 18:30       ` Hollis Blanchard
2008-08-20 18:52         ` Josh Boyer
2008-08-20 19:06           ` Hollis Blanchard
2008-08-20 19:18             ` Josh Boyer
2008-08-21 13:31               ` Christian Ehrhardt
2008-08-21 13:41   ` Kumar Gala
2008-08-21 14:13     ` Christian Ehrhardt
2008-08-21 14:21       ` Kumar Gala
2008-08-21 16:16         ` Scott Wood
2008-08-22  8:08           ` Christian Ehrhardt
2008-08-22  8:17             ` Kumar Gala
2008-08-22 13:56               ` Jimi Xenidis
2008-08-22 15:49                 ` Scott Wood

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=200808220900.50611.hollisb@us.ibm.com \
    --to=hollisb@us.ibm.com \
    --cc=galak@kernel.crashing.org \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=stuart.yoder@freescale.com \
    /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).