| /freebsd/sys/dev/isci/scil/ |
| H A D | scif_io_request.h | 75 * based IO request object (includes core & framework object size).
87 * @param[in] scif_io_request This parameter specifies the framework IO
101 * @note The SCI framework implementation will create an association between
102 * the user IO request object and the framework IO request object.
104 * @param[in] scif_controller the handle to the framework controller object
106 * @param[in] scif_remote_device This parameter specifies the framework
116 * pointer will become the associated object for the framework
119 * to be utilized in the construction of the framework IO request.
139 * associated with the supplied SCI Framework object.
141 * @param[in] scif_io_request This parameter specifies the framework IO
[all …]
|
| H A D | scif_remote_device.h | 61 * by an SCI Framework user on a remote device object. The
62 * framework remote device object provides management of resets for
85 * space for the framework and core device objects.
96 * types in the framework.
100 * the framework construction/destruction methods wrap the core, the
114 * framework device object.
117 * framework remote device.
128 * @brief This method constructs a new framework remote device object. The
133 * the framework construction/destruction methods wrap the core, the
141 * @param[in] remote_device This parameter specifies the framework device
[all …]
|
| H A D | scif_overview.h | 58 @page framework_page SCI Framework
62 The SCI Framework component provides SAS and SATA storage specific abstraction
66 the same SCI Framework with different SCI Core implementations, with the
69 @warning In situations where the SCI framework is utilized, users should NOT
71 framework objects and framework methods. Therefore, if a method is
72 common to both the core and the framework object, do not invoke the
73 core method if utilizing the framework. Some exceptions to this
78 The following is a list of features found in an SCI Framework implementation:
83 -# Automatic Port Configuration (APC). In APC mode the framework will
86 -# Manual Port Configuration (MPC). In MPC mode the framework expects the
[all …]
|
| H A D | scif_library.h | 61 * by an SCI Framework user on the library object. The library is
75 * @brief This method will contsruct the SCI framework library based on the
93 * @brief This method returns the size of the framework library object. The
94 * size of the framework library object includes the associated core
108 * @brief This method will allocate the next available framework controller
109 * object that can be managed by this framework library.
160 * the supplied framework library.
174 * timers required by this framework implementation
185 * timers required by this framework implementation
|
| H A D | scif_controller.h | 73 * @brief This method will attempt to construct a framework controller object
76 * @param[in] library This parameter specifies the handle to the framework
78 * @param[in] controller This parameter specifies the framework controller to
82 * framework controller.
102 * @brief This method will initialize the SCI Framework controller object.
168 * @brief This method will stop an individual framework controller object. This
175 * This method will ensure that all framework IO requests are quiesced
176 * and any additional framework operations are halted.
200 * @brief This method will reset the supplied framework controller regardless
203 * at the actual remote device. However, the framework will
[all …]
|
| H A D | sci_overview.h | 65 -# SCI Framework
96 - SCIF: SCI Framework
122 or Framework.
190 -# Memory Descriptor object methods common to the core and framework.
198 SCI Framework, etc. SCI class methods that MUST NOT be invoked directly
216 Framework library can have it's association set to an operating system
235 situations where the SCI Framework is employed. If the user does not
236 …ociations between objects (i.e. SCIC Library to SCIF Library), then the framework is unable to aut…
237 strongly consider establishing associations between SCI Framework objects and
245 If SCIF is being utilized, then the framework will set the associations
[all …]
|
| H A D | scif_task_request.h | 75 * based task request object (includes core & framework object size).
88 * @note The SCI framework implementation will create an association between
89 * the user task request object and the framework task request object.
91 * @param[in] scif_controller the handle to the framework controller object
93 * @param[in] scif_remote_device This parameter specifies the framework
103 * pointer will become the associated object for the framework
106 * to be utilized in the construction of the framework task request.
|
| H A D | scif_user_callback.h | 61 * be implemented by an SCI Framework user.
119 * @warning All timers in the system started by the SCI Framework are one
122 * Additionally, SCI Framework user's should be able to handle
123 * calls from the SCI Framework to stop a timer that may already
261 * framework, such like scif_cb_domain_change_notification().
647 * that this is an error from the framework.
668 * that this is a warning from the framework.
689 * that this is a debug message from the framework.
712 * framework.
734 * fact that this is an error from the framework.
[all …]
|
| /freebsd/share/man/man9/ |
| H A D | mac.9 | 39 .Nd TrustedBSD Mandatory Access Control framework
51 mandatory access control framework permits dynamically
55 The framework provides a series of entry points which must be called by
58 The framework then calls out to security modules to offer them the
63 .Ss Kernel Objects Supported by the Framework
64 The MAC framework manages labels on a variety of types of in-kernel
85 framework and modules may retrieve security labels and attributes from the
102 permitting the framework to avoid calling into the module.
121 inappropriately calling back into the MAC framework: the framework
140 framework, and modifying appropriate modules to take advantage of
[all …]
|
| H A D | kern_testfrwk.9 | 29 .Nd A kernel testing framework
44 If so, then the kernel test framework is just what you are looking for.
47 There are two components to the system: the test framework and your test.
52 The test you write should have a dependency on the test framework.
57 The framework itself is in
58 .Pa sys/tests/framework/kern_testfrwk.c .
61 The idea is pretty simple; you load the test framework and then load your test.
63 When your test loads, you register your tests with the kernel test framework.
86 int tot_threads_running; /* Private to framework */
99 The framework will start the requested number of kernel threads, all running
[all …]
|
| H A D | crypto_driver.9 | 90 to register with the cryptographic framework.
99 the cryptographic framework.
120 unregisters a driver from the cryptographic framework.
130 is invoked by the cryptographic framework on each active driver to
140 The framework prefers drivers with the largest negative value,
157 Once the framework has chosen a driver for a session,
158 the framework invokes the
162 the framework allocates a per-session driver-specific data structure.
181 and freed by the framework after this method returns.
197 The request will be queued by the framework and retried once the
[all …]
|
| H A D | crypto.9 | 28 is a framework for in-kernel cryptography.
49 describes the interfaces drivers use to register with the framework,
50 helper routines the framework provides to facilitate request processing,
56 The same holds for the framework.
60 The callback is invoked by the framework whether the request was
130 most of the framework code
141 The cryptographic framework first appeared in
146 The framework needs a mechanism for determining which driver is
|
| H A D | khelp.9 | 43 .Nd Kernel Helper Framework
57 provides a framework for managing
82 framework by a
112 The framework takes care of all other fields and modules should refrain from
120 framework prior to completing the registration process.
128 framework during the deregistration process, after the module has been
131 framework.
160 framework.
227 framework when calling into a
414 kernel helper framework first appeared in
[all …]
|
| H A D | intro.9 | 108 The SYSINIT framework provides macros for declaring functions that will be
194 The GEOM framework represents I/O requests using the
214 A framework for managing packet output queues is described by
239 A framework for modular TCP implementations is described by
242 A framework for modular congestion control algorithms is described by
288 framework.
330 framework should be used.
395 The Mandatory Access Control (MAC) framework provides a wide set of hooks,
400 Cryptographic services are provided by the OpenCrypto framework.
414 describes the machine-independent portion of the interrupt framework
[all …]
|
| H A D | hhook.9 | 41 .Nd Helper Hook Framework
57 provides a framework for managing and running arbitrary hook functions at
123 framework's
127 Khelp modules instruct the Khelp framework to register their hook functions with
144 which is handled by the Khelp framework.
183 framework.
219 framework.
358 framework first appeared in
363 framework was first released in 2010 by Lawrence Stewart whilst studying at
373 framework was written by
|
| /freebsd/contrib/llvm-project/clang/lib/Lex/ |
| H A D | HeaderSearch.cpp | 58 ALWAYS_ENABLED_STATISTIC(NumFrameworkLookups, "Number of framework lookups.");
104 llvm::errs() << NumFrameworkLookups << " framework lookups.\n" in PrintStats()
333 // Search for or infer a module map for a framework. Here we use in lookupModule()
338 llvm::sys::path::append(FrameworkDirName, SearchName + ".framework"); in lookupModule()
535 // Check if the headermap maps the filename to a framework include in LookupFile()
537 // framework include. in LookupFile()
556 /// Given a framework directory, find the top-most framework directory.
559 /// \param DirName The name of the framework directory.
561 /// returned top-level module to the originally named framework.
565 assert(llvm::sys::path::extension(DirName) == ".framework" && in getTopFrameworkDir()
[all …]
|
| /freebsd/contrib/llvm-project/clang/lib/InstallAPI/ |
| H A D | DirectoryScanner.cpp | 71 .Case(".framework", true) in isFramework()
161 Library &Framework = getOrCreateLibrary(Curr, Libs); in scanMultipleFrameworks() local
162 if (Error Err = scanFrameworkDirectory(Curr, Framework)) in scanMultipleFrameworks()
202 // Each version should be a framework directory. in scanFrameworkVersionsDirectory()
216 Library &Framework) const { in scanFrameworkDirectory()
217 // If the framework is inside Kernel or IOKit, scan headers in the different in scanFrameworkDirectory()
219 Framework.IsUnwrappedDylib = in scanFrameworkDirectory()
220 Path.contains("Kernel.framework") || Path.contains("IOKit.framework"); in scanFrameworkDirectory()
246 if (Error Err = scanHeaders(Curr, Framework, HeaderType::Public, Curr)) in scanFrameworkDirectory()
252 if (Error Err = scanHeaders(Curr, Framework, HeaderType::Private, Curr)) in scanFrameworkDirectory()
[all …]
|
| H A D | Library.cpp | 14 const Regex Rule("(.+)/(.+)\\.framework/");
16 assert(InstallName.contains(".framework") && "expected a framework"); in getFrameworkNameFromInstallName()
25 assert(!IsUnwrappedDylib && "expected a framework"); in getName()
28 // Return the framework name extracted from path. in getName()
30 if (Path.ends_with(".framework")) in getName()
|
| /freebsd/contrib/bearssl/mk/ |
| H A D | mkT0.cmd | 5 rem provided with the .NET framework. We need framework 3.5 or later
7 rem implemented in the compiler provided with framework 2.0.50727).
10 if exist "%SystemRoot%\Microsoft.NET\Framework\v3.5\csc.exe" (
11 set CSC="%SystemRoot%\Microsoft.NET\Framework\v3.5\csc.exe"
14 if exist "%SystemRoot%\Microsoft.NET\Framework\v4.0.30319\csc.exe" (
15 set CSC="%SystemRoot%\Microsoft.NET\Framework\v4.0.30319\csc.exe"
|
| /freebsd/contrib/llvm-project/llvm/lib/TextAPI/ |
| H A D | Utils.cpp | 26 if (!ParentPath.ends_with(Filename.str() + ".framework")) { in replace_extension()
30 // Framework dylibs do not have a file extension, in those cases the new in replace_extension()
31 // extension is appended. e.g. given Path: "Foo.framework/Foo" and Extension: in replace_extension()
32 // "tbd", the result is "Foo.framework/Foo.tbd". in replace_extension()
140 if (IsSymLink && Rest == "framework") in isPrivateLibrary()
143 // Only top level framework are public. in isPrivateLibrary()
144 // /System/Library/Frameworks/Foo.framework/Foo ==> true in isPrivateLibrary()
145 // /System/Library/Frameworks/Foo.framework/Versions/A/Foo ==> true in isPrivateLibrary()
146 // /System/Library/Frameworks/Foo.framework/Resources/libBar.dylib ==> false in isPrivateLibrary()
147 // /System/Library/Frameworks/Foo.framework/Frameworks/Bar.framework/Bar in isPrivateLibrary()
[all …]
|
| /freebsd/sys/contrib/openzfs/module/icp/core/ |
| H A D | kcf_sched.c | 27 * This file contains the core framework routines for the
28 * kernel cryptographic framework. These routines are at the
68 * We're done with this framework context, so free it. Note that freeing
69 * framework context (kcf_context) frees the global context (crypto_ctx).
73 * to NULL. It should do this before it notifies the framework of the
88 * doesn't unregister from the framework while in kcf_free_context()
137 * Creates and initializes all the structures needed by the framework.
143 * Create all the kmem caches needed by the framework. We set the in kcf_sched_init()
|
| /freebsd/share/man/man4/ |
| H A D | iicmux.4 | 32 .Nd I2C bus mulitiplexer framework
54 framework provides support code to help implement drivers for various
61 This manual page provides an overview of the I2C mux framework and its
73 framework operates automatically when I2C slave devices initiate I/O.
93 framework
117 framework conform to the standard
127 framework drivers :
145 framework first appeared in
|
| /freebsd/contrib/llvm-project/clang/include/clang/Lex/ |
| H A D | HeaderSearch.h | 111 /// Whether this is a header inside a framework that is currently
114 /// When a framework is being built, the headers have not yet been placed
115 /// into the appropriate framework subdirectories, and therefore are
117 /// those framework headers.
135 /// If this header came from a framework include, this is the name
136 /// of the framework.
137 StringRef Framework; member
171 /// This structure is used to record entries in our framework cache.
173 /// The directory entry which should be used for the cached framework.
176 /// Whether this framework has been "user-specified" to be treated as if it
[all …]
|
| /freebsd/sys/dev/isci/ |
| H A D | isci_domain.c | 45 * @brief This callback method informs the framework user that something
49 * This callback is called by the framework outside of discovery or
51 * during these processes are handled by the framework. For example,
55 * stopping/reset process, the framework user should not expect this call
85 * @brief This callback method informs the framework user that a previously
113 * @brief This callback method informs the framework user that a previously
133 * @brief This callback method informs the framework user that the domain
164 * @brief This callback method informs the framework user that the domain
183 * @brief This callback method informs the framework user that a new
232 * @brief This callback method informs the framework user that a new
[all …]
|
| /freebsd/sys/opencrypto/ |
| H A D | cryptodev_if.m | 44 * The crypto framework invokes this method on each crypto driver when
79 * Invoked by the crypto framework to initialize driver-specific data
80 * for a crypto session. The framework allocates and zeroes the
101 * The crypto framework invokes this method when tearing down a crypto
102 * session. After this callback returns, the framework will explicitly
120 * The crypto framework invokes this method for each crypto
127 * framework and retried in the future.
|