On Fri, May 31, 2013 at 08:09:17AM +0400, Max Filippov wrote: > Hi Peter, > > On Wed, May 29, 2013 at 9:51 PM, Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > > What about something like this? > > With that patch I still get mtest05 firing my TLB/PTE incoherency check > in the UP PREEMPT_VOLUNTARY configuration. This happens after > zap_pte_range completion in the end of unmap_region because of > rescheduling called in the following call chain: > > unmap_region > free_pgtables > unlink_anon_vmas > lock_anon_vma_root > down_write > might_sleep > might_resched > _cond_resched > Hurm, yeah. Catching all regular blocking primitives and making it maintainable is going to be a problem :/ I suppose the easiest thing is simply killing fast_mode for now/ -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html