From: Reinette Chatre <reinette.chatre@intel.com>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] x86/resctrl: Fix kernel-doc in pseudo_lock.c
Date: Tue, 15 Jun 2021 11:54:29 -0700 [thread overview]
Message-ID: <94862dff-afbe-10df-3f5c-e9d5c6c90afc@intel.com> (raw)
In-Reply-To: <20210614150929.3151-1-fmdefrancesco@gmail.com>
Hi Fabio,
On 6/14/2021 8:09 AM, Fabio M. De Francesco wrote:
> Add undocumented parameters detected by scripts/kernel-doc.
>
> Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
> ---
...
> diff --git a/arch/x86/kernel/cpu/resctrl/pseudo_lock.c b/arch/x86/kernel/cpu/resctrl/pseudo_lock.c
> index 05a89e33fde2..84b9bf4daa33 100644
> --- a/arch/x86/kernel/cpu/resctrl/pseudo_lock.c
> +++ b/arch/x86/kernel/cpu/resctrl/pseudo_lock.c
> @@ -49,6 +49,7 @@ static struct class *pseudo_lock_class;
>
> /**
> * get_prefetch_disable_bits - prefetch disable bits of supported platforms
> + * @void: It takes no parameters.
> *
> * Capture the list of platforms that have been validated to support
> * pseudo-locking. This includes testing to ensure pseudo-locked regions
> @@ -162,8 +163,9 @@ static struct rdtgroup *region_find_by_minor(unsigned int minor)
> }
>
> /**
> - * pseudo_lock_pm_req - A power management QoS request list entry
> - * @list: Entry within the @pm_reqs list for a pseudo-locked region
> + * struct pseudo_lock_pm_req - A power management QoS request list entry
> + * @list: Entry within the power management requests list for a
> + * pseudo-locked region
Adding "struct" is surely needed.
Regarding the description of list I prefer the original text. Consider
the scenario where somebody is trying to understand this code and using
a source code browser ... the original description would enable a direct
transition to where pm_reqs is defined with more descriptions and
context to understand the code.
> @@ -184,6 +186,7 @@ static void pseudo_lock_cstates_relax(struct pseudo_lock_region *plr)
>
> /**
> * pseudo_lock_cstates_constrain - Restrict cores from entering C6
> + * @plr: Pseudo-locked region
> *
> * To prevent the cache from being affected by power management entering
> * C6 has to be avoided. This is accomplished by requesting a latency
> @@ -196,6 +199,8 @@ static void pseudo_lock_cstates_relax(struct pseudo_lock_region *plr)
> * the ACPI latencies need to be considered while keeping in mind that C2
> * may be set to map to deeper sleep states. In this case the latency
> * requirement needs to prevent entering C2 also.
> + *
> + * Return: 0 on success, <0 on failure
> */
> static int pseudo_lock_cstates_constrain(struct pseudo_lock_region *plr)
> {
> @@ -520,7 +525,7 @@ static int pseudo_lock_fn(void *_rdtgrp)
>
> /**
> * rdtgroup_monitor_in_progress - Test if monitoring in progress
> - * @r: resource group being queried
> + * @rdtgrp: resource group being queried
> *
> * Return: 1 if monitor groups have been created for this resource
> * group, 0 otherwise.
> @@ -1140,6 +1145,8 @@ static int measure_l3_residency(void *_plr)
>
> /**
> * pseudo_lock_measure_cycles - Trigger latency measure to pseudo-locked region
> + * @rdtgrp: Resource group to which the pseudo-locked region belongs.
> + * @sel: Selector of which measurement to perform on a pseudo-locked region.
> *
> * The measurement of latency to access a pseudo-locked region should be
> * done from a cpu that is associated with that pseudo-locked region.
>
The rest looks good, thank you very much.
Reinette
prev parent reply other threads:[~2021-06-15 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 15:09 Fabio M. De Francesco
2021-06-15 18:54 ` Reinette Chatre [this message]
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=94862dff-afbe-10df-3f5c-e9d5c6c90afc@intel.com \
--to=reinette.chatre@intel.com \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=fmdefrancesco@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®