From: Dave Hansen <dave.hansen@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
linux-perf-users@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Cc: dave.hansen@linux.intel.com, Zhang Rui <rui.zhang@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Ulisses Furquim <ulisses.furquim@intel.com>,
intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] perf/x86/rapl: Fix PP1 event for Intel Meteor/Lunar Lake
Date: Thu, 20 Feb 2025 08:28:01 -0800 [thread overview]
Message-ID: <d25ef356-3614-4e69-8cc1-d74dbbd2585f@intel.com> (raw)
In-Reply-To: <20250220153857.2593704-6-lucas.demarchi@intel.com>
On 2/20/25 07:36, Lucas De Marchi wrote:
> On some boots the read of MSR_PP1_ENERGY_STATUS msr returns 0, causing
> perf_msr_probe() to make the power/events/energy-gpu event non-visible.
> When that happens, the msr always read 0 until the graphics module (i915
> for Meteor Lake, xe for Lunar Lake) is loaded. Then it starts returning
> something different and re-loading the rapl module "fixes" it.
What's the root cause here? Did the kernel do something funky? Or is
this a hardware bug?
next prev parent reply other threads:[~2025-02-20 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 15:36 [PATCH] perf/x86/rapl: Fix PP1 event for Intel Meteor/Lunar Lake Lucas De Marchi
2025-02-20 16:28 ` Dave Hansen [this message]
2025-02-20 18:27 ` Lucas De Marchi
2025-02-20 18:53 ` Dave Hansen
2025-02-20 16:47 ` Liang, Kan
2025-02-20 18:30 ` Lucas De Marchi
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=d25ef356-3614-4e69-8cc1-d74dbbd2585f@intel.com \
--to=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rui.zhang@intel.com \
--cc=ulisses.furquim@intel.com \
--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