Date: Mon, 24 Nov 2014 19:57:57 +0100 From: Svatopluk Kraus <onwahe@gmail.com> To: Ian Lepore <ian@freebsd.org> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: Test Run with Alternative pmap Implementation Message-ID: <CAFHCsPUH0JWwJ7uq6FH-%2BgQm-=Yk6o3pXpcaBB4rAPuoK4JUag@mail.gmail.com> In-Reply-To: <1416847163.1147.396.camel@revolution.hippie.lan> References: <20141113125236.b16cd4e5f0e339eac0494cd4@ulrich-grey.de> <C6FED1A5-490C-47BE-B071-484271ED370E@me.com> <20141115143444.5ad037548e06f289d2532fb7@ulrich-grey.de> <CAFHCsPUJ1HhLqAjitPg6mPzhMYSui64Xmu4omO7Pkp%2B0kPZnAA@mail.gmail.com> <20141119225903.81fbbc7809093a0e6e0de9d5@ulrich-grey.de> <CAFHCsPXnSFY_X-O73M%2Bh0xO_XJ0cTmkRwtu-o4omPndnfbEhmg@mail.gmail.com> <20141120151900.a68c6d8316b96a62cb65d17a@ulrich-grey.de> <CAFHCsPWTnU7j0MC7YSHFFDE97%2B%2BBrnkJKGnK9zkxVGemaa6nAw@mail.gmail.com> <20141121115941.54d4e36b103341c3adf7eb36@ulrich-grey.de> <20141124132733.4e96b906f0d1ab69969dddd9@ulrich-grey.de> <1416840814.1147.380.camel@revolution.hippie.lan> <CALF_Tx=S5HjPFLCKb5XQC9XYkpLxERn=s3MtXr0N_UANi79v_g@mail.gmail.com> <1416847163.1147.396.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 24, 2014 at 5:39 PM, Ian Lepore <ian@freebsd.org> wrote: > On Mon, 2014-11-24 at 16:17 +0100, Zbigniew Bodek wrote: > > 2014-11-24 15:53 GMT+01:00 Ian Lepore <ian@freebsd.org>: > > > On Mon, 2014-11-24 at 13:27 +0100, Ulrich Grey wrote: > > >> Hello, > > >> > > >> as a starting point I have build an image (crochet, wandboard-quad) > with > > >> the source tree from here (751adfd(master)): > > >> > > >> https://github.com/strejda/freebsd > > >> > > >> Then I build the kernel with new pmap and rebuild the whole systen. > > >> The system I used for the test run is entirely build on the > > >> wandboard-quad. > > >> [...] > > > > > > I've also been testing those pmap changes this weekend. The only > change > > > I made was to add options ARM_NEW_PMAP and NKPT2PG=64 to the kernel > > > config. In particular, I did not change VM_MEMATTR_UNCACHEABLE (so > that > > > in effect I'm also testing the recent busdma changes). > > > > > > I've had two wandboard quads doing builds continuously all weekend. I > > > did the builds that have previously been reported as problems here -- > > > buildworld -j10, ports libX11, plus a lot of other ports including much > > > of the full xorg (until it ran into some x86 device drivers and died), > > > some of libreoffice (it had a problem that wasn't related to crashing > or > > > anything), python, bash, emacs, boost, rsync. > > > > > > After all that I just set both boards to continuously doing "rm > > > -rf /usr/obj/* ; make -j5 buildworld" in a loop, and they're still > > > running. One is using an SSD drive and the other is using NFS. > > > > > > In all that building all weekend the only glitches I've seen are this: > > > > > > warning: pmap_remove_pages called with non-current pmap > > > > > > that appeared twice on the board using NFS root. > > > > > > For anyone else wanting to test, there is currently one conflict when > > > applying the patches, in busdma_machdep-v6.c, because some of the > > > changes in the patch have already been applied. Just resolve the > > > conflict by skipping that file / restoring the original unpatched file. > > > > > > This stuff is looking really good. It wouldn't hurt at all if some > more > > > people were testing it, especially on other hardware including rpi and > > > beaglebone. > > > > > > > Hello, > > > > This new pmap implementation looks VERY good indeed. > > However I was not able to boot this kernel on Armada XP and currently > > I don't have time to debug this. > > On the other hand after e-mails with crash reports on Wandbord I did > > similar (buildworld, port build) tests on AXP and it didn't crash. > > In particular it survived 2 days of buildworld in loop. > > I wonder, what is the functional difference between AXP and other that > > prevents those crashes. > > > > Ian, are you planning to replace the pmap with the new implementation? > > > > Eventually (and soon I hope), yes it will be committed, but not before > we've tested it on all the platforms we support (or at least all the > ones we can get someone to test, we can't wait forever for obscure > hardware nobody has anymore). > > One quick thing that might be worth trying on AXP is the change > mentioned eariler... in arm/include/vm.h, in the line > > #define VM_MEMATTR_UNCACHEABLE VM_MEMATTR_NOCACHE > > Replace VM_MEMATTR_NOCACHE with VM_MEMATTR_SO; that will cover up a lot > of bugs in old drivers. > > -- Ian > > > Michal has updated git repository. As we are tracking current freebsd tree, we use rebase. This way git pull command does not work and after any update git clone command must be used again. We are sorry for that. We changed default value for NKPT2PG option. Hopefully, it covers needs of all freebsd supported armv6 platforms with RAM up to 2GB for testing purposes. Anyhow, it is an option to be set invidually for each platform. Next, two small fixes was done. The one of them could be critical for system startup. The other was exposed by Ulrich Grey testing. We leave memory attributes for DMA buffer untouched. So, if anything does not work, first try to change this attributes how was already described in this thread. Svata
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFHCsPUH0JWwJ7uq6FH-%2BgQm-=Yk6o3pXpcaBB4rAPuoK4JUag>