Home
last modified time | relevance | path

Searched refs:UUID (Results 1 – 25 of 55) sorted by relevance

123

/kernel/linux/linux-5.10/Documentation/ABI/stable/
Dsysfs-bus-vmbus1 What: /sys/bus/vmbus/devices/<UUID>/id
8 What: /sys/bus/vmbus/devices/<UUID>/class_id
15 What: /sys/bus/vmbus/devices/<UUID>/device_id
22 What: /sys/bus/vmbus/devices/<UUID>/channel_vp_mapping
31 What: /sys/bus/vmbus/devices/<UUID>/device
38 What: /sys/bus/vmbus/devices/<UUID>/vendor
45 What: /sys/bus/vmbus/devices/<UUID>/numa_node
52 What: /sys/bus/vmbus/devices/<UUID>/channels/<N>
59 What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/cpu
66 What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/in_mask
[all …]
/kernel/linux/linux-5.10/Documentation/filesystems/ext4/
Dchecksums.rst39 - The entire superblock up to the checksum field. The UUID lives inside
43 - UUID + the entire MMP block up to the checksum field.
46 - UUID + the entire extended attribute block. The checksum field is set to
50 - UUID + inode number + inode generation + the directory block up to the
54 - UUID + inode number + inode generation + all valid extents + HTREE tail.
58 - UUID + inode number + inode generation + the entire extent block up to
62 - UUID + the entire bitmap. Checksums are stored in the group descriptor,
66 - UUID + inode number + inode generation + the entire inode. The checksum
70 - If metadata\_csum, then UUID + group number + the entire descriptor;
71 else if gdt\_csum, then crc16(UUID + group number + the entire
Djournal.rst85 will be an ext4 super block in the usual place, with a matching UUID.
401 - Checksum of the journal UUID, the sequence number, and the data block.
406 tag, after t_checksum. This field is not present if the "same UUID" flag
411 - A UUID to go with this tag. This field appears to be copied from the
429 - This block has the same UUID as previous, therefore the UUID field is
456 - Checksum of the journal UUID, the sequence number, and the data block.
478 "same UUID" flag is set.
482 - A UUID to go with this tag. This field appears to be copied from the
501 - Checksum of the journal UUID + the descriptor block, with this field set
573 - Checksum of the journal UUID + revocation block
[all …]
Dgroup_descr.rst36 checksum is the crc16 of the FS UUID, the group number, and the group
38 checksum is the lower 16 bits of the checksum of the FS UUID, the group
40 checksums are calculated against the FS UUID, the group number, and the
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-uevent11 ACTION [UUID [KEY=VALUE ...]
18 You need to pass UUID first before any KEY=VALUE pairs.
19 The UUID must be in ``xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx``
20 format where 'x' is a hex digit. The UUID is considered to be
21 a transaction identifier so it's possible to use the same UUID
24 listeners. The UUID value appears in uevent as
28 If UUID is not passed in, the generated synthetic uevent gains
Ddebugfs-hyperv1 What: /sys/kernel/debug/hyperv/<UUID>/fuzz_test_state
9 What: /sys/kernel/debug/hyperv/<UUID>/delay/fuzz_test_buffer_interrupt_delay
17 What: /sys/kernel/debug/hyperv/<UUID>/delay/fuzz_test_message_delay
Dsysfs-block-dm13 Description: Device-mapper device UUID.
14 Read-only string containing DM-UUID or empty string
15 if DM-UUID is not set.
Dsysfs-bus-vfio-mdev28 Writing UUID to this file will create mediated device of
89 What: /sys/.../<device>/<UUID>/
97 What: /sys/.../<device>/<UUID>/mdev_type
104 What: /sys/.../<device>/<UUID>/remove
113 # echo 1 > /sys/bus/mdev/devices/<UUID>/remove
Dconfigfs-stp-policy-p_sys-t5 UUID source identifier string, RW.
8 tagged with this UUID in the MIPI SyS-T packet stream, to
/kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/
DDSD-properties-rules.rst13 be identified by a UUID which must be recognized by the driver processing the
23 generic Device Properties UUID in the _DSD return package as specified in the
24 Device Properties UUID definition document [1]_.
27 that can be returned by _DSD in the Device Properties UUID sub-package for a
32 can be returned in the Device Properties UUID sub-package for the device in
39 Hierarchical Properties Extension UUID definition document [2]_.
48 Valid property sets must follow the guidance given by the Device Properties UUID
56 associated with the Device Properties UUID.
99 .. [1] https://www.uefi.org/sites/default/files/resources/_DSD-device-properties-UUID.pdf
100 .. [2] https://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.…
/kernel/linux/linux-5.10/tools/testing/selftests/pstore/
Dcommon_tests58 UUID=`cat /proc/sys/kernel/random/uuid`
60 LOG_DIR=$TOP_DIR/logs/`date +%Y%m%d-%H%M%S`_${UUID}/
74 prlog "UUID="$UUID
Dpstore_tests22 echo "${TEST_STRING_PATTERN}""$UUID" > /dev/pmsg0
24 echo "$UUID" > $TOP_DIR/uuid
/kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/dsd/
Ddata-node-references.rst93 [1] Hierarchical Data Extension UUID For _DSD.
94 <https://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.1.pdf>,
97 [2] Device Properties UUID For _DSD.
98 <https://www.uefi.org/sites/default/files/resources/_DSD-device-properties-UUID.pdf>,
Dleds.rst103 [5] Device Properties UUID For _DSD.
104 <URL:https://www.uefi.org/sites/default/files/resources/_DSD-device-properties-UUID.pdf>,
107 [6] Hierarchical Data Extension UUID For _DSD.
108 …<URL:https://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.1…
Dgraph.rst164 [4] Device Properties UUID For _DSD.
165 https://www.uefi.org/sites/default/files/resources/_DSD-device-properties-UUID.pdf,
168 [5] Hierarchical Data Extension UUID For _DSD.
169 … https://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.1.pdf,
/kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/
Ddm-uevent.rst72 :Description: UUID of the device-mapper device.
73 :Value: UUID. (Empty string if there isn't one.)
/kernel/linux/linux-5.10/Documentation/driver-api/pldmfw/
Dfile-format.rst52 The package header begins with the UUID of the PLDM file format, and
61 | PLDM UUID |
/kernel/linux/linux-5.10/Documentation/staging/
Dtee.rst60 represented as a device identified via Universally Unique Identifier (UUID) and
66 iterates over the client driver UUID table to find a corresponding
67 match for device UUID. If a match is found, then this particular device is
86 having UUID: ``ac6a4085-0e82-4c33-bf98-8eb8e118b6c2``, so driver registration
/kernel/linux/linux-5.10/Documentation/filesystems/
Dgfs2-uevents.rst104 4. UUID=
107 With recent versions of gfs2-utils, mkfs.gfs2 writes a UUID
Doverlayfs.rst395 handle of the lower layer root directory, along with the UUID of the lower
398 the lower root directory file handle and lower filesystem UUID are compared
402 does not support NFS export, lower filesystem does not have a valid UUID or
483 UUID of the lower filesystem, are encoded and stored in an extended
489 that the found lower directory file handle and lower filesystem UUID
520 - UUID of the underlying filesystem
528 1. Find underlying layer by UUID and path type information.
/kernel/linux/linux-5.10/fs/pstore/
DKconfig209 The UUID may be either an EFI/GPT UUID, or refer to an MSDOS
213 6) PARTUUID=<UUID>/PARTNROFF=<int> to select a partition in relation
/kernel/linux/linux-5.10/Documentation/admin-guide/nfs/
Dnfs-client.rst44 The nfs.nfs4_unique_id string is typically a UUID, though it can contain
47 just as a system's root file system gets a fresh UUID in its label at
/kernel/linux/linux-5.10/security/integrity/evm/
DKconfig21 Include filesystem UUID for HMAC calculation.
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dpstore-blk.rst58 a partition if the partition table provides it. The UUID may be either an
59 EFI/GPT UUID, or refer to an MSDOS partition using the format SSSSSSSS-PP,
63 #. PARTUUID=<UUID>/PARTNROFF=<int> to select a partition in relation to a
/kernel/linux/linux-5.10/Documentation/trace/
Dsys-t.rst46 The most important one here is the "uuid", which determines the UUID

123