Andrea Arcangeli wrote: > On Tue, Jan 22, 2008 at 04:38:49PM +0200, Avi Kivity wrote: >> Andrea Arcangeli wrote: >>>> This is arch independent code, I'm surprised mmu_lock is visible here? >>>> >>> The mmu_lock is arch independent as far as I can tell. Pretty much >>> like the mm->page_table_lock is also independent. All archs will have >>> some form of shadow pagetables in software or hardware, and mmu_lock >>> is the lock to take to serialize the pagetable updates and it also >>> allows to walk the memslots in readonly mode. >>> >>> >> Well, s390 has everything in hardware, but I suppose they can just ignore >> the lock. > > If they don't take it in their lowlevel it's enough I think. It'll > still be useful to lookup memslots like in every other arch. The lock won't be a performance issue for s390. We don't need to look them up frequently afaics.
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
