| /Linux-v5.10/tools/perf/pmu-events/arch/powerpc/power8/ |
| D | frontend.json | 71 …"BriefDescription": "Initial and Final Pump Scope was chip pump (prediction=correct) for an instru…
72 …ope and data sourced across this scope was chip pump (prediction=correct) for an instruction fetch"
89 …hip's L2 or L3 on a different Node or Group (Distant), as this chip due to an instruction fetch (n…
90 …2 or L3 on a different Node or Group (Distant), as this chip due to either an instruction fetch or…
95 …hip's L2 or L3 on a different Node or Group (Distant), as this chip due to an instruction fetch (n…
96 …2 or L3 on a different Node or Group (Distant), as this chip due to either an instruction fetch or…
101 …oaded from another chip's L4 on a different Node or Group (Distant) due to an instruction fetch (n…
102 …rom another chip's L4 on a different Node or Group (Distant) due to either an instruction fetch or…
107 …aded from another chip's memory on the same Node or Group (Distant) due to an instruction fetch (n…
108 …om another chip's memory on the same Node or Group (Distant) due to either an instruction fetch or…
[all …]
|
| /Linux-v5.10/net/netlabel/ |
| D | netlabel_mgmt.h | 26 * Sent by an application to add a domain mapping to the NetLabel system.
53 * Sent by an application to remove a domain mapping from the NetLabel
61 * This message can be sent either from an application or by the kernel in
62 * response to an application generated LISTALL message. When sent by an
90 * Sent by an application to set the default domain mapping for the NetLabel
107 * Sent by an application to remove the default domain mapping from the
111 * This message can be sent either from an application or by the kernel in
112 * response to an application generated LISTDEF message. When sent by an
113 * application there may be an optional payload.
139 * Sent by an application to request a list of configured NetLabel protocols
[all …]
|
| D | netlabel_unlabeled.h | 25 * This message is sent from an application to add a new static label for
44 * This message is sent from an application to remove an existing static
62 * This message can be sent either from an application or by the kernel in
63 * response to an application generated STATICLIST message. When sent by an
83 * This message is sent from an application to set the default static
101 * This message is sent from an application to remove the existing default
115 * This message can be sent either from an application or by the kernel in
116 * response to an application generated STATICLISTDEF message. When sent by
117 * an application there is no payload and the NLM_F_DUMP flag should be set.
135 * This message is sent from an application to specify if the kernel should
[all …]
|
| /Linux-v5.10/include/kunit/ |
| D | test.h | 106 * struct kunit_case - represents an individual test case.
120 * terminated with an empty test case.
162 * &struct kunit_case for an example on how to use it.
266 * an initcall which we don't want as the idea is that for builtins
306 * An alternative is to build the tests as a module. Because modules do not
307 * support multiple initcall()s, we need to initialize an array of suites for a
382 * If an init function is supplied, @data is passed to it instead.
418 * cleaned up at the end of a test case. See &struct kunit_resource for an
422 * specify an @internal_gfp that is compatible with the use context of your
453 * An instance of kunit_resource_match_t that matches a resource whose
[all …]
|
| /Linux-v5.10/Documentation/powerpc/ |
| D | pmu-ebb.rst | 20 Throughout this document we will refer to an "EBB event" or "EBB events". This
39 and attach an EBB event to the process, which will then cause EBBs to be
44 user process. This means once an EBB event is scheduled on the PMU, no non-EBB
55 If an EBB event and a regular event are both pinned, then whichever is enabled
57 section below titled "Enabling an EBB event" for more information.
60 Creating an EBB event
63 To request that an event is counted using EBB, the event code should have bit
70 An EBB event must be created with the "pinned" and "exclusive" attributes set.
74 An EBB event must NOT set any of the "inherit", "sample_period", "freq" or
77 An EBB event must be attached to a task. This is specified to perf_event_open()
[all …]
|
| /Linux-v5.10/include/misc/ |
| D | ocxl.h | 65 * ocxl_function_open() - Open an OpenCAPI function on an OpenCAPI device
68 * Returns an opaque pointer to the function, or an error pointer (check with IS_ERR)
81 * ocxl_function_fetch_afu() - Fetch an AFU instance from an OpenCAPI function
92 * ocxl_afu_get() - Take a reference to an AFU
98 * ocxl_afu_put() - Release a reference to an AFU
105 * ocxl_function_config() - Get the configuration information for an OpenCAPI function
113 * ocxl_function_close() - Close an OpenCAPI function
125 * ocxl_context_alloc() - Allocate an OpenCAPI context
134 * ocxl_context_free() - Free an OpenCAPI context
140 * ocxl_context_attach() - Grant access to an MM to an OpenCAPI context
[all …]
|
| /Linux-v5.10/Documentation/filesystems/caching/ |
| D | backend-api.rst | 7 The FS-Cache system provides an API by which actual caches can be supplied to
83 In either case, this may not be an appropriate context in which to access the
145 is backing. An object should retired when put_object() is called if it is
168 An operation can be made exclusive upon an object by setting the
170 an operation needs more processing time, it should be enqueued again.
194 The to_do field is an empty list available for the cache backend to use as
226 This isn't strictly an operation, but should be pointed at a string naming
249 This method is used to look up an object, given that the object is already
276 This method is called to increment the reference count on an object. It
286 These methods are used to exclusively lock an object. It must be possible
[all …]
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | autofs-mount-control.rst | 17 are things such as setting an autofs mount catatonic, setting the
19 certain types of autofs triggered mounts can end up covering an autofs
38 module source you will see a third type called an offset, which is just
60 For the above indirect map an autofs file system is mounted on /test and
65 The way that direct mounts are handled is by making an autofs mount on
74 For example, an indirect mount map entry could also be::
92 One of the issues with version 4 of autofs was that, when mounting an
107 The current autofs implementation uses an ioctl file descriptor opened
121 implement an isolated operation it was decided to re-implement the
128 autofs maps. They are recorded at mount request time and an operation
[all …]
|
| /Linux-v5.10/drivers/pinctrl/intel/ |
| D | Kconfig | 23 Cherryview/Braswell pinctrl driver provides an interface that
36 provides an interface that allows configuring of PCH pins and
46 Merrifield Family-Level Interface Shim (FLIS) driver provides an
63 Broxton pinctrl driver provides an interface that allows
71 This pinctrl driver provides an interface that allows configuring
79 This pinctrl driver provides an interface that allows configuring
87 This pinctrl driver provides an interface that allows configuring
95 This pinctrl driver provides an interface that allows configuring
103 This pinctrl driver provides an interface that allows configuring
111 This pinctrl driver provides an interface that allows configuring
[all …]
|
| /Linux-v5.10/Documentation/core-api/ |
| D | assoc_array.rst | 8 This associative array implementation is an object container with the following
19 permits an object to be located in multiple arrays simultaneously.
24 4. Index keys must be unique. Inserting an object with the same key as one
52 pack leaf object pointers into spare space in the node rather than making an
53 extra branch until as such time an object needs to be added to a full node.
74 The insertion and deletion functions produce an 'edit script' that can later be
82 after an RCU grace period has passed - thus allowing access functions to
91 1. Apply an edit script::
100 2. Cancel an edit script::
132 2. Get a chunk of an object's index key::
[all …]
|
| D | xarray.rst | 12 The XArray is an abstract data type which behaves like a very large array
32 objects, as long as those objects have an alignment of at least 4.
35 You must first convert it into an entry using xa_mk_value().
36 When you retrieve an entry from the XArray, you can check whether it is
38 an integer by calling xa_to_value().
41 call xa_tag_pointer() to create an entry with a tag, xa_untag_pointer()
42 to turn a tagged entry back into an untagged pointer and xa_pointer_tag()
43 to retrieve the tag of an entry. Tagged pointers use the same bits that
51 An unusual feature of the XArray is the ability to create entries which
61 Start by initialising an XArray, either with DEFINE_XARRAY()
[all …]
|
| /Linux-v5.10/Documentation/i2c/ |
| D | fault-codes.rst | 9 A "Fault" is not always an "Error"
18 result for an operation ... it doesn't indicate that anything is wrong
47 Also returned when trying to invoke an I2C operation in an
52 Returned by SMBus logic when an invalid Packet Error Code byte
67 This rather vague error means an invalid parameter has been
73 performing an I/O operation. Use a more specific fault
90 of a transfer didn't get an ACK. While it might just mean
91 an I2C device was temporarily not responding, usually it
98 Returned by an adapter when asked to perform an operation
101 For example, this would be returned when an adapter that
[all …]
|
| /Linux-v5.10/Documentation/devicetree/bindings/fsi/ |
| D | fsi.txt | 7 busses, which are then exposed by the device tree. For example, an FSI engine
8 that is an I2C master - the I2C bus can be described by the device tree under
19 /* top-level of FSI bus topology, bound to an FSI master driver and
20 * exposes an FSI bus */
40 not be described; this binding only provides an optional facility for
47 value. It's likely that an implementation-specific compatible value will
59 An optional boolean property can be added to indicate that a particular master
70 for an address identifier. Since these are not a range, no size cells are
71 required. For an example, a slave on link 1, with ID 2, could be represented
79 Each slave provides an address-space, under which the engines are accessible.
[all …]
|
| /Linux-v5.10/Documentation/virt/ |
| D | ne_overview.rst | 14 For example, an application that processes sensitive data and runs in a VM,
16 application then runs in a separate VM than the primary VM, namely an enclave.
18 An enclave runs alongside the VM that spawned it. This setup matches low latency
21 process running in the primary VM, that communicates with the NE driver via an
26 1. An enclave abstraction process - a user space process running in the primary
27 VM guest that uses the provided ioctl interface of the NE driver to spawn an
34 maps to an enclave start PCI command. The PCI device commands are then
41 for the enclave VM. An enclave does not have persistent storage attached.
43 The memory regions carved out of the primary VM and given to an enclave need to
46 user space [2][3]. The memory size for an enclave needs to be at least 64 MiB.
[all …]
|
| /Linux-v5.10/Documentation/networking/ |
| D | ila.rst | 12 differentiates between location and identity of a network node. Part of an
18 ILA can be thought of as means to implement an overlay network without
21 the network, an ILA translated packet appears to be no different than any
22 other IPv6 packet. For instance, if the transport protocol is TCP then an
34 A number that identifies an addressable node in the network
40 provide the topological location of an addressed node. ILA
44 A mapping of an ILA identifier to a locator (or to a
45 locator and meta data). An ILA domain maintains a database
49 An IPv6 address composed of a SIR prefix (upper sixty-
50 four bits) and an identifier (lower sixty-four bits).
[all …]
|
| D | ppp_generic.rst | 12 The generic PPP driver in linux-2.4 provides an implementation of the
60 * ioctl() provides an interface which can be used by a user-space
62 procedure will be called when a user-space program does an ioctl
63 system call on an instance of /dev/ppp which is bound to the
90 (e.g. an ioctl) to transmit this back to user-space, as user-space
91 will need it to attach an instance of /dev/ppp to this channel.
105 communications medium and prepare it to do PPP. For example, with an
127 The channel must provide an instance of a ppp_channel struct to
259 this way an effect similar to Solaris' clone open is obtained,
260 allowing us to control an arbitrary number of PPP interfaces and
[all …]
|
| /Linux-v5.10/Documentation/staging/ |
| D | rpmsg.rst | 22 its own instance of RTOS in an AMP configuration.
86 Returns 0 on success and an appropriate error value on failure.
96 its length (in bytes), and an explicit destination address.
109 Returns 0 on success and an appropriate error value on failure.
133 Returns 0 on success and an appropriate error value on failure.
149 Returns 0 on success and an appropriate error value on failure.
160 its length (in bytes), and an explicit destination address.
170 Returns 0 on success and an appropriate error value on failure.
191 Returns 0 on success and an appropriate error value on failure.
199 every rpmsg address in the system is bound to an rx callback (so when
[all …]
|
| /Linux-v5.10/drivers/s390/net/ |
| D | fsm.h | 36 * Definition of an action function, called by a FSM
98 * Creates an FSM
101 * @param state_names An array of names for all states for logging purposes.
102 * @param event_names An array of names for all events for logging purposes.
105 * @param tmpl An array of fsm_nodes, describing this FSM.
116 * Releases an FSM
118 * @param fi Pointer to an FSM, previously created with init_fsm.
131 * Emits an event to a FSM.
132 * If an action function is defined for the current state/event combination,
185 * Modifies the state of an FSM.
[all …]
|
| /Linux-v5.10/include/acpi/ |
| D | acexcep.h | 213 EXCEP_TXT("AE_ALREADY_EXISTS", "An entity already exists"),
218 EXCEP_TXT("AE_STACK_OVERFLOW", "An internal stack overflowed"),
219 EXCEP_TXT("AE_STACK_UNDERFLOW", "An internal stack underflowed"),
229 "An attempt to release a mutex or Global Lock without a previous acquire"),
233 "Hardware did not respond after an I/O operation"),
245 EXCEP_TXT("AE_IO_ERROR", "An I/O error occurred"),
261 "An invalid character was found in a name"),
263 "An invalid character was found in a pathname"),
268 "Invalid character in an Octal constant"),
273 EXCEP_TXT("AE_BAD_ADDRESS", "An illegal null I/O address")
[all …]
|
| /Linux-v5.10/arch/ |
| D | Kconfig | 155 This symbol should be selected by an architecture if it can
217 # An arch should select this if it provides all these things:
244 An architecture should select this when it can successfully
264 # either provide an uncached segement alias for a DMA allocation, or
272 # to undo an in-place page table remap for uncached access.
289 An architecture should select this to provide hardened usercopy
317 This symbol should be selected by an architecure if it provides
324 This symbol should be selected by an architecure if it supports
333 This symbol should be selected by an architecture if it
334 supports an implementation of restartable sequences.
[all …]
|
| /Linux-v5.10/Documentation/driver-api/nfc/ |
| D | nfc-hci.rst | 12 enables easy writing of HCI-based NFC drivers. The HCI layer runs as an NFC Core
13 backend, implementing an abstract nfc device and translating NFC Core API
19 HCI registers as an nfc device with NFC Core. Requests coming from userspace are
37 The Session initialization is an HCI standard which must unfortunately
91 - hci_ready() is an optional entry point that is called right after the hci
95 - start_poll() is an optional entrypoint that shall set the hardware in polling
102 - target_from_gate() is an optional entrypoint to return the nfc protocols
104 - complete_target_discovered() is an optional entry point to let the driver
114 - check_presence() is an optional entry point that will be called regularly
115 by the core to check that an activated tag is still in the field. If this is
[all …]
|
| /Linux-v5.10/Documentation/core-api/irq/ |
| D | irq-domain.rst | 33 top of the irq_alloc_desc*() API. An irq_domain to manage mapping is
37 irq_domain also implements translation from an abstract irq_fwspec
44 An interrupt controller driver creates and registers an irq_domain by
48 provide the allocator function with an irq_domain_ops structure.
58 When an interrupt is received, irq_find_mapping() function should
86 hwirq number. When a hwirq is mapped, an irq_desc is allocated for
97 accepts an Open Firmware specific 'struct device_node', while the latter
111 IRQs. When an hwirq is mapped, an irq_desc is allocated and the
121 accepts an Open Firmware specific 'struct device_node', while the latter
163 controller to manage IRQ allocations and it requires an irq_desc to be
[all …]
|
| /Linux-v5.10/include/linux/ |
| D | srcu.h | 70 * If CONFIG_DEBUG_LOCK_ALLOC is selected, returns nonzero iff in an SRCU
72 * this assumes we are in an SRCU read-side critical section unless it can
80 * is in the idle loop from an RCU point of view or offline.
102 * really are in an SRCU read-side critical section.
105 * If PROVE_RCU is enabled, invoking this outside of an RCU read-side
106 * critical section will result in an RCU-lockdep splat, unless @c evaluates
117 * really are in an SRCU read-side critical section.
120 * is enabled, invoking this outside of an RCU read-side critical
121 * section will result in an RCU-lockdep splat.
129 * really are in an SRCU read-side critical section.
[all …]
|
| /Linux-v5.10/Documentation/driver-api/usb/ |
| D | anchors.rst | 8 a driver to cease all IO to an interface. To do so, a
18 There's no API to allocate an anchor. It is simply declared
31 An association of URBs to an anchor is made by an explicit
33 an URB is finished by (successful) completion. Thus disassociation
35 all URBs associated with an anchor.
44 This function kills all URBs associated with an anchor. The URBs
52 This function unlinks all URBs associated with an anchor. The URBs
62 All URBs of an anchor are unanchored en masse.
67 This function waits for all URBs associated with an anchor to finish
74 Returns true if no URBs are associated with an anchor. Locking
[all …]
|
| /Linux-v5.10/arch/m68k/ifpsp060/ |
| D | fskeleton.S | 9 |THE SOFTWARE is provided on an "AS IS" basis and without warranty.
61 | simply execute an "rte" as with the sample code below.
70 | This is the exit point for the 060FPSP when an enabled overflow exception
72 | for enabled overflow conditions. The exception stack frame is an overflow
76 | does an "rte".
89 | This is the exit point for the 060FPSP when an enabled underflow exception
91 | for enabled underflow conditions. The exception stack frame is an underflow
95 | does an "rte".
107 | This is the exit point for the 060FPSP when an enabled operand error exception
109 | for enabled operand error exceptions. The exception stack frame is an operand error
[all …]
|
