linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Kohei Tarumizu <tarumizu.kohei@fujitsu.com>
Cc: rafael@kernel.org, peterz@infradead.org, catalin.marinas@arm.com,
	linus.walleij@linaro.org, dave.hansen@linux.intel.com,
	conor.dooley@microchip.com, hpa@zytor.com, will@kernel.org,
	mchehab+huawei@kernel.org, x86@kernel.org, mingo@redhat.com,
	eugenis@google.com, arnd@arndb.de, bp@alien8.de,
	tglx@linutronix.de, pcc@google.com,
	linux-arm-kernel@lists.infradead.org, marcos@orca.pet,
	tony.luck@intel.com, marcan@marcan.st,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 6/8] x86: Add hardware prefetch control support for x86
Date: Wed, 18 May 2022 08:44:48 +0200	[thread overview]
Message-ID: <YoSV4CPBXbNlj0Cq@kroah.com> (raw)
In-Reply-To: <20220518063032.2377351-7-tarumizu.kohei@fujitsu.com>

On Wed, May 18, 2022 at 03:30:30PM +0900, Kohei Tarumizu wrote:
> Adds module init/exit code to create sysfs attributes for x86 with
> "hardware_prefetcher_enable", "ip_prefetcher_enable" and
> "adjacent_cache_line_prefetcher_enable".
> 
> This driver works only if a CPU model is mapped to type of register
> specification(e.g. TYPE_L12_BASE) in pfctl_match[].

How will the driver be automatically loaded if this is the case or not?
You can not rely on userspace knowing to load a driver on its own,
please tie into the proper device discovery.

thanks,

greg k-h

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-05-18  6:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18  6:30 [PATCH v4 0/8] Add hardware prefetch control driver for A64FX and x86 Kohei Tarumizu
2022-05-18  6:30 ` [PATCH v4 1/8] drivers: base: Add hardware prefetch control core driver Kohei Tarumizu
2022-05-18  7:09   ` Greg KH
2022-05-18 12:38     ` tarumizu.kohei
2022-05-18  6:30 ` [PATCH v4 2/8] drivers: base: Add Kconfig/Makefile to build " Kohei Tarumizu
2022-05-18  7:04   ` Greg KH
2022-05-20  6:42     ` tarumizu.kohei
2022-05-18  6:30 ` [PATCH v4 3/8] soc: fujitsu: Add hardware prefetch control support for A64FX Kohei Tarumizu
2022-05-18  7:10   ` Greg KH
2022-05-20  7:06     ` tarumizu.kohei
2022-05-18  6:30 ` [PATCH v4 4/8] soc: fujitsu: Add Kconfig/Makefile to build hardware prefetch control driver Kohei Tarumizu
2022-05-18  6:30 ` [PATCH v4 5/8] arm64: Create cache sysfs directory without ACPI PPTT for hardware prefetch control Kohei Tarumizu
2022-05-18  7:09   ` Greg KH
2022-05-20  7:00     ` tarumizu.kohei
2022-05-18  6:30 ` [PATCH v4 6/8] x86: Add hardware prefetch control support for x86 Kohei Tarumizu
2022-05-18  6:43   ` Greg KH
2022-05-20  6:30     ` tarumizu.kohei
2022-05-18  6:44   ` Greg KH [this message]
2022-05-20  6:40     ` tarumizu.kohei
2022-05-18  6:30 ` [PATCH v4 7/8] x86: Add Kconfig/Makefile to build hardware prefetch control driver Kohei Tarumizu
2022-05-18  6:43   ` Greg KH
2022-05-20  6:35     ` tarumizu.kohei
2022-05-18  6:30 ` [PATCH v4 8/8] docs: ABI: Add sysfs documentation interface of " Kohei Tarumizu
2022-05-19  8:29 ` [PATCH v4 0/8] Add hardware prefetch control driver for A64FX and x86 Hector Martin
2022-05-20  8:31   ` 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=YoSV4CPBXbNlj0Cq@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=conor.dooley@microchip.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=eugenis@google.com \
    --cc=hpa@zytor.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcan@marcan.st \
    --cc=marcos@orca.pet \
    --cc=mchehab+huawei@kernel.org \
    --cc=mingo@redhat.com \
    --cc=pcc@google.com \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=tarumizu.kohei@fujitsu.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --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).