On 12/01/2016 17:32, Alex Bennée wrote: >> I need to look at the branch... The latest version I have here does >> not require tb_lock taken in tb_invalidate_phys_range. > > The tb_locks asserts where added in Fred's branch which makes sense as > we are going to mess with the translation block cache. Looking more > closely at tb_invalidate_phys_page_range I see it jumps through some > hoops when cpu == current_cpu == NULL.
Does tb_invalidate_phys_page_range not take tb_lock itself? Paolo
