From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: Zide Chen <zide.chen@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
Eranian Stephane <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH V2 0/7] perf/x86/intel/uncore: Bug fixes and cleanups
Date: Wed, 27 May 2026 13:17:28 +0800 [thread overview]
Message-ID: <22cb9525-3cdd-4962-bc98-d9e905f195ab@linux.intel.com> (raw)
In-Reply-To: <20260526211846.121640-1-zide.chen@intel.com>
Seems only cover letter is here. Where are the patches?
On 5/27/2026 5:18 AM, Zide Chen wrote:
> This series includes bug fixes and cleanups for the Intel uncore PMU
> driver.
>
> - Patch 1 fixes a theoretical bug in discovery unit lookup on multi-die
> systems.
> - Patch 2 guards against an invalid box control address.
> - Patch 3 fixes a PCI device refcount leak in UPI topology discovery.
> - Patch 4 works around a hardware issue on Raptor Cove CPUs.
> - Patches 5-7 implement a global MSR init callback for GNR/GRR/SRF/CWF
> uncore.
>
> Changes in v2:
> - Add patch 2 to guard against invalid box control address (Sashiko)
> - Remove WARN_ON_ONCE() from patch 1
> - Move cpus_read_{lock,unlock}() out of uncore_die_to_cpu() (Sashiko)
>
> Zide Chen (7):
> perf/x86/intel/uncore: Fix discovery unit lookup for multi-die systems
> perf/x86/intel/uncore: Guard against invalid box control address
> perf/x86/intel/uncore: Fix PCI device refcount leak in UPI discovery
> perf/x86/intel/uncore: Defer ADL global PMON enable to enable_box()
> perf/x86/intel/uncore: Move die_to_cpu() to uncore.c
> perf/x86/intel/uncore: Fix uncore_die_to_cpu() for offline dies
> perf/x86/intel/uncore: Implement global init callback for GNR uncore
>
> arch/x86/events/intel/uncore.c | 32 ++++++++++++++++++-
> arch/x86/events/intel/uncore.h | 3 +-
> arch/x86/events/intel/uncore_discovery.c | 40 +++++++++++++++++-------
> arch/x86/events/intel/uncore_snb.c | 7 -----
> arch/x86/events/intel/uncore_snbep.c | 36 +++++++--------------
> 5 files changed, 74 insertions(+), 44 deletions(-)
>
next prev parent reply other threads:[~2026-05-27 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 21:18 [PATCH V2 0/7] perf/x86/intel/uncore: Bug fixes and cleanups Zide Chen
2026-05-27 5:17 ` Mi, Dapeng [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-27 15:14 Zide Chen
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=22cb9525-3cdd-4962-bc98-d9e905f195ab@linux.intel.com \
--to=dapeng1.mi@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=zide.chen@intel.com \
/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