public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001253] New: Kernel tests on small memory targets Date: Tue, 31 May 2011 13:53:00 -0000 [thread overview] Message-ID: <bug-1001253-13@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001253 Summary: Kernel tests on small memory targets Product: eCos Version: CVS Platform: All OS/Version: All Status: UNCONFIRMED Severity: enhancement Priority: low Component: Other AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: ilijak@siva.com.mk CC: ecos-bugs@ecos.sourceware.org Class: Advice Request Created an attachment (id=1269) --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1269) tm_basic.cxx Some kernel tests have execution or compilation problems when applied on targets with small RAM (example 32Kib LPC-1766-STK). Submitted patches provide for application of these tests on devices with 32 KiB RAM. They have been tested on LPC-1766-STK with kernel template. Dependent on behavior and proposed solution (patch) I have sorted the problems in 3 groups: 1. tm_basic behaviour: Compiles, but hangs during execution. cause: dependent on system RAM amount, array is defined for NTEST_THREADS threads. If RAM is small enough (such as 32KiB) this can be 1 which is in conflict with some tests that employ 2 threads. proposal: At least 2 thread members are enforced. Compiles and executes complete test on target with 32KiB. For lower memory devices ld should report error. 2. bin_sem2.cxx kmutex4 timeslice2 mutex3 timeslice kmutex3 thread_gdb behavior: ld complains for not enough memory. proposal: Dependent on system RAM tests are generated with less threads. For "large" systems number of threads remains as before. 2. fptests behavior: Linker complains for not enough memory. proposal (workaround): In order to enable error free compilation of kernel tests this program is modified so it is compiled wihout threads. On execution a message is printed: "This platform doesn't have enough RAM to run fptest.". -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2011-05-31 13:53 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-31 13:53 bugzilla-daemon [this message] 2011-05-31 13:54 ` [Bug 1001253] " bugzilla-daemon 2011-05-31 13:55 ` bugzilla-daemon 2011-05-31 13:55 ` bugzilla-daemon 2011-05-31 13:56 ` bugzilla-daemon 2011-05-31 13:57 ` bugzilla-daemon 2011-05-31 13:58 ` bugzilla-daemon 2011-05-31 13:59 ` bugzilla-daemon 2011-05-31 14:01 ` bugzilla-daemon 2011-06-02 19:06 ` bugzilla-daemon 2011-07-02 9:14 ` bugzilla-daemon 2011-07-02 21:32 ` bugzilla-daemon 2011-07-03 7:47 ` bugzilla-daemon 2011-07-03 15:10 ` bugzilla-daemon 2011-07-04 10:11 ` bugzilla-daemon 2011-07-04 19:57 ` bugzilla-daemon 2011-07-05 8:15 ` bugzilla-daemon 2011-07-05 10:01 ` bugzilla-daemon 2011-07-05 10:16 ` bugzilla-daemon 2011-07-05 10:52 ` bugzilla-daemon 2011-07-05 14:44 ` bugzilla-daemon 2011-07-05 15:09 ` bugzilla-daemon 2011-07-05 16:10 ` bugzilla-daemon 2011-07-05 17:25 ` bugzilla-daemon 2011-07-06 8:28 ` bugzilla-daemon 2011-07-06 9:07 ` bugzilla-daemon 2011-07-06 12:01 ` bugzilla-daemon 2011-07-06 14:30 ` bugzilla-daemon 2011-07-06 19:00 ` bugzilla-daemon 2011-07-06 19:30 ` bugzilla-daemon 2011-07-09 17:02 ` bugzilla-daemon 2011-07-09 17:15 ` bugzilla-daemon 2011-07-09 17:17 ` bugzilla-daemon 2011-07-09 17:18 ` bugzilla-daemon 2011-07-09 17:20 ` bugzilla-daemon 2011-07-09 17:20 ` bugzilla-daemon 2011-07-09 17:21 ` bugzilla-daemon 2011-07-09 17:25 ` bugzilla-daemon 2011-07-09 19:09 ` bugzilla-daemon 2011-07-10 16:14 ` bugzilla-daemon 2011-07-10 18:12 ` bugzilla-daemon 2011-08-25 8:27 ` bugzilla-daemon 2011-05-31 13:53 [Bug 1001253] New: " bugzilla-daemon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-1001253-13@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-bugs@ecos.sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).