Lines Matching refs:we
34 tracking i.e. the SPTE_SPECIAL_MASK is set. That means we need to
38 caused by write-protect. That means we just need to change the W bit of
41 What we use to avoid all the race is the SPTE_HOST_WRITEABLE bit and
49 On fast page fault path, we will use cmpxchg to atomically set the spte W
54 But we need carefully check these cases:
58 The mapping from gfn to pfn may be changed since we can only ensure the pfn
98 For direct sp, we can easily avoid it since the spte of direct sp is fixed
99 to gfn. For indirect sp, we disabled fast page fault for simplicity.
109 Then, we can ensure the dirty bitmaps is correctly set for a gfn.
159 In order to avoid this kind of issue, we always treat the spte as "volatile"
165 If the spte is updated from writable to readonly, we should flush all TLBs,
170 fast page fault path, in order to easily audit the path, we see if TLBs need
174 Since the spte is "volatile" if it can be updated out of mmu-lock, we always
238 devices, we put the blocked vCPU on the list blocked_vcpu_on_cpu
241 assigned devices happens, we will find the vCPU on the list to