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: <20250403042504.GB22360@lst.de>
Date: Thu, 3 Apr 2025 06:25:04 +0200
From: Christoph Hellwig <hch@....de>
To: Yaxiong Tian <iambestgod@...com>
Cc: kbusch@...nel.org, axboe@...nel.dk, hch@....de, sagi@...mberg.me,
	chaitanyak@...dia.com, linux-nvme@...ts.infradead.org,
	linux-kernel@...r.kernel.org, Yaxiong Tian <tianyaxiong@...inos.cn>
Subject: Re: [PATCH v3 0/3] nvme: Add sysfs interface for APST
 configuration management

On Tue, Apr 01, 2025 at 05:22:06PM +0800, Yaxiong Tian wrote:
> From: Yaxiong Tian <tianyaxiong@...inos.cn>
> 
> This series enhances NVMe APST (Autonomous Power State Transition) support by:
> 1. Adding warnings for PST table allocation failures

That looks fine.

> 2. Exposing APST tables via sysfs for runtime inspection
> 3. Providing per-controller sysfs interface for APST configuration

Who is going to use this and how?  We'll need proper tools for that,
and in general I'd prefer to have a common set of policies for APST
configurations and not random people coming up with lots of random
policies.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ