From: Nikolay Borisov <nik.borisov@suse.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,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Kai Huang <kai.huang@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCHv6 2/4] x86/tdx: Rename tdx_parse_tdinfo() to tdx_setup()
Date: Wed, 28 Aug 2024 16:53:57 +0300 [thread overview]
Message-ID: <e042faa6-91be-49bb-ae59-e87792756fa4@suse.com> (raw)
In-Reply-To: <20240828093505.2359947-3-kirill.shutemov@linux.intel.com>
On 28.08.24 г. 12:35 ч., Kirill A. Shutemov wrote:
> Rename tdx_parse_tdinfo() to tdx_setup() and move setting NOTIFY_ENABLES
> there.
>
> The function will be extended to adjust TD configuration.
<offtopic>
Since this deals with renaming, I think it will make sense to rename
tdx_early_init() to tdx_guest_init/tdx_guest_early_init as it becomes
confusing as to which parts of the TDX pertain to the host and which to
the guest. Right now we only have the guest portions under
arch/x86/coco/tdx but when the kvm/vmx stuff land things will become
somewhat messy..
</offtopic>
<snip>
next prev parent reply other threads:[~2024-08-28 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 9:35 [PATCHv6 0/4] x86/tdx: Adjust TD settings on boot Kirill A. Shutemov
2024-08-28 9:35 ` [PATCHv6 1/4] x86/tdx: Introduce wrappers to read and write TD metadata Kirill A. Shutemov
2024-08-28 14:28 ` Nikolay Borisov
2024-08-28 9:35 ` [PATCHv6 2/4] x86/tdx: Rename tdx_parse_tdinfo() to tdx_setup() Kirill A. Shutemov
2024-08-28 13:53 ` Nikolay Borisov [this message]
2024-09-09 11:24 ` Kirill A. Shutemov
2024-08-28 9:35 ` [PATCHv6 3/4] x86/tdx: Dynamically disable SEPT violations from causing #VEs Kirill A. Shutemov
2024-08-28 14:27 ` Nikolay Borisov
2024-09-09 11:29 ` Kirill A. Shutemov
2024-08-28 9:35 ` [PATCHv6 4/4] x86/tdx: Enable CPU topology enumeration 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=e042faa6-91be-49bb-ae59-e87792756fa4@suse.com \
--to=nik.borisov@suse.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kai.huang@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=stable@vger.kernel.org \
--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