Home
last modified time | relevance | path

Searched refs:SEV (Results 1 – 18 of 18) sorted by relevance

/linux-6.1.9/Documentation/virt/coco/
Dsev-guest.rst4 The Definitive SEV Guest API Documentation
10 The SEV API is a set of ioctls that are used by the guest or hypervisor
11 to get or set a certain aspect of the SEV virtual machine. The ioctls belong
15 whole SEV firmware. These ioctl are used by platform provisioning tools.
17 - Guest ioctls: These query and set attributes of the SEV virtual machine.
22 This section describes ioctls that is used for querying the SEV guest report
23 from the SEV firmware. For each ioctl, the following information is provided
27 which SEV technology provides this ioctl. SEV, SEV-ES, SEV-SNP or all.
73 SEV-SNP firmware. The ioctl uses the SNP_GUEST_REQUEST (MSG_REPORT_REQ) command
74 provided by the SEV-SNP firmware to query the attestation report.
[all …]
/linux-6.1.9/Documentation/virt/kvm/x86/
Damd-memory-encryption.rst4 Secure Encrypted Virtualization (SEV)
10 Secure Encrypted Virtualization (SEV) is a feature found on AMD processors.
12 SEV is an extension to the AMD-V architecture which supports running
17 The hypervisor can determine the SEV support through the CPUID
19 to SEV::
22 Bit[1] indicates support for SEV
27 If support for SEV is present, MSR 0xc001_0010 (MSR_AMD64_SYSCFG) and MSR 0xc001_0015
38 When SEV support is available, it can be enabled in a specific VM by
39 setting the SEV bit before executing VMRUN.::
42 Bit[1] 1 = SEV is enabled
[all …]
/linux-6.1.9/Documentation/x86/
Damd-memory-encryption.rst7 Secure Memory Encryption (SME) and Secure Encrypted Virtualization (SEV) are
16 SEV enables running encrypted virtual machines (VMs) in which the code and data
18 within the VM itself. SEV guest VMs have the concept of private and shared
36 When SEV is enabled, instruction pages and guest page tables are always treated
39 is operating in 64-bit or 32-bit PAE mode, in all other modes the SEV hardware
42 Support for SME and SEV can be determined through the CPUID instruction. The
47 Bit[1] indicates support for SEV
63 If SEV is supported, MSR 0xc0010131 (MSR_AMD64_SEV) can be used to determine if
64 SEV is active::
102 SEV-SNP introduces new features (SEV_FEATURES[1:63]) which can be enabled
/linux-6.1.9/drivers/virt/coco/sev-guest/
DKconfig2 tristate "AMD SEV Guest driver"
8 SEV-SNP firmware provides the guest a mechanism to communicate with
/linux-6.1.9/Documentation/security/secrets/
Dcoco.rst15 Confidential Computing (coco) hardware such as AMD SEV (Secure Encrypted
17 memory without the host/hypervisor being able to read them. In SEV,
36 area. In AMD SEV and SEV-ES this is performed using the
99 See [sev-api-spec]_ for more info regarding SEV ``LAUNCH_SECRET`` operation.
/linux-6.1.9/arch/arm/include/asm/
Dspinlock.h39 #define SEV __ALT_SMP_ASM(WASM(sev), WASM(nop)) macro
45 __asm__(SEV); in dsb_sev()
/linux-6.1.9/arch/x86/kvm/
DKconfig114 bool "AMD Secure Encrypted Virtualization (SEV) support"
118 Provides support for launching Encrypted VMs (SEV) and Encrypted VMs
119 with Encrypted State (SEV-ES) on AMD processors.
Dcpuid.c730 0 /* SME */ | F(SEV) | 0 /* VM_PAGE_FLUSH */ | F(SEV_ES) | in kvm_set_cpu_caps()
/linux-6.1.9/Documentation/ABI/testing/
Dsecurityfs-secrets-coco9 platforms (such as AMD SEV and SEV-ES) for secret injection by
/linux-6.1.9/drivers/virt/coco/efi_secret/
DKconfig10 confidential computing secret injection (for example for AMD SEV
/linux-6.1.9/arch/riscv/boot/dts/microchip/
Dmpfs-sev-kit.dts15 model = "Microchip PolarFire-SoC SEV Kit";
/linux-6.1.9/drivers/crypto/ccp/
DKconfig45 management commands in Secure Encrypted Virtualization (SEV) mode,
/linux-6.1.9/tools/arch/x86/kcpuid/
Dcpuid.csv396 0x8000001F, 0, EAX, 3, seves, SEV Encrypted State
399 0x8000001F, 0, ECX, 31:0, num_encrypted_guests, Maximum ASID value that may be used for an SEV-en…
400 …31:0, minimum_sev_asid, Minimum ASID value that must be used for an SEV-enabled, SEV-ES-disabled g…
/linux-6.1.9/Documentation/x86/x86_64/
Dboot-options.rst308 AMD SEV (Secure Encrypted Virtualization)
310 Options relating to AMD SEV, specified via the following format:
/linux-6.1.9/drivers/firmware/efi/
DKconfig305 Confidential Computing platforms (such as AMD SEV) allow the
/linux-6.1.9/Documentation/virt/hyperv/
Dvmbus.rst157 guest to not trust the hypervisor (AMD SNP-SEV, Intel TDX), trusting
/linux-6.1.9/Documentation/virt/kvm/
Dapi.rst4681 (SEV) commands on AMD Processors. The SEV commands are defined in
4696 It is used in the SEV-enabled guest. When encryption is enabled, a guest
4697 memory region may contain encrypted data. The SEV memory encryption
4701 swapped. So relocating (or migrating) physical backing pages for the SEV
4704 Note: The current SEV key management spec does not provide commands to
6281 - KVM_SYSTEM_EVENT_SEV_TERM -- an AMD SEV guest requested termination.
7297 Architectures: x86 SEV enabled
7396 Architectures: x86 SEV enabled
/linux-6.1.9/
DMAINTAINERS948 AMD CRYPTOGRAPHIC COPROCESSOR (CCP) DRIVER - SEV SUPPORT