Date: Fri, 08 Aug 2014 19:36:43 +0200 From: "Ronald Klop" <ronald-lists@klop.ws> To: freebsd-arm@freebsd.org Subject: Re: testing new pmap code Message-ID: <op.xkaa7hi0kndu52@82-171-231-144.ip.telfort.nl> In-Reply-To: <53CFE285.9040101@rice.edu> References: <53CFE285.9040101@rice.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 Jul 2014 18:27:49 +0200, Alan Cox <alc@rice.edu> wrote: > Folks, > > About a week ago I committed some new pmap code on all architectures, > including arm. However, that code isn't "active" until the attached > patch is committed. Before I commit this patch, I'd like to ask people > to test it on arm "classic" and especially v6. (The v6 pmap changes > were more complicated.) > > Here is how to test it. Before you apply the kernel patch, compile and > run the attached program, mlockall2A.c, in a loop. Something like this: > > # while ( 1 ) > while? ./mlockall2A > while? sysctl vm.stats.vm.v_wire_count > while? sleep 7 > while? end > > You should see the wire count steadily increase, because there is a > wired page leak. > > Now, apply the kernel patch, and repeat the same test. This time, the > wire count should stabilize. > > If you're testing on arm v6, substitute > > sysctl vm.stats.vm.v_wire_count vm.pmap.section > > for > > sysctl vm.stats.vm.v_wire_count > > so that I can verify that we're handling superpages correctly. > > Thanks, > Alan > I setup my Sheevaplug (armv5?) with 11-CURRENT. Does this need testing still? I saw that the patch is already committed. And running the test does not crash my machine. The v_wire_count goes up, seems to stabilize and after I stop the loop it goes down again. Ronald.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.xkaa7hi0kndu52>