From: "Kip Walker" <kwalker@broadcom.com>
To: "Jun Sun" <jsun@mvista.com>
Cc: "Ralf Baechle" <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [pathch] kernel/sched.c bogon?
Date: Thu, 24 Apr 2003 10:03:05 -0700 [thread overview]
Message-ID: <3EA818C9.3E46E560@broadcom.com> (raw)
In-Reply-To: 20030310095907.U26071@mvista.com
Jun Sun wrote:
>
> On Mon, Mar 10, 2003 at 01:55:31PM +0100, Ralf Baechle wrote:
> > On Thu, Mar 06, 2003 at 05:40:01PM -0800, Jun Sun wrote:
> >
> > > I reported this bug last May. Apparently it is still not
> > > taken up-stream. Ralf, why don't we fix it here and push
> > > it up from you?
> > >
> > > BTW, this bug actually has effect on real-time performance under
> > > preemptible kernel.
> >
> > < = 2.4.x preemptible kernel is OPP.
> >
> > > It can delay the execution of the highest
> > > priority real-time process from execution up to 1 jiffy.
> >
> > Quite a number of users get_cycles() in the kernel assume it to return a
> > 64-bit number. I guess we'll have to fake a 64-bit counter in software ...
> >
>
> Whether we fake 64-bit or not, oldest_idle is declared as cycles_t.
> So comparing it with (cycles_t)-1 should be always be correct. And it
> actually makes a correct C program. :-)
>
> I don't see any possible reason for rejecting the change. My previous
> report is probably just lost in the noise.
And once again, the patch hasn't made it in. Can we either apply it get
a good reason not to?
Kip
next prev parent reply other threads:[~2003-04-24 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 1:01 [pathch] kernel/sched.c bogon? Kip Walker
2003-03-07 1:40 ` Jun Sun
2003-03-10 12:55 ` Ralf Baechle
2003-03-10 17:59 ` Jun Sun
2003-04-24 17:03 ` Kip Walker [this message]
2003-04-25 15:28 ` Kip Walker
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=3EA818C9.3E46E560@broadcom.com \
--to=kwalker@broadcom.com \
--cc=jsun@mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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