From: Peter Zijlstra <peterz@infradead.org>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>,
Ian Rogers <irogers@google.com>,
Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Subject: Re: [PATCH 3/5] perf: Add pmu get/put
Date: Thu, 31 Oct 2024 10:45:51 +0100 [thread overview]
Message-ID: <20241031094551.GT14555@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <kouwyypgqthwklgdlckavoasu3bbjmustsxp3sncztztijmykd@djnbwa4sm4wz>
On Thu, Oct 31, 2024 at 12:07:42AM -0500, Lucas De Marchi wrote:
> On Wed, Oct 23, 2024 at 12:07:58AM -0500, Lucas De Marchi wrote:
> > On Tue, Oct 22, 2024 at 11:52:10PM +0200, Peter Zijlstra wrote:
> > > On Fri, Oct 18, 2024 at 02:46:31PM -0500, Lucas De Marchi wrote:
> > >
> > > > I will give this a try with i915 and/or xe.
> > >
> > > Less horrible version here:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git perf/pmu-unregister
> > >
> > > I've just pushed it out to the robots, but it builds, passes perf test
> > > and your dummy_pmu testcase (for me, on my one testbox and .config
> > > etc..)
> >
> > It passed for me as well with both dummy_pmu and with i915. I have some
> > changes to igt (i915/xe testsuite) that should bring some more coverage.
> > I minimized the pending test changes I had and posted to trigger CI:
> >
> > https://patchwork.freedesktop.org/series/140355/
>
> Our CI also didn't trigger that pmu issue and the test could run
> succesfully.
Excellent.
> I did get a report from kernel test robot though:
>
> https://lore.kernel.org/all/202410281436.8246527d-lkp@intel.com/
Yeah, I think I fixed that one, but the robot gifted me another one that
I still need to find time to address. I'm hoping this weel.
I'll repost properly once I fix it.
Thanks!
next prev parent reply other threads:[~2024-10-31 9:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 18:34 [PATCH 0/5] perf: Fix pmu for drivers with bind/unbind Lucas De Marchi
2024-10-08 18:34 ` [PATCH 1/5] perf: Add dummy pmu module Lucas De Marchi
2024-10-15 0:26 ` Jeff Johnson
2024-10-15 4:23 ` Lucas De Marchi
2024-10-16 8:51 ` Peter Zijlstra
2024-10-18 19:30 ` Lucas De Marchi
2024-10-08 18:34 ` [PATCH 2/5] perf: Move free outside of the mutex Lucas De Marchi
2024-10-08 18:34 ` [PATCH 3/5] perf: Add pmu get/put Lucas De Marchi
2024-10-09 10:44 ` kernel test robot
2024-10-14 17:32 ` Peter Zijlstra
2024-10-14 18:20 ` Lucas De Marchi
2024-10-14 19:25 ` Peter Zijlstra
2024-10-14 20:12 ` Lucas De Marchi
2024-10-16 12:03 ` Peter Zijlstra
2024-10-18 19:46 ` Lucas De Marchi
2024-10-22 21:52 ` Peter Zijlstra
2024-10-23 5:07 ` Lucas De Marchi
2024-10-31 5:07 ` Lucas De Marchi
2024-10-31 9:45 ` Peter Zijlstra [this message]
2024-10-08 18:35 ` [PATCH 4/5] perf/dummy_pmu: Tie pmu to device lifecycle Lucas De Marchi
2024-10-08 18:35 ` [PATCH 5/5] perf/dummy_pmu: Track and disable active events Lucas De Marchi
2024-10-11 22:21 ` [PATCH 0/5] perf: Fix pmu for drivers with bind/unbind Umesh Nerlige Ramappa
2024-10-11 23:03 ` Lucas De Marchi
2024-10-11 22:59 ` 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=20241031094551.GT14555@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=mingo@redhat.com \
--cc=tvrtko.ursulin@igalia.com \
--cc=umesh.nerlige.ramappa@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®