diff options
author | Masanari Iida <standby24x7@gmail.com> | 2013-12-21 11:21:23 -0500 |
---|---|---|
committer | Marcelo Tosatti <mtosatti@redhat.com> | 2013-12-31 14:24:54 -0500 |
commit | 171800328f6e2443e0e356de5b41fb7e0fff4448 (patch) | |
tree | a8b3e28495a7786b73bdf705e24edb25ec0059c4 /Documentation/virtual | |
parent | da91747cda0fdbaa05b80becb5cecfac35c8de36 (diff) |
KVM: doc: Fix typo in doc/virtual/kvm
Correct spelling typo in Documentations/virtual/kvm
Signed-off-by: Masanari Iida <standby24x7@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'Documentation/virtual')
-rw-r--r-- | Documentation/virtual/kvm/api.txt | 4 | ||||
-rw-r--r-- | Documentation/virtual/kvm/hypercalls.txt | 2 | ||||
-rw-r--r-- | Documentation/virtual/kvm/locking.txt | 4 | ||||
-rw-r--r-- | Documentation/virtual/kvm/ppc-pv.txt | 2 | ||||
-rw-r--r-- | Documentation/virtual/kvm/timekeeping.txt | 2 |
5 files changed, 7 insertions, 7 deletions
diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt index 867112f1968d..a8cdc7b72281 100644 --- a/Documentation/virtual/kvm/api.txt +++ b/Documentation/virtual/kvm/api.txt | |||
@@ -2104,7 +2104,7 @@ Returns: 0 on success, -1 on error | |||
2104 | Allows setting an eventfd to directly trigger a guest interrupt. | 2104 | Allows setting an eventfd to directly trigger a guest interrupt. |
2105 | kvm_irqfd.fd specifies the file descriptor to use as the eventfd and | 2105 | kvm_irqfd.fd specifies the file descriptor to use as the eventfd and |
2106 | kvm_irqfd.gsi specifies the irqchip pin toggled by this event. When | 2106 | kvm_irqfd.gsi specifies the irqchip pin toggled by this event. When |
2107 | an event is tiggered on the eventfd, an interrupt is injected into | 2107 | an event is triggered on the eventfd, an interrupt is injected into |
2108 | the guest using the specified gsi pin. The irqfd is removed using | 2108 | the guest using the specified gsi pin. The irqfd is removed using |
2109 | the KVM_IRQFD_FLAG_DEASSIGN flag, specifying both kvm_irqfd.fd | 2109 | the KVM_IRQFD_FLAG_DEASSIGN flag, specifying both kvm_irqfd.fd |
2110 | and kvm_irqfd.gsi. | 2110 | and kvm_irqfd.gsi. |
@@ -2115,7 +2115,7 @@ interrupts. When KVM_IRQFD_FLAG_RESAMPLE is set the user must pass an | |||
2115 | additional eventfd in the kvm_irqfd.resamplefd field. When operating | 2115 | additional eventfd in the kvm_irqfd.resamplefd field. When operating |
2116 | in resample mode, posting of an interrupt through kvm_irq.fd asserts | 2116 | in resample mode, posting of an interrupt through kvm_irq.fd asserts |
2117 | the specified gsi in the irqchip. When the irqchip is resampled, such | 2117 | the specified gsi in the irqchip. When the irqchip is resampled, such |
2118 | as from an EOI, the gsi is de-asserted and the user is notifed via | 2118 | as from an EOI, the gsi is de-asserted and the user is notified via |
2119 | kvm_irqfd.resamplefd. It is the user's responsibility to re-queue | 2119 | kvm_irqfd.resamplefd. It is the user's responsibility to re-queue |
2120 | the interrupt if the device making use of it still requires service. | 2120 | the interrupt if the device making use of it still requires service. |
2121 | Note that closing the resamplefd is not sufficient to disable the | 2121 | Note that closing the resamplefd is not sufficient to disable the |
diff --git a/Documentation/virtual/kvm/hypercalls.txt b/Documentation/virtual/kvm/hypercalls.txt index d922d73efa7b..c8d040e27046 100644 --- a/Documentation/virtual/kvm/hypercalls.txt +++ b/Documentation/virtual/kvm/hypercalls.txt | |||
@@ -77,7 +77,7 @@ Usage example : A vcpu of a paravirtualized guest that is busywaiting in guest | |||
77 | kernel mode for an event to occur (ex: a spinlock to become available) can | 77 | kernel mode for an event to occur (ex: a spinlock to become available) can |
78 | execute HLT instruction once it has busy-waited for more than a threshold | 78 | execute HLT instruction once it has busy-waited for more than a threshold |
79 | time-interval. Execution of HLT instruction would cause the hypervisor to put | 79 | time-interval. Execution of HLT instruction would cause the hypervisor to put |
80 | the vcpu to sleep until occurence of an appropriate event. Another vcpu of the | 80 | the vcpu to sleep until occurrence of an appropriate event. Another vcpu of the |
81 | same guest can wakeup the sleeping vcpu by issuing KVM_HC_KICK_CPU hypercall, | 81 | same guest can wakeup the sleeping vcpu by issuing KVM_HC_KICK_CPU hypercall, |
82 | specifying APIC ID (a1) of the vcpu to be woken up. An additional argument (a0) | 82 | specifying APIC ID (a1) of the vcpu to be woken up. An additional argument (a0) |
83 | is used in the hypercall for future use. | 83 | is used in the hypercall for future use. |
diff --git a/Documentation/virtual/kvm/locking.txt b/Documentation/virtual/kvm/locking.txt index f8869410d40c..d68af4dc3006 100644 --- a/Documentation/virtual/kvm/locking.txt +++ b/Documentation/virtual/kvm/locking.txt | |||
@@ -112,7 +112,7 @@ The Dirty bit is lost in this case. | |||
112 | 112 | ||
113 | In order to avoid this kind of issue, we always treat the spte as "volatile" | 113 | In order to avoid this kind of issue, we always treat the spte as "volatile" |
114 | if it can be updated out of mmu-lock, see spte_has_volatile_bits(), it means, | 114 | if it can be updated out of mmu-lock, see spte_has_volatile_bits(), it means, |
115 | the spte is always atomicly updated in this case. | 115 | the spte is always atomically updated in this case. |
116 | 116 | ||
117 | 3): flush tlbs due to spte updated | 117 | 3): flush tlbs due to spte updated |
118 | If the spte is updated from writable to readonly, we should flush all TLBs, | 118 | If the spte is updated from writable to readonly, we should flush all TLBs, |
@@ -125,7 +125,7 @@ be flushed caused by this reason in mmu_spte_update() since this is a common | |||
125 | function to update spte (present -> present). | 125 | function to update spte (present -> present). |
126 | 126 | ||
127 | Since the spte is "volatile" if it can be updated out of mmu-lock, we always | 127 | Since the spte is "volatile" if it can be updated out of mmu-lock, we always |
128 | atomicly update the spte, the race caused by fast page fault can be avoided, | 128 | atomically update the spte, the race caused by fast page fault can be avoided, |
129 | See the comments in spte_has_volatile_bits() and mmu_spte_update(). | 129 | See the comments in spte_has_volatile_bits() and mmu_spte_update(). |
130 | 130 | ||
131 | 3. Reference | 131 | 3. Reference |
diff --git a/Documentation/virtual/kvm/ppc-pv.txt b/Documentation/virtual/kvm/ppc-pv.txt index 4cd076febb02..4643cde517c4 100644 --- a/Documentation/virtual/kvm/ppc-pv.txt +++ b/Documentation/virtual/kvm/ppc-pv.txt | |||
@@ -115,7 +115,7 @@ If any other bit changes in the MSR, please still use mtmsr(d). | |||
115 | Patched instructions | 115 | Patched instructions |
116 | ==================== | 116 | ==================== |
117 | 117 | ||
118 | The "ld" and "std" instructions are transormed to "lwz" and "stw" instructions | 118 | The "ld" and "std" instructions are transformed to "lwz" and "stw" instructions |
119 | respectively on 32 bit systems with an added offset of 4 to accommodate for big | 119 | respectively on 32 bit systems with an added offset of 4 to accommodate for big |
120 | endianness. | 120 | endianness. |
121 | 121 | ||
diff --git a/Documentation/virtual/kvm/timekeeping.txt b/Documentation/virtual/kvm/timekeeping.txt index df8946377cb6..76808a17ad84 100644 --- a/Documentation/virtual/kvm/timekeeping.txt +++ b/Documentation/virtual/kvm/timekeeping.txt | |||
@@ -467,7 +467,7 @@ at any time. This causes problems as the passage of real time, the injection | |||
467 | of machine interrupts and the associated clock sources are no longer completely | 467 | of machine interrupts and the associated clock sources are no longer completely |
468 | synchronized with real time. | 468 | synchronized with real time. |
469 | 469 | ||
470 | This same problem can occur on native harware to a degree, as SMM mode may | 470 | This same problem can occur on native hardware to a degree, as SMM mode may |
471 | steal cycles from the naturally on X86 systems when SMM mode is used by the | 471 | steal cycles from the naturally on X86 systems when SMM mode is used by the |
472 | BIOS, but not in such an extreme fashion. However, the fact that SMM mode may | 472 | BIOS, but not in such an extreme fashion. However, the fact that SMM mode may |
473 | cause similar problems to virtualization makes it a good justification for | 473 | cause similar problems to virtualization makes it a good justification for |