public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] lib: Extend -D flag to support multiple debug levels
Date: Mon, 2 Mar 2026 10:59:54 +0100	[thread overview]
Message-ID: <aaVfmr0jWE-_4SYG@yuki.lan> (raw)
In-Reply-To: <20260301012808.15588-1-liwang@redhat.com>

Hi!
> This patch extends the LTP debugging framework by introducing multiple
> levels of verbosity for the '-D' command line option. Instead of a simple
> on/off toggle, it now allows developers to specify whether they want debug
> output exclusively from the test process, or from both the test and library
> processes.
> 
> The supported debug levels are:
>   -D0     : Disable all debug logs (default behavior)
>   -D1 (-D): Enable debug logs for the test process only
>   -D2     : Enable verbose debug logs for both the test and library processes
> 
> Signed-off-by: Li Wang <liwang@redhat.com>
> ---
>  doc/developers/debugging.rst |  6 ++++++
>  lib/tst_test.c               | 25 +++++++++++++++----------
>  2 files changed, 21 insertions(+), 10 deletions(-)
> 
> diff --git a/doc/developers/debugging.rst b/doc/developers/debugging.rst
> index 181e5b096..8b5550b73 100644
> --- a/doc/developers/debugging.rst
> +++ b/doc/developers/debugging.rst
> @@ -12,6 +12,12 @@ The LTP framework supports ``TDEBUG`` flag test debug messages. These
>  messages can be enabled using the ``-D`` parameter or setting ``LTP_ENABLE_DEBUG=1``
>  environment variable (see :doc:`../users/setup_tests`).
>  
> +The ``-D`` parameter also supports the following verbosity levels:
> +
> +  ``-D0``: Disable all debug logs (default behavior).
> +  ``-D1`` (or ``-D``): Enable debug logs for the test process only.
> +  ``-D2``: Enable verbose debug logs for both the test and library processes.
> +
>  Tracing and debugging syscalls
>  ------------------------------
>  
> diff --git a/lib/tst_test.c b/lib/tst_test.c
> index 239494b6f..f7907223e 100644
> --- a/lib/tst_test.c
> +++ b/lib/tst_test.c
> @@ -83,7 +83,7 @@ struct context {
>  	tst_atomic_t abort_flag;
>  	uint32_t mntpoint_mounted:1;
>  	uint32_t ovl_mounted:1;
> -	uint32_t tdebug:1;
> +	uint32_t tdebug;
>  };
>  
>  struct results {
> @@ -217,7 +217,7 @@ void tst_reinit(void)
>  	tst_max_futexes = (size - offsetof(struct ipc_region, futexes)) / sizeof(futex_t);
>  
>  	if (context->tdebug)
> -		tst_res(TINFO, "Restored metadata for PID %d", getpid());
> +		tst_res(TDEBUG, "Restored metadata for PID %d", getpid());

I suppose that we do not need the if (context->tdebug) now.


Otherwise it looks good.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-03-02 10:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01  1:28 [LTP] [PATCH] lib: Extend -D flag to support multiple debug levels Li Wang via ltp
2026-03-02  9:59 ` Cyril Hrubis [this message]
2026-03-02 15:11 ` Andrea Cervesato via ltp
2026-03-03  2:45   ` Li Wang via ltp
2026-03-03  2:55     ` Li Wang via ltp
  -- strict thread matches above, loose matches on Subject: below --
2026-03-02 14:41 Andrea Cervesato via ltp

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=aaVfmr0jWE-_4SYG@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    /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