linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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 3/5] driver: hwpf: Add support for Intel to hardware prefetch driver
Date: Sun, 7 Nov 2021 17:51:00 -0800	[thread overview]
Message-ID: <664cf198-55b9-469f-ebdd-c8fb436544d5@intel.com> (raw)
In-Reply-To: <20211104052122.553868-4-tarumizu.kohei@fujitsu.com>

On 11/3/21 10:21 PM, Kohei Tarumizu wrote:
> +enum register_type __init get_register_type(void)
> +{
> +	if (boot_cpu_data.x86_vendor != X86_VENDOR_INTEL)
> +		return REGISTER_TYPE_NONE;
> +
> +	switch (boot_cpu_data.x86_model) {
> +	/*
> +	 * Note: In addition to BROADWELL, NEHALEM and others have same register
> +	 * specifications as REGISTER_TYPE_BROADWELL. If you want to add support
> +	 * for these processor, add the target model case here.
> +	 */
> +	case INTEL_FAM6_BROADWELL_X:
> +		return REGISTER_TYPE_BROADWELL;
> +	default:
> +		return REGISTER_TYPE_NONE;
> +	}
> +}

Can you do this with a struct and x86_match_cpu() instead?

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

  reply	other threads:[~2021-11-08  1:52 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 [this message]
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
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=664cf198-55b9-469f-ebdd-c8fb436544d5@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;
as well as URLs for NNTP newsgroup(s).