[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YwOgxhfS99Rquwct@worktop.programming.kicks-ass.net>
Date: Mon, 22 Aug 2022 17:29:10 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Ravi Bangoria <ravi.bangoria@....com>
Cc: acme@...nel.org, alexander.shishkin@...ux.intel.com,
jolsa@...hat.com, namhyung@...nel.org, songliubraving@...com,
eranian@...gle.com, alexey.budankov@...ux.intel.com,
ak@...ux.intel.com, mark.rutland@....com, megha.dey@...el.com,
frederic@...nel.org, maddy@...ux.ibm.com, irogers@...gle.com,
kim.phillips@....com, linux-kernel@...r.kernel.org,
santosh.shukla@....com
Subject: Re: [RFC v2] perf: Rewrite core context handling
On Tue, Aug 02, 2022 at 11:41:42AM +0530, Ravi Bangoria wrote:
>
> > pulling up the ctx->mutex makes things simpler, but also violates the
> > locking order vs exec_update_lock.
> >
> > Pull that lock up as well...
>
> I'm not able to apply this patch as is but I get the idea. Few
> questions below...
I was just about to rebase the 'series' to current, let me do that and
get back to you on the specifics.
Powered by blists - more mailing lists