From: "Huang, Kai" <kai.huang@intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Cc: <linux-coco@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv5, REBASED 4/4] x86/tdx: Enable CPU topology enumeration
Date: Wed, 21 Aug 2024 14:01:48 +1200 [thread overview]
Message-ID: <adf05a71-49a8-4b4c-ae64-8e3d4eee1e41@intel.com> (raw)
In-Reply-To: <20240809130923.3893765-5-kirill.shutemov@linux.intel.com>
On 10/08/2024 1:09 am, Kirill A. Shutemov wrote:
> TDX 1.0 defines baseline behaviour of TDX guest platform. In TDX 1.0
> generates a #VE when accessing topology-related CPUID leafs (0xB and
"In TDX 1.0 generates" -> "TDX 1.0 generates"
[...]
> + * The ENUM_TOPOLOGY feature allows the VMM to provide topology information.
> + * Enabling the feature eliminates topology-related #VEs: the TDX module
^
double space
[...]
Acked-by: Kai Huang <kai.huang@intel.com>
prev parent reply other threads:[~2024-08-21 2:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 13:09 [PATCHv5, REBASED 0/4] x86/tdx: Adjust TD settings on boot Kirill A. Shutemov
2024-08-09 13:09 ` [PATCHv5, REBASED 1/4] x86/tdx: Introduce wrappers to read and write TD metadata Kirill A. Shutemov
2024-08-09 13:09 ` [PATCHv5, REBASED 2/4] x86/tdx: Rename tdx_parse_tdinfo() to tdx_setup() Kirill A. Shutemov
2024-08-09 13:09 ` [PATCHv5, REBASED 3/4] x86/tdx: Dynamically disable SEPT violations from causing #VEs Kirill A. Shutemov
2024-08-21 1:52 ` Huang, Kai
2024-08-27 10:04 ` Kirill A. Shutemov
2024-08-28 0:44 ` Huang, Kai
2024-08-09 13:09 ` [PATCHv5, REBASED 4/4] x86/tdx: Enable CPU topology enumeration Kirill A. Shutemov
2024-08-21 2:01 ` Huang, Kai [this message]
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=adf05a71-49a8-4b4c-ae64-8e3d4eee1e41@intel.com \
--to=kai.huang@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).