On Fri, 15 Jul 2022, Dave Jiang wrote:
+config CXL_PMEM_SECURITY + tristate "CXL PMEM SECURITY: Persistent Memory Security Support" + depends on CXL_PMEM + default CXL_BUS + help + CXL memory device "Persistent Memory Data-at-rest Security" command set + support. Support opcode 0x4500..0x4505. The commands supported are "Get + Security State", "Set Passphrase", "Disable Passphrase", "Unlock", + "Freeze Security State", and "Passphrase Secure Erase". Security operation + is done through nvdimm security_ops. + + See Chapter 8.2.9.5.6 in the CXL 2.0 specification for a detailed description + of the Persistent Memory Security. + + If unsure say 'm'.
Is there any fundamental reason why we need to add a new CXL Kconfig option instead of just tucking this under CXL_PMEM?
