Home
last modified time | relevance | path

Searched refs:structure (Results 1 – 25 of 329) sorted by relevance

12345678910>>...14

/linux-3.4.99/drivers/infiniband/core/
Dpacker.c39 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()
115 structure + desc[i].struct_offset_bytes, in ib_pack()
127 static void value_write(int offset, int size, u64 val, void *structure) in value_write() argument
[all …]
/linux-3.4.99/arch/arm/nwfpe/
DChangeLog12 - 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-3.4.99/Documentation/powerpc/
Dqe_firmware.txt89 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-3.4.99/Documentation/ioctl/
Dcdrom.txt62 DVD_READ_STRUCT Read structure
63 DVD_WRITE_STRUCT Write structure
133 cdrom_msf structure, describing a segment of music to play
157 cdrom_ti structure, describing a segment of music to play
178 cdrom_tochdr structure
181 cdrom_tochdr structure
196 cdrom_tocentry structure
199 cdrom_tocentry structure
297 cdrom_volctrl structure containing volumes for up to 4
333 cdrom_subchnl structure
[all …]
/linux-3.4.99/Documentation/virtual/kvm/
Dmsr.txt20 structure:
51 a copy of the following structure:
66 updates of this structure is arbitrary and implementation-dependent.
67 The hypervisor may update this structure at any time it sees fit until
77 of the update of this structure. Guests can subtract this value
79 structure update.
82 time at the time this structure was last updated. Unit is
193 hold a copy of the following structure:
204 updates of this structure is arbitrary and implementation-dependent.
205 The hypervisor may update this structure at any time it sees fit until
[all …]
Dnested-vmx.txt71 As a VMX implementation, nested VMX presents a VMCS structure to L1.
73 this structure is *opaque* to its user, who is not supposed to know or care
74 about its internal structure. Rather, the structure is accessed through the
77 internals of this structure; This is struct vmcs12 from arch/x86/kvm/vmx.c.
85 of this structure changes, this can break live migration across KVM versions.
/linux-3.4.99/Documentation/
Dunshare.txt182 with the current task structure and releases corresponding shared
186 structure, where as unshare operates on the current active
196 new namespace structure, the error return code will have to
199 structure, which may not exist anymore.
202 current context structure was moved into new dup_* functions. Now,
205 task structure that is being constructed. unshare system call on
208 2) For each context structure, call the corresponding unshare
210 structure, if the appropriate bit is set in the flags argument.
212 are new context structures then lock the current task structure,
213 associate new context structures with the current task structure,
[all …]
Dpadata.txt11 The first step in using padata is to set up a padata_instance structure for
98 padata_priv structure:
106 This structure will almost certainly be embedded within some larger
107 structure specific to the work to be done. Most of its fields are private to
108 padata, but the structure should be zeroed at initialisation time, and the
131 function gets the padata_priv structure pointer as its lone parameter;
133 container_of() to find the enclosing structure.
146 serial() function in the padata_priv structure. That call will happen on
Dmedia-framework.txt44 include/media/media-device.h. Allocation of the structure is handled by the
46 larger driver-specific structure.
52 The caller is responsible for initializing the media_device structure before
100 include/media/media-entity.h. The structure is usually embedded into a
101 higher-level structure, such as a v4l2_subdev or video_device instance,
116 pads array in a driver-specific structure, avoiding dynamic allocation.
179 driver-specific structure.
182 Both information are stored in the media_pad structure, making the media_pad
250 The graph structure, provided by the caller, is initialized to start graph
260 required and the graph structure can be freed normally.
[all …]
Dkobject.txt25 usually embedded within some other structure which contains the stuff
28 No structure should EVER have more than one kobject embedded within it.
32 - A ktype is the type of object that embeds a kobject. Every structure
59 direct expression of inheritance, so other techniques - such as structure
67 So, for example, the UIO code in drivers/uio/uio.c has a structure that
75 If you have a struct uio_map structure, finding its embedded kobject is
78 what is the pointer to the containing structure? You must avoid tricks
79 (such as assuming that the kobject is at the beginning of the structure)
87 * "type" is the type of the containing structure, and
88 * "member" is the name of the structure field to which "pointer" points.
[all …]
Dunaligned-memory-access.txt76 structure:
84 Let us assume that an instance of the above structure resides in memory
88 structure, i.e. address 0x10002, but that address is not evenly divisible
93 Therefore, for standard structure types you can always rely on the compiler
106 that you could reorder the fields in the structure in order to place fields
108 resident memory size of structure instances. The optimal layout of the
118 byte of padding at the end of the structure. This padding is added in order
122 structure type. This GCC-specific attribute tells the compiler never to
133 structure padding is of importance.
/linux-3.4.99/Documentation/filesystems/
Dfiles.txt25 table are in a separate structure - struct fdtable.
29 expansion of fdtable, a new fdtable structure is allocated
30 and files->fdtab points to the new structure. The fdtable
31 structure is freed with RCU and lock-free readers either
34 the fdtable structure -
61 4. To look up the file structure given an fd, a reader
79 file structure. This is avoided using atomic_long_inc_not_zero()
Dseq_file.txt88 The entire data structure for this iterator is a single loff_t value
95 structure can be used. There is also a special value which can be returned
104 modules will do what is needed to step through some data structure. The
141 seq_file iterator is finished by creating a seq_operations structure with
151 This structure will be needed to tie our iterator to the /proc file in
220 Here, the call to seq_open() takes the seq_operations structure we created
226 private field of the seq_file structure; that value can then be retrieved
231 file_operations structure will look like:
242 seq_file private field to kfree() before releasing the structure.
274 seq_list_* helpers with a pointer to the appropriate list_head structure.
[all …]
/linux-3.4.99/Documentation/rapidio/
Drapidio.txt29 structure. The core logical components of the RapidIO subsystem are defined
37 by a rio_mport data structure. This structure contains master port specific
44 independent interface for RapidIO subsystem operations, rio_mport structure
45 includes rio_ops data structure which contains pointers to hardware specific
52 structure. Devices form one global device list and per-network device lists
60 RapidIO subsystem by rio_dev data structure expanded by additional rio_switch
61 data structure, which contains switch specific information such as copy of the
72 data structure. This structure includes lists of all devices and local master
114 is successfully acquired, the enumerator allocates a new rio_dev structure and
121 structure to store switch specific information. Then the switch's vendor ID and
[all …]
/linux-3.4.99/drivers/message/fusion/lsi/
Dmpi_history.txt106 * 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-3.4.99/Documentation/hid/
Dhiddev.txt85 the value that it was changed to. Note that the structure is defined
107 hiddev_devinfo structure.
119 Gets a hiddev_devinfo structure which describes the device.
148 Fills in a hiddev_report_info structure for the user. The report is
157 filled into the returned hiddev_report_info structure.
161 hiddev_field_info structure. The user must fill in report_id and
162 report_type in this structure, as above. The field_index should also
167 Returns the usage_code in a hiddev_usage_ref structure, given that
169 field have already been filled into the structure.
172 Returns the value of a usage in a hiddev_usage_ref structure. The
[all …]
/linux-3.4.99/Documentation/ABI/stable/
Dsysfs-firmware-efi-vars41 a structure that contains everything
43 For structure definition see "struct
50 match byte for byte with the structure
54 **Note** the efi_variable structure
/linux-3.4.99/Documentation/watchdog/
Dwatchdog-kernel-api.txt32 The parameter of this routine is a pointer to a watchdog_device structure.
37 watchdog_device structure.
39 The watchdog device structure looks like this:
53 * info: a pointer to a watchdog_info structure. This structure gives some
92 The routine needs a pointer to the watchdog timer device structure as a
95 The routine needs a pointer to the watchdog timer device structure as a
107 The routine needs a pointer to the watchdog timer device structure as a
116 info structure).
126 watchdog's info structure).
158 WDIOF_MAGICCLOSE bit in the options field of the watchdog's info structure.
/linux-3.4.99/Documentation/networking/
Dsecid.txt1 flowi structure:
3 The secid member in the flow structure is used in LSMs (e.g. SELinux) to indicate
/linux-3.4.99/arch/m32r/platforms/oaks32r/
Ddot.gdbinit.nommu58 # Show current task structure
65 # Show user assigned task structure
72 Show user assigned task structure
73 arg0 : task structure address
/linux-3.4.99/Documentation/ia64/
Dparavirt_ops.txt94 This structure describes the execution environment.
96 This structure describes the various initialization hooks.
98 This structure describes hooks to iosapic operations.
100 This structure describes hooks to irq related operations
102 This structure describes hooks to steal time accounting.
127 corresponding structure in the source code.
/linux-3.4.99/Documentation/networking/caif/
Dspi_porting.txt34 a stream of data from the master. The xfer structure contains
56 returned from the platform probe function in the SPI device structure.
65 returned from the platform probe function in the SPI device structure.
69 - Filling in the SPI slave device structure:
75 Assign your private data (can be used to map to your structure).
77 - Filling in the SPI slave platform device structure:
79 Assign the SPI slave device structure as platform data.
/linux-3.4.99/Documentation/isdn/
DINTERFACE.CAPI28 capi_driver. This structure must be filled with the name and revision of the
35 struct capi_ctr before they can be used. This structure must be filled with
43 structure of the device, and signal its readiness by calling capi_ctr_ready().
58 parameter structure provided by the application. This is analogous to the
77 This structure describes a Kernel CAPI driver itself. It is used in the
92 This structure describes an ISDN device (controller) handled by a Kernel CAPI
159 capi_ctr structure is available from struct proc_dir_entry::data
198 The _cmsg structure stores the contents of a CAPI 2.0 message in an easily
237 _cmsg structure members.
241 and their _cmsg structure representation. Note that capi_cmsg2message() does
[all …]
/linux-3.4.99/Documentation/driver-model/
Doverview.txt17 Traditional driver models implemented some sort of tree-like structure
40 data structure. These fields must still be accessed by the bus layers,
57 front of the pci_dev structure. This is to make people think about what
62 the structure of struct pci_dev, and it should know the structure of struct
/linux-3.4.99/Documentation/RCU/
DwhatisRCU.txt52 within a data structure (possibly by replacing them with references to
56 either the old or the new version of the data structure rather than a
58 (e.g., freeing) the data items removed from the data structure during the
74 a. Remove pointers to a data structure, so that subsequent
81 to the data structure, so it now may safely be reclaimed
89 prevent an updater from deleting the data structure out from under them.
94 and replacement of data items in a linked structure without disrupting
141 read-side critical sections. Any RCU-protected data structure
224 given structure becomes accessible to other CPUs. That said,
257 RCU-protected structure, using the local variable is of
[all …]

12345678910>>...14