From mboxrd@z Thu Jan 1 00:00:00 1970 From: Raghavendra K T Subject: Re: [PATCH RFC V4 5/5] Documentation/kvm : Add documentation on Hypercalls and features used for PV spinlock Date: Mon, 16 Jan 2012 14:14:27 +0530 Message-ID: <4F13E36B.9020408@linux.vnet.ibm.com> References: <20120114182501.8604.68416.sendpatchset@oc5400248562.ibm.com> <20120114182710.8604.22277.sendpatchset@oc5400248562.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Cc: Jeremy Fitzhardinge , linux-doc@vger.kernel.org, Peter Zijlstra , Jan Kiszka , Virtualization , Paul Mackerras , "H. Peter Anvin" , Stefano Stabellini , Xen , Dave Jiang , KVM , Glauber Costa , X86 , Ingo Molnar , Avi Kivity , Rik van Riel , Konrad Rzeszutek Wilk , Srivatsa Vaddagiri , Sasha Levin , Sedat Dilek , Thomas Gleixner , Greg Kroah-Hartman , LKML , Dave Hansen Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org List-Id: kvm.vger.kernel.org On 01/16/2012 08:53 AM, Alexander Graf wrote: > > On 14.01.2012, at 19:27, Raghavendra K T wrote: > >> Add Documentation on CPUID, KVM_CAP_PVLOCK_KICK, and Hypercalls supported. >> >> KVM_HC_KICK_CPU hypercall added to wakeup halted vcpu in >> paravirtual spinlock enabled guest. >> >> KVM_FEATURE_PVLOCK_KICK enables guest to check whether pv spinlock can >> be enabled in guest. support in host is queried via >> ioctl(KVM_CHECK_EXTENSION, KVM_CAP_PVLOCK_KICK) >> >> A minimal Documentation and template is added for hypercalls. >> >> Signed-off-by: Raghavendra K T >> Signed-off-by: Srivatsa Vaddagiri >> --- [...] >> diff --git a/Documentation/virtual/kvm/hypercalls.txt b/Documentation/virtual/kvm/hypercalls.txt >> new file mode 100644 >> index 0000000..7872da5 >> --- /dev/null >> +++ b/Documentation/virtual/kvm/hypercalls.txt >> @@ -0,0 +1,54 @@ >> +KVM Hypercalls Documentation >> +=========================== >> +2. KVM_HC_MMU_OP >> +------------------------ >> +value: 2 >> +Architecture: x86 >> +Purpose: Support MMU operations such as writing to PTE, >> +flushing TLB, release PT. > > This one is deprecated, no? Should probably be mentioned here. Ok, then may be adding state = deprecated/obsolete/in use (active) may be good idea. > >> + >> +3. KVM_HC_FEATURES >> +------------------------ >> +value: 3 >> +Architecture: PPC >> +Purpose: > > Expose hypercall availability to the guest. On x86 you use cpuid to enumerate which hypercalls are available. The natural fit on ppc would be device tree based lookup (which is also what EPAPR dictates), but we also have a second enumeration mechanism that's KVM specific - which is this hypercall. > Thanks, will add this. I hope you are OK if I add Signed-off-by: you. >> + >> +4. KVM_HC_PPC_MAP_MAGIC_PAGE >> +------------------------ >> +value: 4 >> +Architecture: PPC >> +Purpose: To enable communication between the hypervisor and guest there is a >> +new > > It's not new anymore :) > >> shared page that contains parts of supervisor visible register state. >> +The guest can map this shared page using this hypercall. > > ... to access its supervisor register through memory. > Will update accordingly. - Raghu From mboxrd@z Thu Jan 1 00:00:00 1970 From: Raghavendra K T Subject: Re: [PATCH RFC V4 5/5] Documentation/kvm : Add documentation on Hypercalls and features used for PV spinlock Date: Mon, 16 Jan 2012 14:14:27 +0530 Message-ID: <4F13E36B.9020408@linux.vnet.ibm.com> References: <20120114182501.8604.68416.sendpatchset@oc5400248562.ibm.com> <20120114182710.8604.22277.sendpatchset@oc5400248562.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Alexander Graf Cc: Jeremy Fitzhardinge , linux-doc@vger.kernel.org, Peter Zijlstra , Jan Kiszka , Virtualization , Paul Mackerras , "H. Peter Anvin" , Stefano Stabellini , Xen , Dave Jiang , KVM , Glauber Costa , X86 , Ingo Molnar , Avi Kivity , Rik van Riel , Konrad Rzeszutek Wilk , Srivatsa Vaddagiri , Sasha Levin , Sedat Dilek , Thomas Gleixner , Greg Kroah-Hartman , LKML , Dave Hansen List-Id: virtualization@lists.linuxfoundation.org On 01/16/2012 08:53 AM, Alexander Graf wrote: > > On 14.01.2012, at 19:27, Raghavendra K T wrote: > >> Add Documentation on CPUID, KVM_CAP_PVLOCK_KICK, and Hypercalls supported. >> >> KVM_HC_KICK_CPU hypercall added to wakeup halted vcpu in >> paravirtual spinlock enabled guest. >> >> KVM_FEATURE_PVLOCK_KICK enables guest to check whether pv spinlock can >> be enabled in guest. support in host is queried via >> ioctl(KVM_CHECK_EXTENSION, KVM_CAP_PVLOCK_KICK) >> >> A minimal Documentation and template is added for hypercalls. >> >> Signed-off-by: Raghavendra K T >> Signed-off-by: Srivatsa Vaddagiri >> --- [...] >> diff --git a/Documentation/virtual/kvm/hypercalls.txt b/Documentation/virtual/kvm/hypercalls.txt >> new file mode 100644 >> index 0000000..7872da5 >> --- /dev/null >> +++ b/Documentation/virtual/kvm/hypercalls.txt >> @@ -0,0 +1,54 @@ >> +KVM Hypercalls Documentation >> +=========================== >> +2. KVM_HC_MMU_OP >> +------------------------ >> +value: 2 >> +Architecture: x86 >> +Purpose: Support MMU operations such as writing to PTE, >> +flushing TLB, release PT. > > This one is deprecated, no? Should probably be mentioned here. Ok, then may be adding state = deprecated/obsolete/in use (active) may be good idea. > >> + >> +3. KVM_HC_FEATURES >> +------------------------ >> +value: 3 >> +Architecture: PPC >> +Purpose: > > Expose hypercall availability to the guest. On x86 you use cpuid to enumerate which hypercalls are available. The natural fit on ppc would be device tree based lookup (which is also what EPAPR dictates), but we also have a second enumeration mechanism that's KVM specific - which is this hypercall. > Thanks, will add this. I hope you are OK if I add Signed-off-by: you. >> + >> +4. KVM_HC_PPC_MAP_MAGIC_PAGE >> +------------------------ >> +value: 4 >> +Architecture: PPC >> +Purpose: To enable communication between the hypervisor and guest there is a >> +new > > It's not new anymore :) > >> shared page that contains parts of supervisor visible register state. >> +The guest can map this shared page using this hypercall. > > ... to access its supervisor register through memory. > Will update accordingly. - Raghu