summaryrefslogtreecommitdiffstats
path: root/lib/libc/net/addr2ascii.c
diff options
context:
space:
mode:
authormarius <marius@FreeBSD.org>2006-04-04 21:00:44 +0000
committermarius <marius@FreeBSD.org>2006-04-04 21:00:44 +0000
commit8ea6d154a2636d979bcad320762c6ecb0af4ea1b (patch)
tree9745d193b0a146f8300190b494d7b7f7c3c6260d /lib/libc/net/addr2ascii.c
parent06e487e0f33f00ead0bfc827bf2911db179ef034 (diff)
downloadFreeBSD-src-8ea6d154a2636d979bcad320762c6ecb0af4ea1b.zip
FreeBSD-src-8ea6d154a2636d979bcad320762c6ecb0af4ea1b.tar.gz
For USIII CPUs the type of the trap caused by peeking/poking non-existent
PCI devices apparently was changed from a special deferred trap with TPC pointing to the membar #Sync following the failing load/store instruction to a precise trap with TPC pointing to the failing load/store instruction. Thus remove the check the check whether TPC points to a membar #Sync in case of a data access trap as it's off-by-one for USIII CPUs and it should be sufficient to check whether the trap happend while in fasword*() to properly detect traps caused by peeking/poking. This also corresponds to what other OSs do. Note that also only the USIIi manual suggests to check the TPC for such traps while the USII one doesn't (in the public USIII manual device peeking/poking isn't mentioned at all).
Diffstat (limited to 'lib/libc/net/addr2ascii.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud