| /linux/arch/s390/mm/ |
| H A D | dump_pagetables.c | 27 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 D | yamltree.c | 32 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()
|
| H A D | data.c | 12 m = d.markers; in data_free()
123 /* Adjust all markers after the one we're inserting at */ in data_insert_at_marker()
132 struct marker **mp = &d.markers; in data_append_markers()
144 struct marker *m2 = d2.markers; in data_merge()
152 d2.markers = NULL; /* So data_free() doesn't clobber them */ in data_merge()
264 /* Copy all markers from old value */
265 marker = old.markers;
|
| H A D | treesource.c | 146 * - for a single offset that has both a type marker and non-type markers, the in add_string_markers()
180 struct marker **mi = &prop->val.markers; in guess_value_type()
190 struct marker *m = prop->val.markers; in guess_value_type()
224 struct marker *m = prop->val.markers; in write_propval()
247 dummy_marker.next = prop->val.markers; in write_propval()
273 m_phandle = prop->val.markers; in write_propval()
|
| H A D | livetree.c | 485 m = p->val.markers; in get_marker_label()
906 m = prop->val.markers; in any_fixup_tree()
958 m = prop->val.markers; in generate_fixups_tree_internal()
977 m = prop->val.markers; in any_local_fixup_tree()
1037 m = prop->val.markers; in generate_local_fixups_tree_internal()
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-jpeg.rst | 56 markers (m = 0..7). The purpose of these markers is to additionally
62 markers will not be inserted.
82 Specify which JPEG markers are included in compressed stream. This
|
| H A D | vidioc-g-jpegcomp.rst | 40 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 D | jpeg-core.h | 164 * 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 D | guard-regions.c | 543 /* We want guard markers at start/end of each VMA. */ in TEST_F()
614 /* Assert that unmapping ranges does not leave guard markers behind. */
652 /* Assert that mprotect() operations have no bearing on guard markers. */
831 /* Assert that MADV_DONTNEED does not remove guard markers. */
860 /* Check to ensure guard markers are still in place. */ in TEST_F()
892 /* Assert that mlock()'ed pages work correctly with guard markers. */
962 * guard markers where possible.
964 * - Moving a mapping alone should retain markers as they are.
976 /* Place guard markers at both ends of the 5 page span. */ in TEST_F()
993 /* Make sure the guard markers are retained. */ in TEST_F()
[all …]
|
| /linux/include/linux/ |
| H A D | userfaultfd_k.h | 233 * If user requested uffd-wp but not enabled pte markers for in vma_can_userfault()
422 /* Only wr-protect mode uses pte markers */ in userfaultfd_wp_use_markers()
426 /* File-based uffd-wp always need markers */ in userfaultfd_wp_use_markers()
431 * Anonymous uffd-wp only needs the markers if WP_UNPOPULATED in userfaultfd_wp_use_markers()
432 * enabled (to apply markers on zero pages). in userfaultfd_wp_use_markers()
|
| /linux/tools/include/uapi/linux/ |
| H A D | coredump.h | 82 * enum coredump_mark - Markers for the coredump socket
85 * markers notify userspace whether the coredump ack succeeded or
|
| /linux/include/uapi/linux/ |
| H A D | coredump.h | 82 * enum coredump_mark - Markers for the coredump socket
85 * markers notify userspace whether the coredump ack succeeded or
|
| H A D | atm_nicstar.h | 28 /* set buffer level markers */
|
| /linux/Documentation/devicetree/bindings/mtd/ |
| H A D | raw-nand-chip.yaml | 66 find Bad Block Markers (BBM). These markers will help to
|
| /linux/Documentation/process/ |
| H A D | backporting.rst | 43 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/include/media/ |
| H A D | jpeg.h | 6 /* JPEG markers */
|
| /linux/arch/arm/include/asm/ |
| H A D | ptdump.h | 18 const struct addr_marker *markers; member
|
| /linux/drivers/char/ |
| H A D | dtlk.c | 28 read from the TTS port, and index markers (which mark the progress
30 DoubleTalk PC implement index markers. Both the TTS and LPC ports
44 "read" gets index markers from the LPC port. If the device does
45 not implement index markers, the read will fail with error EINVAL.
|
| /linux/Documentation/trace/ |
| H A D | mmiotrace.rst | 70 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 D | nand_esmt.c | 46 * with the factory bad block markers in the first or last page in esmt_nand_init()
|
| H A D | nand_amd.c | 41 * the bad block markers can be in the first, second or last in amd_nand_init()
|
| /linux/arch/x86/mm/ |
| H A D | dump_pagetables.c | 49 /* Address space markers hints */
364 * We print markers for special areas of address space, in note_page()
517 * Various markers are not compile-time constants, so assign them in pt_dump_init()
|
| /linux/tools/testing/selftests/hid/tests/ |
| H A D | conftest.py | 44 "markers",
|
| /linux/arch/arm64/include/asm/ |
| H A D | ptdump.h | 24 const struct addr_marker *markers; member
|
| /linux/drivers/net/ethernet/intel/ice/ |
| H A D | ice_parser.h | 327 u8 markers[ICE_MK_COUNT_PER_GRP]; member
440 u8 markers[ICE_MARKER_ID_SIZE]; member
|