Re: [PATCH 2/3] DMA mapping: Move SME handling to x86-specific files
From: Thiago Jung Bauermann <hidden>
Date: 2019-07-18 19:47:29
Also in:
linux-fsdevel, linux-iommu, linux-s390, lkml
From: Thiago Jung Bauermann <hidden>
Date: 2019-07-18 19:47:29
Also in:
linux-fsdevel, linux-iommu, linux-s390, lkml
Thomas Gleixner [off-list ref] writes:
On Fri, 12 Jul 2019, Thiago Jung Bauermann wrote:quoted
diff --git a/include/linux/mem_encrypt.h b/include/linux/mem_encrypt.h index b310a9c18113..f2e399fb626b 100644 --- a/include/linux/mem_encrypt.h +++ b/include/linux/mem_encrypt.h@@ -21,23 +21,11 @@ #else /* !CONFIG_ARCH_HAS_MEM_ENCRYPT */ -#define sme_me_mask 0ULL - -static inline bool sme_active(void) { return false; } static inline bool sev_active(void) { return false; }You want to move out sev_active as well, the only relevant thing is mem_encrypt_active(). Everything SME/SEV is an architecture detail.
I'm sure you saw it. I addressed sev_active in a separate patch. Thanks for reviewing this series!
quoted
+static inline bool mem_encrypt_active(void) { return false; }Thanks, tglx
-- Thiago Jung Bauermann IBM Linux Technology Center