name it smpmm01
On Tue, Jul 9, 2013 at 11:59 AM, Hesham Moustafa <heshamelmat...@gmail.com> wrote: > > > > On Tue, Jul 9, 2013 at 3:16 AM, Gedare Bloom <ged...@rtems.org> wrote: >> >> I suggest we move mmtest3 into smptests. The mmtests should run on all >> targets, just some targets will only have stubs without functionality. The >> goal in the end is a usable high level api for all targets if it is >> possible. > > Actually I was confused about where is the best place for mmtest3 and I > thought of smptests too. Should I move it with the same name ? >> >> Until we have bsp specific tests it will be hard to construct good generic >> tests. >> >> On Jul 8, 2013 8:07 PM, "Rempel, Cynthia" <cynt6...@vandals.uidaho.edu> >> wrote: >>> >>> Hi Hesham Moustafa, >>> >>> Thanks for adding the .doc s :) >>> >>> Is there a way to conditionally build the mmtests based on whether libmm >>> is being built? >>> >>> My initial thought is something like an AM_CONDITIONAL >>> >>> http://www.gnu.org/software/automake/manual/html_node/Subdirectories-with-AM_005fCONDITIONAL.html >>> Although another way to conditionally build the tests may be better... >>> >>> Ideally if we went that route (and if feasible), if there was a >>> conditional being used for building libmm, we would use the same conditional >>> for the libmm tests... >>> >>> That might make it a little easier to commit these tests incrementally >>> into RTEMS... and thus reduce the number of patches at the end of the summer >>> :) >>> >>> Thanks! >>> Cindy >>> ________________________________________ >>> From: rtems-devel-boun...@rtems.org [rtems-devel-boun...@rtems.org] on >>> behalf of Rempel, Cynthia [cynt6...@vandals.uidaho.edu] >>> Sent: Monday, July 08, 2013 3:55 PM >>> To: Hesham Moustafa; rtems-devel@rtems.org >>> Cc: Gedare Bloom >>> Subject: RE: [GSoC] libmm project status >>> >>> Hi, >>> >>> Thanks for providing the link directly to the testcases! >>> Could you copy the information about each test into: >>> >>> mmtest1/mmtest1.doc >>> Simple tests that tries to install memory management entries >>> >>> mmtest2/mmtest2.doc >>> + Install entries with specific memory attributes (e.g read only region) >>> : >>> + Check for memory protection violations (writing to read only blocks) >>> + Reading from read only blocks. >>> + Write/Read to/from unmapped region (error!). >>> + Write to a valid entry that was installed and then uninstalled >>> (error!). >>> >>> mmtest3/mmtest3.doc >>> + Tests for libmm behavior on SMP environments. >>> + Create tasks for each core and start it. >>> + Check for memory consistency and page tables and memory attributes >>> validity. >>> >>> That way we can quickly identify what each test does in 5 years... Good >>> job with the documentation :) >>> >>> Cindy >>> ________________________________________ >>> From: rtems-devel-boun...@rtems.org [rtems-devel-boun...@rtems.org] on >>> behalf of Hesham Moustafa [heshamelmat...@gmail.com] >>> Sent: Monday, July 08, 2013 3:39 PM >>> To: rtems-devel@rtems.org >>> Cc: Gedare Bloom >>> Subject: [GSoC] libmm project status >>> >>> Hi all, >>> >>> I have posted a new thread to my blog that contains a brief introduction >>> to libmm and latest updates, here is the thread [1] Please take a look. >>> >>> TODO: port libmm for Raspberry PI board on real hardware. >>> >>> Questions : >>> >>> I have created a new test case at libtests called mmtest3 [2] which >>> simulate SMP use case on QEMU/Realview. It simply tries to invoke the same >>> task (which calls libmm function) for each core. There is a fatal error at >>> startup that branches to data exception handler but I am not sure why. >>> Please take a look and tell me if I am doing something wrong with that test >>> case. >>> >>> Other test cases (mmtest1, mmtest2) run successfully on the same >>> platform. >>> >>> [1] >>> http://heshamelmatary.blogspot.com/2013/07/gsoc-2013-libmm-for-rtems.html >>> [2] >>> https://github.com/heshamelmatary/rtems-gsoc2013/tree/low-level-libmm/testsuites/libtests/mmtest3 >>> >>> Regards, >>> Hesham >>> >>> >>> _______________________________________________ >>> rtems-devel mailing list >>> rtems-devel@rtems.org >>> http://www.rtems.org/mailman/listinfo/rtems-devel >>> >>> > _______________________________________________ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
