[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3f70c656-f583-4360-b321-31a0e92fc844@intel.com>
Date: Thu, 25 Apr 2024 08:49:48 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Tony Luck <tony.luck@...el.com>, Borislav Petkov <bp@...en8.de>,
Thomas Gleixner <tglx@...utronix.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org
Cc: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Namhyung Kim <namhyung@...nel.org>, Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>, "H. Peter Anvin" <hpa@...or.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev
Subject: Re: [PATCH v4 24/71] perf/x86/msr: Switch to new Intel CPU model
defines
On 4/24/24 11:15, Tony Luck wrote:
> @@ -43,75 +43,75 @@ static bool test_intel(int idx, void *data)
> boot_cpu_data.x86 != 6)
> return false;
It arguably makes these easier to review when you _aren't_ removing the
explicit family 6 checks, but what's the plan for these? They can go
away now, right?
Powered by blists - more mailing lists