Lines Matching refs:we
31 tracking i.e. the SPTE_SPECIAL_MASK is set. That means we need to
35 caused by write-protect. That means we just need to change the W bit of the
38 What we use to avoid all the race is the SPTE_HOST_WRITEABLE bit and
45 On fast page fault path, we will use cmpxchg to atomically set the spte W
50 But we need carefully check these cases:
52 The mapping from gfn to pfn may be changed since we can only ensure the pfn
81 For direct sp, we can easily avoid it since the spte of direct sp is fixed
82 to gfn. For indirect sp, before we do cmpxchg, we call gfn_to_pfn_atomic()
89 Then, we can ensure the dirty bitmaps is correctly set for a gfn.
91 Currently, to simplify the whole things, we disable fast page fault for
133 In order to avoid this kind of issue, we always treat the spte as "volatile"
138 If the spte is updated from writable to readonly, we should flush all TLBs,
143 fast page fault path, in order to easily audit the path, we see if TLBs need
147 Since the spte is "volatile" if it can be updated out of mmu-lock, we always
211 devices, we put the blocked vCPU on the list blocked_vcpu_on_cpu
214 assigned devices happens, we will find the vCPU on the list to