From: "tarumizu.kohei@fujitsu.com" <tarumizu.kohei@fujitsu.com>
To: 'Dave Hansen' <dave.hansen@intel.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 0/8] Add hardware prefetch control driver for arm64 and x86
Date: Wed, 26 Jan 2022 09:24:35 +0000 [thread overview]
Message-ID: <OSBPR01MB203754574F2AC6281EFA1FDE80209@OSBPR01MB2037.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <931f6d2a-9001-e736-e7e2-7f86f87539cc@intel.com>
> Doesn't this break the one-value-per-file sysfs rules?
Sorry, I forgot the sysfs rules.
The current interface specification was decided referring to the
specification of /sys/class/rnbd-client/ctl/map_device. However,
I thought that the current specification of preftch_control was
inappropriate because it relevant to "Mixing types, expressing
multiple lines of data" in Documentation/filesystems/sysfs.rst.
The next version patch divides the attribute file by option, as
described below.
* Current version interface
```
/sys/devices/system/cpu/cpu0/cache/index0/
prefetch_control (attribute file)
```
* Next version interface look like this
```
/sys/devices/system/cpu/cpu0/cache/index0/prefetch_control/
hardware_prefetcher_enable (attribute file)
ip_prefetcher_enable (attribute file)
```
prev parent reply other threads:[~2022-01-26 9:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 7:14 [PATCH 0/8] Add hardware prefetch control driver for arm64 and x86 Kohei Tarumizu
2022-01-25 7:14 ` [PATCH 1/8] drivers: base: Add hardware prefetch control core driver Kohei Tarumizu
2022-01-25 7:14 ` [PATCH 2/8] drivers: base: Add Kconfig/Makefile to build " Kohei Tarumizu
2022-01-25 7:14 ` [PATCH 3/8] arm64: Add hardware prefetch control support for ARM64 Kohei Tarumizu
2022-01-25 7:14 ` [PATCH 4/8] arm64: Add Kconfig/Makefile to build hardware prefetch control driver Kohei Tarumizu
2022-01-29 17:03 ` Randy Dunlap
2022-02-01 12:04 ` tarumizu.kohei
2022-01-25 7:14 ` [PATCH 5/8] arm64: Create cache sysfs directory without ACPI PPTT for hardware prefetch control Kohei Tarumizu
2022-01-26 10:36 ` Sudeep Holla
2022-02-01 11:56 ` tarumizu.kohei
2022-07-07 14:37 ` Jeremy Linton
2022-07-07 14:44 ` Sudeep Holla
2022-07-08 10:21 ` tarumizu.kohei
2022-01-25 7:14 ` [PATCH 6/8] x86: Add hardware prefetch control support for x86 Kohei Tarumizu
2022-01-25 7:14 ` [PATCH 7/8] x86: Add Kconfig/Makefile to build hardware prefetch control driver Kohei Tarumizu
2022-01-25 7:14 ` [PATCH 8/8] docs: ABI: Add sysfs documentation interface of " Kohei Tarumizu
2022-01-25 15:12 ` [PATCH 0/8] Add hardware prefetch control driver for arm64 and x86 Dave Hansen
2022-01-26 9:24 ` tarumizu.kohei [this message]
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=OSBPR01MB203754574F2AC6281EFA1FDE80209@OSBPR01MB2037.jpnprd01.prod.outlook.com \
--to=tarumizu.kohei@fujitsu.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@intel.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=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;
as well as URLs for NNTP newsgroup(s).