linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
To: Tony Breeds <tony@bakeyournoodle.com>
Cc: linuxppc-dev@ozlabs.org, embedded-hypervisor@power.org,
	hollisb@us.ibm.com, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 3/6] kvmppc: add hypercall infrastructure - guest part
Date: Thu, 24 Jul 2008 09:56:39 +0200	[thread overview]
Message-ID: <488835B7.90702@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080724014538.GJ20457@bakeyournoodle.com>

Tony Breeds wrote:
> On Wed, Jul 23, 2008 at 10:36:44AM +0200, ehrhardt@linux.vnet.ibm.com wrote:
>   
>> From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
>>     
>
> Hi Christian,
>   
>> 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 |   16 ++++++++++++++++
>>  1 file changed, 16 insertions(+)
>>
>> [diff]
>> diff --git a/include/asm-powerpc/kvm_para.h b/include/asm-powerpc/kvm_para.h
>> --- a/include/asm-powerpc/kvm_para.h
>> +++ b/include/asm-powerpc/kvm_para.h
>> @@ -25,6 +25,8 @@
>>  #ifdef __KERNEL__
>>  
>>  #include <linux/of.h>
>> +
>> +#define KVM_HYPERCALL_BIN 0x03ffffff
>>     
>
> Ummm didn't you add this in patch 2 of 6?
>   
This is just because I initially wanted to split Host & Guest patch series.
I need to separate my patches a bit more anyway for the next submission 
thanks for pointing out this duplication.

> Yours Tony
>
>   linux.conf.au    http://www.marchsouth.org/
>   Jan 19 - 24 2009 The Australian Linux Technical Conference!
>
>   


-- 

Grüsse / regards, 
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization

  reply	other threads:[~2008-07-24  7:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23  8:36 [PATCH 0/6][RFC] kvmppc: paravirtualization interface ehrhardt
2008-07-23  8:36 ` [PATCH 1/6] kvmppc: read device tree hypervisor node infrastructure ehrhardt
2008-07-24  1:41   ` Tony Breeds
2008-07-24  7:44     ` Christian Ehrhardt
2008-07-23  8:36 ` [PATCH 2/6] kvmppc: add hypercall infrastructure - host part ehrhardt
2008-07-24  1:43   ` Tony Breeds
2008-07-30 13:41     ` Geert Uytterhoeven
2008-07-23  8:36 ` [PATCH 3/6] kvmppc: add hypercall infrastructure - guest part ehrhardt
2008-07-24  1:45   ` Tony Breeds
2008-07-24  7:56     ` Christian Ehrhardt [this message]
2008-07-23  8:36 ` [PATCH 4/6] kvmppc: magic page hypercall - host part ehrhardt
2008-07-24  1:49   ` Tony Breeds
2008-07-23  8:36 ` [PATCH 5/6] kvmppc: magic page paravirtualization - guest part ehrhardt
2008-07-24  1:59   ` Tony Breeds
2008-07-23  8:36 ` [PATCH 6/6] kvmppc: kvm-userspace: device tree modification for magicpage ehrhardt
2008-07-24  2:01 ` [PATCH 0/6][RFC] kvmppc: paravirtualization interface Tony Breeds
2008-07-24  8:17   ` Christian Ehrhardt
2008-07-25  1:08     ` Tony Breeds

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=488835B7.90702@linux.vnet.ibm.com \
    --to=ehrhardt@linux.vnet.ibm.com \
    --cc=embedded-hypervisor@power.org \
    --cc=hollisb@us.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=tony@bakeyournoodle.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).