Difference between revisions of "MDS NO"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
Tags: Mobile web edit, Mobile edit |
||
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
Note - When MDS_NO is enabled, MD_CLEAR is enabled read-only. | Note - When MDS_NO is enabled, MD_CLEAR is enabled read-only. | ||
| + | |||
| + | == Related terms == | ||
| + | * [[VMware vMotion]] | ||
| + | * [[CVE]]-2019-11135, in the [[Linux upstream kernel]] versions before 5.5 | ||
== See also == | == See also == | ||
Latest revision as of 08:23, 8 April 2021
wikipedia:Microarchitectural Data Sampling Hardware Avoidance Mitigation (MDS_NO) is a read-only extension that is only enabled if the CPU is not vulnerable to the Microarchitectural Data Sampling (MDS) series of vulnerabilities that the MD_CLEAR extension mitigates in software.
Note - When MDS_NO is enabled, MD_CLEAR is enabled read-only.
Related terms[edit]
- VMware vMotion
- CVE-2019-11135, in the Linux upstream kernel versions before 5.5
See also[edit]
- CPU, GPU, NPU, TPU, DPU, Groq, Proliant, thread (
Pthreads), processor, CPU socket, core, ARM , CPU Virtualization, Intel, AMD,nm,lscpu, AVX-512, Passthrough, CPU intensive, Graviton processor, Branch predictor, vCPU, SSE, Power - VMware, VMware vSphere, VMware ESXi (ESXi Patching), VMware Fusion hypervisor for macOS, CloudFoundry, Workspace ONE intelligent hub, AirWatch, open-vm-tools, VMware Tanzu, vCenter, VMware Cloud Foundation (VCF), VMFS,
esxcli,vim-cmd, Storage DRS (SDRS), VSphere Lifecycle Manager, Virtualization Based Security, VMware vMotion, VMware desktop, Greenplum, VMware Workstation Player, VMware Workspace ONE: VMware Workspace ONE UEM, VMware Verify, vRO, vRA, CloudHealth, Bitnami, VMware Application Catalog
Advertising:
