From: "Huang, Kai" <kai.huang@intel.com>
To: "tglx@linutronix.de" <tglx@linutronix.de>,
"Schofield, Alison" <alison.schofield@intel.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"x86@kernel.org" <x86@kernel.org>, "bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>
Cc: "hpa@zytor.com" <hpa@zytor.com>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kai.huang@linux.intel.com" <kai.huang@linux.intel.com>
Subject: Re: [PATCH 2/2] x86/pconfig: Remove unused MKTME pconfig code
Date: Mon, 29 Apr 2024 10:49:57 +0000 [thread overview]
Message-ID: <1314b726ac899a1c492c0753e27dbb3ae5a29c4c.camel@intel.com> (raw)
In-Reply-To: <029c84dd5743c8d56734593455ae3d576387f72b.1713929290.git.alison.schofield@intel.com>
On Thu, 2024-04-25 at 21:24 -0700, alison.schofield@intel.com wrote:
> From: Alison Schofield <alison.schofield@intel.com>
>
> Code supporting Intel PCONFIG targets was an early piece of enabling
> for MKTME (Multi-Key Total Memory Encryption).
>
> Since MKTME feature enablement did not follow into the kernel, remove
> the unused PCONFIG code.
>
> Signed-off-by: Alison Schofield <alison.schofield@intel.com>
>
Acked-by: Kai Huang <kai.huang@intel.com>
next prev parent reply other threads:[~2024-04-29 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 4:24 [PATCH 0/2] Remove unneeded MKTME detection alison.schofield
2024-04-26 4:24 ` [PATCH 1/2] x86/cpu: Remove useless work in detect_tme_early() alison.schofield
2024-04-29 11:17 ` Huang, Kai
2024-05-07 3:51 ` Alison Schofield
2024-04-26 4:24 ` [PATCH 2/2] x86/pconfig: Remove unused MKTME pconfig code alison.schofield
2024-04-29 10:49 ` Huang, Kai [this message]
2024-04-26 19:07 ` [PATCH 0/2] Remove unneeded MKTME detection Kirill A. Shutemov
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=1314b726ac899a1c492c0753e27dbb3ae5a29c4c.camel@intel.com \
--to=kai.huang@intel.com \
--cc=alison.schofield@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kai.huang@linux.intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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®