linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Crystal Wood <crwood@redhat.com>
To: Wander Lairson Costa <wander@redhat.com>,
	Steven Rostedt	 <rostedt@goodmis.org>,
	Tomas Glozar <tglozar@redhat.com>,
	Ivan Pravdin	 <ipravdin.official@gmail.com>,
	John Kacur <jkacur@redhat.com>,
	Costa Shulyupin	 <costa.shul@redhat.com>,
	Tiezhu Yang <yangtiezhu@loongson.cn>,
	"open list:Real-time Linux Analysis (RTLA) tools"	
	<linux-trace-kernel@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	 "open list:BPF [MISC]:Keyword:(?:\\b|_)bpf(?:\\b|_)"	
	<bpf@vger.kernel.org>
Subject: Re: [rtla 07/13] rtla: Introduce timerlat_restart() helper
Date: Mon, 24 Nov 2025 18:46:36 -0600	[thread overview]
Message-ID: <fb5b468b38ac9570a5f3fb948452d1b5b03c9f9c.camel@redhat.com> (raw)
In-Reply-To: <20251117184409.42831-8-wander@redhat.com>

On Mon, 2025-11-17 at 15:41 -0300, Wander Lairson Costa wrote:

> +enum restart_result
> +timerlat_restart(const struct osnoise_tool *tool, struct timerlat_params *params)
> +{
> +	actions_perform(&params->common.threshold_actions);
> +
> +	if (!params->common.threshold_actions.continue_flag)
> +		/* continue flag not set, break */
> +		return RESTART_STOP;
> +
> +	/* continue action reached, re-enable tracing */
> +	if (tool->record && trace_instance_start(&tool->record->trace))
> +		goto err;
> +	if (tool->aa && trace_instance_start(&tool->aa->trace))
> +		goto err;
> +	return RESTART_OK;
> +
> +err:
> +	err_msg("Error restarting trace\n");
> +	return RESTART_ERROR;
> +}

The non-BPF functions in common.c have the same logic and should also
call this.  This isn't timerlat-specific.


> diff --git a/tools/tracing/rtla/src/timerlat_hist.c b/tools/tracing/rtla/src/timerlat_hist.c
> index 09a3da3f58630..f14fc56c5b4a5 100644
> --- a/tools/tracing/rtla/src/timerlat_hist.c
> +++ b/tools/tracing/rtla/src/timerlat_hist.c
> @@ -1165,18 +1165,19 @@ static int timerlat_hist_bpf_main_loop(struct osnoise_tool *tool)
>  
>  		if (!stop_tracing) {
>  			/* Threshold overflow, perform actions on threshold */
> -			actions_perform(&params->common.threshold_actions);
> +			enum restart_result result;
>  
> -			if (!params->common.threshold_actions.continue_flag)
> -				/* continue flag not set, break */
> +			result = timerlat_restart(tool, params);
> +			if (result == RESTART_STOP)
>  				break;
>  
> -			/* continue action reached, re-enable tracing */
> -			if (tool->record)
> -				trace_instance_start(&tool->record->trace);
> -			if (tool->aa)
> -				trace_instance_start(&tool->aa->trace);
> -			timerlat_bpf_restart_tracing();
> +			if (result == RESTART_ERROR)
> +				return -1;

Does it matter that we're not detaching on an error here?  Is this
something that gets cleaned up automatically (and if so, why do we ever
need to do it explicitly)?

> +
> +			if (timerlat_bpf_restart_tracing()) {
> +				err_msg("Error restarting BPF trace\n");
> +				return -1;
> +			}

[insert rant about not being able to use exceptions in userspace code in
the year 2025]

-Crystal


  reply	other threads:[~2025-11-25  0:46 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 18:41 [PATCH 0/13] rtla: Code robustness and maintainability improvements Wander Lairson Costa
2025-11-17 18:41 ` [rtla 01/13] rtla: Check for memory allocation failures Wander Lairson Costa
2025-11-18  2:09   ` Masami Hiramatsu
2025-11-18  3:06     ` Steven Rostedt
2025-11-18  5:13       ` Masami Hiramatsu
2025-11-28 13:29   ` Costa Shulyupin
2025-11-28 13:52     ` Wander Lairson Costa
2025-11-17 18:41 ` [rtla 02/13] rtla: Use strdup() to simplify code Wander Lairson Costa
2025-11-17 18:41 ` [rtla 03/13] rtla: Introduce for_each_action() helper Wander Lairson Costa
2025-11-17 18:41 ` [rtla 04/13] rtla: Replace atoi() with a robust strtoi() Wander Lairson Costa
2025-11-25  0:46   ` Crystal Wood
2025-11-25 13:34     ` Wander Lairson Costa
2025-11-25  8:35   ` Costa Shulyupin
2025-11-25 13:49     ` Wander Lairson Costa
2025-11-17 18:41 ` [rtla 05/13] rtla: Simplify argument parsing Wander Lairson Costa
2025-11-25  0:46   ` Crystal Wood
2025-11-25 13:45     ` Wander Lairson Costa
2025-11-25 16:53       ` Crystal Wood
2025-11-17 18:41 ` [rtla 06/13] rtla: Use strncmp_static() in more places Wander Lairson Costa
2025-11-17 18:41 ` [rtla 07/13] rtla: Introduce timerlat_restart() helper Wander Lairson Costa
2025-11-25  0:46   ` Crystal Wood [this message]
2025-11-25 14:20     ` Wander Lairson Costa
2025-11-25 17:35       ` Crystal Wood
2025-11-25 18:09         ` Wander Lairson Costa
2025-11-17 18:41 ` [rtla 08/13] rtla: Use standard exit codes for result enum Wander Lairson Costa
     [not found]   ` <CADDUTFz_gU0C8uqwDS3ewFRUxk7nbkGv1UU09Omjy0Ew2wB5VQ@mail.gmail.com>
2025-11-28 14:04     ` Wander Lairson Costa
2025-11-17 18:41 ` [rtla 09/13] rtla: Exit if trace output action fails Wander Lairson Costa
2025-11-17 18:41 ` [rtla 10/13] rtla: Remove redundant memset after calloc Wander Lairson Costa
2025-11-17 18:41 ` [rtla 11/13] rtla: Replace magic number with MAX_PATH Wander Lairson Costa
2025-11-17 18:41 ` [rtla 12/13] rtla: Remove unused headers Wander Lairson Costa
2025-11-17 18:41 ` [rtla 13/13] rtla: Fix inconsistent state in actions_add_* functions Wander Lairson Costa

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=fb5b468b38ac9570a5f3fb948452d1b5b03c9f9c.camel@redhat.com \
    --to=crwood@redhat.com \
    --cc=bpf@vger.kernel.org \
    --cc=costa.shul@redhat.com \
    --cc=ipravdin.official@gmail.com \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglozar@redhat.com \
    --cc=wander@redhat.com \
    --cc=yangtiezhu@loongson.cn \
    /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).