Searched refs:UUID (Results 1 – 25 of 43) sorted by relevance
12
/Linux-v4.19/Documentation/ABI/stable/ |
D | sysfs-bus-vmbus | 1 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>/cpu [all …]
|
D | sysfs-hypervisor-xen | 93 UUID of the guest as known to the Xen hypervisor.
|
/Linux-v4.19/Documentation/filesystems/ext4/ondisk/ |
D | checksums.rst | 39 - 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
|
D | journal.rst | 74 will be an ext4 super block in the usual place, with a matching UUID. 384 - Checksum of the journal UUID, the sequence number, and the data block. 389 tag, after t_checksum. This field is not present if the "same UUID" flag 394 - A UUID to go with this tag. This field appears to be copied from the 412 - This block has the same UUID as previous, therefore the UUID field is 439 - Checksum of the journal UUID, the sequence number, and the data block. 461 "same UUID" flag is set. 465 - A UUID to go with this tag. This field appears to be copied from the 484 - Checksum of the journal UUID + the descriptor block, with this field set 556 - Checksum of the journal UUID + revocation block [all …]
|
D | group_descr.rst | 36 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
|
D | mmp.rst | 31 The checksum is calculated against the FS UUID and the MMP structure.
|
D | super.rst | 16 which includes the FS UUID. 178 - 128-bit UUID for volume. 218 - UUID of journal superblock 631 the administrator to change the UUID of a metadata\_csum filesystem
|
/Linux-v4.19/Documentation/ABI/testing/ |
D | sysfs-uevent | 9 Recognized extended format is ACTION [UUID [KEY=VALUE ...]. 16 You need to pass UUID first before any KEY=VALUE pairs. 17 The UUID must be in "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" 18 format where 'x' is a hex digit. The UUID is considered to be 19 a transaction identifier so it's possible to use the same UUID 22 listeners. The UUID value appears in uevent as 26 If UUID is not passed in, the generated synthetic uevent gains
|
D | sysfs-block-dm | 13 Description: Device-mapper device UUID. 14 Read-only string containing DM-UUID or empty string 15 if DM-UUID is not set.
|
D | sysfs-bus-vfio-mdev | 28 Writing UUID to this file will create mediated device of 88 What: /sys/.../<device>/<UUID>/ 96 What: /sys/.../<device>/<UUID>/mdev_type 103 What: /sys/.../<device>/<UUID>/remove 111 # echo 1 > /sys/bus/mdev/devices/<UUID>/remove
|
D | ima_policy | 35 fsuuid:= file system UUID (e.g 8bcbe394-4f13-4144-be8e-5aa9ea2ce2f6)
|
D | sysfs-bus-rbd | 157 cluster_fsid: (RO) The ceph cluster UUID.
|
/Linux-v4.19/Documentation/acpi/ |
D | DSD-properties-rules.txt | 10 be identified by a UUID which must be recognized by the driver processing the 20 generic Device Properties UUID in the _DSD return package as specified in the 21 Device Properties UUID definition document [1]. 24 that can be returned by _DSD in the Device Properties UUID sub-package for a 29 can be returned in the Device Properties UUID sub-package for the device in 36 Hierarchical Properties Extension UUID definition document [2]. 45 Valid property sets must follow the guidance given by the Device Properties UUID 53 associated with the Device Properties UUID. 96 [1] http://www.uefi.org/sites/default/files/resources/_DSD-device-properties-UUID.pdf 97 [2] http://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.1.pdf
|
/Linux-v4.19/tools/testing/selftests/pstore/ |
D | common_tests | 58 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
|
D | pstore_tests | 22 echo "${TEST_STRING_PATTERN}""$UUID" > /dev/pmsg0 24 echo "$UUID" > $TOP_DIR/uuid
|
/Linux-v4.19/Documentation/acpi/dsd/ |
D | data-node-references.txt | 83 [1] Hierarchical Data Extension UUID For _DSD. 84 …<URL:http://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.1.… 87 [2] Device Properties UUID For _DSD. 88 <URL:http://www.uefi.org/sites/default/files/resources/_DSD-device-properties-UUID.pdf>,
|
D | graph.txt | 161 [4] Device Properties UUID For _DSD. 162 <URL:http://www.uefi.org/sites/default/files/resources/_DSD-device-properties-UUID.pdf>, 165 [5] Hierarchical Data Extension UUID For _DSD. 166 …<URL:http://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.1.…
|
/Linux-v4.19/Documentation/device-mapper/ |
D | dm-uevent.txt | 61 Description: UUID of the device-mapper device. 62 Value: UUID. (Empty string if there isn't one.)
|
/Linux-v4.19/Documentation/misc-devices/mei/ |
D | mei.txt | 17 Each Intel ME feature (Intel ME Client) is addressed by a GUID/UUID and 55 MEI_CONNECT_CLIENT_IOCTL, which passes the desired UUID. 110 in_client_uuid - UUID of the FW Feature that needs 118 (e.g. Wrong UUID) 195 firmware feature using a defined UUID and then communicates with the feature
|
/Linux-v4.19/Documentation/filesystems/ |
D | gfs2-uevents.txt | 93 4. UUID= 95 With recent versions of gfs2-utils, mkfs.gfs2 writes a UUID
|
D | overlayfs.txt | 310 handle of the lower layer root directory, along with the UUID of the lower 313 the lower root directory file handle and lower filesystem UUID are compared 317 does not support NFS export, lower filesystem does not have a valid UUID or 385 UUID of the lower filesystem, are encoded and stored in an extended 391 that the found lower directory file handle and lower filesystem UUID 422 - UUID of the underlying filesystem 430 1. Find underlying layer by UUID and path type information.
|
/Linux-v4.19/sound/soc/intel/skylake/ |
D | skl-sst-utils.c | 31 struct UUID { struct 68 struct UUID uuid;
|
/Linux-v4.19/Documentation/filesystems/nfs/ |
D | nfs.txt | 41 The nfs.nfs4_unique_id string is typically a UUID, though it can contain 44 just as a system's root file system gets a fresh UUID in its label at
|
/Linux-v4.19/security/integrity/evm/ |
D | Kconfig | 20 Include filesystem UUID for HMAC calculation.
|
/Linux-v4.19/Documentation/admin-guide/ |
D | bcache.rst | 89 cache set shows up as /sys/fs/bcache/<UUID> 96 device to a cache set is done thusly, with the UUID of the cache set in 99 echo <CSET-UUID> > /sys/block/bcache0/bcache/attach 214 UUID: 7be7e175-8f4c-4f99-94b2-9c904d227045 215 Set UUID: 5bc072a8-ab17-446d-9744-e247949913c1 300 The device names will show which UUID is relevant, cd in that directory 403 Echo the UUID of a cache set to this file to enable caching.
|
12