From: Richard Zidlicky <rz@linux-m68k.org>
To: john stultz <johnstul@us.ibm.com>
Cc: Dave Jones <davej@suse.de>, lkml <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
george anzinger <george@mvista.com>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [RFC][PATCH] linux-2.5.34_timer-change_A2
Date: Tue, 10 Sep 2002 13:12:43 +0200 [thread overview]
Message-ID: <20020910131242.C960@linux-m68k.org> (raw)
In-Reply-To: <1031604509.24775.206.camel@cog>; from johnstul@us.ibm.com on Mon, Sep 09, 2002 at 01:48:29PM -0700
On Mon, Sep 09, 2002 at 01:48:29PM -0700, john stultz wrote:
> Just a resync/resend:
>
> Hi all,
> Here is my timer-change patch resynced with 2.5.34. As I said
> before, this patch breaks up arch/i386/kernel/time.c into various
> timer_pit, timer_tsc chunks. The hope is to cleanup the existing code so
> it doesn't care what type of clock is providing the high-resolution
> offset for gettimeofday. This will also simplify adding support for my
> cyclone-timer patch as well as ACPI pm timer or any other high res
> counter.
while at it, could we also finaly drop the broken CMOS clock
update "feature" from arch/*/kenrel/time.c?
It was already mentioned a few times on this list and iirc there
was never any argument against removing it.
In short the code does nothing that couldn't be done much better
from userspace, it implements policy that belongs into userspace
and wastes time in an interrupt handler.
At least one architecture has it already completely disabled.
Richard
prev parent reply other threads:[~2002-09-10 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 20:48 [RFC][PATCH] linux-2.5.34_timer-change_A2 john stultz
2002-09-10 11:12 ` Richard Zidlicky [this message]
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=20020910131242.C960@linux-m68k.org \
--to=rz@linux-m68k.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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