From: Peter Zijlstra <peterz@infradead.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Zide Chen <zide.chen@intel.com>,
Falcon Thomas <thomas.falcon@intel.com>,
Dapeng Mi <dapeng1.mi@intel.com>,
Xudong Hao <xudong.hao@intel.com>
Subject: Re: [Patch v10 00/10] Perf tools: Support eGPRs/SSP/SIMD registers sampling
Date: Thu, 10 Sep 2026 15:44:25 +0200 [thread overview]
Message-ID: <20260910134425.GV776954@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <aqKxtHweUZEdcI_H@x2>
On Thu, Sep 10, 2026 at 10:33:40AM -0300, Arnaldo Carvalho de Melo wrote:
> On Thu, Sep 10, 2026 at 10:59:51AM +0800, Mi, Dapeng wrote:
> > Peter queued the dependent perf patches into the tip perf/core tree.
>
> > https://lore.kernel.org/all/20260824082731.1013973-1-dapeng1.mi@linux.intel.com/
>
> > But since there are UAPI changes, these perf-tools patches would lead to
> > errors without the corresponding perf patches.
>
> > @Arnaldo, @Namhyung, @Ian how would we handle such kind of dependency
> > issues generally? Wait for the dependent perf patches merged into mainline
> > and then merge the perf-tools patches?
>
> That would slow down development, if it made perf kernel upstream, even
> if not yet to Linus, we can update the header in perf-tools-next, the
> check_headers script will warn about it, but now it is not running by
> default so no distracting warning and if when we decide to run it we got
> advanced warning that it will take some time to sort out, i.e. when the
> perf kernel UAPI header hits upstream and perf-tools-next merges with
> it.
>
> So send perf kernel patches to Peter and the tooling ones to me and
> Namhyung.
>
Patches are in tip/perf/core.
next prev parent reply other threads:[~2026-09-10 13:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 7:26 Dapeng Mi
2026-07-21 7:26 ` [Patch v10 01/10] perf dwarf-regs: Fix DWARF register index bounds check Dapeng Mi
2026-07-21 7:26 ` [Patch v10 02/10] perf util: Add missed fields in _attr__fprintf() and __attr_swap() Dapeng Mi
2026-07-21 7:27 ` [Patch v10 03/10] tools headers: Sync x86 headers with kernel sources Dapeng Mi
2026-07-21 7:27 ` [Patch v10 04/10] perf headers: Sync perf_event.h/perf_regs.h with the kernel headers Dapeng Mi
2026-07-21 7:27 ` [Patch v10 05/10] perf regs: Support x86 eGPRs/SSP sampling Dapeng Mi
2026-07-21 7:27 ` [Patch v10 06/10] perf regs: Support x86 SIMD registers sampling Dapeng Mi
2026-07-21 7:27 ` [Patch v10 07/10] perf regs: Enable dumping of SIMD registers Dapeng Mi
2026-07-21 7:27 ` [Patch v10 08/10] perf dwarf-regs: Add SIMD/eGPRs support for x86 DWARF registers Dapeng Mi
2026-07-21 7:27 ` [Patch v10 09/10] perf tests: Add x86 eGPRs/SSP registers sampling test Dapeng Mi
2026-07-21 7:27 ` [Patch v10 10/10] perf tests: Add SIMD " Dapeng Mi
2026-09-10 2:59 ` [Patch v10 00/10] Perf tools: Support eGPRs/SSP/SIMD registers sampling Mi, Dapeng
2026-09-10 6:37 ` Mi, Dapeng
2026-09-10 13:33 ` Arnaldo Carvalho de Melo
2026-09-10 13:44 ` Peter Zijlstra [this message]
2026-09-11 0:36 ` Mi, Dapeng
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=20260910134425.GV776954@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dapeng1.mi@intel.com \
--cc=dapeng1.mi@linux.intel.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=thomas.falcon@intel.com \
--cc=xudong.hao@intel.com \
--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
all inboxes | Powered by JetHome®