From: Peter Zijlstra <peterz@infradead.org> To: Kohei Tarumizu <tarumizu.kohei@fujitsu.com> Cc: 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 0/5] Add hardware prefetch driver for A64FX and Intel processors Date: Thu, 4 Nov 2021 18:10:12 +0100 [thread overview] Message-ID: <20211104171012.GC174703@worktop.programming.kicks-ass.net> (raw) In-Reply-To: <20211104052122.553868-1-tarumizu.kohei@fujitsu.com> On Thu, Nov 04, 2021 at 02:21:17PM +0900, Kohei Tarumizu wrote: > This patch series add hardware prefetch driver register/unregister > function. The purpose of this driver is to provide an interface to > control the hardware prefetch mechanism depending on the application > characteristics. Here you talk about applications.. > An earlier RFC[1], we were suggested that we create a hardware > prefetch directory under /sys/devices/system/cpu/[CPUNUM]/cache. > Hardware prefetch is a cache-related feature, but it does not require > cache sysfs feature. Therefore, we decided to isolate the code. > Specifically, create a directory under cpu/[CPUNUM]. Here you talk about CPUs.. How does that work? _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org> To: Kohei Tarumizu <tarumizu.kohei@fujitsu.com> Cc: 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 0/5] Add hardware prefetch driver for A64FX and Intel processors Date: Thu, 4 Nov 2021 18:10:12 +0100 [thread overview] Message-ID: <20211104171012.GC174703@worktop.programming.kicks-ass.net> (raw) In-Reply-To: <20211104052122.553868-1-tarumizu.kohei@fujitsu.com> On Thu, Nov 04, 2021 at 02:21:17PM +0900, Kohei Tarumizu wrote: > This patch series add hardware prefetch driver register/unregister > function. The purpose of this driver is to provide an interface to > control the hardware prefetch mechanism depending on the application > characteristics. Here you talk about applications.. > An earlier RFC[1], we were suggested that we create a hardware > prefetch directory under /sys/devices/system/cpu/[CPUNUM]/cache. > Hardware prefetch is a cache-related feature, but it does not require > cache sysfs feature. Therefore, we decided to isolate the code. > Specifically, create a directory under cpu/[CPUNUM]. Here you talk about CPUs.. How does that work?
next prev parent reply other threads:[~2021-11-04 17:14 UTC|newest] Thread overview: 44+ 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 ` 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 ` 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 ` Kohei Tarumizu 2021-11-04 5:21 ` [RFC PATCH v2 3/5] driver: hwpf: Add support for Intel " Kohei Tarumizu 2021-11-04 5:21 ` Kohei Tarumizu 2021-11-08 1:51 ` Dave Hansen 2021-11-08 1:51 ` Dave Hansen 2021-11-09 9:44 ` tarumizu.kohei 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 ` Kohei Tarumizu 2021-11-04 5:21 ` [RFC PATCH v2 5/5] docs: ABI: Add sysfs documentation interface of " Kohei Tarumizu 2021-11-04 5:21 ` Kohei Tarumizu 2021-11-04 14:55 ` Dave Hansen 2021-11-04 14:55 ` Dave Hansen 2021-11-08 1:29 ` tarumizu.kohei 2021-11-08 1:29 ` tarumizu.kohei 2021-11-08 1:49 ` Dave Hansen 2021-11-08 1:49 ` Dave Hansen 2021-11-09 9:41 ` tarumizu.kohei 2021-11-09 9:41 ` tarumizu.kohei 2021-11-09 17:44 ` Dave Hansen 2021-11-09 17:44 ` Dave Hansen 2021-11-10 9:25 ` tarumizu.kohei 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-04 15:13 ` Borislav Petkov 2021-11-08 2:17 ` tarumizu.kohei 2021-11-08 2:17 ` tarumizu.kohei 2021-11-10 8:34 ` Borislav Petkov 2021-11-10 8:34 ` Borislav Petkov 2021-11-18 6:14 ` tarumizu.kohei 2021-11-18 6:14 ` tarumizu.kohei 2021-11-18 7:09 ` tarumizu.kohei 2021-11-18 7:09 ` tarumizu.kohei 2021-12-06 9:30 ` tarumizu.kohei 2021-12-06 9:30 ` tarumizu.kohei 2021-11-04 17:10 ` Peter Zijlstra [this message] 2021-11-04 17:10 ` Peter Zijlstra 2021-11-08 2:36 ` tarumizu.kohei 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=20211104171012.GC174703@worktop.programming.kicks-ass.net \ --to=peterz@infradead.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.