From: Peter Zijlstra <peterz@infradead.org>
To: kan.liang@linux.intel.com
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
namhyung@kernel.org, eranian@google.com, irogers@google.com,
gmx@google.com, acme@kernel.org, jolsa@redhat.com,
ak@linux.intel.com, benh@kernel.crashing.org, paulus@samba.org,
mpe@ellerman.id.au
Subject: Re: [PATCH V2 3/3] perf: Optimize sched_task() in a context switch
Date: Wed, 2 Dec 2020 11:26:09 +0100 [thread overview]
Message-ID: <20201202102609.GO3092@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20201201172903.GT3040@hirez.programming.kicks-ass.net>
On Tue, Dec 01, 2020 at 06:29:03PM +0100, Peter Zijlstra wrote:
> +static void context_sched_task(struct perf_cpu_context *cpuctx,
> + struct perf_event_context *ctx,
> + bool sched_in)
> +{
> + struct pmu *pmu = ctx->pmu;
> +
> + if (cpuctx->sched_cb_dir[sched_in] && pmu->sched_task)
> + pmu->sched_task(ctx, false);
> +}
s/false/sched_in/
next prev parent reply other threads:[~2020-12-02 10:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 19:38 [PATCH V2 1/3] perf/core: Flush PMU internal buffers for per-CPU events kan.liang
2020-11-30 19:38 ` [PATCH V2 2/3] perf/x86/intel: Set PERF_ATTACH_SCHED_CB for large PEBS and LBR kan.liang
2021-03-01 10:16 ` [tip: perf/urgent] " tip-bot2 for Kan Liang
2021-03-06 11:54 ` tip-bot2 for Kan Liang
2020-11-30 19:38 ` [PATCH V2 3/3] perf: Optimize sched_task() in a context switch kan.liang
2020-12-01 17:29 ` Peter Zijlstra
2020-12-02 10:26 ` Peter Zijlstra [this message]
2020-12-02 14:40 ` Namhyung Kim
2020-12-04 7:14 ` Namhyung Kim
2020-12-10 7:13 ` Namhyung Kim
2020-12-10 13:52 ` Liang, Kan
2020-12-10 14:25 ` Peter Zijlstra
2021-01-18 7:04 ` Namhyung Kim
2021-01-27 4:41 ` Namhyung Kim
2021-02-22 9:46 ` Namhyung Kim
2020-12-01 17:21 ` [PATCH V2 1/3] perf/core: Flush PMU internal buffers for per-CPU events Peter Zijlstra
2021-03-01 10:16 ` [tip: perf/urgent] " tip-bot2 for Kan Liang
2021-03-06 11:54 ` tip-bot2 for Kan Liang
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=20201202102609.GO3092@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=benh@kernel.crashing.org \
--cc=eranian@google.com \
--cc=gmx@google.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
/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;
as well as URLs for NNTP newsgroup(s).