From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Avi Kivity <avi@redhat.com>, Ingo Molnar <mingo@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andi Kleen <ak@linux.intel.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH RFC] sched: add notifier for process migration
Date: Wed, 14 Oct 2009 09:05:08 +0200 [thread overview]
Message-ID: <20091014070508.GI784@elte.hu> (raw)
In-Reply-To: <4AD4F02C.9060203@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> @@ -1981,6 +1989,12 @@ void set_task_cpu(struct task_struct *p, unsigned int new_cpu)
> #endif
> perf_swcounter_event(PERF_COUNT_SW_CPU_MIGRATIONS,
> 1, 1, NULL, 0);
> +
> + tmn.task = p;
> + tmn.from_cpu = old_cpu;
> + tmn.to_cpu = new_cpu;
> +
> + atomic_notifier_call_chain(&task_migration_notifier, 0, &tmn);
We already have one event notifier there - look at the
perf_swcounter_event() callback. Why add a second one for essentially
the same thing?
We should only put a single callback there - a tracepoint defined via
TRACE_EVENT() - and any secondary users can register a callback to the
tracepoint itself.
There's many similar places in the kernel - with notifier chains and
also with a need to get tracepoints there. The fastest (and most
consistent) solution is to add just a single event callback facility.
Ingo
next prev parent reply other threads:[~2009-10-14 7:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 21:01 [PATCH RFC] sched: add notifier for process migration Jeremy Fitzhardinge
2009-10-09 22:02 ` Peter Zijlstra
2009-10-09 22:43 ` Jeremy Fitzhardinge
2009-10-10 7:14 ` Peter Zijlstra
2009-10-10 9:05 ` Avi Kivity
2009-10-10 9:24 ` Peter Zijlstra
2009-10-10 9:36 ` Jeremy Fitzhardinge
2009-10-10 10:12 ` Peter Zijlstra
2009-10-13 21:25 ` Jeremy Fitzhardinge
2009-10-14 7:05 ` Ingo Molnar [this message]
2009-10-14 9:26 ` Peter Zijlstra
2009-10-14 10:37 ` Avi Kivity
2009-10-14 14:41 ` Jason Baron
2009-10-14 16:15 ` Jeremy Fitzhardinge
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=20091014070508.GI784@elte.hu \
--to=mingo@elte.hu \
--cc=ak@linux.intel.com \
--cc=avi@redhat.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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