From: Tom Lendacky <thomas.lendacky@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
John Allen <john.allen@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>
Cc: open list <linux-kernel@vger.kernel.org>,
"open list:AMD CRYPTOGRAPHIC COPROCESSOR (CCP) DRIVER"
<linux-crypto@vger.kernel.org>,
Kerneis Gabriel <Gabriel.Kerneis@ssi.gouv.fr>,
Richard Hughes <hughsient@gmail.com>
Subject: Re: [PATCH v3 4/4] crypto: ccp: When TSME and SME both detected notify user
Date: Tue, 5 Apr 2022 16:06:50 -0500 [thread overview]
Message-ID: <a20da39f-845d-5b63-6efc-53d91fe86278@amd.com> (raw)
In-Reply-To: <20220331211213.2844-5-mario.limonciello@amd.com>
On 3/31/22 16:12, Mario Limonciello wrote:
> CC_ATTR_HOST_MEM_ENCRYPT is used to relay that memory encryption has been
> activated by the kernel.
>
> As it's technically possible to enable both SME and TSME at the same time,
> detect this scenario and notify the user that enabling TSME and SME at the
> same time is unnecessary.
>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Acked-by: Tom Lendacky <thomas.lendacky@amd.com>
> ---
next prev parent reply other threads:[~2022-04-06 2:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 21:12 [PATCH v3 0/4] Export PSP security attributes Mario Limonciello
2022-03-31 21:12 ` [PATCH v3 1/4] crypto: ccp: cache capability into psp device Mario Limonciello
2022-03-31 21:12 ` [PATCH v3 2/4] crypto: ccp: Export PSP security bits to userspace Mario Limonciello
2022-03-31 21:12 ` [PATCH v3 3/4] crypto: ccp: Allow PSP driver to load without SEV/TEE support Mario Limonciello
2022-04-05 21:05 ` Tom Lendacky
2022-03-31 21:12 ` [PATCH v3 4/4] crypto: ccp: When TSME and SME both detected notify user Mario Limonciello
2022-04-05 21:06 ` Tom Lendacky [this message]
2022-04-08 8:32 ` [PATCH v3 0/4] Export PSP security attributes Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a20da39f-845d-5b63-6efc-53d91fe86278@amd.com \
--to=thomas.lendacky@amd.com \
--cc=Gabriel.Kerneis@ssi.gouv.fr \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hughsient@gmail.com \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®