From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: linux-debuggers@vger.kernel.org
Subject: Re: [PATCH v2] SUNRPC: convert RPC_TASK_* constants to enum
Date: Mon, 19 Aug 2024 09:00:35 -0700 [thread overview]
Message-ID: <87r0akpknw.fsf@oracle.com> (raw)
In-Reply-To: <20240819155901.416560-1-stephen.s.brennan@oracle.com>
Forgot to CC linux-debuggers, sorry! Check lore for replies.
Stephen Brennan <stephen.s.brennan@oracle.com> writes:
> The RPC_TASK_* constants are defined as macros, which means that most
> kernel builds will not contain their definitions in the debuginfo.
> However, it's quite useful for debuggers to be able to view the task
> state constant and interpret it correctly. Conversion to an enum will
> ensure the constants are present in debuginfo and can be interpreted by
> debuggers without needing to hard-code them and track their changes.
>
> Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
> ---
>
> Hi all,
>
> For context, please see v1:
> https://lore.kernel.org/linux-nfs/20240816220604.2688389-1-stephen.s.brennan@oracle.com/
>
> include/linux/sunrpc/sched.h | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/include/linux/sunrpc/sched.h b/include/linux/sunrpc/sched.h
> index 0c77ba488bbae..fec1e8a1570c3 100644
> --- a/include/linux/sunrpc/sched.h
> +++ b/include/linux/sunrpc/sched.h
> @@ -151,13 +151,15 @@ struct rpc_task_setup {
> #define RPC_WAS_SENT(t) ((t)->tk_flags & RPC_TASK_SENT)
> #define RPC_IS_MOVEABLE(t) ((t)->tk_flags & RPC_TASK_MOVEABLE)
>
> -#define RPC_TASK_RUNNING 0
> -#define RPC_TASK_QUEUED 1
> -#define RPC_TASK_ACTIVE 2
> -#define RPC_TASK_NEED_XMIT 3
> -#define RPC_TASK_NEED_RECV 4
> -#define RPC_TASK_MSG_PIN_WAIT 5
> -#define RPC_TASK_SIGNALLED 6
> +enum {
> + RPC_TASK_RUNNING,
> + RPC_TASK_QUEUED,
> + RPC_TASK_ACTIVE,
> + RPC_TASK_NEED_XMIT,
> + RPC_TASK_NEED_RECV,
> + RPC_TASK_MSG_PIN_WAIT,
> + RPC_TASK_SIGNALLED,
> +};
>
> #define rpc_test_and_set_running(t) \
> test_and_set_bit(RPC_TASK_RUNNING, &(t)->tk_runstate)
> --
> 2.43.5
parent reply other threads:[~2024-08-19 16:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240819155901.416560-1-stephen.s.brennan@oracle.com>]
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=87r0akpknw.fsf@oracle.com \
--to=stephen.s.brennan@oracle.com \
--cc=linux-debuggers@vger.kernel.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).