summaryrefslogtreecommitdiffstats
path: root/lib/libarchive
diff options
context:
space:
mode:
authormarius <marius@FreeBSD.org>2008-09-03 17:39:19 +0000
committermarius <marius@FreeBSD.org>2008-09-03 17:39:19 +0000
commita030d21a6ff5f8342f1faed5ca24f25ad37944f8 (patch)
tree4ee9a429ab0d10c1eb85191073e29aeae98587e6 /lib/libarchive
parentb31f010c0be48005fd17b9bd3cb76c5c91d0a4da (diff)
downloadFreeBSD-src-a030d21a6ff5f8342f1faed5ca24f25ad37944f8.zip
FreeBSD-src-a030d21a6ff5f8342f1faed5ca24f25ad37944f8.tar.gz
- USIII-based machines can consist of CPUs running at different
frequencies (and having different cache sizes) so use the STICK (System TICK) timer, which was introduced due to this and is driven by the same frequency across all CPUs, instead of the TICK timer, whose frequency varies with the CPU clock, to drive hardclock. We try to use the STICK counter with all CPUs that are USIII or beyond, even when not necessary due to identical CPUs, as we can can also avoid the workaround for the BlackBird erratum #1 there. Unfortunately, using the STICK counter currently causes a hang with USIIIi MP machines for reasons unknown, so we still use the TICK timer there (which is okay as they can only consist of identical CPUs). - Given that we only (try to) synchronize the (S)TICK timers of APs with the BSP during startup, we could end up spinning forever in DELAY(9) if that function is migrated to another CPU while we're spinning due to clock drift afterwards, so pin to the CPU in order to avoid migration. Unfortunately, pinning doesn't work at the point DELAY(9) is required by the low-level console drivers, yet, so switch to a function pointer, which is updated accordingly, for implementing DELAY(9). For USIII and beyond, this would also allow to easily use the STICK counter instead of the TICK one here, there's no benefit in doing so however. While at it, use cpu_spinwait(9) for spinning in the delay- functions. This currently is a NOP though. - Don't set the TICK timer of the BSP to 0 during at startup as there's no need to do so. - Implement cpu_est_clockrate(). - Unfortunately, USIIIi-based machines don't provide a timecounter device besides the STICK and TICK counters (well, in theory the Tomatillo bridges have a performance counter that can be (ab)used as timecounter by configuring it to count bus cycles, though unlike the performance counter of Schizo bridges, the Tomatillo one is broken and counts Sun knows what in this mode). This means that we've to use a (S)TICK counter for timecounting, which has the old problem of not being in sync across CPUs, so provide an additional timecounter function which binds itself to the BSP but has an adequate low priority.
Diffstat (limited to 'lib/libarchive')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud