All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Righi <arighi@nvidia.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
	David Vernet <void@manifault.com>,
	Changwoo Min <changwoo@igalia.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	bpf@vger.kernel.org
Subject: Re: [PATCH] sched_ext: fix kernel-doc warnings
Date: Sat, 11 Jan 2025 10:45:25 +0100	[thread overview]
Message-ID: <Z4I9tXouDIVdWBN5@gpd3> (raw)
In-Reply-To: <20250111063136.910862-1-rdunlap@infradead.org>

Hi Randy,

On Fri, Jan 10, 2025 at 10:31:36PM -0800, Randy Dunlap wrote:
> Use the correct function parameter names and function names.
> Use the correct kernel-doc comment format for struct sched_ext_ops
> to eliminate a bunch of warnings.
> 
> ext.c:1418: warning: Excess function parameter 'include_dead' description in 'scx_task_iter_next_locked'
> ext.c:7261: warning: expecting prototype for scx_bpf_dump(). Prototype was for scx_bpf_dump_bstr() instead
> ext.c:7352: warning: Excess function parameter 'flags' description in 'scx_bpf_cpuperf_set'
> 
> ext.c:3150: warning: Function parameter or struct member 'in_fi' not described in 'scx_prio_less'
> ext.c:4711: warning: Function parameter or struct member 'dur_s' not described in 'scx_softlockup'
> ext.c:4775: warning: Function parameter or struct member 'bypass' not described in 'scx_ops_bypass'
> ext.c:7453: warning: Function parameter or struct member 'idle_mask' not described in 'scx_bpf_put_idle_cpumask'
> 
> ext.c:209: warning: Incorrect use of kernel-doc format:          * select_cpu - Pick the target CPU for a task which is being woken up
> ext.c:236: warning: Incorrect use of kernel-doc format:          * enqueue - Enqueue a task on the BPF scheduler
> ext.c:251: warning: Incorrect use of kernel-doc format:          * dequeue - Remove a task from the BPF scheduler
> ext.c:267: warning: Incorrect use of kernel-doc format:          * dispatch - Dispatch tasks from the BPF scheduler and/or user DSQs
> ext.c:290: warning: Incorrect use of kernel-doc format:          * tick - Periodic tick
> ext.c:300: warning: Incorrect use of kernel-doc format:          * runnable - A task is becoming runnable on its associated CPU
> ext.c:327: warning: Incorrect use of kernel-doc format:          * running - A task is starting to run on its associated CPU
> ext.c:335: warning: Incorrect use of kernel-doc format:          * stopping - A task is stopping execution
> ext.c:346: warning: Incorrect use of kernel-doc format:          * quiescent - A task is becoming not runnable on its associated CPU
> ext.c:366: warning: Incorrect use of kernel-doc format:          * yield - Yield CPU
> ext.c:381: warning: Incorrect use of kernel-doc format:          * core_sched_before - Task ordering for core-sched
> ext.c:399: warning: Incorrect use of kernel-doc format:          * set_weight - Set task weight
> ext.c:408: warning: Incorrect use of kernel-doc format:          * set_cpumask - Set CPU affinity
> ext.c:418: warning: Incorrect use of kernel-doc format:          * update_idle - Update the idle state of a CPU
> ext.c:439: warning: Incorrect use of kernel-doc format:          * cpu_acquire - A CPU is becoming available to the BPF scheduler
> ext.c:449: warning: Incorrect use of kernel-doc format:          * cpu_release - A CPU is taken away from the BPF scheduler
> ext.c:461: warning: Incorrect use of kernel-doc format:          * init_task - Initialize a task to run in a BPF scheduler
> ext.c:476: warning: Incorrect use of kernel-doc format:          * exit_task - Exit a previously-running task from the system
> ext.c:485: warning: Incorrect use of kernel-doc format:          * enable - Enable BPF scheduling for a task
> ext.c:494: warning: Incorrect use of kernel-doc format:          * disable - Disable BPF scheduling for a task
> ext.c:504: warning: Incorrect use of kernel-doc format:          * dump - Dump BPF scheduler state on error
> ext.c:512: warning: Incorrect use of kernel-doc format:          * dump_cpu - Dump BPF scheduler state for a CPU on error
> ext.c:524: warning: Incorrect use of kernel-doc format:          * dump_task - Dump BPF scheduler state for a runnable task on error
> ext.c:535: warning: Incorrect use of kernel-doc format:          * cgroup_init - Initialize a cgroup
> ext.c:550: warning: Incorrect use of kernel-doc format:          * cgroup_exit - Exit a cgroup
> ext.c:559: warning: Incorrect use of kernel-doc format:          * cgroup_prep_move - Prepare a task to be moved to a different cgroup
> ext.c:574: warning: Incorrect use of kernel-doc format:          * cgroup_move - Commit cgroup move
> ext.c:585: warning: Incorrect use of kernel-doc format:          * cgroup_cancel_move - Cancel cgroup move
> ext.c:597: warning: Incorrect use of kernel-doc format:          * cgroup_set_weight - A cgroup's weight is being changed
> ext.c:611: warning: Incorrect use of kernel-doc format:          * cpu_online - A CPU became online
> ext.c:620: warning: Incorrect use of kernel-doc format:          * cpu_offline - A CPU is going offline
> ext.c:633: warning: Incorrect use of kernel-doc format:          * init - Initialize the BPF scheduler
> ext.c:638: warning: Incorrect use of kernel-doc format:          * exit - Clean up after the BPF scheduler
> ext.c:648: warning: Incorrect use of kernel-doc format:          * dispatch_max_batch - Max nr of tasks that dispatch() can dispatch
> ext.c:653: warning: Incorrect use of kernel-doc format:          * flags - %SCX_OPS_* flags
> ext.c:658: warning: Incorrect use of kernel-doc format:          * timeout_ms - The maximum amount of time, in milliseconds, that a
> ext.c:667: warning: Incorrect use of kernel-doc format:          * exit_dump_len - scx_exit_info.dump buffer length. If 0, the default
> ext.c:673: warning: Incorrect use of kernel-doc format:          * hotplug_seq - A sequence number that may be set by the scheduler to
> ext.c:682: warning: Incorrect use of kernel-doc format:          * name - BPF scheduler's name
> 
> ext.c:689: warning: Function parameter or struct member 'select_cpu' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'enqueue' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'dequeue' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'dispatch' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'tick' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'runnable' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'running' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'stopping' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'quiescent' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'yield' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'core_sched_before' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'set_weight' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'set_cpumask' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'update_idle' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'cpu_acquire' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'cpu_release' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'init_task' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'exit_task' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'enable' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'disable' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'dump' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'dump_cpu' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'dump_task' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'cgroup_init' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'cgroup_exit' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'cgroup_prep_move' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'cgroup_move' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'cgroup_cancel_move' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'cgroup_set_weight' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'cpu_online' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'cpu_offline' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'init' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'exit' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'dispatch_max_batch' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'flags' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'timeout_ms' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'exit_dump_len' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'hotplug_seq' not described in 'sched_ext_ops'
> ext.c:689: warning: Function parameter or struct member 'name' not described in 'sched_ext_ops'
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: David Vernet <void@manifault.com>
> Cc: Andrea Righi <arighi@nvidia.com>
> Cc: Changwoo Min <changwoo@igalia.com>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: bpf@vger.kernel.org

Thanks for this cleanup, looks good to me. I left a small comment below,
but feel free to ignore.

Acked-by: Andrea Righi <arighi@nvidia.com>

> @@ -1408,7 +1409,6 @@ static struct task_struct *scx_task_iter
>  /**
>   * scx_task_iter_next_locked - Next non-idle task with its rq locked
>   * @iter: iterator to walk
> - * @include_dead: Whether we should include dead tasks in the iteration
>   *
>   * Visit the non-idle task with its rq lock held. Allows callers to specify
>   * whether they would like to filter out dead tasks. See scx_task_iter_start()
> @@ -3132,6 +3132,7 @@ static struct task_struct *pick_task_scx
>   * scx_prio_less - Task ordering for core-sched
>   * @a: task A
>   * @b: task B
> + * @in_fi: in forced idle state

in_fi is currently not used / not passed to ops.core_sched_before(), should
we metion this? Like appending (unused) or similar to the description?

-Andrea

  reply	other threads:[~2025-01-11  9:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-11  6:31 [PATCH] sched_ext: fix kernel-doc warnings Randy Dunlap
2025-01-11  9:45 ` Andrea Righi [this message]
2025-01-11 17:27   ` Randy Dunlap
2025-01-11 17:30     ` Andrea Righi
2025-01-13 18:24 ` Tejun Heo

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=Z4I9tXouDIVdWBN5@gpd3 \
    --to=arighi@nvidia.com \
    --cc=bpf@vger.kernel.org \
    --cc=changwoo@igalia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=tj@kernel.org \
    --cc=void@manifault.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.