/linux/Documentation/ABI/stable/ |
H A D | sysfs-bus-vmbus | 8 What: /sys/bus/vmbus/devices/<UUID>/id 15 What: /sys/bus/vmbus/devices/<UUID>/class_id 22 What: /sys/bus/vmbus/devices/<UUID>/device_id 29 What: /sys/bus/vmbus/devices/<UUID>/channel_vp_mapping 38 What: /sys/bus/vmbus/devices/<UUID>/device 45 What: /sys/bus/vmbus/devices/<UUID>/vendor 52 What: /sys/bus/vmbus/devices/<UUID>/numa_node 59 What: /sys/bus/vmbus/devices/<UUID>/channels/<N> 66 What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/cpu 73 What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/in_mask [all …]
|
/linux/Documentation/filesystems/ext4/ |
H A 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
|
H A D | journal.rst | 85 will be an ext4 super block in the usual place, with a matching UUID. 406 - Checksum of the journal UUID, the sequence number, and the data block. 411 tag, after t_checksum. This field is not present if the "same UUID" flag 416 - A UUID to go with this tag. This field appears to be copied from the 434 - This block has the same UUID as previous, therefore the UUID field is 461 - Checksum of the journal UUID, the sequence number, and the data block. 483 "same UUID" flag is set. 487 - A UUID to go with this tag. This field appears to be copied from the 506 - Checksum of the journal UUID + the descriptor block, with this field set 578 - Checksum of the journal UUID + revocation block [all …]
|
H A 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
|
/linux/Documentation/ABI/testing/ |
H A D | sysfs-uevent | 11 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
|
H A D | debugfs-hyperv | 1 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
|
H A D | sysfs-bus-vfio-mdev | 28 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
|
H A 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.
|
H A D | configfs-stp-policy-p_sys-t | 5 UUID source identifier string, RW. 8 tagged with this UUID in the MIPI SyS-T packet stream, to
|
H A D | sysfs-class-fc | 7 identifier is typically a UUID that is associated with
|
H A D | ima_policy | 42 fsuuid:= file system UUID (e.g 8bcbe394-4f13-4144-be8e-5aa9ea2ce2f6) 189 either based on a filesystem's UUID (fsuuid) or based on LSM
|
/linux/tools/testing/selftests/pstore/ |
H A 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
|
H A D | pstore_tests | 22 echo "${TEST_STRING_PATTERN}""$UUID" > /dev/pmsg0 24 echo "$UUID" > $TOP_DIR/uuid
|
/linux/Documentation/driver-api/ |
H A D | tee.rst | 8 represented as a device identified via Universally Unique Identifier (UUID) and 14 iterates over the client driver UUID table to find a corresponding 15 match for device UUID. If a match is found, then this particular device is 34 having UUID: ``ac6a4085-0e82-4c33-bf98-8eb8e118b6c2``, so driver registration
|
/linux/Documentation/firmware-guide/acpi/ |
H A D | DSD-properties-rules.rst | 13 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 25 "Device Properties UUID" in _DSD (Device Specific Data) Implementation Guide 29 that can be returned by _DSD in the Device Properties UUID sub-package for a 34 can be returned in the Device Properties UUID sub-package for the device in 42 "Hierarchical Data Extension UUID" in _DSD (Device Specific Data) 52 Valid property sets must follow the guidance given by the Device Properties UUID 60 associated with the Device Properties UUID.
|
/linux/Documentation/admin-guide/device-mapper/ |
H A D | dm-uevent.rst | 72 :Description: UUID of the device-mapper device. 73 :Value: UUID. (Empty string if there isn't one.)
|
/linux/Documentation/firmware-guide/acpi/dsd/ |
H A D | phy.rst | 17 Properties UUID For _DSD" [dsd-guide] document and the 18 daffd814-6eba-4d8c-8a91-bc9bbf4aa301 UUID must be used in the Device 62 hierarchical data extension (UUID dbb8e3e6-5886-4ba6-8795-1319f52a966b
|
/linux/Documentation/filesystems/ |
H A D | overlayfs.rst | 633 UUID of the lower filesystem, are encoded and stored in an extended 639 that the found lower directory file handle and lower filesystem UUID 671 - UUID of the underlying filesystem 679 1. Find underlying layer by UUID and path type information. 724 UUID and fsid 731 UUID of overlayfs is null. fsid is taken from upper most filesystem. 733 UUID of overlayfs is null. fsid is taken from upper most filesystem. 734 UUID of underlying layers is ignored. 736 UUID of overlayfs is generated and used to report a unique fsid. 737 UUID is stored in xattr "trusted.overlay.uuid", making overlayfs fsid [all …]
|
H A D | gfs2-uevents.rst | 104 4. UUID= 107 With recent versions of gfs2-utils, mkfs.gfs2 writes a UUID
|
/linux/Documentation/tee/ |
H A D | ts-tee.rst | 20 All Trusted Services (TS) SPs have the same FF-A UUID; it identifies the TS RPC 22 A service is identified by its service UUID; the same type of service cannot be
|
/linux/Documentation/driver-api/pldmfw/ |
H A D | file-format.rst | 52 The package header begins with the UUID of the PLDM file format, and 61 | PLDM UUID |
|
/linux/fs/pstore/ |
H A D | Kconfig | 122 The UUID may be either an EFI/GPT UUID, or refer to an MSDOS 126 6) PARTUUID=<UUID>/PARTNROFF=<int> to select a partition in relation
|
/linux/drivers/platform/mellanox/ |
H A D | mlxbf-bootctl.c | 771 u64 uuid_data[MLNX_MFG_VAL_QWORD_CNT(UUID) + 1] = { 0 }; in uuid_show() 776 for (word = 0; word < MLNX_MFG_VAL_QWORD_CNT(UUID); word++) { in uuid_show() 795 u64 uuid[MLNX_MFG_VAL_QWORD_CNT(UUID)] = { 0 }; in uuid_store() 805 for (word = 0; word < MLNX_MFG_VAL_QWORD_CNT(UUID); word++) { in uuid_store()
|
/linux/Documentation/admin-guide/nfs/ |
H A D | nfs-client.rst | 43 The nfs.nfs4_unique_id string is typically a UUID, though it can contain 46 just as a system's root file system gets a fresh UUID in its label at
|
/linux/Documentation/translations/zh_CN/core-api/ |
H A D | printk-formats.rst | 365 UUID/GUID地址 375 用于打印16字节的UUID/GUIDs地址。附加的 ``l`` , ``L`` , ``b`` 和 ``B`` 占位符用
|