From: Josh Stone <jistone@redhat.com>
To: Przemyslaw Pawelczyk <przemyslaw@pawelczyk.it>
Cc: systemtap@sourceware.org
Subject: Re: [PATCH 1/2] Add the .call modifier to syscall entry probes.
Date: Tue, 13 Oct 2009 01:02:00 -0000 [thread overview]
Message-ID: <4AD3D1B7.9060306@redhat.com> (raw)
In-Reply-To: <1255172131.839802.8753@debian>
On 10/10/2009 03:14 AM, Przemyslaw Pawelczyk wrote:
> Inline functions do not have an indentifiable return point and require
> kernel built using VTA-enabled gcc to get tracking of variables. OTOH
> syscall functions are very rarely inlined (depending on the compiler
> mood), therefore filtering probes to include only non-inlined functions
> ensures consistent behavior between different kernels.
>
> This removes the problem of inaccessible variables in inlined syscalls
> that is described in comments #6-9 to PR5890 and gives us the status quo
> w.r.t. syscall probing, because before the commit solving PR10572
> (b7478964) inline instances were masked anyway by non-inline ones.
This is now committed - thanks!
Josh
prev parent reply other threads:[~2009-10-13 1:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 10:56 Przemyslaw Pawelczyk
2009-10-13 1:02 ` Josh Stone [this message]
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=4AD3D1B7.9060306@redhat.com \
--to=jistone@redhat.com \
--cc=przemyslaw@pawelczyk.it \
--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).