From: Jarkko Sakkinen <jarkko@kernel.org>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-sgx@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] x86/sgx: Remove unused TCS definitions
Date: Sat, 11 Jul 2026 21:22:01 +0300 [thread overview]
Message-ID: <alKJya_l4SzvtGBa@kernel.org> (raw)
In-Reply-To: <20260711100053.739588-6-thorsten.blum@linux.dev>
On Sat, Jul 11, 2026 at 12:00:55PM +0200, Thorsten Blum wrote:
> The TCS structure was added with commit 70d3b8ddcd20 ("x86/sgx: Add SGX
> architectural data structures"), but has never had an in-tree user.
> Remove the unused TCS structure and its corresponding definitions.
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
> arch/x86/include/asm/sgx.h | 50 --------------------------------------
> 1 file changed, 50 deletions(-)
>
> diff --git a/arch/x86/include/asm/sgx.h b/arch/x86/include/asm/sgx.h
> index 04958459a7ca..fe106c55a593 100644
> --- a/arch/x86/include/asm/sgx.h
> +++ b/arch/x86/include/asm/sgx.h
> @@ -193,56 +193,6 @@ struct sgx_secs {
> u8 reserved4[3834];
> } __packed;
>
> -/**
> - * enum sgx_tcs_flags - execution flags for TCS
> - * @SGX_TCS_DBGOPTIN: If enabled allows single-stepping and breakpoints
> - * inside an enclave. It is cleared by EADD but can
> - * be set later with EDBGWR.
> - */
> -enum sgx_tcs_flags {
> - SGX_TCS_DBGOPTIN = 0x01,
> -};
> -
> -#define SGX_TCS_RESERVED_MASK GENMASK_ULL(63, 1)
> -#define SGX_TCS_RESERVED_SIZE 4024
> -
> -/**
> - * struct sgx_tcs - Thread Control Structure (TCS)
> - * @state: used to mark an entered TCS
> - * @flags: execution flags (cleared by EADD)
> - * @ssa_offset: SSA stack offset relative to the enclave base
> - * @ssa_index: the current SSA frame index (cleard by EADD)
> - * @nr_ssa_frames: the number of frame in the SSA stack
> - * @entry_offset: entry point offset relative to the enclave base
> - * @exit_addr: address outside the enclave to exit on an exception or
> - * interrupt
> - * @fs_offset: offset relative to the enclave base to become FS
> - * segment inside the enclave
> - * @gs_offset: offset relative to the enclave base to become GS
> - * segment inside the enclave
> - * @fs_limit: size to become a new FS-limit (only 32-bit enclaves)
> - * @gs_limit: size to become a new GS-limit (only 32-bit enclaves)
> - *
> - * Thread Control Structure (TCS) is an enclave page visible in its address
> - * space that defines an entry point inside the enclave. A thread enters inside
> - * an enclave by supplying address of TCS to ENCLU(EENTER). A TCS can be entered
> - * by only one thread at a time.
> - */
> -struct sgx_tcs {
> - u64 state;
> - u64 flags;
> - u64 ssa_offset;
> - u32 ssa_index;
> - u32 nr_ssa_frames;
> - u64 entry_offset;
> - u64 exit_addr;
> - u64 fs_offset;
> - u64 gs_offset;
> - u32 fs_limit;
> - u32 gs_limit;
> - u8 reserved[SGX_TCS_RESERVED_SIZE];
> -} __packed;
> -
> /**
> * struct sgx_pageinfo - an enclave page descriptor
> * @addr: address of the enclave page
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
BR, Jarkko
next prev parent reply other threads:[~2026-07-11 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 10:00 [PATCH 0/3] x86/sgx: Remove unused definitions and reuse launch token size Thorsten Blum
2026-07-11 10:00 ` [PATCH 1/3] x86/sgx: Remove unused TCS definitions Thorsten Blum
2026-07-11 18:22 ` Jarkko Sakkinen [this message]
2026-07-11 10:00 ` [PATCH 2/3] x86/sgx: Remove unused size and count definitions Thorsten Blum
2026-07-11 18:22 ` Jarkko Sakkinen
2026-07-11 10:00 ` [PATCH 3/3] x86/sgx: Use SGX_LAUNCH_TOKEN_SIZE in __sgx_virt_einit() Thorsten Blum
2026-07-11 18:23 ` Jarkko Sakkinen
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=alKJya_l4SzvtGBa@kernel.org \
--to=jarkko@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--cc=thorsten.blum@linux.dev \
--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