Home
last modified time | relevance | path

Searched full:markers (Results 1 – 25 of 80) sorted by relevance

1234

/linux/arch/s390/mm/
H A Ddump_pagetables.c27 static struct addr_marker *markers; variable
247 .marker = markers, in ptdump_show()
268 * If the start addresses of two markers are identical sort markers in an in ptdump_cmp()
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()
[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
137 die("No markers present in property '%s' value\n", prop->name); in yaml_propval()
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:
98 .. flat-table:: JPEG Markers Flags
/linux/drivers/media/platform/samsung/s5p-jpeg/
H A Djpeg-core.h164 * struct s5p_jpeg_marker - collection of markers from jpeg header
165 * @marker: markers' positions relative to the buffer beginning
166 * @len: markers' payload lengths (without length field)
167 * @n: number of markers in collection
/linux/tools/testing/selftests/mm/
H A Dguard-regions.c593 /* We want guard markers at start/end of each VMA. */ in TEST_F()
664 /* Assert that unmapping ranges does not leave guard markers behind. */ in TEST_F()
702 /* Assert that mprotect() operations have no bearing on guard markers. */ in TEST_F()
881 /* Assert that MADV_DONTNEED does not remove guard markers. */ in TEST_F()
910 /* Check to ensure guard markers are still in place. */ in TEST_F()
942 /* Assert that mlock()'ed pages work correctly with guard markers. */ in TEST_F()
1012 * guard markers where possible.
1014 * - Moving a mapping alone should retain markers as they are.
1026 /* Place guard markers at both ends of the 5 page span. */ in TEST_F()
1043 /* Make sure the guard markers ar in TEST_F()
[all...]
/linux/scripts/
H A Dkallsyms.c343 unsigned int *markers, markers_cnt; in write_src() local
352 /* table of offset markers, that give the offset in the compressed stream in write_src()
355 markers = xmalloc(sizeof(*markers) * markers_cnt); in write_src()
361 markers[i >> 8] = off; in write_src()
406 printf("\t.long\t%u\n", markers[i]); in write_src()
410 free(markers); in write_src()
/linux/tools/include/uapi/linux/
H A Dcoredump.h82 * enum coredump_mark - Markers for the coredump socket
85 * markers notify userspace whether the coredump ack succeeded or
/linux/include/uapi/linux/
H A Dcoredump.h82 * enum coredump_mark - Markers for the coredump socket
85 * markers notify userspace whether the coredump ack succeeded or
/linux/include/media/
H A Djpeg.h6 /* JPEG markers */
/linux/arch/arm/include/asm/
H A Dptdump.h18 const struct addr_marker *markers; member
/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/drivers/mtd/nand/raw/
H A Dnand_esmt.c46 * with the factory bad block markers in the first or last page in esmt_nand_init()
H A Dnand_amd.c41 * the bad block markers can be in the first, second or last in amd_nand_init()
/linux/tools/testing/selftests/hid/tests/
H A Dconftest.py58 "markers",
/linux/include/linux/
H A Dmmiotrace.h52 /* For anyone to insert markers. Remember trailing newline. */
/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
/linux/Documentation/power/
H A Ds2ram.rst24 time-consuming - having to insert TRACE_RESUME() markers into the device
/linux/drivers/media/pci/zoran/
H A Dzr36050.h133 /* zr36050 markers-enable register bits */
H A Dzr36060.h152 /* ZR36060 Markers Enable register */
/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/tools/lib/api/fs/
H A Dtracing_path.c144 /* sdt markers */ in tracing_path__strerror_open_tp()
/linux/drivers/firmware/efi/
H A Darm-runtime.c33 .markers = (struct addr_marker[]){
/linux/arch/arm/mm/
H A Ddump.c419 .marker = info->markers, in ptdump_walk_pgd()
449 .markers = address_markers,
/linux/include/linux/mtd/
H A Dbbm.h94 * Do not write new bad block markers to OOB; useful, e.g., when ECC covers

1234