[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Using %stick where available
-----BEGIN PGP SIGNED MESSAGE-----
On Nov 6, 2012, at 9:49 PM, Erik Fair wrote:
On Nov 6, 2012, at 18:37, Michael wrote:
Good question, I didn't do any measurements other than 'looks ok to
I think there's a bug in the code that's supposed to synchronize
the CPUs' time bases - that could cause crap you'd call 'terrible
timekeeping', like the clock appearing to jump back and forth semi-
randomly ( whenever you hop to a different CPU )
Keeping them in sync should be much easier with the time base
running at only 12MHz though.
I have a dual core HP Microserver N40L (AMD Turion II Neo) that
keeps quite good time, even when not using the HPET device, which
suggests that the amd64 port has the problem of which CPU to get
time from solved.
Well, the problem isn't exactly difficult. If it is what I think it is
it's only one extra, unnecessary settick(0) on the boot CPU which
happens when initializing the timecounter, some time after syncing
time bases on SMP boxes.
I guess I need to test the patches on my v240 ...
Please do. It's likely to have the same problem though, so as long as
it's not getting worse we're doing good.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: GPGTools - http://gpgtools.org
-----END PGP SIGNATURE-----
Main Index |
Thread Index |