Displaying 3 results from an estimated 3 matches for "ptep_clear_flush_dirti".
Did you mean:
ptep_clear_flush_dirty
2007 Apr 18
1
[PATCH 6/9] 00mm9 optimize ptep establish for pae.patch
The ptep_establish macro is only used on user-level PTEs, for P->P mapping
changes. Since these always happen under protection of the pagetable lock, the
strong synchronization of a 64-bit cmpxchg is not needed, in fact, not
even a lock prefix needs to be used. We can simply instead clear the P-bit,
followed by a normal set. The write ordering is still important to avoid the
possibility of
2007 Apr 18
0
[PATCH 4/9] 00mm5 combine flush accessed dirty.patch
Remove ptep_test_and_clear_{dirty|young} from i386, and instead use the
dominating functions, ptep_clear_flush_{dirty|young}. This allows the
TLB page flush to be contained in the same macro, and allows for an
eager optimization - if reading the PTE initially returned dirty/accessed,
we can assume the fact that no subsequent update to the PTE which cleared
accessed / dirty has occurred, as the
2006 Mar 14
12
[RFC] VMI for Xen?
I''m sure everyone has seen the drop of VMI patches for Linux at this
point, but just in case, the link is included below.
I''ve read this version of the VMI spec and have made my way through most
of the patches. While I wasn''t really that impressed with the first
spec wrt Xen, the second version seems to be much more palatable.
Specifically, the code inlining and