Searched hist:"655 a0fa3" (Results 1 – 4 of 4) sorted by relevance
/openbmc/linux/arch/x86/include/asm/ |
H A D | coco.h | 655a0fa3 Tue Feb 22 12:57:39 CST 2022 Kirill A. Shutemov <kirill.shutemov@linux.intel.com> x86/coco: Explicitly declare type of confidential computing platform
The kernel derives the confidential computing platform type it is running as from sme_me_mask on AMD or by using hv_is_isolation_supported() on HyperV isolation VMs. This detection process will be more complicated as more platforms get added.
Declare a confidential computing vendor variable explicitly and set it via cc_set_vendor() on the respective platform.
[ bp: Massage commit message, fixup HyperV check. ]
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Signed-off-by: Borislav Petkov <bp@suse.de> Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com> Link: https://lore.kernel.org/r/20220222185740.26228-4-kirill.shutemov@linux.intel.com
|
/openbmc/linux/arch/x86/coco/ |
H A D | core.c | 655a0fa3 Tue Feb 22 12:57:39 CST 2022 Kirill A. Shutemov <kirill.shutemov@linux.intel.com> x86/coco: Explicitly declare type of confidential computing platform
The kernel derives the confidential computing platform type it is running as from sme_me_mask on AMD or by using hv_is_isolation_supported() on HyperV isolation VMs. This detection process will be more complicated as more platforms get added.
Declare a confidential computing vendor variable explicitly and set it via cc_set_vendor() on the respective platform.
[ bp: Massage commit message, fixup HyperV check. ]
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Signed-off-by: Borislav Petkov <bp@suse.de> Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com> Link: https://lore.kernel.org/r/20220222185740.26228-4-kirill.shutemov@linux.intel.com
|
/openbmc/linux/arch/x86/mm/ |
H A D | mem_encrypt_identity.c | 655a0fa3 Tue Feb 22 12:57:39 CST 2022 Kirill A. Shutemov <kirill.shutemov@linux.intel.com> x86/coco: Explicitly declare type of confidential computing platform
The kernel derives the confidential computing platform type it is running as from sme_me_mask on AMD or by using hv_is_isolation_supported() on HyperV isolation VMs. This detection process will be more complicated as more platforms get added.
Declare a confidential computing vendor variable explicitly and set it via cc_set_vendor() on the respective platform.
[ bp: Massage commit message, fixup HyperV check. ]
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Signed-off-by: Borislav Petkov <bp@suse.de> Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com> Link: https://lore.kernel.org/r/20220222185740.26228-4-kirill.shutemov@linux.intel.com
|
/openbmc/linux/arch/x86/kernel/cpu/ |
H A D | mshyperv.c | 655a0fa3 Tue Feb 22 12:57:39 CST 2022 Kirill A. Shutemov <kirill.shutemov@linux.intel.com> x86/coco: Explicitly declare type of confidential computing platform
The kernel derives the confidential computing platform type it is running as from sme_me_mask on AMD or by using hv_is_isolation_supported() on HyperV isolation VMs. This detection process will be more complicated as more platforms get added.
Declare a confidential computing vendor variable explicitly and set it via cc_set_vendor() on the respective platform.
[ bp: Massage commit message, fixup HyperV check. ]
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Signed-off-by: Borislav Petkov <bp@suse.de> Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com> Link: https://lore.kernel.org/r/20220222185740.26228-4-kirill.shutemov@linux.intel.com
|