summaryrefslogtreecommitdiffstats
path: root/sys/nfsclient/nfs_vfsops.c
diff options
context:
space:
mode:
authormarius <marius@FreeBSD.org>2013-03-02 00:37:31 +0000
committermarius <marius@FreeBSD.org>2013-03-02 00:37:31 +0000
commit2774e0404e6c83cc801bf5edbedcb8ceb5ee1e16 (patch)
tree47c03ab3e147cee5fe05e38499fbda5d9143f056 /sys/nfsclient/nfs_vfsops.c
parent24853370053f911de81d645be20801b842a3dda9 (diff)
downloadFreeBSD-src-2774e0404e6c83cc801bf5edbedcb8ceb5ee1e16.zip
FreeBSD-src-2774e0404e6c83cc801bf5edbedcb8ceb5ee1e16.tar.gz
- While Netra X1 generally show no ill effects when registering a power
fail interrupt handler, there seems to be either a broken batch of them or a tendency to develop a defect which causes this interrupt to fire inadvertedly. Given that apart from this problem these machines work just fine, add a tunable allowing the setup of the power fail interrupt to be disabled. While at it, remove the DEBUGGER_ON_POWERFAIL compile time option and make that behavior also selectable via the newly added tunable. - Apparently, it's no longer a problem to call shutdown_nice(9) from within an interrupt filter (some other drivers in the tree do the same). So change the power fail interrupt from an handler in order to simplify the code and get rid of a !INTR_MPSAFE handler. - Use NULL instead of 0 for pointers. MFC after: 1 week
Diffstat (limited to 'sys/nfsclient/nfs_vfsops.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud