Lines Matching refs:which

4 L1 Terminal Fault is a hardware vulnerability which allows unprivileged
5 speculative access to data which is available in the Level 1 Data Cache
6 when the page table entry controlling the virtual address, which is used
24    - Intel processors which have the ARCH_CAP_RDCL_NO bit set in the
46 If an instruction accesses a virtual address for which the relevant page
72    PTE which is marked non present. This allows a malicious user space
73    application to attack the physical memory to which these PTEs resolve.
79    inversion, which is permanently enabled and has no performance
80    impact. The kernel ensures that the address bits of PTEs, which are not
90    OSes, which can control the PTEs directly, and malicious guest user
91    space applications, which run on an unprotected guest kernel lacking the
98    only to attack data which is present in L1D, a malicious guest running
99    on one Hyperthread can attack the data which is brought into the L1D by
100    the context which runs on the sibling Hyperthread of the same physical
110    mechanisms which can be utilized to address the problem depending on the
123 status of the system: whether the system is vulnerable, and which
173    To make sure that a guest cannot attack data which is present in the L1D
176    Flushing the L1D evicts not only the data which should not be accessed
191    The conditional mode avoids L1D flushing after VMEXITs which execute
206    sibling thread will also bring back its data into the L1D which makes it
230    which the host OS executes, i.e. interrupts, soft interrupts and kernel
252    true because there are types of interrupts which are truly per CPU
257    Moving the interrupts, which can be affinity controlled, away from CPUs
258    which run untrusted guests, reduces the attack vector space.
260    Whether the interrupts with are affine to CPUs, which run untrusted
262    configuration and the scenarios which run on the system. While for some
332      The possible states which can be written into this file to control SMT
431 		VMENTER can leak host memory which is considered
433 		which allows e.g. to determine the hosts address space layout.
509     Confinement of guests to a single or a group of physical cores which
520     about the host address space layout. The interrupts which have a fixed
521     affinity to the CPUs which run the untrusted guests can depending on
523     which might expose valuable information. See
589   The kernel does not by default enforce the disabling of SMT, which leaves
598     just an add on to other malware which might be embedded in an untrusted
612     mitigation choices, which might even vary across their deployed