lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cabab318-95a4-4e81-a931-458ee6023f3a@linaro.org>
Date: Tue, 8 Jul 2025 16:58:00 +0100
From: Tudor Ambarus <tudor.ambarus@...aro.org>
To: Randy Dunlap <rdunlap@...radead.org>, Jonathan Corbet <corbet@....net>,
 "Rafael J. Wysocki" <rafael@...nel.org>, Pavel Machek <pavel@...nel.org>,
 Len Brown <len.brown@...el.com>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-pm@...r.kernel.org, peter.griffin@...aro.org,
 andre.draszik@...aro.org, willmcvicker@...gle.com, kernel-team@...roid.com
Subject: Re: [PATCH v2] PM: add kernel parameter to disable asynchronous
 suspend/resume



On 7/8/25 4:36 PM, Randy Dunlap wrote:
> Hi,
> 

Hi, Randy!

> On 7/8/25 8:16 AM, Tudor Ambarus wrote:
> 
>> ---
>>  Documentation/admin-guide/kernel-parameters.txt | 11 +++++++++++
>>  kernel/power/main.c                             |  9 +++++++++
>>  2 files changed, 20 insertions(+)
>>
>> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
>> index f1f2c0874da9ddfc95058c464fdf5dabaf0de713..33ca6b881b1d77bdeea765b19291a90b2a82e8a3 100644
>> --- a/Documentation/admin-guide/kernel-parameters.txt
>> +++ b/Documentation/admin-guide/kernel-parameters.txt
>> @@ -5000,6 +5000,17 @@
>>  			that number, otherwise (e.g., 'pmu_override=on'), MMCR1
>>  			remains 0.
>>  
> 
> This should be more like:
> 
> 
> 	pm_async=off	[PM]
> 
> or
> 
>> +	pm_async	[PM]
> 
> 	pm_async=	[PM]
> 			Format: off

Indeed. I see this second description, "kernel_param=", largely used in
the existing kernel parameters, so maybe that's what I shall follow.
However, I don't really know which format to choose, I see:

Format: <string>
Format: { off }
Format: {off}
Format: { "off" }
Format: {"off"}
Format: off

Any idea if there's an already agreed string format?
Thanks,
ta

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ