public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] KVM: trivial document fixes
@ 2009-12-24  1:04 Wu Fengguang
  2009-12-24 14:23 ` Marcelo Tosatti
  0 siblings, 1 reply; 2+ messages in thread
From: Wu Fengguang @ 2009-12-24  1:04 UTC (permalink / raw)
  To: Avi Kivity, Marcelo Tosatti; +Cc: kvm

Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
---
 Documentation/kvm/api.txt |   12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

--- linux.orig/Documentation/kvm/api.txt	2009-12-12 09:54:19.000000000 +0800
+++ linux/Documentation/kvm/api.txt	2009-12-12 10:48:02.000000000 +0800
@@ -23,12 +23,12 @@ of a virtual machine.  The ioctls belong
    Only run vcpu ioctls from the same thread that was used to create the
    vcpu.
 
-2. File descritpors
+2. File descriptors
 
 The kvm API is centered around file descriptors.  An initial
 open("/dev/kvm") obtains a handle to the kvm subsystem; this handle
 can be used to issue system ioctls.  A KVM_CREATE_VM ioctl on this
-handle will create a VM file descripror which can be used to issue VM
+handle will create a VM file descriptor which can be used to issue VM
 ioctls.  A KVM_CREATE_VCPU ioctl on a VM fd will create a virtual cpu
 and return a file descriptor pointing to it.  Finally, ioctls on a vcpu
 fd can be used to control the vcpu, including the important task of
@@ -643,7 +643,7 @@ Type: vm ioctl
 Parameters: struct kvm_clock_data (in)
 Returns: 0 on success, -1 on error
 
-Sets the current timestamp of kvmclock to the valued specific in its parameter.
+Sets the current timestamp of kvmclock to the value specified in its parameter.
 In conjunction with KVM_GET_CLOCK, it is used to ensure monotonicity on scenarios
 such as migration.
 
@@ -787,11 +787,11 @@ Unused.
 			__u64 data_offset; /* relative to kvm_run start */
 		} io;
 
-If exit_reason is KVM_EXIT_IO_IN or KVM_EXIT_IO_OUT, then the vcpu has
+If exit_reason is KVM_EXIT_IO, then the vcpu has
 executed a port I/O instruction which could not be satisfied by kvm.
 data_offset describes where the data is located (KVM_EXIT_IO_OUT) or
 where kvm expects application code to place the data for the next
-KVM_RUN invocation (KVM_EXIT_IO_IN).  Data format is a patcked array.
+KVM_RUN invocation (KVM_EXIT_IO_IN).  Data format is a packed array.
 
 		struct {
 			struct kvm_debug_exit_arch arch;
@@ -807,7 +807,7 @@ Unused.
 			__u8  is_write;
 		} mmio;
 
-If exit_reason is KVM_EXIT_MMIO or KVM_EXIT_IO_OUT, then the vcpu has
+If exit_reason is KVM_EXIT_MMIO, then the vcpu has
 executed a memory-mapped I/O instruction which could not be satisfied
 by kvm.  The 'data' member contains the written data if 'is_write' is
 true, and should be filled by application code otherwise.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH] KVM: trivial document fixes
  2009-12-24  1:04 [PATCH] KVM: trivial document fixes Wu Fengguang
@ 2009-12-24 14:23 ` Marcelo Tosatti
  0 siblings, 0 replies; 2+ messages in thread
From: Marcelo Tosatti @ 2009-12-24 14:23 UTC (permalink / raw)
  To: Wu Fengguang; +Cc: Avi Kivity, kvm

On Thu, Dec 24, 2009 at 09:04:16AM +0800, Wu Fengguang wrote:
> Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> ---
>  Documentation/kvm/api.txt |   12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)

Applied, thanks.


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-12-24 15:16 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-12-24  1:04 [PATCH] KVM: trivial document fixes Wu Fengguang
2009-12-24 14:23 ` Marcelo Tosatti

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox