From: Thomas Giesel <skoe@directbox.com>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-kernel@vger.kernel.org, Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: rt scheduler may calculate wrong rt_time
Date: Wed, 27 Apr 2011 19:51:13 +0200 [thread overview]
Message-ID: <20110427195113.4e0064bb@acer> (raw)
In-Reply-To: <1303460491.28545.12.camel@marge.simson.net>
> Hm. Does forcing a clock update if we're idle when we release the
> throttle do the trick?
It does. I tested it today and it works as expected. Even with ftrace I
couldn't see any suspicious behaviour anymore.
Mike: Can you send the patch to the right people to get it into the
kernel or should I do it? Or is Peter the right one already?
Thanks for your help.
Thomas
next prev parent reply other threads:[~2011-04-27 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 12:55 rt scheduler may calculate wrong rt_time Thomas Giesel
2011-04-22 8:21 ` Mike Galbraith
2011-04-22 20:52 ` Thomas Giesel
2011-04-27 17:51 ` Thomas Giesel [this message]
2011-04-29 6:36 ` [patch] " Mike Galbraith
2011-05-16 10:37 ` [tip:sched/core] sched, rt: Update rq clock when unthrottling of an otherwise idle CPU tip-bot for Mike Galbraith
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=20110427195113.4e0064bb@acer \
--to=skoe@directbox.com \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.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).