search for: pmd_k

...86/mm/fault.c =================================================================== --- linux-2.6.13.orig/arch/i386/mm/fault.c 2005-08-24 09:30:53.000000000 -0700 +++ linux-2.6.13/arch/i386/mm/fault.c 2005-08-24 09:43:27.000000000 -0700 @@ -562,6 +562,15 @@ vmalloc_fault: pte_k = pte_offset_kernel(pmd_k, address); if (!pte_present(*pte_k)) goto no_context; + + /* + * We have just updated this root with a copy of the kernel + * pmd. To return without flushing would introduce a fault + * loop if running on a hypervisor which uses queued page + * table updates. + */ + update_mmu_c...

...86/mm/fault.c =================================================================== --- linux-2.6.13.orig/arch/i386/mm/fault.c 2005-08-24 09:30:53.000000000 -0700 +++ linux-2.6.13/arch/i386/mm/fault.c 2005-08-24 09:43:27.000000000 -0700 @@ -562,6 +562,15 @@ vmalloc_fault: pte_k = pte_offset_kernel(pmd_k, address); if (!pte_present(*pte_k)) goto no_context; + + /* + * We have just updated this root with a copy of the kernel + * pmd. To return without flushing would introduce a fault + * loop if running on a hypervisor which uses queued page + * table updates. + */ + update_mmu_c...

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

...================================================================ --- linux-2.6.16-rc5.orig/arch/i386/mm/fault.c 2006-03-10 12:55:05.000000000 -0800 +++ linux-2.6.16-rc5/arch/i386/mm/fault.c 2006-03-10 15:57:08.000000000 -0800 @@ -552,6 +552,13 @@ vmalloc_fault: goto no_context; set_pmd(pmd, *pmd_k); + /* + * Needed. We have just updated this root with a copy of + * the kernel pmd. To return without flushing would + * introduce a fault loop. + */ + update_mmu_cache(NULL, pmd, pmd_k->pmd); + pte_k = pte_offset_kernel(pmd_k, address); if (!pte_present(*pte_k)) goto no...

...================================================================ --- linux-2.6.16-rc5.orig/arch/i386/mm/fault.c 2006-03-10 12:55:05.000000000 -0800 +++ linux-2.6.16-rc5/arch/i386/mm/fault.c 2006-03-10 15:57:08.000000000 -0800 @@ -552,6 +552,13 @@ vmalloc_fault: goto no_context; set_pmd(pmd, *pmd_k); + /* + * Needed. We have just updated this root with a copy of + * the kernel pmd. To return without flushing would + * introduce a fault loop. + */ + update_mmu_cache(NULL, pmd, pmd_k->pmd); + pte_k = pte_offset_kernel(pmd_k, address); if (!pte_present(*pte_k)) goto no...

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. This series

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. This series

Hi, Here is the version 3 of NOKPORBE_SYMBOL series. Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've introduced NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined

Hi, Here is the version 3 of NOKPORBE_SYMBOL series. Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've introduced NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined