summaryrefslogtreecommitdiffstats
path: root/sys/geom/raid/g_raid.c
diff options
context:
space:
mode:
authorattilio <attilio@FreeBSD.org>2012-05-03 21:44:01 +0000
committerattilio <attilio@FreeBSD.org>2012-05-03 21:44:01 +0000
commitb8cdf306fdaa71dc249156aac00fb9e58436c014 (patch)
treeae4c799ab9e627a002f079ad6c0ae43852579015 /sys/geom/raid/g_raid.c
parent18b00ce05256ac1bef00083a0ce9a34fcb4c49a9 (diff)
downloadFreeBSD-src-b8cdf306fdaa71dc249156aac00fb9e58436c014.zip
FreeBSD-src-b8cdf306fdaa71dc249156aac00fb9e58436c014.tar.gz
Revert part of r234723 by re-enabling the SMP protection for
intr_bind() on x86. This has been requested by jhb and I strongly disagree with this, but as long as he is the x86 and interrupt subsystem maintainer I will follow his directives. The disagreement cames from what we should really consider as a public KPI. IMHO, if we really need a selection between the kernel functions, we may need an explicit protection like _KERNEL_KPI, which defines which subset of the kernel function might really be considered as part of the KPI (for thirdy part modules) and which not. As long as we don't have this mechanism I just consider any possible function as usable by thirdy part code, thus intr_bind() included. MFC after: 1 week
Diffstat (limited to 'sys/geom/raid/g_raid.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud