From: Masami Hiramatsu <mhiramat@kernel.org>
To: Beau Belgrave <beaub@linux.microsoft.com>
Cc: rostedt@goodmis.org, linux-trace-devel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 10/12] user_events: Add sample code for typical usage
Date: Thu, 23 Dec 2021 08:18:14 +0900 [thread overview]
Message-ID: <20211223081814.1ca544cdf18e29a93f60c597@kernel.org> (raw)
In-Reply-To: <20211216173511.10390-11-beaub@linux.microsoft.com>
On Thu, 16 Dec 2021 09:35:09 -0800
Beau Belgrave <beaub@linux.microsoft.com> wrote:
> Add sample code for user_events typical usage to show how to register
> and monitor status, as well as to write out data.
Ah, here is the sample code. OK.
Reviewed-by: Masami Hiramatsu <mhiramat@kernel.org>
Thanks!
>
> Signed-off-by: Beau Belgrave <beaub@linux.microsoft.com>
> ---
> samples/user_events/Makefile | 5 ++
> samples/user_events/example.c | 91 +++++++++++++++++++++++++++++++++++
> 2 files changed, 96 insertions(+)
> create mode 100644 samples/user_events/Makefile
> create mode 100644 samples/user_events/example.c
>
> diff --git a/samples/user_events/Makefile b/samples/user_events/Makefile
> new file mode 100644
> index 000000000000..7252b589db57
> --- /dev/null
> +++ b/samples/user_events/Makefile
> @@ -0,0 +1,5 @@
> +# SPDX-License-Identifier: GPL-2.0
> +CFLAGS += -Wl,-no-as-needed -Wall -I../../usr/include
> +
> +example: example.o
> +example.o: example.c
> diff --git a/samples/user_events/example.c b/samples/user_events/example.c
> new file mode 100644
> index 000000000000..4f5778e441c0
> --- /dev/null
> +++ b/samples/user_events/example.c
> @@ -0,0 +1,91 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright (c) 2021, Microsoft Corporation.
> + *
> + * Authors:
> + * Beau Belgrave <beaub@linux.microsoft.com>
> + */
> +
> +#include <errno.h>
> +#include <sys/ioctl.h>
> +#include <sys/mman.h>
> +#include <fcntl.h>
> +#include <stdio.h>
> +#include <unistd.h>
> +#include <linux/user_events.h>
> +
> +/* Assumes debugfs is mounted */
> +const char *data_file = "/sys/kernel/debug/tracing/user_events_data";
> +const char *status_file = "/sys/kernel/debug/tracing/user_events_status";
> +
> +static int event_status(char **status)
> +{
> + int fd = open(status_file, O_RDONLY);
> +
> + *status = mmap(NULL, sysconf(_SC_PAGESIZE), PROT_READ,
> + MAP_SHARED, fd, 0);
> +
> + close(fd);
> +
> + if (*status == MAP_FAILED)
> + return -1;
> +
> + return 0;
> +}
> +
> +static int event_reg(int fd, const char *command, int *status, int *write)
> +{
> + struct user_reg reg = {0};
> +
> + reg.size = sizeof(reg);
> + reg.name_args = (__u64)command;
> +
> + if (ioctl(fd, DIAG_IOCSREG, ®) == -1)
> + return -1;
> +
> + *status = reg.status_index;
> + *write = reg.write_index;
> +
> + return 0;
> +}
> +
> +int main(int argc, char **argv)
> +{
> + int data_fd, status, write;
> + char *status_page;
> + struct iovec io[2];
> + __u32 count = 0;
> +
> + if (event_status(&status_page) == -1)
> + return errno;
> +
> + data_fd = open(data_file, O_RDWR);
> +
> + if (event_reg(data_fd, "test u32 count", &status, &write) == -1)
> + return errno;
> +
> + /* Setup iovec */
> + io[0].iov_base = &write;
> + io[0].iov_len = sizeof(write);
> + io[1].iov_base = &count;
> + io[1].iov_len = sizeof(count);
> +
> +ask:
> + printf("Press enter to check status...\n");
> + getchar();
> +
> + /* Check if anyone is listening */
> + if (status_page[status]) {
> + /* Yep, trace out our data */
> + writev(data_fd, (const struct iovec *)io, 2);
> +
> + /* Increase the count */
> + count++;
> +
> + printf("Something was attached, wrote data\n");
> + }
> +
> + goto ask;
> +
> + return 0;
> +}
> --
> 2.17.1
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2021-12-22 23:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 17:34 [PATCH v8 00/12] user_events: Enable user processes to create and write to trace events Beau Belgrave
2021-12-16 17:35 ` [PATCH v8 01/12] user_events: Add minimal support for trace_event into ftrace Beau Belgrave
2021-12-21 15:16 ` Masami Hiramatsu
2022-01-03 18:22 ` Beau Belgrave
2021-12-16 17:35 ` [PATCH v8 02/12] user_events: Add print_fmt generation support for basic types Beau Belgrave
2021-12-22 0:30 ` Masami Hiramatsu
2022-01-03 18:56 ` Beau Belgrave
2021-12-16 17:35 ` [PATCH v8 03/12] user_events: Handle matching arguments from dyn_events Beau Belgrave
2021-12-22 6:19 ` Masami Hiramatsu
2021-12-16 17:35 ` [PATCH v8 04/12] user_events: Add basic perf and eBPF support Beau Belgrave
2021-12-22 7:55 ` Masami Hiramatsu
2021-12-16 17:35 ` [PATCH v8 05/12] user_events: Add self-test for ftrace integration Beau Belgrave
2021-12-16 17:35 ` [PATCH v8 06/12] user_events: Add self-test for dynamic_events integration Beau Belgrave
2021-12-16 17:35 ` [PATCH v8 07/12] user_events: Add self-test for perf_event integration Beau Belgrave
2021-12-16 17:35 ` [PATCH v8 08/12] user_events: Optimize writing events by only copying data once Beau Belgrave
2021-12-22 15:11 ` Masami Hiramatsu
2022-01-03 18:58 ` Beau Belgrave
2022-01-06 22:17 ` Steven Rostedt
2022-01-06 23:05 ` Beau Belgrave
2021-12-16 17:35 ` [PATCH v8 09/12] user_events: Add documentation file Beau Belgrave
2021-12-22 14:18 ` Masami Hiramatsu
2022-01-03 23:01 ` Beau Belgrave
2022-01-06 21:14 ` Steven Rostedt
2021-12-16 17:35 ` [PATCH v8 10/12] user_events: Add sample code for typical usage Beau Belgrave
2021-12-22 23:18 ` Masami Hiramatsu [this message]
2022-01-06 22:09 ` Steven Rostedt
2022-01-06 23:06 ` Beau Belgrave
2021-12-16 17:35 ` [PATCH v8 11/12] user_events: Validate user payloads for size and null termination Beau Belgrave
2021-12-23 0:08 ` Masami Hiramatsu
2022-01-03 18:53 ` Beau Belgrave
2022-01-06 23:32 ` Masami Hiramatsu
2022-01-07 1:01 ` Beau Belgrave
2021-12-16 17:35 ` [PATCH v8 12/12] user_events: Add self-test for validator boundaries Beau Belgrave
2022-04-18 20:43 ` [PATCH v8 00/12] user_events: Enable user processes to create and write to trace events Hagen Paul Pfeifer
2022-04-19 0:25 ` Beau Belgrave
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=20211223081814.1ca544cdf18e29a93f60c597@kernel.org \
--to=mhiramat@kernel.org \
--cc=beaub@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®