/linux/arch/x86/kernel/cpu/sgx/ |
H A D | encls.h | 17 /* Issue a WARN() about an ENCLS function. */ 26 * encls_faulted() - Check if an ENCLS leaf faulted given an error code 27 * @ret: the return value of an ENCLS leaf function call 39 * encls_failed() - Check if an ENCLS function failed 40 * @ret: the return value of an ENCLS function call 42 * Check if an ENCLS function failed. This happens when the function causes a 43 * fault that is not caused by an EPCM conflict or when the function returns a 55 * __encls_ret_N - encode an ENCLS function that returns an erro [all...] |
/linux/tools/perf/pmu-events/arch/powerpc/power8/ |
H A D | frontend.json | 71 "BriefDescription": "Initial and Final Pump Scope was chip pump (prediction=correct) for an instruction fetch", 72 "PublicDescription": "Initial and Final Pump Scope and data sourced across this scope was chip pump (prediction=correct) for an instruction fetch" 89 "BriefDescription": "The processor's Instruction cache was reloaded with Modified (M) data from another chip's L2 or L3 on a different Node or Group (Distant), as this chip due to an instruction fetch (not prefetch)", 90 "PublicDescription": "The processor's Instruction cache was reloaded with Modified (M) data from another chip's L2 or L3 on a different Node or Group (Distant), as this chip due to either an instruction fetch or instruction fetch plus prefetch if MMCR1[17] is 1" 95 "BriefDescription": "The processor's Instruction cache was reloaded with Shared (S) data from another chip's L2 or L3 on a different Node or Group (Distant), as this chip due to an instruction fetch (not prefetch)", 96 "PublicDescription": "The processor's Instruction cache was reloaded with Shared (S) data from another chip's L2 or L3 on a different Node or Group (Distant), as this chip due to either an instruction fetch or instruction fetch plus prefetch if MMCR1[17] is 1" 101 "BriefDescription": "The processor's Instruction cache was reloaded from another chip's L4 on a different Node or Group (Distant) due to an instruction fetch (not prefetch)", 102 "PublicDescription": "The processor's Instruction cache was reloaded from another chip's L4 on a different Node or Group (Distant) due to either an instruction fetch or instruction fetch plus prefetch if MMCR1[17] is 1" 107 "BriefDescription": "The processor's Instruction cache was reloaded from another chip's memory on the same Node or Group (Distant) due to an instruction fetch (not prefetch)", 108 "PublicDescription": "The processor's Instruction cache was reloaded from another chip's memory on the same Node or Group (Distant) due to either an instructio [all...] |
/linux/drivers/pinctrl/intel/ |
H A D | Kconfig | 21 Cherryview/Braswell pinctrl driver provides an interface that 29 provides an interface that allows configuring of PCH pins and 44 This pinctrl driver provides an interface that allows configuring 54 This pinctrl driver provides an interface that allows configuring 61 Broxton pinctrl driver provides an interface that allows 68 This pinctrl driver provides an interface that allows configuring 75 This pinctrl driver provides an interface that allows configuring 82 This pinctrl driver provides an interface that allows configuring 89 This pinctrl driver provides an interface that allows configuring 96 This pinctrl driver provides an interfac [all...] |
/linux/include/kunit/ |
H A D | test.h | 69 * Speed Attribute is stored as an enum and separated into categories of 89 * struct kunit_case - represents an individual test case. 105 * terminated with an empty test case. 157 * &struct kunit_case for an example on how to use it. 260 /* Stores an array of suites, end points one past the end */ 619 * kunit_info() - Prints an INFO level message associated with @test. 624 * Prints an info level message associated with the test suite being run. 642 * kunit_err() - Prints an ERROR level message associated with @test. 647 * Prints an error level message. 665 * The opposite of KUNIT_FAIL(), it is an expectatio [all...] |
/linux/net/netlabel/ |
H A 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 [all...] |
H A 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 applicatio [all...] |
/linux/Documentation/userspace-api/ |
H A D | iommufd.rst | 35 - IOMMUFD_OBJ_IOAS, representing an I/O address space (IOAS), allowing map/unmap 39 container it copies an IOVA map to a list of iommu_domains held within it. 41 - IOMMUFD_OBJ_DEVICE, representing a device that is bound to iommufd by an 44 - IOMMUFD_OBJ_HWPT_PAGING, representing an actual hardware I/O page table 46 primarly indicates this type of HWPT should be linked to an IOAS. It also 47 indicates that it is backed by an iommu_domain with __IOMMU_DOMAIN_PAGING 48 feature flag. This can be either an UNMANAGED stage-1 domain for a device 55 - IOMMUFD_OBJ_HWPT_NESTED, representing an actual hardware I/O page table 57 "NESTED" indicates that this type of HWPT should be linked to an HWPT_PAGING. 58 It also indicates that it is backed by an iommu_domai [all...] |
/linux/Documentation/i2c/ |
H A 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 44 they are requested to use such an address. 51 Also returned when trying to invoke an I2C operation in an 56 Returned by SMBus logic when an invalid Packet Error Code byte 71 This rather vague error means an invalid parameter has been 77 performing an I/O operation. Use a more specific fault 94 of a transfer didn't get an ACK. While it might just mean 95 an I2 [all...] |
/linux/Documentation/arch/powerpc/ |
H A 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 EB [all...] |
/linux/include/misc/ |
H A 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 OpenCAP [all...] |
/linux/Documentation/filesystems/ |
H A 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 operatio [all...] |
/linux/Documentation/core-api/ |
H A 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 objec [all...] |
/linux/drivers/md/dm-vdo/indexer/ |
H A D | index-session.h | 19 * it can be used to open, close, suspend, or recreate an index. It implements the majority of the 22 * If any deduplication request fails due to an internal error, the index is marked disabled. It 28 /* Post requests that found an entry */ in __aligned() 36 /* Post requests that did not find an entry */ in __aligned() 38 /* Update requests that found an entry */ in __aligned() 40 /* Update requests that did not find an entry */ in __aligned() 42 /* Delete requests that found an entry */ in __aligned() 44 /* Delete requests that did not find an entry */ in __aligned() 46 /* Query requests that found an entry */ in __aligned() 48 /* Query requests that did not find an entr in __aligned() [all...] |
/linux/Documentation/devicetree/bindings/fsi/ |
H A 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 addres [all...] |
/linux/include/linux/ |
H A D | err.h | 12 * scheme where we can return either an error code or a normal 23 * IS_ERR_VALUE - Detect an error pointer. 31 * ERR_PTR - Create an error pointer. 47 /* Cast an error pointer to __iomem. */ 51 * PTR_ERR - Extract the error code from an error pointer. 52 * @ptr: An error pointer. 60 /* Read an error pointer from the percpu address space. */ 64 * IS_ERR - Detect an error pointer. 66 * Return: true if @ptr is an error pointer, false otherwise. 73 /* Read an erro [all...] |
/linux/Documentation/networking/ |
H A 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 identifie [all...] |
H A 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 arbitrar [all...] |
/linux/Documentation/staging/ |
H A D | rpmsg.rst | 22 its own instance of RTOS in an AMP configuration. 87 Returns 0 on success and an appropriate error value on failure. 97 its length (in bytes), and an explicit destination address. 111 Returns 0 on success and an appropriate error value on failure. 128 Returns 0 on success and an appropriate error value on failure. 139 its length (in bytes), and an explicit destination address. 149 Returns 0 on success and an appropriate error value on failure. 157 every rpmsg address in the system is bound to an rx callback (so when 159 appropriate callback handler) by means of an rpmsg_endpoint struct. 161 This function allows drivers to create such an endpoin [all...] |
/linux/Documentation/virt/ |
H A 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. 25 primary VM, that communicates with the NE kernel driver via an ioctl interface. 29 1. An enclave abstraction process - a user space process running in the primary 30 VM guest that uses the provided ioctl interface of the NE driver to spawn an 37 maps to an enclave start PCI command. The PCI device commands are then 44 for the enclave VM. An enclave does not have persistent storage attached. 46 The memory regions carved out of the primary VM and given to an enclave need to 49 user space [2][3][7]. The memory size for an enclave needs to be at least 52 An enclav [all...] |
/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a510/ |
H A D | pipeline.json | 21 "PublicDescription": "No operation issued due to the frontend, cache miss. This event counts every cycle that the Data Processing Unit (DPU) instruction queue is empty and there is an instruction cache miss being processed", 24 "BriefDescription": "No operation issued due to the frontend, cache miss. This event counts every cycle that the Data Processing Unit (DPU) instruction queue is empty and there is an instruction cache miss being processed" 27 "PublicDescription": "No operation issued due to the frontend, TLB miss. This event counts every cycle that the DPU instruction queue is empty and there is an instruction L1 TLB miss being processed", 30 "BriefDescription": "No operation issued due to the frontend, TLB miss. This event counts every cycle that the DPU instruction queue is empty and there is an instruction L1 TLB miss being processed" 39 "PublicDescription": "No operation issued due to the backend interlock. This event counts every cycle where the issue of an operation is stalled and there is an interlock. Stall cycles due to a stall in the Wr stage are excluded", 42 "BriefDescription": "No operation issued due to the backend interlock. This event counts every cycle where the issue of an operation is stalled and there is an interlock. Stall cycles due to a stall in the Wr stage are excluded" 45 "PublicDescription": "No operation issued due to the backend, address interlock. This event counts every cycle where the issue of an operation is stalled and there is an interloc [all...] |
/linux/drivers/s390/net/ |
H A 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 FS [all...] |
/linux/tools/perf/pmu-events/arch/x86/broadwellde/ |
H A D | memory.json | 13 "BriefDescription": "Number of times an HLE execution aborted due to various memory events (e.g., read/write capacity and conflicts).", 17 "PublicDescription": "Number of times an HLE abort was attributed to a Memory condition (See TSX_Memory event for additional details).", 22 "BriefDescription": "Number of times an HLE execution aborted due to uncommon conditions", 26 "PublicDescription": "Number of times the TSX watchdog signaled an HLE abort.", 31 "BriefDescription": "Number of times an HLE execution aborted due to HLE-unfriendly instructions", 35 "PublicDescription": "Number of times a disallowed operation caused an HLE abort.", 40 "BriefDescription": "Number of times an HLE execution aborted due to incompatible memory type", 49 "BriefDescription": "Number of times an HLE execution aborted due to none of the previous 4 categories (e.g. interrupts)", 67 "BriefDescription": "Number of times we entered an HLE region; does not count nested transactions", 71 "PublicDescription": "Number of times we entered an HL [all...] |
/linux/Documentation/arch/x86/ |
H A D | sgx.rst | 15 * Unprivileged (ring-3) ENCLU functions allow an application to enter and 18 These memory regions are called enclaves. An enclave can be only entered at a 37 SGX utilizes an *Enclave Page Cache (EPC)* to store pages that are associated 38 with an enclave. It is contained in a BIOS-reserved region of physical memory. 42 Only a CPU executing inside an enclave can directly access enclave memory. 43 However, a CPU executing inside an enclave may access normal memory outside the 56 Regular EPC pages contain the code and data of an enclave. 59 Thread Control Structure pages define the entry points to an enclave and 60 track the execution state of an enclave thread. 70 *Enclave Page Cache Map (EPCM)*. The EPCM contains an entr [all...] |
/linux/include/acpi/ |
H A 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 illega [all...] |
/linux/Documentation/core-api/irq/ |
H A D | concepts.rst | 2 What is an IRQ? 5 An IRQ is an interrupt request from a device. Currently, they can come 7 the same pin thus sharing an IRQ. Such as on legacy PCI bus: All devices 8 typically share 4 lanes/pins. Note that each device can request an 11 An IRQ number is a kernel identifier used to talk about a hardware 12 interrupt source. Typically, this is an index into the global irq_desc 16 An IRQ number is an enumeration of the possible interrupt sources on a
|