Home
last modified time | relevance | path

Searched refs:markers (Results 1 – 23 of 23) sorted by relevance

/linux/arch/s390/mm/
H A Ddump_pagetables.c27 static struct addr_marker *markers; variable
247 .marker = markers, in ptdump_show()
297 newsize = (markers_cnt + 2) * sizeof(*markers); in add_marker()
298 new = kvrealloc(markers, newsize, GFP_KERNEL); in add_marker()
301 markers = new; in add_marker()
302 markers[markers_cnt].is_start = 1; in add_marker()
303 markers[markers_cnt].start_address = start; in add_marker()
304 markers[markers_cnt].size = end - start; in add_marker()
305 markers[markers_cnt].name = name; in add_marker()
307 markers[markers_cnt].is_start = 0; in add_marker()
[all …]
/linux/scripts/dtc/
H A Dyamltree.c32 static void yaml_propval_int(yaml_emitter_t *emitter, struct marker *markers, in yaml_propval_int() argument
67 m = markers; in yaml_propval_int()
117 struct marker *m = prop->val.markers; in yaml_propval()
118 struct marker *markers = prop->val.markers; in yaml_propval() local
156 yaml_propval_int(emitter, markers, data, m->offset, chunk_len, 2); in yaml_propval()
159 yaml_propval_int(emitter, markers, data, m->offset, chunk_len, 4); in yaml_propval()
162 yaml_propval_int(emitter, markers, data, m->offset, chunk_len, 8); in yaml_propval()
168 yaml_propval_int(emitter, markers, data, m->offset, chunk_len, 1); in yaml_propval()
/linux/Documentation/userspace-api/media/v4l/
H A Dext-ctrls-jpeg.rst57 markers (m = 0..7). The purpose of these markers is to additionally
63 markers will not be inserted.
83 Specify which JPEG markers are included in compressed stream. This
H A Dvidioc-g-jpegcomp.rst40 markers control.
89 - See :ref:`jpeg-markers`. Deprecated. If
96 .. _jpeg-markers:
/linux/scripts/
H A Dkallsyms.c343 unsigned int *markers, markers_cnt; in write_src() local
355 markers = xmalloc(sizeof(*markers) * markers_cnt); in write_src()
361 markers[i >> 8] = off; in write_src()
405 printf("\t.long\t%u\n", markers[i]); in write_src()
408 free(markers); in write_src()
/linux/arch/riscv/mm/
H A Dptdump.c55 const struct addr_marker *markers; member
108 .markers = address_markers,
122 .markers = efi_addr_markers,
356 .marker = pinfo->markers, in ptdump_walk()
/linux/arch/arm/include/asm/
H A Dptdump.h18 const struct addr_marker *markers; member
/linux/arch/arm64/include/asm/
H A Dptdump.h24 const struct addr_marker *markers; member
/linux/drivers/firmware/efi/
H A Darm-runtime.c33 .markers = (struct addr_marker[]){
/linux/arch/arm64/mm/
H A Dptdump.c303 .marker = info->markers, in ptdump_walk()
402 kernel_ptdump_info.markers = memcpy(address_markers, m, sizeof(m)); in ptdump_init()
/linux/drivers/net/ethernet/intel/ice/
H A Dice_parser.h327 u8 markers[ICE_MK_COUNT_PER_GRP]; member
440 u8 markers[ICE_MARKER_ID_SIZE]; member
H A Dice_parser_rt.c668 rt->markers[byte] |= (u8)BIT(bit); in ice_marker_set()
681 u8 marker = mk_grp->markers[i]; in ice_marker_update()
705 rt->markers, ICE_MARKER_ID_SIZE); in ice_ptype_resolve()
H A Dice_parser.c1524 dev_info(dev, "%d ", item->markers[i]); in ice_mk_grp_dump()
1539 grp->markers[i] = buf[i]; in ice_mk_grp_parse_item()
/linux/arch/arm/mm/
H A Ddump.c419 .marker = info->markers, in ptdump_walk_pgd()
449 .markers = address_markers,
/linux/
H A D.gitignore74 /Module.markers
/linux/Documentation/process/
H A Dbackporting.rst43 destination tree, as this will make git output conflict markers and let
105 edits the files to include so-called conflict markers showing you where
247 Understanding conflict markers
255 inserted conflict markers into your file. Out of the box, this will look
277 from its normal behavior. Notice the two columns of diff markers
374 For particularly nasty conflicts with many conflict markers, you can use
385 renamed, as that typically means git won't even put in conflict markers,
/linux/Documentation/trace/
H A Dmmiotrace.rst70 During tracing you can place comments (markers) into the trace by
73 which action. It is recommended to place descriptive markers about what you
/linux/Documentation/power/
H A Ds2ram.rst24 time-consuming - having to insert TRACE_RESUME() markers into the device
/linux/tools/memory-model/Documentation/
H A Dordering.txt374 This category includes read-side markers such as rcu_read_lock()
378 Compared to locking primitives and RMW atomic operations, markers
381 For example, the rcu_read_lock() and rcu_read_unlock() markers interact
/linux/Documentation/driver-api/soundwire/
H A Dbra.rst184 hardware typically inserts markers to help software and hardware
/linux/Documentation/input/
H A Devent-codes.rst36 - Used as markers to separate events. Events may be separated in time or in
/linux/Documentation/RCU/
H A Dchecklist.rst365 and the read-side markers (rcu_read_lock() and rcu_read_unlock(),
/linux/Documentation/scsi/
H A DChangeLog.lpfc428 * Fix sparse warnings by adding __iomem markers to lpfc_compat.h.