Skip to content

AMD SME

Architecture referenceFeex

AMD Secure Memory Encryption, SME, provides memory-encryption facilities managed by the platform and operating system. It differs from per-VM SEV protection and does not itself establish a confidential-computing deployment.

What you need to know

AMD Secure Memory Encryption, SME, provides memory-encryption facilities managed by the platform and operating system. It differs from per-VM SEV protection and does not itself establish a confidential-computing deployment.

How it works

The memory-encryption architecture identifies encrypted mappings through a defined address-bit mechanism and platform controls. The OS must account for the encryption bit and any effect on available physical address bits, and handle shared or device-visible memory according to the platform's rules.

Where it is useful

An OS can arrange for appropriate memory pages to be encrypted as data travels to external memory. DMA buffers and other shared mappings need a compatible treatment, so enabling a bit in isolation is not a complete deployment procedure.

How to check support and enablement

Use the AMD memory-encryption CPUID information and exact platform firmware/OS documentation to establish support and enablement. Check the active encryption policy and device compatibility. Preserve vendor recovery guidance before changing firmware memory-encryption settings.

Capability, enablement and enforcement must be checked separately. A processor can support a protection while the OS, application or virtual-machine policy does not activate it. A database support field is not an attestation of a running system.

What the feature does not establish

SME does not imply per-guest isolation, memory integrity, SEV-SNP or protection against every attack by privileged software. Transparent platform encryption policies and OS-managed SME configurations should not be assumed identical from a summary field.

Compatibility and performance in practice

Keep the OS, firmware and affected runtime current. If a protection exposes a compatibility problem, use vendor diagnostics and supported updates first. A broad protection toggle can affect unrelated applications and should follow an explicit deployment and recovery policy.

A practical verification checklist

  1. Record the exact processor or platform model and the application, OS and runtime versions involved. Preserve the wording of the actual error or requirement.
  2. Check the manufacturer reference for that exact model, then inspect the effective capability and enabled state in the environment where the program runs.
  3. Compare every requirement of the selected binary or backend. A similarly named feature, alias or broad technology label is not enough.
  4. Confirm the application selected the intended implementation. Use its documented diagnostics and a supported fallback when requirements are not met.
  5. Make one supported change at a time and repeat the same workload. Keep the original configuration and recovery path available.

If the feature is listed but software cannot use it

Start with the exact failing component. A hardware database describes recorded capability; the operating system or hypervisor can expose a different effective environment. An illegal-instruction error also needs investigation of the actual faulting instruction and binary build, because corruption or an unrelated unsupported instruction can produce a similar symptom.

Install the application, driver or runtime version supported for the exact platform, and use the vendor's documented baseline or fallback build if needed. A software update cannot create an instruction that the processor lacks. Firmware and security-policy changes should follow the system manufacturer's procedure and a recovery plan rather than a generic optimization recipe.

Sources and scope of this explanation

AMD Secure Encrypted Virtualization developer resources · Linux kernel: AMD memory encryption · AMD64 Architecture Programmer's Manual, Volume 2: System Programming

These references establish architectural behavior and software requirements. They do not independently verify every feature value on a linked hardware model page. For model support, use that page's manufacturer evidence and check the effective system configuration. This article does not supply a benchmark, certification or independent review date.

Sources and verification

Editorial ownership: Feex. No independent review date is recorded. How we research.

Report a correction to Feex

Was this article useful?

A yes or no is enough. Pick a reason if you want, or add a short note.

Was this article useful?