From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Mike Galbraith <umgwanakikbuti@gmail.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] sched/rt: don't try to balance rt_runtime when it is futile
Date: Tue, 20 May 2014 18:36:51 +0200 [thread overview]
Message-ID: <20140520163651.GY2485@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <20140520162433.GE17741@localhost.localdomain>
On Tue, May 20, 2014 at 06:24:36PM +0200, Frederic Weisbecker wrote:
> Of course one can argue that we can find out that the task is resuming in userspace from
> CPU 0 scheduler entry without the need for previous context tracking, but I couldn't find safe
> solution for that. This is because probing on user/kernel boundaries can only be done
> in the soft way, throught explicit function calls. So there is an inevitable shift
> between soft and hard boundaries, between what we probe and what we can guess.
you can hook into set_task_cpu(), not sure its going to be pretty, but
that is _the_ place to hook migration related nonsense.
next prev parent reply other threads:[~2014-05-20 16:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 15:08 [PATCH] sched/rt: don't try to balance rt_runtime when it is futile Paul Gortmaker
2014-05-14 15:44 ` Paul E. McKenney
2014-05-14 19:11 ` Paul Gortmaker
2014-05-14 19:27 ` Paul E. McKenney
2014-05-15 2:49 ` Mike Galbraith
2014-05-15 14:09 ` Paul Gortmaker
2014-11-27 9:17 ` Wanpeng Li
2014-11-27 15:31 ` Mike Galbraith
2014-11-27 11:36 ` Wanpeng Li
2014-05-15 3:18 ` Mike Galbraith
2014-05-15 14:45 ` Paul E. McKenney
2014-05-15 17:27 ` Mike Galbraith
2014-05-18 4:22 ` Mike Galbraith
2014-05-18 5:20 ` Paul E. McKenney
2014-05-18 8:36 ` Mike Galbraith
2014-05-18 15:58 ` Paul E. McKenney
2014-05-19 2:44 ` Mike Galbraith
2014-05-19 5:34 ` Paul E. McKenney
2014-05-20 14:53 ` Frederic Weisbecker
2014-05-20 15:53 ` Paul E. McKenney
2014-05-20 16:24 ` Frederic Weisbecker
2014-05-20 16:36 ` Peter Zijlstra [this message]
2014-05-20 17:20 ` Paul E. McKenney
2014-05-21 4:29 ` Mike Galbraith
2014-05-21 4:18 ` Mike Galbraith
2014-05-21 12:03 ` Paul E. McKenney
2014-05-21 3:52 ` Mike Galbraith
2014-05-19 10:54 ` Peter Zijlstra
2014-05-19 12:40 ` Peter Zijlstra
2014-05-22 19:40 ` Paul Gortmaker
2014-11-27 11:21 ` Wanpeng Li
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=20140520163651.GY2485@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.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