/linux/drivers/infiniband/core/ |
H A D | packer.c | 39 static u64 value_read(int offset, int size, void *structure) in value_read() argument 42 case 1: return *(u8 *) (structure + offset); in value_read() 43 case 2: return be16_to_cpup((__be16 *) (structure + offset)); in value_read() 44 case 4: return be32_to_cpup((__be32 *) (structure + offset)); in value_read() 45 case 8: return be64_to_cpup((__be64 *) (structure + offset)); in value_read() 64 void *structure, in ib_pack() argument 80 structure) << shift; in ib_pack() 97 structure) << shift; in ib_pack() 114 structure + desc[i].struct_offset_bytes, in ib_pack() 126 static void value_write(int offset, int size, u64 val, void *structure) in value_write() argument [all …]
|
/linux/arch/arm/nwfpe/ |
H A D | ChangeLog | 12 - remove userRegisters pointer from this structure. 18 * The FPA11 structure is not a kernel-specific data structure. 21 FPA11 structure (size or position of elements contained 24 * Since 128-bit float requires the FPA11 structure to change 27 overflow the available space in the task structure. 36 * fpa11.c - Changes due to FPA11, FPREG structure alterations. 37 * fpa11_cpdo.c - Changes due to FPA11, FPREG structure alterations. 38 * fpa11_cpdt.c - Changes due to FPA11, FPREG structure alterations. 39 * fpa11_cprt.c - Changes due to FPA11, FPREG structure alterations. 40 * single_cpdo.c - Changes due to FPA11, FPREG structure alterations. [all …]
|
/linux/Documentation/admin-guide/kdump/ |
H A D | vmcoreinfo.rst | 9 information from the kernel like structure size, page size, symbol 36 data structure used to store information returned by the uname(2) system 87 Makedumpfile gets the pglist_data structure from this symbol, which is 95 The address of the mem_section array, its length, structure size, and 110 The size of a page structure. struct page is an important data structure 116 The size of a pglist_data structure. This value is used to check if the 117 pglist_data structure is valid. It is also used for checking the memory 123 The size of a zone structure. This value is used to check if the zone 124 structure has been found. It is also used for excluding free pages. 129 The size of a free_area structure. It indicates whether the free_area [all …]
|
/linux/Documentation/RCU/Design/Data-Structures/ |
H A D | Data-Structures.rst | 27 This diagram shows an enclosing ``rcu_state`` structure containing a tree 31 This structure is adjusted at boot time, if needed, to handle the common 47 structure. 105 structure need advance to the ``rcu_node`` structure at the next level 106 up the tree. This means that at the leaf-level ``rcu_node`` structure, 113 period will progress all the way to the root ``rcu_node`` structure, 115 structure remains acceptably low. 138 are protected by the corresponding root ``rcu_node`` structure's lock. 139 #. Each ``rcu_node`` structure has a spinlock. 154 #. ``rcu_state``: This structure forms the interconnection between the [all …]
|
/linux/Documentation/arch/powerpc/ |
H A D | qe_firmware.rst | 89 structure signals the microcode which of these virtual traps is active. 91 This structure contains 6 words that the application should copy to some 92 specific been defined. This table describes the structure:: 121 and has special instructions for the s/w associated with it. This structure is 183 This structure supports versioning, where the version of the structure is 184 embedded into the structure itself. To ensure forward and backwards 185 compatibility, all versions of the structure must use the same 'qe_header' 186 structure at the beginning. 189 The 'length' field is the size, in bytes, of the entire structure, 195 structure is a QE Firmware structure. [all …]
|
/linux/Documentation/RCU/Design/Memory-Ordering/ |
H A D | Tree-RCU-Memory-Ordering.rst | 37 a linked RCU-protected data structure, and phase two frees that element. 50 critical section for the ``rcu_node`` structure's 62 Therefore, for any given ``rcu_node`` structure, any access 118 | But the chain of rcu_node-structure lock acquisitions guarantees | 166 | by the CPU's leaf ``rcu_node`` structure's ``->lock`` as described | 194 the ``rcu_node`` structure's ``->lock`` field, so much so that it is 247 The box represents the ``rcu_node`` structure's ``->lock`` critical 283 RCU-protected data structure). It simply enqueues the ``rcu_head`` 284 structure on a per-CPU list, which cannot become associated with a grace 305 ``rcu_node`` structure's ``->lock``. In all cases, there is full [all …]
|
/linux/Documentation/virt/kvm/arm/ |
H A D | pvtime.rst | 39 Return value: (int64) IPA of the stolen time data structure for this 47 meaningfully filled by the hypervisor (see structure below). 49 PV_TIME_ST returns the structure for the calling VCPU. 54 The structure pointed to by the PV_TIME_ST hypercall is as follows: 70 All values in the structure are stored little-endian. 72 The structure will be updated by the hypervisor prior to scheduling a VCPU. It 75 structure per VCPU of the guest.
|
/linux/Documentation/userspace-api/ioctl/ |
H A D | cdrom.rst | 67 DVD_READ_STRUCT Read structure 68 DVD_WRITE_STRUCT Write structure 154 cdrom_msf structure, describing a segment of music to play 185 cdrom_ti structure, describing a segment of music to play 214 cdrom_tochdr structure 218 cdrom_tochdr structure 239 cdrom_tocentry structure 243 cdrom_tocentry structure 375 cdrom_volctrl structure containing volumes for up to 4 425 cdrom_subchnl structure [all …]
|
/linux/Documentation/userspace-api/media/dvb/ |
H A D | dvb-frontend-parameters.rst | 14 data, the structure size weren't enough to fit, and just extending its 27 ``dvb_frontend_parameters`` structure: 58 structure: 74 for cable QAM frontend you use the ``dvb_qam_parameters`` structure: 91 ATSC frontends are supported by the ``dvb_vsb_parameters`` structure: 106 DVB-T frontends are supported by the ``dvb_ofdm_parameters`` structure:
|
/linux/Documentation/userspace-api/ |
H A D | unshare.rst | 190 with the current task structure and releases corresponding shared 195 structure, where as unshare() operates on the current active 206 new namespace structure, the error return code will have to 209 structure, which may not exist anymore. 212 current context structure was moved into new dup_* functions. Now, 215 task structure that is being constructed. unshare() system call on 220 2) For each context structure, call the corresponding unshare() 222 structure, if the appropriate bit is set in the flags argument. 225 are new context structures then lock the current task structure, 226 associate new context structures with the current task structure, [all …]
|
/linux/Documentation/userspace-api/media/v4l/ |
H A D | metafmt-rkisp1.rst | 30 The buffer contains a single instance of the C structure 31 :c:type:`rkisp1_params_cfg` defined in ``rkisp1-config.h``. So the structure can 50 The buffer contains a single instance of the C structure 52 :c:type:`rkisp1_ext_params_cfg` structure is designed to allow userspace to 72 instance of the C structure :c:type:`rkisp1_stat_buffer` defined in 73 ``rkisp1-config.h``. So the structure can be obtained from the buffer by:
|
H A D | vidioc-g-crop.rst | 39 ``type`` field of a struct :c:type:`v4l2_crop` structure to the 41 with a pointer to this structure. The driver fills the rest of the 42 structure or returns the ``EINVAL`` error code if cropping is not supported. 46 v4l2_crop structure and call the :ref:`VIDIOC_S_CROP <VIDIOC_G_CROP>` ioctl with a pointer 47 to this structure.
|
/linux/drivers/message/fusion/lsi/ |
H A D | mpi_history.txt | 106 * 05-24-00 00.10.02 Added _MSG_IOC_INIT_REPLY structure. 108 * 06-12-00 01.00.02 Added _MSG_PORT_ENABLE_REPLY structure. 109 * Added _MSG_EVENT_ACK_REPLY structure. 110 * Added _MSG_FW_DOWNLOAD_REPLY structure. 111 * Added _MSG_TOOLBOX_REPLY structure. 112 * 06-30-00 01.00.03 Added MaxLanBuckets to _PORT_FACT_REPLY structure. 113 * 07-27-00 01.00.04 Added _EVENT_DATA structure definitions for _SCSI, 116 * _MSG_EVENT_ACK_REPLY structure to match specification. 128 * Added structure offset comments. 129 * 04-09-01 01.01.07 Added structure EVENT_DATA_EVENT_CHANGE. [all …]
|
/linux/Documentation/hid/ |
H A D | hiddev.rst | 94 the value that it was changed to. Note that the structure is defined 122 hiddev_devinfo structure. 138 Gets a hiddev_devinfo structure which describes the device. 179 Fills in a hiddev_report_info structure for the user. The report is 188 filled into the returned hiddev_report_info structure. 194 hiddev_field_info structure. The user must fill in report_id and 195 report_type in this structure, as above. The field_index should also 202 Returns the usage_code in a hiddev_usage_ref structure, given that 204 field have already been filled into the structure. 209 Returns the value of a usage in a hiddev_usage_ref structure. The [all …]
|
H A D | amd-sfh-hid.rst | 57 client layer fills the HID request structure and descriptors. HID client layer is complex as it is 61 enumeration of each sensor, client layer fills the HID Descriptor structure and HID input report 62 structure. HID Feature report structure is optional. The report descriptor structure varies from
|
/linux/Documentation/crypto/ |
H A D | crypto_engine.rst | 12 You must put, at the start of your transform context your_tfm_ctx, the structure 24 has access to the transform structure. It is not possible to access the context 26 structure "``struct your_tfm_ctx``". The engine assumes (requires) the placement 55 Note that these functions access the crypto_async_request structure
|
H A D | userspace-if.rst | 103 filled struct sockaddr data structure. This data structure must be 142 initialization, the struct sockaddr data structure must be filled as 160 specified with the data structure provided by the sendmsg() system call. 163 struct cmsghdr data structure. See recv(2) and cmsg(3) for more 164 information on how the cmsghdr data structure is used together with the 165 send/recv system call family. That cmsghdr data structure holds the 196 initialization, the struct sockaddr data structure must be filled as 219 specified with the data structure provided by the sendmsg() system call. 222 struct cmsghdr data structure. See recv(2) and cmsg(3) for more 223 information on how the cmsghdr data structure is used together with the [all …]
|
/linux/Documentation/security/ |
H A D | SCTP.rst | 30 @asoc - pointer to sctp association structure. 42 @sk - Pointer to sock structure. 117 @asoc - pointer to current sctp association structure. 118 @sk - pointer to current sock structure. 119 @newsk - pointer to new sock structure. 127 @asoc - pointer to sctp association structure. 208 @asoc - pointer to sctp association structure. 267 @asoc - pointer to current sctp association structure. 268 @sk - pointer to current sock structure. 269 @newsk - pointer to new sock structure. [all …]
|
/linux/Documentation/core-api/ |
H A D | padata.rst | 26 padata_instance structure for overall control of how jobs are to be run:: 84 padata_priv structure, which represents one job:: 92 This structure will almost certainly be embedded within some larger 93 structure specific to the work to be done. Most of its fields are private to 94 padata, but the structure should be zeroed at initialisation time, and the 118 function gets the padata_priv structure pointer as its lone parameter; 120 container_of() to find the enclosing structure. 137 serial() function in the padata_priv structure. That call will happen on 165 job by defining a padata_mt_job structure, which is explained in the Interface
|
/linux/Documentation/driver-api/ |
H A D | miscellaneous.rst | 33 are expected to embed this structure in a driver-specific structure. 34 This structure contains fields that describe a particular chip.
|
/linux/Documentation/devicetree/bindings/clock/st/ |
H A D | st,flexgen.txt | 1 Binding for a type of flexgen structure found on certain 4 This structure includes: 8 Flexgen structure is a part of Clockgen[1]. 14 | Flexgen structure |
|
/linux/Documentation/filesystems/ |
H A D | files.rst | 28 table are in a separate structure - struct fdtable. 32 expansion of fdtable, a new fdtable structure is allocated 33 and files->fdtab points to the new structure. The fdtable 34 structure is freed with RCU and lock-free readers either 37 the fdtable structure - 64 4. To look up the file structure given an fd, a reader
|
/linux/Documentation/admin-guide/blockdev/drbd/ |
H A D | data-structure-v9.rst | 2 kernel data structure for DRBD-9 5 This describes the in kernel data structure for DRBD-9. Starting with 6 Linux v3.14 we are reorganizing DRBD to use this data structure.
|
/linux/Documentation/devicetree/ |
H A D | of_unittest.rst | 23 from the unflattened device tree data structure. This interface is used by 83 Un-flattened device tree structure: 86 structure described below:: 97 Figure 1, describes a generic structure of machine's un-flattened device tree 126 Figure 1: Generic structure of un-flattened device tree 164 data node is attached to the live tree above (Figure 1), the final structure is 200 Figure 3: Live device tree structure after attaching the testcase-data. 204 sibling compared to the earlier structure (Figure 2). After attaching first
|
/linux/Documentation/virt/kvm/x86/ |
H A D | msr.rst | 26 structure:: 65 a copy of the following structure:: 80 updates of this structure is arbitrary and implementation-dependent. 81 The hypervisor may update this structure at any time it sees fit until 93 of the update of this structure. Guests can subtract this value 95 structure update. 99 time at the time this structure was last updated. Unit is 197 following structure:: 265 hold a copy of the following structure:: 278 updates of this structure is arbitrary and implementation-dependent. [all …]
|