From: William Cohen <wcohen@redhat.com>
To: systemtap@sourceware.org
Cc: William Cohen <wcohen@redhat.com>
Subject: [PATCH 2/4] Adjust comment in tapset/errno.stp so the documentation can be built.
Date: Fri, 21 Sep 2018 14:56:00 -0000 [thread overview]
Message-ID: <20180921145607.5484-3-wcohen@redhat.com> (raw)
In-Reply-To: <20180921145607.5484-1-wcohen@redhat.com>
---
tapset/errno.stp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tapset/errno.stp b/tapset/errno.stp
index affa33c4f..a75e3bac2 100644
--- a/tapset/errno.stp
+++ b/tapset/errno.stp
@@ -415,6 +415,8 @@ function set_returnval(val:long) %{
%) /* compatible <= 4.0 */
+/* NB: The following function is not STABLE because it depends on varying
+ state in the context. */
/**
* sfunction returnval - Possible return value of probed function
*
@@ -423,8 +425,6 @@ function set_returnval(val:long) %{
* available. This is only a guess of the actual return value and can be
* totally wrong. Normally only used in dwarfless probes.
*/
-/* NB: this function is not STABLE because it depends on varying
- state in the context. */
function returnval:long () %{ /* pure */
struct pt_regs *regs;
#if STAP_COMPAT_VERSION <= STAP_VERSION(4,0)
--
2.17.1
prev parent reply other threads:[~2018-09-21 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 14:56 [PATCH 0/4] syscall_any tapset to improve performance William Cohen
2018-09-21 14:56 ` [PATCH 4/4] Convert the various systemtap examples to use the syscall any tapset William Cohen
2018-09-21 14:56 ` [PATCH 1/4] Use sys_enter and sys_exit tracepoints in place of syscall.*{.return} William Cohen
2018-09-21 14:56 ` [PATCH 3/4] Add the syscall_any and syscall_any.return probe points William Cohen
2018-09-21 14:56 ` William Cohen [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=20180921145607.5484-3-wcohen@redhat.com \
--to=wcohen@redhat.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).