From: Peter Zijlstra <peterz@infradead.org>
To: Puranjay Mohan <puranjay12@gmail.com>
Cc: skhan@linuxfoundation.org, Ingo Molnar <mingo@redhat.com>,
"open list:SCHEDULER" <linux-kernel@vger.kernel.org>,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] Sched: Change type of 'overrun' from int to u64
Date: Fri, 5 Jul 2019 13:52:12 +0200 [thread overview]
Message-ID: <20190705115212.GT3402@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190705085609.24453-1-puranjay12@gmail.com>
On Fri, Jul 05, 2019 at 02:26:09PM +0530, Puranjay Mohan wrote:
> Callers of hrtimer_forward_now() should save the return value in u64.
> function sched_rt_period_timer() stores
> it in variable 'overrun' of type int
> change type of overrun from int to u64 to solve the issue.
Is there an actual issue? If we've missed _that_ many periods, something
is really buggered.
From a code consistency PoV this patch makes sense, but I don't think
there anything really wrong with the current code.
> Signed-off-by: Puranjay Mohan <puranjay12@gmail.com>
> ---
> kernel/sched/rt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
> index 1e6b909dca36..f5d3893914f5 100644
> --- a/kernel/sched/rt.c
> +++ b/kernel/sched/rt.c
> @@ -19,7 +19,7 @@ static enum hrtimer_restart sched_rt_period_timer(struct hrtimer *timer)
> struct rt_bandwidth *rt_b =
> container_of(timer, struct rt_bandwidth, rt_period_timer);
> int idle = 0;
> - int overrun;
> + u64 overrun;
>
> raw_spin_lock(&rt_b->rt_runtime_lock);
> for (;;) {
> --
> 2.21.0
>
next prev parent reply other threads:[~2019-07-05 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 8:56 Puranjay Mohan
2019-07-05 11:52 ` Peter Zijlstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-18 16:59 Puranjay Mohan
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=20190705115212.GT3402@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=puranjay12@gmail.com \
--cc=skhan@linuxfoundation.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
Powered by JetHome