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: <553FDD06.8090504@ezchip.com>
Date:	Tue, 28 Apr 2015 15:18:30 -0400
From:	Chris Metcalf <cmetcalf@...hip.com>
To:	<riel@...hat.com>, <linux-kernel@...r.kernel.org>
CC:	<tj@...nel.org>, <umgwanakikbuti@...il.com>, <lizefan@...wei.com>,
	<fweisbec@...il.com>, <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 2/2] show nohz_full cpus in sysfs

On 04/24/2015 03:24 PM, riel@...hat.com wrote:
> From: Rik van Riel<riel@...hat.com>
>
> Currently there is no way to query which CPUs are in nohz_full
> mode from userspace.
>
> Export the CPU list running in nohz_full mode in sysfs,
> specifically in the file /sys/devices/system/cpu/nohz_full
>
> This can be used by system management tools like libvirt,
> openstack, and others to ensure proper task placement.
>
> Signed-off-by: Rik van Riel<riel@...hat.com>
> ---
>   drivers/base/cpu.c | 17 +++++++++++++++++
>   1 file changed, 17 insertions(+)

In the arch/tile distribution with our "dataplane" support, we have
traditionally had a /sys/devices/system/cpu/dataplane file with
the same semantics you are proposing.  It's definitely helpful
to userspace applications figuring out how to appropriately take
over the machine they are being run on.

Acked-by: Chris Metcalf <cmetcalf@...hip.com>
-- 
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ