David S. Miller <mailto:[EMAIL PROTECTED]> wrote on Friday, March 18, 2005 8:06 PM:
> > Take a look at set_pte_at(). You get the "mm", the > virtual address, the pte pointer, and the new pte value. > Thanks for pointing out the updated interface in 2.6.12-* kernel. I think I can overload the arch specific part of set_pte_at(or for that matter set_pte, as what I need is only pte_t) to always check if we need to do lazy I/D coherency for IA-64.....but this incurs extra cost for making a check every time set_pte_at is called. This new hook, lazy_mmu_prot_update, though needs to be used only when the permissions on a valid PTE is changing. For example, at the time of remap or swap, this API is not called. > What else could you possibly need to track stuff like this > and react appropriately? :-) > Stuff is there, though the call needs to be made to ensure we are reacting to it most optimally and correctly.....I guess something similar to why update_mmu_cache API is still existing in generic part and not overloading arch specific set_pte_at definition. -rohit - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
