/linux/drivers/gpu/drm/amd/pm/swsmu/inc/pmfw_if/ |
H A D | smu_v13_0_6_pmfw.h | 222 uint32_t PCIeL0ToRecoveryCountAcc; // The Pcie counter itself is accumulated 223 uint32_t PCIenReplayAAcc; // The Pcie counter itself is accumulated 224 uint32_t PCIenReplayARolloverCountAcc; // The Pcie counter itself is accumulated 225 uint32_t PCIeNAKSentCountAcc; // The Pcie counter itself is accumulated 226 uint32_t PCIeNAKReceivedCountAcc; // The Pcie counter itself is accumulated 241 uint32_t PCIeOtherEndRecoveryAcc; // The Pcie counter itself is accumulated 427 uint32_t PCIeL0ToRecoveryCountAcc; // The Pcie counter itself is accumulated 428 uint32_t PCIenReplayAAcc; // The Pcie counter itself is accumulated 429 uint32_t PCIenReplayARolloverCountAcc; // The Pcie counter itself is accumulated 430 uint32_t PCIeNAKSentCountAcc; // The Pcie counter itself is accumulated [all …]
|
/linux/drivers/xen/ |
H A D | xen-front-pgdir-shbuf.c | 89 * shared by the frontend itself) or map the provided granted 110 * shared by the frontend itself) or unmap the provided granted 154 * Get the number of pages the page directory consumes itself. 171 /* Only for pages the page directory consumes itself. */ in backend_calc_num_grefs() 184 * Number of pages the page directory consumes itself in guest_calc_num_grefs() 268 * so buf->num_grefs has number of pages in the page directory itself. in backend_map() 325 * page directory itself. 341 /* Fill only grefs for the page directory itself. */ in backend_fill_page_dir() 369 * granted for the page directory itself. in guest_fill_page_dir()
|
/linux/Documentation/ABI/testing/ |
H A D | sysfs-hypervisor-xen | 22 "self" The guest can profile itself 23 "hv" The guest can profile itself and, if it is 25 "all" The guest can profile itself, the hypervisor
|
H A D | sysfs-firmware-dmi-entries | 10 The kernel itself does not rely on the majority of the 45 assigned entry handles as the kernel itself makes no 58 entry itself. Note that this is _not the
|
/linux/security/landlock/ |
H A D | domain.h | 43 * @pid: PID of the task that initially restricted itself. It still 49 * @uid: UID of the task that initially restricted itself, at creation time. 53 * @comm: Command line of the task that initially restricted itself, at 59 * itself, at creation time. Always NULL terminated, and never greater
|
/linux/arch/x86/virt/vmx/tdx/ |
H A D | seamcall.S | 18 * Return (via RAX) TDX_SEAMCALL_VMFAILINVALID if the SEAMCALL itself 37 * Return (via RAX) TDX_SEAMCALL_VMFAILINVALID if the SEAMCALL itself 59 * Return (via RAX) TDX_SEAMCALL_VMFAILINVALID if the SEAMCALL itself
|
/linux/scripts/kconfig/tests/err_recursive_dep/ |
H A D | Kconfig | 3 # depends on itself 9 # select itself
|
/linux/Documentation/tools/rv/ |
H A D | common_ikm.rst | 12 command itself. If the **rv** command itself generates too many events,
|
/linux/drivers/hwmon/occ/ |
H A D | Kconfig | 14 the P8, not the POWER processor itself. Communications with the OCC are 28 the P9, not the POWER processor itself. Communications with the OCC are
|
/linux/Documentation/ABI/stable/ |
H A D | sysfs-driver-usb-usbtmc | 7 by the device itself. The full description of the bitfields 21 by the device itself. The full description of the bitfields
|
/linux/drivers/char/ |
H A D | nwbutton.h | 10 #ifdef __NWBUTTON_C /* Actually compiling the driver itself */ 34 #else /* Not compiling the driver itself */
|
/linux/include/linux/ |
H A D | posix-clock.h | 122 * A clock driver calls this function to register itself with the 135 * A clock driver calls this function to remove itself from the clock 136 * device subsystem. The posix_clock itself will remain (in an
|
/linux/Documentation/security/tpm/ |
H A D | tpm_ftpm_tee.rst | 19 implemented in firmware. The driver itself doesn't contain much logic and is 22 The firmware itself is based on the following paper:
|
/linux/Documentation/devicetree/bindings/i2c/ |
H A D | i2c-opal.txt | 5 used by the firmware itself for configuring the port. From the linux 21 The node contains a number of other properties that are used by the FW itself
|
/linux/Documentation/admin-guide/ |
H A D | dell_rbu.rst | 16 update itself with the image downloaded in to the memory. 90 to the data file as is without any change to the BIOS image itself. 126 the BIOS knows about the new image downloaded and it updates itself.
|
/linux/Documentation/filesystems/ext4/ |
H A D | verity.rst | 12 stored after the end of the file data itself, in the following format: 38 is encrypted as well as the data itself.
|
/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a73/ |
H A D | cache.json | 102 "PublicDescription": "Data cache hit in itself due to VIPT aliasing", 105 "BriefDescription": "Data cache hit in itself due to VIPT aliasing"
|
/linux/fs/ocfs2/cluster/ |
H A D | tcp_internal.h | 96 * itself if a connect attempt fails and so can be self-arming. 133 * still on the nn and will call ensure_shutdown itself.. this 138 * sc and rearm itself.
|
/linux/arch/arm64/include/asm/ |
H A D | cputype.h | 215 * - Qualcomm Kryo 5XX Silver IDs itself as MIDR_QCOM_KRYO_4XX_SILVER 216 * - Qualcomm Kryo 6XX Prime IDs itself as MIDR_CORTEX_X1 217 * - Qualcomm Kryo 6XX Gold IDs itself as ARM_CPU_PART_CORTEX_A78 218 * - Qualcomm Kryo 6XX Silver IDs itself as MIDR_CORTEX_A55
|
/linux/include/xen/ |
H A D | xen-front-pgdir-shbuf.h | 30 * of grant references for the page directory itself as grant 39 * Number of pages for the shared buffer itself (excluding the page
|
/linux/Documentation/networking/ |
H A D | x25.rst | 11 implement LAPB on the card itself, and unintelligent ones that simply do 17 layer of the Linux kernel and therefore it did not concern itself with
|
/linux/Documentation/core-api/irq/ |
H A D | irqflags-tracing.rst | 35 irq-flags state, and complains loudly (and turns itself off) if the 48 turn itself off. I.e. the lock validator will still be reliable. There
|
/linux/include/xen/interface/ |
H A D | xenpmu.h | 47 * itself and Xen 49 * everyone: itself, the hypervisor and the guests.
|
/linux/Documentation/locking/ |
H A D | spinlocks.rst | 19 spinlock itself will guarantee the global lock, so it will guarantee that 45 NOTE! The spin-lock is safe only when you **also** use the lock itself 81 itself. The read lock allows many concurrent readers. Anything that
|
/linux/Documentation/userspace-api/ |
H A D | no_new_privs.rst | 52 - By itself, ``no_new_privs`` can be used to reduce the attack surface 63 dangerous than chroot by itself.
|