<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 9, 2013 at 3:16 AM, Gedare Bloom <span dir="ltr"><<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p>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.</p>
</blockquote><div>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 ? </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>Until we have bsp specific tests it will be hard to construct good generic tests.</p><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On Jul 8, 2013 8:07 PM, "Rempel, Cynthia" <<a href="mailto:cynt6007@vandals.uidaho.edu" target="_blank">cynt6007@vandals.uidaho.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Hesham Moustafa,<br>
<br>
Thanks for adding the .doc s :)<br>
<br>
Is there a way to conditionally build the mmtests based on whether libmm is being built?<br>
<br>
My initial thought is something like an AM_CONDITIONAL<br>
<a href="http://www.gnu.org/software/automake/manual/html_node/Subdirectories-with-AM_005fCONDITIONAL.html" target="_blank">http://www.gnu.org/software/automake/manual/html_node/Subdirectories-with-AM_005fCONDITIONAL.html</a><br>
Although another way to conditionally build the tests may be better...<br>
<br>
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...<br>
<br>
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 :)<br>
<br>
Thanks!<br>
Cindy<br>
________________________________________<br>
From: <a href="mailto:rtems-devel-bounces@rtems.org" target="_blank">rtems-devel-bounces@rtems.org</a> [<a href="mailto:rtems-devel-bounces@rtems.org" target="_blank">rtems-devel-bounces@rtems.org</a>] on behalf of Rempel, Cynthia [<a href="mailto:cynt6007@vandals.uidaho.edu" target="_blank">cynt6007@vandals.uidaho.edu</a>]<br>
Sent: Monday, July 08, 2013 3:55 PM<br>
To: Hesham Moustafa; <a href="mailto:rtems-devel@rtems.org" target="_blank">rtems-devel@rtems.org</a><br>
Cc: Gedare Bloom<br>
Subject: RE: [GSoC] libmm project status<br>
<br>
Hi,<br>
<br>
Thanks for providing the link directly to the testcases!<br>
Could you copy the information about each test into:<br>
<br>
mmtest1/mmtest1.doc<br>
Simple tests that tries to install memory management entries<br>
<br>
mmtest2/mmtest2.doc<br>
+ Install entries with specific memory attributes (e.g read only region) :<br>
+ Check for memory protection violations (writing to read only blocks)<br>
+ Reading from read only blocks.<br>
+ Write/Read to/from unmapped region (error!).<br>
+ Write to a valid entry that was installed and then uninstalled (error!).<br>
<br>
mmtest3/mmtest3.doc<br>
+ Tests for libmm behavior on SMP environments.<br>
+ Create tasks for each core and start it.<br>
+ Check for memory consistency and page tables and memory attributes validity.<br>
<br>
That way we can quickly identify what each test does in 5 years... Good job with the documentation :)<br>
<br>
Cindy<br>
________________________________________<br>
From: <a href="mailto:rtems-devel-bounces@rtems.org" target="_blank">rtems-devel-bounces@rtems.org</a> [<a href="mailto:rtems-devel-bounces@rtems.org" target="_blank">rtems-devel-bounces@rtems.org</a>] on behalf of Hesham Moustafa [<a href="mailto:heshamelmatary@gmail.com" target="_blank">heshamelmatary@gmail.com</a>]<br>
Sent: Monday, July 08, 2013 3:39 PM<br>
To: <a href="mailto:rtems-devel@rtems.org" target="_blank">rtems-devel@rtems.org</a><br>
Cc: Gedare Bloom<br>
Subject: [GSoC] libmm project status<br>
<br>
Hi all,<br>
<br>
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.<br>
<br>
TODO: port libmm for Raspberry PI board on real hardware.<br>
<br>
Questions :<br>
<br>
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.<br>
<br>
Other test cases (mmtest1, mmtest2) run successfully on the same platform.<br>
<br>
[1] <a href="http://heshamelmatary.blogspot.com/2013/07/gsoc-2013-libmm-for-rtems.html" target="_blank">http://heshamelmatary.blogspot.com/2013/07/gsoc-2013-libmm-for-rtems.html</a><br>
[2] <a href="https://github.com/heshamelmatary/rtems-gsoc2013/tree/low-level-libmm/testsuites/libtests/mmtest3" target="_blank">https://github.com/heshamelmatary/rtems-gsoc2013/tree/low-level-libmm/testsuites/libtests/mmtest3</a><br>
<br>
Regards,<br>
Hesham<br>
<br>
<br>
_______________________________________________<br>
rtems-devel mailing list<br>
<a href="mailto:rtems-devel@rtems.org" target="_blank">rtems-devel@rtems.org</a><br>
<a href="http://www.rtems.org/mailman/listinfo/rtems-devel" target="_blank">http://www.rtems.org/mailman/listinfo/rtems-devel</a><br>
<br>
<br>
</blockquote></div>
</div></div></blockquote></div><br></div></div>