From: "John B. Wyatt IV" <jwyatt@redhat.com>
To: Vishnu Sanal T <t.v.s10123@gmail.com>
Cc: linux-pm@vger.kernel.org, trenn@suse.com, shuah@kernel.org,
jkacur@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] implement set_enabled functions on powercap.c
Date: Wed, 30 Oct 2024 12:57:45 -0400 [thread overview]
Message-ID: <ZyJliZ3Uka8R5ilh@rhfedora> (raw)
In-Reply-To: <20241030152706.179779-2-t.v.s10123@gmail.com>
On Wed, Oct 30, 2024 at 08:57:07PM +0530, Vishnu Sanal T wrote:
> Implement the functions sysfs_set_enabled, powercap_set_enabled,
> and powercap_zone_set_enabled on powercap.c.
>
> Signed-off-by: Vishnu Sanal T <t.v.s10123@gmail.com>
> ---
> Changes in v2:
>
> - simplify the implementation of sysfs_set_enabled using system()
> function.
Hello Vishnu,
Ty for sending a patch to implement this.
I got several warnings trying to compile your patch. Please resolve
them. I have not tested your code yet. How are you testing your code?
> ---
> tools/power/cpupower/lib/powercap.c | 31 +++++++++++++++++++++++------
> 1 file changed, 25 insertions(+), 6 deletions(-)
>
> diff --git a/tools/power/cpupower/lib/powercap.c b/tools/power/cpupower/lib/powercap.c
> index 94a0c69e55ef..a2c0c33b7729 100644
> --- a/tools/power/cpupower/lib/powercap.c
> +++ b/tools/power/cpupower/lib/powercap.c
> @@ -70,6 +70,17 @@ static int sysfs_get_enabled(char *path, int *mode)
> return ret;
> }
>
> +static int sysfs_set_enabled(char *path, int mode)
> +{
> + char command[SYSFS_PATH_MAX + 10];
> +
> + char yes_no = (char)(mode + '0');
What does yes or no mean for setting a value?
`is_set` or using something with the word 'mode' would be a better
variable name?
> +
> + sprintf(command, "echo -n %c > %s", yes_no, path);
> +
> + return system(command);
> +}
> +
In function ‘sysfs_set_enabled’,
inlined from ‘powercap_set_enabled’ at lib/powercap.c:95:9:
lib/powercap.c:79:9: note: ‘sprintf’ output between 13 and 267 bytes into a destination of size 265
79 | sprintf(command, "echo -n %c > %s", yes_no, path);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
lib/powercap.c: In function ‘powercap_zone_set_enabled’:
lib/powercap.c:79:40: warning: ‘%s’ directive writing up to 254 bytes into a region of size 253 [-Wformat-overflow=]
79 | sprintf(command, "echo -n %c > %s", yes_no, path);
| ^~
......
203 | return sysfs_set_enabled(path, mode);
| ~~~~
In function ‘sysfs_set_enabled’,
inlined from ‘powercap_zone_set_enabled’ at lib/powercap.c:203:9:
lib/powercap.c:79:9: note: ‘sprintf’ output between 13 and 267 bytes into a destination of size 265
79 | sprintf(command, "echo -n %c > %s", yes_no, path);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> int powercap_get_enabled(int *mode)
> {
> char path[SYSFS_PATH_MAX] = PATH_TO_POWERCAP "/intel-rapl/enabled";
> @@ -77,12 +88,11 @@ int powercap_get_enabled(int *mode)
> return sysfs_get_enabled(path, mode);
> }
>
> -/*
> - * TODO: implement function. Returns dummy 0 for now.
> - */
> int powercap_set_enabled(int mode)
> {
> - return 0;
> + char path[SYSFS_PATH_MAX] = PATH_TO_POWERCAP "/intel-rapl/enabled";
> +
> + return sysfs_set_enabled(path, mode);
> }
lib/powercap.c: In function ‘powercap_set_enabled’:
lib/powercap.c:79:40: warning: ‘%s’ directive writing up to 254 bytes into a region of size 253 [-Wformat-overflow=]
79 | sprintf(command, "echo -n %c > %s", yes_no, path);
| ^~
......
95 | return sysfs_set_enabled(path, mode);
>
> /*
> @@ -180,8 +190,17 @@ int powercap_zone_get_enabled(struct powercap_zone *zone, int *mode)
>
> int powercap_zone_set_enabled(struct powercap_zone *zone, int mode)
> {
> - /* To be done if needed */
> - return 0;
> + char path[SYSFS_PATH_MAX] = PATH_TO_POWERCAP;
> +
> + if ((strlen(PATH_TO_POWERCAP) + strlen(zone->sys_name)) +
> + strlen("/enabled") + 1 >= SYSFS_PATH_MAX)
> + return -1;
> +
> + strcat(path, "/");
> + strcat(path, zone->sys_name);
> + strcat(path, "/enabled");
> +
> + return sysfs_set_enabled(path, mode);
> }
>
>
> --
> 2.47.0
>
--
Sincerely,
John Wyatt
Software Engineer, Core Kernel
Red Hat
next prev parent reply other threads:[~2024-10-30 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 12:42 [PATCH] implement set_enabled functions on powercap.c Vishnu Sanal T
2024-10-21 20:36 ` Shuah Khan
2024-10-30 15:27 ` [PATCH v2] " Vishnu Sanal T
2024-10-30 16:57 ` John B. Wyatt IV [this message]
2024-11-03 16:27 ` kernel test robot
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=ZyJliZ3Uka8R5ilh@rhfedora \
--to=jwyatt@redhat.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=t.v.s10123@gmail.com \
--cc=trenn@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox