From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
irogers@google.com, adrian.hunter@intel.com
Cc: linux-perf-users@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/x86/cstate: Remove unused struct 'perf_cstate_msr'
Date: Mon, 20 May 2024 13:50:16 +0000 [thread overview]
Message-ID: <ZktVGHl5PVd2hAqF@gallifrey> (raw)
In-Reply-To: <20240506004009.770451-1-linux@treblig.org>
* linux@treblig.org (linux@treblig.org) wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
> This looks like it's unused since
> Commit 8f2a28c5859b ("perf/x86/cstate: Use new probe function")
>
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
Ping
> ---
> arch/x86/events/intel/cstate.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/arch/x86/events/intel/cstate.c b/arch/x86/events/intel/cstate.c
> index 326c8cd5aa2d2..dcf3f152a2a64 100644
> --- a/arch/x86/events/intel/cstate.c
> +++ b/arch/x86/events/intel/cstate.c
> @@ -143,12 +143,6 @@ struct cstate_model {
> #define SLM_PKG_C6_USE_C7_MSR (1UL << 0)
> #define KNL_CORE_C6_MSR (1UL << 1)
>
> -struct perf_cstate_msr {
> - u64 msr;
> - struct perf_pmu_events_attr *attr;
> -};
> -
> -
> /* cstate_core PMU */
> static struct pmu cstate_core_pmu;
> static bool has_cstate_core;
> --
> 2.45.0
>
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
prev parent reply other threads:[~2024-05-20 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 0:40 [PATCH] perf/x86/cstate: Remove unused struct 'perf_cstate_msr' linux
2024-05-20 13:50 ` Dr. David Alan Gilbert [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=ZktVGHl5PVd2hAqF@gallifrey \
--to=linux@treblig.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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).