From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <444AED9A.7040009@domain.hid> Date: Sat, 22 Apr 2006 22:59:38 -0400 From: Jim Cromie MIME-Version: 1.0 References: <4447D9CA.9010809@domain.hid> In-Reply-To: <4447D9CA.9010809@domain.hid> Content-Type: multipart/mixed; boundary="------------060904060708040205030407" Subject: [Xenomai-core] Re: xeno-test updates [patch] List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: xenomai-core This is a multi-part message in MIME format. --------------060904060708040205030407 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Jim Cromie wrote: > > > Ive started adding to xeno-test, as outlined previously (plus some) > , except where noted > - now run cyclictest and switch, in addition to latency -t 0,1,2 > cycletest now has decent options passed in. I havent given any thought to exposing options thru xeno-test's command line. Instead, Im thinking of adding statistics, ala latency. for that, Im also pondering a new -g 100 option to group the tests for stats-calcs, ie given: -g 100 -l 1000 -v it would compute statistics on 10 sets of 100 cycles, and report 10 lines. Again, this is notional, comments/feedback needed. > - changed the prewired -m email-addy to xenotest.output@domain.hid email options now work w/o actually writing a file. Also changed default location of file writes to /tmp, they no longer get written to $PWD by default added a -U , completely untested, but mostly lifted from LiveCD This looks necessary, since my hobby-box doesnt have a working mail setup my laptop (and presumably yours) doesnt have a FQDN, which pretty well precludes sending mail to anywhere useful. (Id bet we could span the unwashed winbloze masses, but wheres the sport in that ? ;-) > > - now grep more config-items out of config (for non-verbose mode) > latency-killers, PREEMPT, others ? > added items per RPMs email. Im considering stripping the warning issued when CPU_FREQ ia xonfig'd warning: CONFIG_CPU_FREQ=y may be problematic. I have it in cuz nothing actually changes (can change) it, so its harmless. (I think) Its easier than making the list complete, and the .config dump covers the reporting. > > > Dont apply yet, not tested recently. > Its reasonbly tested; we can shake out some more with some distributed testing (hint - try it !) Heres some tests I ran, files got written.. ./xeno-test -T 30 -l30 -m ./xeno-test -T 30 -l30 ./xeno-test -T 30 -l30 -L ./xeno-test -T 30 -l30 -N foo ./xeno-test -T 30 -l30 -LN bar ./xeno-test -T 30 -l30 -LN buzz -m ./xeno-test -T 5 -l30 -L -m ./xeno-test -T 5 -l30 -N /tmp/box- -m ./xeno-test -T 5 -l30 -N ~/trucklab/ -w2 -W 'dd if=/dev/hda1 of=/dev/null' > Qs > > - should I run boxstatus just after latency tests or b4 and after (as > currently) ? > > - /proc/xenomai/* contents are dynamic (ie run by boxstatus) ? > > - any bits of boxinfo and boxstatus that should be shuffled around ? > > - check NPTL availability (kinda overkill, since its absence when > needed is already detected) > > > - anything else come to mind ? these are still open, but not crtical. I hope thats everything for now, it needs a good shakedown, and I need a beer. --------------060904060708040205030407 Content-Type: text/plain; name="patch-xeno-test" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="patch-xeno-test" Index: scripts/prepare-kernel.sh =================================================================== --- scripts/prepare-kernel.sh (revision 974) +++ scripts/prepare-kernel.sh (working copy) @@ -48,6 +48,7 @@ patch_append() { file="$1" if test "x$output_patch" = "x"; then + chmod +w "$linux_tree/$file" cat >> "$linux_tree/$file" else if test `check_filter $file` = "ok"; then Index: scripts/xeno-test.in =================================================================== --- scripts/xeno-test.in (revision 974) +++ scripts/xeno-test.in (working copy) @@ -12,15 +12,18 @@ -W