summaryrefslogtreecommitdiffstats
path: root/secure/lib/libcrypto/Makefile
diff options
context:
space:
mode:
authorgibbs <gibbs@FreeBSD.org>2010-08-12 19:50:40 +0000
committergibbs <gibbs@FreeBSD.org>2010-08-12 19:50:40 +0000
commitf5039e4d7d8e1560261d601afb862ce88acf3322 (patch)
tree16218c233f1d4bac63d2bd0006c4445738e01ce0 /secure/lib/libcrypto/Makefile
parent2ac8e0568d718056f6f7f95a62d8fbde0585bf1b (diff)
downloadFreeBSD-src-f5039e4d7d8e1560261d601afb862ce88acf3322.zip
FreeBSD-src-f5039e4d7d8e1560261d601afb862ce88acf3322.tar.gz
Allow interrupt driven config hooks to be registered from config hook callbacks.
Interrupt driven configuration hooks serve two purposes: they are a mechanism for registering for a callback that is invoked once interrupt services are available, and they hold off root device selection so long as any configuration hooks are still active. Before this change, it was not possible to safely register additional hooks from the context of a configuration hook callback. The need for this feature arises when interrupts are required to discover new devices (e.g. access to the XenStore to find para-virtualized devices) which in turn also require the ability to hold off root device selection until some lengthy, interrupt driven, configuration task has completed (e.g. Xen front/back device driver negotiation). More specifically, the mutex protecting the list of active configuration hooks is never held during a callback, and static information is used to ensure proper ordering and only a single callback to each hook even when faced with registration or removal of a hook during an active run. Sponsored by: Spectra Logic Corporation MFC after: 1 week.
Diffstat (limited to 'secure/lib/libcrypto/Makefile')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud