public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: "Liang, Kan" <kan.liang@linux.intel.com>,
	Ingo Molnar <mingo@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ravi Bangoria <ravi.bangoria@amd.com>,
	Stephane Eranian <eranian@google.com>,
	Ian Rogers <irogers@google.com>,
	Mingwei Zhang <mizhang@google.com>
Subject: Re: [PATCH v2] perf/core: Optimize event reschedule for a PMU
Date: Mon, 5 Aug 2024 11:05:58 +0200	[thread overview]
Message-ID: <20240805090558.GI37996@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CAM9d7cgNZQrJk7-TnMgqvCMpkYkcpBT78Ts_5oTsAzNB9gp+_w@mail.gmail.com>

On Sat, Aug 03, 2024 at 10:08:32AM -0700, Namhyung Kim wrote:

> > @@ -2802,9 +2821,10 @@ static int  __perf_install_in_context(void *info)
> >  #endif
> >
> >         if (reprogram) {
> > -               ctx_sched_out(ctx, EVENT_TIME);
> > +               ctx_update_time(cpuctx, ctx);
> 
> So you don't want to stop the context time while adding or enabling a new
> event, right?  Then I'm not sure if it's needed to update the time here as
> it'll be updated in the ctx_sched_out() again.
> 
> Also calling ctx_sched_out() will clear EVENT_TIME when is_active has
> no EVENT_ALL and it'll stop the context time anyway, right?
> 

Hmm, I knew I was missing something. Let me ponder rhat a bit more, and
maybe read some of the history on this thing back to remember what exact
issue was being fixed here.

> 
> 
> >                 add_event_to_ctx(event, ctx);
> > -               ctx_resched(cpuctx, task_ctx, get_event_type(event));
> > +               ctx_resched(cpuctx, task_ctx, event->pmu_ctx->pmu,
> > +                           get_event_type(event));
> >         } else {
> >                 add_event_to_ctx(event, ctx);
> >         }

  parent reply	other threads:[~2024-08-05  9:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31  0:06 [PATCH v2] perf/core: Optimize event reschedule for a PMU Namhyung Kim
2024-08-02 17:39 ` Namhyung Kim
2024-08-02 18:30 ` Liang, Kan
2024-08-02 18:38   ` Peter Zijlstra
2024-08-02 18:43     ` Peter Zijlstra
2024-08-02 18:50       ` Peter Zijlstra
2024-08-02 19:11         ` Peter Zijlstra
2024-08-02 19:31           ` Liang, Kan
2024-08-02 19:32           ` Namhyung Kim
2024-08-03 10:32           ` Peter Zijlstra
2024-08-03 17:08             ` Namhyung Kim
2024-08-05  6:39               ` Namhyung Kim
2024-08-05  9:15                 ` Peter Zijlstra
2024-08-05  9:05               ` Peter Zijlstra [this message]
2024-08-05  9:20   ` Peter Zijlstra
2024-08-05 14:58     ` Peter Zijlstra
2024-08-06  6:19       ` Namhyung Kim
2024-08-06  7:56         ` Peter Zijlstra
2024-08-06  8:07           ` Peter Zijlstra
2024-08-06 19:29             ` Namhyung Kim
2024-08-06 13:54       ` Liang, Kan

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=20240805090558.GI37996@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@kernel.org \
    --cc=mizhang@google.com \
    --cc=namhyung@kernel.org \
    --cc=ravi.bangoria@amd.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