public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Turgis, Frederic" <f-turgis@ti.com>
To: "systemtap@sourceware.org" <systemtap@sourceware.org>
Subject: Systemtap testsuite for arm architecture - results
Date: Fri, 01 Apr 2011 07:21:00 -0000	[thread overview]
Message-ID: <13872098A06B02418CF379A158C0F146016100D125@dnce02.ent.ti.com> (raw)

Hi,

Latest ARM "testsuite" report I found was on March 2008. So here is 1 "nono privileged" made on PandaBoard (ARM-A9). Unfortunately, Ubuntu natty includes only systemtap v1.3 that I recently patched with upstream fixes to 2.6.38 (all present or retroffited in systemtap project)

Host: Linux localhost.localdomain 2.6.38-1000-linaro-omap #1-Ubuntu SMP Thu Feb
24 04:55:52 UTC 2011 armv7l armv7l armv7l GNU/Linux
Snapshot: version 1.3/0.148 non-git sources
GCC: 4.5.2 [gcc (Ubuntu/Linaro 4.5.2-2ubuntu3) 4.5.2]
Distro: Linaro N (development branch)

Numbers below are simply an indication, I solved issues in parallel and I didn't keep the first report with more failures:
# of expected passes            488
# of unexpected failures        22
# of unexpected successes       10
# of expected failures          230
# of known failures             3
# of untested testcases         402


FAILURES: unless explicitly stated, they should still be present in latest version (checked source code) and I could make them PASS (eventually by hacking):

* Relevant issues:
- systemtap.examples/general/badname, semok/thirtynine.stp "semantic error: not accessible at this address (0xc0171f34): identifier '$child'
 at :19:28  source:   if (filter(kernel_string($child->d_name->name)))"

"stap -L" confirmed it, it seems I don't have access to parameters of inline functions. I found some bug mentioning issue with GCC < 4.5 but I have GCC4.5.2 I need to dig more into defect database.

- buildok/conversions-guru-embedded.stp:
"invalid lvalue in asm output 1" -> I root caused it to set_kernel_xxx calling __put_user_asm_dword inline assembly. Code looks correct and identical to kernel arch/arm/include/asm/uaccess.h. I will try to find someone in Linaro to inspect more in deep this assembly code.

- sunrpc kernel module: 3 causes
   * Ubuntu still puts debuginfo in /usr/lib/debug. Thanks to  http://sourceware.org/systemtap/wiki/SystemtapOnUbuntu for the script
   * build-id check fails for kernel module probes -> solved by PR10812, commit 71fa1fe39faa153cf6ede620c4855e508059aa39
   * "rpc_new_client" function can be probed as an inline function or not. The "not inline" probe is not ported to kernel > 2.6.18 (so I imagine function is inlined on x86 and not on ARM)

tapset/rpc.stp:
probe _sunrpc.clnt.create_client.rpc_new_client =
        kernel.function("rpc_new_client").call !,
        module("sunrpc").function("rpc_new_client").call
{
        # kernel <= 2.6.18 => no porting to > 2.6.18 unlike inline version


* "Not ported for ARM" issues
- semok/doubleglob.stp, buildok/fortyfive.stp "semantic error: unresolved arity-1 function: identifier 'int_arg' at :834:11^"
Non dwarf probing is not ported for ARM (already raised on mailing list) -> I will have to follow-up with Linaro


* "test configuration" issues
- systemtap.base/dtrace.exp:
if {[installtest_p]} {
    set dtrace $env(SYSTEMTAP_PATH)/dtrace } else {
    set dtrace ../dtrace
}
This selects ../dtrace whereas dtrace is in /usr/bin/dtrace thus obvious failure. Shall I set it or the tool shall set it ?

- systemtap.base/optionalprobe.exp
60s timeout is too small, test executes in 97s ;-)

- systemtap.base/preprocessor.exp
%( arch %) = arm while $arch=uname -i=armv7l. I guess this requires same normalization than ppc64, s390x and i686 at beginning of test

- buildok/eighteen.stp
__audit_getname() seems to depend upon CONFIG_AUDITSYSCALL which is not available for ARM

- buildok/pr10678.stp
ne2k_pci module is not present on such boards so it obviously fails (but next generations will have SATA and PCIe, we are closing the gap ;-) )

- transok/tval-opt.stp
Header "#! /bin/sh" chooses sh over bash but sh does not support "set -o pipefail".
$SHELL=/bin/bash on target. Using "#! /bin/bash" worked.

Regards
Fred

Frederic Turgis
OMAP Platform Business Unit - OMAP System Engineering - Platform Enablement


Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920



             reply	other threads:[~2011-04-01  7:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01  7:21 Turgis, Frederic [this message]
2011-07-19 13:59 ` William Cohen
2011-07-21 21:23 ` William Cohen
2011-07-21 21:42   ` Turgis, Frederic
2011-07-21 22:08     ` William Cohen
2011-07-22 11:12       ` Frank Ch. Eigler

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=13872098A06B02418CF379A158C0F146016100D125@dnce02.ent.ti.com \
    --to=f-turgis@ti.com \
    --cc=systemtap@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: link
Be 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).