public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
Cc: mingo@redhat.com, hpa@zytor.com, x86@kernel.org, gleb@redhat.com,
	pbonzini@redhat.com, jeremy@goop.org, konrad.wilk@oracle.com,
	peterz@infradead.org, tglx@linutronix.de, agraf@suse.de,
	digitaleric@google.com, riel@redhat.com, avi.kivity@gmail.com,
	habanero@linux.vnet.ibm.com, chegu_vinod@hp.com,
	ouyang@cs.pitt.edu, drjones@redhat.com,
	linux-doc@vger.kernel.org, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	andi@firstfloor.org, virtualization@lists.linux-foundation.org,
	mtosatti@redhat.com, srivatsa.vaddagiri@gmail.com,
	Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
	Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
Subject: Re: [PATCH V13 4/4] Documentation/kvm : Add documentation on Hypercalls and features used for PV spinlock
Date: Wed, 28 Aug 2013 13:01:42 -0500	[thread overview]
Message-ID: <1377712902.2737.137@driftwood> (raw)
In-Reply-To: <1377506916-26946-5-git-send-email-raghavendra.kt@linux.vnet.ibm.com> (from raghavendra.kt@linux.vnet.ibm.com on Mon Aug 26 03:48:36 2013)

On 08/26/2013 03:48:36 AM, Raghavendra K T wrote:
> KVM_HC_KICK_CPU  hypercall added to wakeup halted vcpu in paravirtual  
> spinlock
> enabled guest.
> 
> KVM_FEATURE_PV_UNHALT enables guest to check whether pv spinlock can  
> be enabled
> in guest.
> 
> Thanks Vatsa for rewriting KVM_HC_KICK_CPU
> Cc: Rob Landley <rob@landley.net>

Looks like documentation to me:

Acked-by: Rob Landley <rob@landley.net>

Rob

  reply	other threads:[~2013-08-28 18:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26  8:48 [PATCH V13 0/4] Paravirtualized ticket spinlocks for KVM host Raghavendra K T
2013-08-26  8:48 ` [PATCH V13 1/4] kvm uapi: Add KICK_CPU and PV_UNHALT definition to uapi Raghavendra K T
2013-08-26  8:48 ` [PATCH V13 2/4] kvm hypervisor : Add a hypercall to KVM hypervisor to support pv-ticketlocks Raghavendra K T
2013-08-26  8:48 ` [PATCH V13 3/4] kvm hypervisor: Simplify kvm_for_each_vcpu with kvm_irq_delivery_to_apic Raghavendra K T
2013-08-26  8:48 ` [PATCH V13 4/4] Documentation/kvm : Add documentation on Hypercalls and features used for PV spinlock Raghavendra K T
2013-08-28 18:01   ` Rob Landley [this message]
2013-08-26 10:04 ` [PATCH V13 0/4] Paravirtualized ticket spinlocks for KVM host Gleb Natapov
2013-08-26 10:28   ` 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=1377712902.2737.137@driftwood \
    --to=rob@landley.net \
    --cc=agraf@suse.de \
    --cc=andi@firstfloor.org \
    --cc=avi.kivity@gmail.com \
    --cc=chegu_vinod@hp.com \
    --cc=digitaleric@google.com \
    --cc=drjones@redhat.com \
    --cc=gleb@redhat.com \
    --cc=habanero@linux.vnet.ibm.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.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=ouyang@cs.pitt.edu \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=raghavendra.kt@linux.vnet.ibm.com \
    --cc=riel@redhat.com \
    --cc=srivatsa.vaddagiri@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=vatsa@linux.vnet.ibm.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=x86@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