From: peterz@infradead.org (Peter Zijlstra)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] sched: Fix the irqtime code to deal with u64 wraps
Date: Sat, 11 Dec 2010 10:55:52 +0100 [thread overview]
Message-ID: <1292061352.13513.191.camel@laptop> (raw)
In-Reply-To: <alpine.LFD.2.00.1012102116540.10437@xanadu.home>
On Fri, 2010-12-10 at 21:23 -0500, Nicolas Pitre wrote:
> On Fri, 10 Dec 2010, Peter Zijlstra wrote:
>
> > OK, so here's the latest version, using fancy __this_cpu thingies.
> >
> > I started a new thread since the old one was quite unwieldy.
> >
> > Now, admittedly this patch is a tad large, esp for -rc5. So either we
> > need lots of Reviewed-by and such or I need to shrink this patch
> > somehow.
> >
> >
> > ---
> > Subject: sched: Fix the irqtime code to deal with u64 wraps
> > From: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > Date: Thu Dec 09 14:15:34 CET 2010
> >
> > ARM systems have a 32bit sched_clock() [ which needs to be fixed ],
> > but this exposed a bug in the irq_time code as well, it doesn't deal
> > with wraps at all.
> [...]
>
> That would be more close to reality if you stated "Some ARM systems have
> a 32bit sched_clock() [" above. Most ARM systems in use today have a
> sched_clock() with more than 32 bits, like 55 bits or so.
OK, I'll rephrase.
next prev parent reply other threads:[~2010-12-11 9:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 20:38 [PATCH] sched: Fix the irqtime code to deal with u64 wraps Peter Zijlstra
2010-12-10 22:09 ` Venkatesh Pallipadi
2010-12-13 12:13 ` [PATCH 1/2] " Peter Zijlstra
2010-12-15 18:16 ` Venkatesh Pallipadi
2010-12-15 18:24 ` Peter Zijlstra
2010-12-13 12:13 ` [PATCH 2/2] sched: Fix the irqtime code for 32bit Peter Zijlstra
2010-12-11 2:23 ` [PATCH] sched: Fix the irqtime code to deal with u64 wraps Nicolas Pitre
2010-12-11 9:55 ` Peter Zijlstra [this message]
2010-12-12 13:03 ` Mikael Pettersson
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=1292061352.13513.191.camel@laptop \
--to=peterz@infradead.org \
--cc=linux-arm-kernel@lists.infradead.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