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: <2a939a62-7016-bbd6-6e2f-2824214687fd@intel.com>
Date:   Thu, 4 Nov 2021 07:55:10 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     Kohei Tarumizu <tarumizu.kohei@...itsu.com>,
        catalin.marinas@....com, will@...nel.org, tglx@...utronix.de,
        mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com,
        x86@...nel.org, hpa@...or.com,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v2 5/5] docs: ABI: Add sysfs documentation interface
 of hardware prefetch driver

On 11/3/21 10:21 PM, Kohei Tarumizu wrote:
> +What:		/sys/devices/system/cpu/cpu*/hwpf/l*/enable
> +		/sys/devices/system/cpu/cpu*/hwpf/l*/available_dist
> +		/sys/devices/system/cpu/cpu*/hwpf/l*/dist
> +		/sys/devices/system/cpu/cpu*/hwpf/l*/reliable

How does this look in practice?

	# ls /sys/devices/system/cpu/cpu0/hwpf/
	l0
	l1
	l2
	...

?

Dumb question, but why don't we give these things names?  If the Intel
one is called "L2 Hardware Prefetcher Disable", couldn't the directory
be "l2_prefetch"?

BTW, your "reliable" is mismatched with the "strong" value in the docs.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ