From: Steven Rostedt <rostedt@goodmis.org>
To: Dave Jiang <dave.jiang@intel.com>
Cc: linux-cxl@vger.kernel.org, dan.j.williams@intel.com,
ira.weiny@intel.com, vishal.l.verma@intel.com,
alison.schofield@intel.com
Subject: Re: [PATCH v3 04/10] cxl: add common function to disable event trace
Date: Thu, 3 Nov 2022 02:02:34 -0400 [thread overview]
Message-ID: <20221103020234.63fd7ab2@rorschach.local.home> (raw)
In-Reply-To: <166742402697.2654617.15955710715103932892.stgit@djiang5-desk3.ch.intel.com>
On Wed, 02 Nov 2022 14:20:26 -0700
Dave Jiang <dave.jiang@intel.com> wrote:
> Add a common function for cxl command that disables the event trace for the
> instance created.
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> cxl/event_trace.c | 8 ++++++++
> cxl/event_trace.h | 1 +
> 2 files changed, 9 insertions(+)
>
> diff --git a/cxl/event_trace.c b/cxl/event_trace.c
> index d59e54c33df6..bcd4f8b2968e 100644
> --- a/cxl/event_trace.c
> +++ b/cxl/event_trace.c
> @@ -221,3 +221,11 @@ int cxl_event_tracing_enable(struct tracefs_instance *inst, const char *system)
> tracefs_trace_on(inst);
> return 0;
> }
> +
> +int cxl_event_tracing_disable(struct tracefs_instance *inst)
> +{
> + if (!tracefs_trace_is_on(inst))
> + return 0;
Why bother checking if tracing is on or not. It's not any more
efficient. You're not eliminating a system call. You are actually
adding another one.
-- Steve
> +
> + return tracefs_trace_off(inst);
> +}
> diff --git a/cxl/event_trace.h b/cxl/event_trace.h
> index 0258b8dc65a3..17d922f922c1 100644
> --- a/cxl/event_trace.h
> +++ b/cxl/event_trace.h
> @@ -21,5 +21,6 @@ struct event_ctx {
>
> int cxl_parse_events(struct tracefs_instance *inst, struct event_ctx *ectx);
> int cxl_event_tracing_enable(struct tracefs_instance *inst, const char *system);
> +int cxl_event_tracing_disable(struct tracefs_instance *inst);
>
> #endif
>
next prev parent reply other threads:[~2022-11-03 6:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 21:20 [PATCH v3 00/10] cxl: add monitor support for trace events Dave Jiang
2022-11-02 21:20 ` [PATCH v3 01/10] cxl: add helper function to parse trace event to json object Dave Jiang
2022-11-03 5:48 ` Steven Rostedt
2022-11-03 16:15 ` Dave Jiang
2022-11-04 18:56 ` Ira Weiny
2022-11-14 17:32 ` Steven Rostedt
2022-11-14 20:44 ` Alison Schofield
2022-11-14 20:53 ` Steven Rostedt
2022-11-02 21:20 ` [PATCH v3 02/10] cxl: add helper to parse through all current events Dave Jiang
2022-11-02 21:20 ` [PATCH v3 03/10] cxl: add common function to enable event trace Dave Jiang
2022-11-03 6:00 ` Steven Rostedt
2022-11-03 16:21 ` Dave Jiang
2022-11-02 21:20 ` [PATCH v3 04/10] cxl: add common function to disable " Dave Jiang
2022-11-03 6:02 ` Steven Rostedt [this message]
2022-11-03 16:30 ` Dave Jiang
2022-11-02 21:20 ` [PATCH v3 05/10] cxl: add monitor function for event trace events Dave Jiang
2022-11-03 6:06 ` Steven Rostedt
2022-11-03 16:34 ` Dave Jiang
2022-11-02 21:20 ` [PATCH v3 06/10] cxl: add logging functions for monitor Dave Jiang
2022-11-02 21:20 ` [PATCH v3 07/10] cxl: add monitor command to cxl Dave Jiang
2022-11-02 21:20 ` [PATCH v3 08/10] cxl: add an optional pid check to event parsing Dave Jiang
2022-11-03 6:08 ` Steven Rostedt
2022-11-03 15:57 ` Alison Schofield
2022-11-02 21:20 ` [PATCH v3 09/10] cxl: add systemd service for monitor Dave Jiang
2022-11-02 21:21 ` [PATCH v3 10/10] cxl: add man page documentation " Dave Jiang
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=20221103020234.63fd7ab2@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
/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