From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Stephen Boyd <sboyd@kernel.org>,
netdev <netdev@vger.kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
John Stultz <john.stultz@linaro.org>,
Jakub Kicinski <kuba@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/3] timekeeping: remove arch_gettimeoffset
Date: Sun, 18 Oct 2020 10:51:38 +0100 [thread overview]
Message-ID: <20201018095137.GV1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <CACRpkdaOuMHfqrToVPRVW1zEYDY6H-gPm1QkR2CydtbLj-7csw@mail.gmail.com>
On Thu, Oct 15, 2020 at 02:38:07PM +0200, Linus Walleij wrote:
> On Thu, Oct 15, 2020 at 11:53 AM Russell King - ARM Linux admin
> <linux@armlinux.org.uk> wrote:
>
> > Don't be misled. It was not a matter of "enough gritty people", it
> > was a matter that EBSA110 was blocking it.
>
> I remember that EBSA110 was quite different in that it had this
> especially limited PIT timer, true that. At one point I even read
> up on the details of it and then forgot them :/
Yes, it was so basic that it required software to reprogram it on every
interrupt - it had no sensible periodic mode. The side effect of which
was that unless done carefully, your timekeeping varied all over the
place (so much that ntpd was not happy.) The final implementation made
ntpd really quite happy on the machine despite the timer's weirdness,
up until Linux stopped allowing interrupts to be nested. At that point,
it was back to utterly crap timekeeping.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
John Stultz <john.stultz@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, netdev <netdev@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/3] timekeeping: remove arch_gettimeoffset
Date: Sun, 18 Oct 2020 10:51:38 +0100 [thread overview]
Message-ID: <20201018095137.GV1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <CACRpkdaOuMHfqrToVPRVW1zEYDY6H-gPm1QkR2CydtbLj-7csw@mail.gmail.com>
On Thu, Oct 15, 2020 at 02:38:07PM +0200, Linus Walleij wrote:
> On Thu, Oct 15, 2020 at 11:53 AM Russell King - ARM Linux admin
> <linux@armlinux.org.uk> wrote:
>
> > Don't be misled. It was not a matter of "enough gritty people", it
> > was a matter that EBSA110 was blocking it.
>
> I remember that EBSA110 was quite different in that it had this
> especially limited PIT timer, true that. At one point I even read
> up on the details of it and then forgot them :/
Yes, it was so basic that it required software to reprogram it on every
interrupt - it had no sensible periodic mode. The side effect of which
was that unless done carefully, your timekeeping varied all over the
place (so much that ntpd was not happy.) The final implementation made
ntpd really quite happy on the machine despite the timer's weirdness,
up until Linux stopped allowing interrupts to be nested. At that point,
it was back to utterly crap timekeeping.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2020-10-18 9:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 15:45 [PATCH 0/3] ARM, timers: ebsa110 cleanup Arnd Bergmann
2020-10-08 15:45 ` Arnd Bergmann
2020-10-08 15:45 ` [PATCH 1/3] ARM: remove ebsa110 platform Arnd Bergmann
2020-10-08 15:45 ` Arnd Bergmann
2020-10-08 15:46 ` [PATCH 2/3] net: remove am79c961a driver Arnd Bergmann
2020-10-08 15:46 ` Arnd Bergmann
2020-10-09 17:40 ` Jakub Kicinski
2020-10-09 17:40 ` Jakub Kicinski
2020-10-08 15:46 ` [PATCH 3/3] timekeeping: remove arch_gettimeoffset Arnd Bergmann
2020-10-08 15:46 ` Arnd Bergmann
2020-10-14 0:41 ` Thomas Gleixner
2020-10-14 0:41 ` Thomas Gleixner
2020-10-15 7:53 ` Linus Walleij
2020-10-15 7:53 ` Linus Walleij
2020-10-15 9:53 ` Russell King - ARM Linux admin
2020-10-15 9:53 ` Russell King - ARM Linux admin
2020-10-15 12:38 ` Linus Walleij
2020-10-15 12:38 ` Linus Walleij
2020-10-18 9:51 ` Russell King - ARM Linux admin [this message]
2020-10-18 9:51 ` Russell King - ARM Linux admin
2020-10-08 15:55 ` [PATCH 0/3] ARM, timers: ebsa110 cleanup Russell King - ARM Linux admin
2020-10-08 15:55 ` Russell King - ARM Linux admin
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=20201018095137.GV1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=davem@davemloft.net \
--cc=john.stultz@linaro.org \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.