From: "mysecondaccountabc at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/22847] ARM OABI syscall tracing issues
Date: Tue, 20 Feb 2018 01:05:00 -0000 [thread overview]
Message-ID: <bug-22847-6586-8NpdEdaNb4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22847-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22847
--- Comment #11 from Gustavo Moreira <mysecondaccountabc at gmail dot com> ---
(In reply to David Smith from comment #10)
> (In reply to Gustavo Moreira from comment #9)
>
> > > With that patch added, does the following return the correct value?
> > >
> > > # stap -ve 'kernel.function("sys_socketcall").call { printf("%s - %d\n",
> > > ppfunc(), _stp_syscall_nr()) }' -c test_program
> >
> > I've added "probe" at the beginning and changed the syscall to "sys_connect"
> > because it doesn't use sys_socketcall.
>
> Sorry, I misremembered how your kernel worked.
>
> > # stap -ve 'probe kernel.function("sys_connect").call { printf("%s - %d\n",
> > ppfunc(), _stp_syscall_nr()) }' -c ./ex_socket_OABI
> > Pass 1: parsed user script and 452 library scripts using
> > 40896virt/33624res/4948shr/28920data kb, in 4780usr/1090sys/5869real ms.
> > Pass 2: analyzed script: 1 probe, 2 functions, 97 embeds, 0 globals using
> > 77520virt/70912res/5528shr/65544data kb, in 13480usr/11970sys/25472real ms.
> > Pass 3: translated to C into
> > "/tmp/stapSl5Rx9/stap_195c43dcde9908a38abbe97ece0f593b_53976_src.c" using
> > 77520virt/71040res/5656shr/65544data kb, in 1670usr/10930sys/12604real ms.
> > Pass 4: compiled C into "stap_195c43dcde9908a38abbe97ece0f593b_53976.ko" in
> > 58570usr/20570sys/73572real ms.
> > Pass 5: starting run.
> > SyS_connect - 32916
> > Connected
> > Pass 5: run completed in 370usr/1000sys/2316real ms.
> >
> > However, the result seems to be the same. I've patched the file in the
> > installation directory (/usr/share/systemtap/runtime/syscall.h). I don't
> > think SystemTap needs to be completely recompiled again, right? The change
> > should be included when it compiles the LKM in the above stap execution.
>
> Right. Hmm.
>
> I wonder if we've got to handle both ABIs at once (more like a 32-bit ia32
> executable on a x86_64 kernel). Is CONFIG_OABI_COMPAT defined in your config
> file?
exactly, CONFIG_OABI_COMPAT=y. I think so, because when that is enabled the
kernel is able to execute both sort of ABI binaries.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-02-20 1:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-22847-6586@http.sourceware.org/bugzilla/>
2018-02-15 6:01 ` mysecondaccountabc at gmail dot com
2018-02-15 6:09 ` mysecondaccountabc at gmail dot com
2018-02-15 15:45 ` dsmith at redhat dot com
2018-02-15 16:08 ` dsmith at redhat dot com
2018-02-16 4:06 ` mysecondaccountabc at gmail dot com
2018-02-19 6:55 ` mysecondaccountabc at gmail dot com
2018-02-19 7:02 ` mysecondaccountabc at gmail dot com
2018-02-19 14:31 ` dsmith at redhat dot com
2018-02-19 22:42 ` mysecondaccountabc at gmail dot com
2018-02-19 22:53 ` dsmith at redhat dot com
2018-02-20 1:05 ` mysecondaccountabc at gmail dot com [this message]
2018-02-20 16:03 ` dsmith at redhat dot com
2018-02-22 0:04 ` gmoreira at gmail dot com
2018-02-22 16:58 ` dsmith at redhat dot com
2018-04-18 6:50 ` gmoreira at gmail dot com
2018-04-18 6:52 ` gmoreira at gmail dot com
2018-04-18 7:05 ` gmoreira at gmail dot com
2018-04-18 7:26 ` gmoreira at gmail dot com
2018-04-30 17:16 ` dsmith at redhat dot com
2018-05-01 2:46 ` gmoreira at gmail dot com
2018-05-01 15:11 ` dsmith at redhat dot com
2023-10-06 15:55 ` wcohen at redhat dot com
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-22847-6586-8NpdEdaNb4@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).