Loading .clang-format +1 −0 Original line number Diff line number Diff line Loading @@ -222,6 +222,7 @@ ForEachMacros: - 'for_each_component_dais' - 'for_each_component_dais_safe' - 'for_each_console' - 'for_each_console_srcu' - 'for_each_cpu' - 'for_each_cpu_and' - 'for_each_cpu_not' Loading .mailmap +1 −0 Original line number Diff line number Diff line Loading @@ -137,6 +137,7 @@ Filipe Lautert <filipe@icewall.org> Finn Thain <fthain@linux-m68k.org> <fthain@telegraphics.com.au> Franck Bui-Huu <vagabon.xyz@gmail.com> Frank Rowand <frowand.list@gmail.com> <frank.rowand@am.sony.com> Frank Rowand <frowand.list@gmail.com> <frank.rowand@sony.com> Frank Rowand <frowand.list@gmail.com> <frank.rowand@sonymobile.com> Frank Rowand <frowand.list@gmail.com> <frowand@mvista.com> Frank Zago <fzago@systemfabricworks.com> Loading Documentation/ABI/testing/sysfs-bus-pci +33 −0 Original line number Diff line number Diff line Loading @@ -457,3 +457,36 @@ Description: The file is writable if the PF is bound to a driver that implements ->sriov_set_msix_vec_count(). What: /sys/bus/pci/devices/.../resourceN_resize Date: September 2022 Contact: Alex Williamson <alex.williamson@redhat.com> Description: These files provide an interface to PCIe Resizable BAR support. A file is created for each BAR resource (N) supported by the PCIe Resizable BAR extended capability of the device. Reading each file exposes the bitmap of available resource sizes: # cat resource1_resize 00000000000001c0 The bitmap represents supported resource sizes for the BAR, where bit0 = 1MB, bit1 = 2MB, bit2 = 4MB, etc. In the above example the device supports 64MB, 128MB, and 256MB BAR sizes. When writing the file, the user provides the bit position of the desired resource size, for example: # echo 7 > resource1_resize This indicates to set the size value corresponding to bit 7, 128MB. The resulting size is 2 ^ (bit# + 20). This definition matches the PCIe specification of this capability. In order to make use of resource resizing, all PCI drivers must be unbound from the device and peer devices under the same parent bridge may need to be soft removed. In the case of VGA devices, writing a resize value will remove low level console drivers from the device. Raw users of pci-sysfs resourceN attributes must be terminated prior to resizing. Success of the resizing operation is not guaranteed. Documentation/ABI/testing/sysfs-devices-vfio-dev 0 → 100644 +8 −0 Original line number Diff line number Diff line What: /sys/.../<device>/vfio-dev/vfioX/ Date: September 2022 Contact: Yi Liu <yi.l.liu@intel.com> Description: This directory is created when the device is bound to a vfio driver. The layout under this directory matches what exists for a standard 'struct device'. 'X' is a unique index marking this device in vfio. Documentation/ABI/testing/sysfs-fs-f2fs +24 −0 Original line number Diff line number Diff line Loading @@ -466,6 +466,30 @@ Description: Show status of f2fs superblock in real time. 0x4000 SBI_IS_FREEZING freefs is in process ====== ===================== ================================= What: /sys/fs/f2fs/<disk>/stat/cp_status Date: September 2022 Contact: "Chao Yu" <chao.yu@oppo.com> Description: Show status of f2fs checkpoint in real time. =============================== ============================== cp flag value CP_UMOUNT_FLAG 0x00000001 CP_ORPHAN_PRESENT_FLAG 0x00000002 CP_COMPACT_SUM_FLAG 0x00000004 CP_ERROR_FLAG 0x00000008 CP_FSCK_FLAG 0x00000010 CP_FASTBOOT_FLAG 0x00000020 CP_CRC_RECOVERY_FLAG 0x00000040 CP_NAT_BITS_FLAG 0x00000080 CP_TRIMMED_FLAG 0x00000100 CP_NOCRC_RECOVERY_FLAG 0x00000200 CP_LARGE_NAT_BITMAP_FLAG 0x00000400 CP_QUOTA_NEED_FSCK_FLAG 0x00000800 CP_DISABLED_FLAG 0x00001000 CP_DISABLED_QUICK_FLAG 0x00002000 CP_RESIZEFS_FLAG 0x00004000 =============================== ============================== What: /sys/fs/f2fs/<disk>/ckpt_thread_ioprio Date: January 2021 Contact: "Daeho Jeong" <daehojeong@google.com> Loading Loading
.clang-format +1 −0 Original line number Diff line number Diff line Loading @@ -222,6 +222,7 @@ ForEachMacros: - 'for_each_component_dais' - 'for_each_component_dais_safe' - 'for_each_console' - 'for_each_console_srcu' - 'for_each_cpu' - 'for_each_cpu_and' - 'for_each_cpu_not' Loading
.mailmap +1 −0 Original line number Diff line number Diff line Loading @@ -137,6 +137,7 @@ Filipe Lautert <filipe@icewall.org> Finn Thain <fthain@linux-m68k.org> <fthain@telegraphics.com.au> Franck Bui-Huu <vagabon.xyz@gmail.com> Frank Rowand <frowand.list@gmail.com> <frank.rowand@am.sony.com> Frank Rowand <frowand.list@gmail.com> <frank.rowand@sony.com> Frank Rowand <frowand.list@gmail.com> <frank.rowand@sonymobile.com> Frank Rowand <frowand.list@gmail.com> <frowand@mvista.com> Frank Zago <fzago@systemfabricworks.com> Loading
Documentation/ABI/testing/sysfs-bus-pci +33 −0 Original line number Diff line number Diff line Loading @@ -457,3 +457,36 @@ Description: The file is writable if the PF is bound to a driver that implements ->sriov_set_msix_vec_count(). What: /sys/bus/pci/devices/.../resourceN_resize Date: September 2022 Contact: Alex Williamson <alex.williamson@redhat.com> Description: These files provide an interface to PCIe Resizable BAR support. A file is created for each BAR resource (N) supported by the PCIe Resizable BAR extended capability of the device. Reading each file exposes the bitmap of available resource sizes: # cat resource1_resize 00000000000001c0 The bitmap represents supported resource sizes for the BAR, where bit0 = 1MB, bit1 = 2MB, bit2 = 4MB, etc. In the above example the device supports 64MB, 128MB, and 256MB BAR sizes. When writing the file, the user provides the bit position of the desired resource size, for example: # echo 7 > resource1_resize This indicates to set the size value corresponding to bit 7, 128MB. The resulting size is 2 ^ (bit# + 20). This definition matches the PCIe specification of this capability. In order to make use of resource resizing, all PCI drivers must be unbound from the device and peer devices under the same parent bridge may need to be soft removed. In the case of VGA devices, writing a resize value will remove low level console drivers from the device. Raw users of pci-sysfs resourceN attributes must be terminated prior to resizing. Success of the resizing operation is not guaranteed.
Documentation/ABI/testing/sysfs-devices-vfio-dev 0 → 100644 +8 −0 Original line number Diff line number Diff line What: /sys/.../<device>/vfio-dev/vfioX/ Date: September 2022 Contact: Yi Liu <yi.l.liu@intel.com> Description: This directory is created when the device is bound to a vfio driver. The layout under this directory matches what exists for a standard 'struct device'. 'X' is a unique index marking this device in vfio.
Documentation/ABI/testing/sysfs-fs-f2fs +24 −0 Original line number Diff line number Diff line Loading @@ -466,6 +466,30 @@ Description: Show status of f2fs superblock in real time. 0x4000 SBI_IS_FREEZING freefs is in process ====== ===================== ================================= What: /sys/fs/f2fs/<disk>/stat/cp_status Date: September 2022 Contact: "Chao Yu" <chao.yu@oppo.com> Description: Show status of f2fs checkpoint in real time. =============================== ============================== cp flag value CP_UMOUNT_FLAG 0x00000001 CP_ORPHAN_PRESENT_FLAG 0x00000002 CP_COMPACT_SUM_FLAG 0x00000004 CP_ERROR_FLAG 0x00000008 CP_FSCK_FLAG 0x00000010 CP_FASTBOOT_FLAG 0x00000020 CP_CRC_RECOVERY_FLAG 0x00000040 CP_NAT_BITS_FLAG 0x00000080 CP_TRIMMED_FLAG 0x00000100 CP_NOCRC_RECOVERY_FLAG 0x00000200 CP_LARGE_NAT_BITMAP_FLAG 0x00000400 CP_QUOTA_NEED_FSCK_FLAG 0x00000800 CP_DISABLED_FLAG 0x00001000 CP_DISABLED_QUICK_FLAG 0x00002000 CP_RESIZEFS_FLAG 0x00004000 =============================== ============================== What: /sys/fs/f2fs/<disk>/ckpt_thread_ioprio Date: January 2021 Contact: "Daeho Jeong" <daehojeong@google.com> Loading
