diff options
Diffstat (limited to 'Documentation/virtual/kvm/locking.txt')
| -rw-r--r-- | Documentation/virtual/kvm/locking.txt | 4 |
1 files changed, 2 insertions, 2 deletions
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 |