From: Dave Hansen <dave.hansen@intel.com>
To: Kohei Tarumizu <tarumizu.kohei@fujitsu.com>,
catalin.marinas@arm.com, will@kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 5/5] docs: ABI: Add sysfs documentation interface of hardware prefetch driver
Date: Thu, 4 Nov 2021 07:55:10 -0700 [thread overview]
Message-ID: <2a939a62-7016-bbd6-6e2f-2824214687fd@intel.com> (raw)
In-Reply-To: <20211104052122.553868-6-tarumizu.kohei@fujitsu.com>
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.
next prev parent reply other threads:[~2021-11-04 14:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 5:21 [RFC PATCH v2 0/5] Add hardware prefetch driver for A64FX and Intel processors Kohei Tarumizu
2021-11-04 5:21 ` [RFC PATCH v2 1/5] driver: hwpf: Add hardware prefetch core driver register/unregister functions Kohei Tarumizu
2021-11-04 5:21 ` [RFC PATCH v2 2/5] driver: hwpf: Add support for A64FX to hardware prefetch driver Kohei Tarumizu
2021-11-04 5:21 ` [RFC PATCH v2 3/5] driver: hwpf: Add support for Intel " Kohei Tarumizu
2021-11-08 1:51 ` Dave Hansen
2021-11-09 9:44 ` tarumizu.kohei
2021-11-04 5:21 ` [RFC PATCH v2 4/5] driver: hwpf: Add Kconfig/Makefile to build " Kohei Tarumizu
2021-11-04 5:21 ` [RFC PATCH v2 5/5] docs: ABI: Add sysfs documentation interface of " Kohei Tarumizu
2021-11-04 14:55 ` Dave Hansen [this message]
2021-11-08 1:29 ` tarumizu.kohei
2021-11-08 1:49 ` Dave Hansen
2021-11-09 9:41 ` tarumizu.kohei
2021-11-09 17:44 ` Dave Hansen
2021-11-10 9:25 ` tarumizu.kohei
2021-11-04 15:13 ` [RFC PATCH v2 0/5] Add hardware prefetch driver for A64FX and Intel processors Borislav Petkov
2021-11-08 2:17 ` tarumizu.kohei
2021-11-10 8:34 ` Borislav Petkov
2021-11-18 6:14 ` tarumizu.kohei
2021-11-18 7:09 ` tarumizu.kohei
2021-12-06 9:30 ` tarumizu.kohei
2021-11-04 17:10 ` Peter Zijlstra
2021-11-08 2:36 ` tarumizu.kohei
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=2a939a62-7016-bbd6-6e2f-2824214687fd@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tarumizu.kohei@fujitsu.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®