All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
To: Marcelo Tosatti <mtosatti@redhat.com>, Alexander Graf <agraf@suse.de>
Cc: Rob Landley <rob@landley.net>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	Randy Dunlap <rdunlap@xenotime.net>, KVM <kvm@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Gleb Natapov <gleb@redhat.com>,
	Ingo Molnar <mingo@redhat.com>, Avi Kivity <avi@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH] Documentation/kvm : Add documentation on Hypercalls
Date: Thu, 02 Aug 2012 12:38:37 +0530	[thread overview]
Message-ID: <501A2775.90404@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120801182554.GA9464@amt.cnet>

On 08/01/2012 11:55 PM, Marcelo Tosatti wrote:
> On Wed, Aug 01, 2012 at 04:19:01PM +0530, Raghavendra K T wrote:
>> On 08/01/2012 08:37 AM, Marcelo Tosatti wrote:
>>> On Tue, Jul 24, 2012 at 02:23:59PM +0530, Raghavendra K T wrote:
>>>> From: Raghavendra K T<raghavendra.kt@linux.vnet.ibm.com>
>>>>
>>>> Thanks Alex for KVM_HC_FEATURES inputs and Jan for VAPIC_POLL_IRQ,
>>>> and Peter (HPA) for suggesting hypercall ABI addition.
>>>>
>>>> Signed-off-by: Raghavendra K T<raghavendra.kt@linux.vnet.ibm.com>
>>>> ---
[...]
>>>> +
>>>> + Up to four arguments may be passed in rbx, rcx, rdx, and rsi respectively.
>>>> + The hypercall number should be placed in rax and the return value will be
>>>> + placed in rax.  No other registers will be clobbered unless explicitly stated
>>>> + by the particular hypercall.
>>>
>>> It depends on the hypercall. It happens that current hypercalls use
>>> the four registers, but its not an ABI (hyper-v hypercalls uses r8, for example).
>>>
>>
>> Okay, agree. I did not know about hyper-v. Above one is for X86 and
>> KVM  (and not X86 / hyper-v). So I should remove ABI and probably say,
>
> Just say "Linux x86 Hypercall", yeah.
>

Ok, Thanks Marcelo.will respin patches with the changes you suggested.

Also I would  like add Alex's description on ppc hypercalls
into Documentation/virtual/kvm/ppc-pv.txt with Alex from/sob or
suggested-by in a separate patch unless I see any objection to that.


  reply	other threads:[~2012-08-02  7:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24  8:53 [PATCH] Documentation/kvm : Add documentation on Hypercalls Raghavendra K T
2012-07-24 12:13 ` Alexander Graf
2012-07-24 13:14   ` Raghavendra K T
2012-08-01  3:07 ` Marcelo Tosatti
2012-08-01 10:49   ` Raghavendra K T
2012-08-01 18:25     ` Marcelo Tosatti
2012-08-02  7:08       ` Raghavendra K T [this message]
2012-08-02 10:13         ` Alexander Graf
  -- strict thread matches above, loose matches on Subject: below --
2012-05-31  8:01 Raghavendra K T
2012-05-31 17:44 ` Randy Dunlap
2012-05-31 18:55   ` Jan Kiszka
2012-05-31 18:59     ` H. Peter Anvin
2012-06-04  7:29   ` Raghavendra K T
2012-05-31 17:46 ` H. Peter Anvin
2012-06-04  4:00   ` Rob Landley
2012-06-04  8:21     ` Raghavendra K T

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=501A2775.90404@linux.vnet.ibm.com \
    --to=raghavendra.kt@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=hpa@zytor.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=rdunlap@xenotime.net \
    --cc=rob@landley.net \
    /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.