| /linux-6.3-rc2/drivers/infiniband/core/ |
| 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()
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()
129 case 8: *( u8 *) (structure + offset) = val; break; in value_write()
151 void *structure) in ib_unpack() argument
172 structure); in ib_unpack()
186 structure); in ib_unpack()
[all …]
|
| /linux-6.3-rc2/arch/arm/nwfpe/ |
| 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.
50 embedded in the process task structure. Thus we were scribbling
[all …]
|
| /linux-6.3-rc2/Documentation/admin-guide/kdump/ |
| A D | vmcoreinfo.rst | 110 The size of a page structure. struct page is an important data structure
225 The size of a printk_ringbuffer structure. This structure contains all
234 declaration of the structure.
239 The size of the prb_desc_ring structure. This structure contains
247 requiring the declaration of the structure.
252 The size of the prb_desc structure. This structure contains
260 the declaration of the structure.
265 The size of the prb_data_blk_lpos structure. This structure contains
279 The size of the printk_info structure. This structure contains all
287 the declaration of the structure.
[all …]
|
| /linux-6.3-rc2/Documentation/RCU/Design/Data-Structures/ |
| A D | Data-Structures.rst | 47 structure.
105 structure need advance to the ``rcu_node`` structure at the next level
115 structure remains acceptably low.
185 structure.
195 The ``rcu_state`` structure is the base structure that represents the
252 first leaf ``rcu_node`` structure.
260 corresponding CPU's ``rcu_data`` structure.
843 structure's ``->gp_seq`` are zero, then this ``rcu_data`` structure
1031 enclosing RCU-protected data structure.
1056 the ``task_struct`` structure:
[all …]
|
| /linux-6.3-rc2/Documentation/powerpc/ |
| A D | qe_firmware.rst | 89 structure signals the microcode which of these virtual traps is active.
92 specific been defined. This table describes the structure::
183 This structure supports versioning, where the version of the structure is
184 embedded into the structure itself. To ensure forward and backwards
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.
198 structure. If the layout of the structure should ever need to be
243 'microcode' structure is for the first RISC, and so on.
262 structure where the microcode itself can be found. The first
[all …]
|
| /linux-6.3-rc2/Documentation/virt/kvm/arm/ |
| 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-6.3-rc2/Documentation/RCU/Design/Memory-Ordering/ |
| A D | Tree-RCU-Memory-Ordering.rst | 50 critical section for the ``rcu_node`` structure's
62 Therefore, for any given ``rcu_node`` structure, any access
305 ``rcu_node`` structure's ``->lock``. In all cases, there is full
309 structure's ``->lock``.
348 root ``rcu_node`` structure is touched.
358 leaf ``rcu_node`` structure has transitioned to zero,
361 ``rcu_node`` structure onlines its first CPU and if the next
364 ``rcu_node`` structure has no online CPUs).
420 that ``rcu_node`` structure's ``->lock``.
477 structure's ``->qsmask`` field.
[all …]
|
| /linux-6.3-rc2/Documentation/userspace-api/media/dvb/ |
| 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-6.3-rc2/Documentation/userspace-api/ioctl/ |
| A D | cdrom.rst | 67 DVD_READ_STRUCT Read structure
68 DVD_WRITE_STRUCT Write structure
214 cdrom_tochdr structure
218 cdrom_tochdr structure
239 cdrom_tocentry structure
243 cdrom_tocentry structure
425 cdrom_subchnl structure
429 cdrom_subchnl structure
1095 DVD_READ_STRUCT Read structure
1133 DVD_WRITE_STRUCT Write structure
[all …]
|
| /linux-6.3-rc2/Documentation/userspace-api/media/v4l/ |
| A D | pixfmt-meta-rkisp1.rst | 17 a single instance of the C structure :c:type:`rkisp1_params_cfg` defined in
18 ``rkisp1-config.h``. So the structure can be obtained from the buffer by:
33 instance of the C structure :c:type:`rkisp1_stat_buffer` defined in
34 ``rkisp1-config.h``. So the structure can be obtained from the buffer by:
|
| A D | dev-meta.rst | 25 :c:type:`v4l2_capability` structure returned by the :c:func:`VIDIOC_QUERYCAP`
29 :c:type:`v4l2_capability` structure. That flag means the device can read
44 :c:type:`v4l2_format` structure to ``V4L2_BUF_TYPE_META_CAPTURE`` or to
47 and applications must set the remainder of the :c:type:`v4l2_format` structure
|
| 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-6.3-rc2/Documentation/userspace-api/ |
| 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.
220 2) For each context structure, call the corresponding unshare()
227 and release the lock on the current task structure.
254 context structure. The reorganized copy_* functions invoked
256 duplicated structures to the task structure with which the
270 reference to pointer pointing the new unshared structure
286 required for that structure. If it is, invoke the corresponding
[all …]
|
| A D | iommu.rst | 51 2. Adding new union members at the end. May increase the structure sizes.
55 be introduced whenever a change affects the structure using either
63 structure passed by setting argsz appropriately.
71 When IOMMU UAPI extension results in some structure size increase,
142 A "__u32 argsz" field is *always* at the beginning of each structure.
151 /* IOMMU paging structure cache */
183 where there's vendor data outside of the structure definition.
187 - structure contains vendor data
190 - structure contains only generic data
|
| /linux-6.3-rc2/Documentation/filesystems/ |
| 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
83 file structure. This is avoided using atomic_long_inc_not_zero()
|
| /linux-6.3-rc2/drivers/message/fusion/lsi/ |
| A D | mpi_history.txt | 111 * Added _MSG_TOOLBOX_REPLY structure.
128 * Added structure offset comments.
134 * related structure and defines.
186 * data structure.
188 * data structure.
195 * data structure.
209 * Overflow event data structure.
270 * Added structure offset comments.
280 * proper structure.
514 * Added BIOS Page 4 structure.
[all …]
|
| /linux-6.3-rc2/Documentation/crypto/ |
| 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
|
| /linux-6.3-rc2/Documentation/hid/ |
| 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
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
220 the hiddev_usage_ref structure as above, but additionally fills in
[all …]
|
| 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-6.3-rc2/Documentation/ABI/stable/ |
| A D | sysfs-firmware-efi-vars | 42 a structure that contains everything
44 For structure definition see "struct
51 match byte for byte with the structure
55 **Note** the efi_variable structure
|
| /linux-6.3-rc2/Documentation/driver-api/ |
| 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-6.3-rc2/Documentation/security/ |
| 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-6.3-rc2/Documentation/core-api/ |
| 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-6.3-rc2/Documentation/devicetree/bindings/clock/st/ |
| 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-6.3-rc2/Documentation/admin-guide/blockdev/drbd/ |
| 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.
|