From: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Martin Schwidefsky
<schwidefsky-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>,
linux-s390-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
QingFeng Hao
<haoqf-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
Jan Glauber
<jang-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
Alexey Ishchuk
<aishchuk-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Subject: [man-pages PATCH 1/5] s390_runtime_instr.2: note that runtime_instr.h is not a public header
Date: Sun, 14 Jan 2018 19:56:22 +0100 [thread overview]
Message-ID: <20180114185622.GA23506@asgard.redhat.com> (raw)
For some reason, runtime_instr.h is inside arch/s390/include/asm/ and
not arch/s390/include/uapi/asm/, so it's not readily available to the
user space programs. Let's reflect it.
* man2/s390_runtime_instr.2 (.SH SYNOPSYS): Comment out the #include
<asm/runtime_instr.h> statement.
(.SH NOTES): Note the existence and presence of runtime_instr.h header
inside the Linux kernel source tree.
---
man2/s390_runtime_instr.2 | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/man2/s390_runtime_instr.2 b/man2/s390_runtime_instr.2
index 18c2c07..f979692 100644
--- a/man2/s390_runtime_instr.2
+++ b/man2/s390_runtime_instr.2
@@ -27,8 +27,9 @@
s390_runtime_instr \- enable/disable s390 CPU run-time instrumentation
.SH SYNOPSIS
.nf
-.B #include <asm/runtime_instr.h>
-.PP
+.\" This header never had been a part of uapi as of 4.15
+.\" .B #include <asm/runtime_instr.h>
+.\" .PP
.BI "int s390_runtime_instr(int " command ", int " signum ");
.fi
.SH DESCRIPTION
@@ -85,6 +86,12 @@ The run-time instrumentation facility is available beginning with System z EC12.
Glibc does not provide a wrapper for this system call, use
.BR syscall (2)
to call it.
+.PP
+Kernel's header
+.B arch/s390/include/asm/runtime_instr.h
+contains the necessary declarations for using run-time instrumentation.
+Unfortunately, it hasn't been included as a part of Linux's UAPI
+as of Linux 4.15.
.SH SEE ALSO
.BR syscall (2),
.BR signal (7)
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-01-14 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 18:56 Eugene Syromyatnikov [this message]
[not found] ` <20180114185622.GA23506-ZbobWygYI+YXGNroddHbYwC/G2K4zDHf@public.gmane.org>
2018-01-20 11:28 ` [man-pages PATCH 1/5] s390_runtime_instr.2: note that runtime_instr.h is not a public header Heiko Carstens
2018-01-22 13:11 ` Eugene Syromyatnikov
[not found] ` <CACGkJduJ2SyWVZ7b-obLC_sB5TwHRfdpdfY5qDGrpzGgTC-H+A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-22 15:11 ` Heiko Carstens
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=20180114185622.GA23506@asgard.redhat.com \
--to=evgsyr-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=aishchuk-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=haoqf-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=jang-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-s390-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=schwidefsky-tA70FqPdS9bQT0dZR+AlfA@public.gmane.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 NNTP newsgroup(s).