arch/x86/kernel/cpu/sgx/driver.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
A kernel requires X86_FEATURE_SGX_LC to be able to create SGX enclaves.
There is quite a number of hardware which has X86_FEATURE_SGX but not
X86_FEATURE_SGX_LC. A kernel running on such a hardware does not create
/dev/sgx_enclave file silently. Explicitly warn if X86_FEATURE_SGX_LC
is not enabled to properly nofity a user about this condition.
The X86_FEATURE_SGX_LC is a CPU feature that enables LE hash MSRs to be
writable when running native enclaves, i.e. using a custom root key rather
than the Intel proprietary key for enclave signing.
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
---
an out-of-commit-message note:
I've hit this issue myself and have spent some time researching where is
my /dev/sgx_enclave file on an SGX-enabled hardware, so this is a bit
personal.
Links related:
https://github.com/intel/linux-sgx/issues/837
https://patchwork.kernel.org/project/platform-driver-x86/patch/20180827185507.17087-3-jarkko.sakkinen@linux.intel.com/
arch/x86/kernel/cpu/sgx/driver.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/cpu/sgx/driver.c b/arch/x86/kernel/cpu/sgx/driver.c
index 22b65a5f5ec6..df4fbfaa6616 100644
--- a/arch/x86/kernel/cpu/sgx/driver.c
+++ b/arch/x86/kernel/cpu/sgx/driver.c
@@ -150,8 +150,10 @@ int __init sgx_drv_init(void)
u64 xfrm_mask;
int ret;
- if (!cpu_feature_enabled(X86_FEATURE_SGX_LC))
+ if (!cpu_feature_enabled(X86_FEATURE_SGX_LC)) {
+ pr_err("SGX disabled: SGX launch control is not available.\n");
return -ENODEV;
+ }
cpuid_count(SGX_CPUID, 0, &eax, &ebx, &ecx, &edx);
--
2.48.1On Sun, 2025-03-09 at 18:22 +0100, Vladis Dronov wrote:
> A kernel requires X86_FEATURE_SGX_LC to be able to create SGX enclaves.
The kernel requires ...
> There is quite a number of hardware which has X86_FEATURE_SGX but not
> X86_FEATURE_SGX_LC. A kernel running on such a hardware does not create
> /dev/sgx_enclave file silently. Explicitly warn if X86_FEATURE_SGX_LC
> is not enabled to properly nofity a user about this condition.
^
notify
And I don't think "notify" is correct because the reality is the kernel only
prints some error message so that the user can check and see when it wants.
How about:
Explicitly print error message if X86_FEATURE_SGX_LC is not present so that the
users can be aware of this condition which results in SGX driver being disabled.
>
> The X86_FEATURE_SGX_LC is a CPU feature that enables LE hash MSRs to be
> writable when running native enclaves, i.e. using a custom root key rather
> than the Intel proprietary key for enclave signing.
Using "root key" can be controversial. Let's just say "key" instead.
And the X86_FEATURE_SGX_LC feature itself doesn't automatically enable LE MSRs
to be writable. We still need to opt-in in the 'feature control' MSR.
How about:
The X86_FEATURE_SGX_LC, a.k.a. SGX Launch Control, is a CPU feature that enables
LE (Launch Enclave) hash MSRs to be writable (with additional opt-in required in
the 'feature control' MSR) when running enclaves, i.e., using a custom key
rather than the Intel proprietary key for enclave signing.
>
> Signed-off-by: Vladis Dronov <vdronov@redhat.com>
I think this message will be useful for someone who knows SGX in general but
doesn't know that Linux SGX driver requires the LE MSRs to be writable, thus
requires the CPU supports SGX_LC feature bit.
With the above addressed, feel free to add:
Acked-by: Kai Huang <kai.huang@intel.com>
> ---
>
> an out-of-commit-message note:
>
> I've hit this issue myself and have spent some time researching where is
> my /dev/sgx_enclave file on an SGX-enabled hardware, so this is a bit
> personal.
>
> Links related:
> https://github.com/intel/linux-sgx/issues/837
> https://patchwork.kernel.org/project/platform-driver-x86/patch/20180827185507.17087-3-jarkko.sakkinen@linux.intel.com/
>
> arch/x86/kernel/cpu/sgx/driver.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/cpu/sgx/driver.c b/arch/x86/kernel/cpu/sgx/driver.c
> index 22b65a5f5ec6..df4fbfaa6616 100644
> --- a/arch/x86/kernel/cpu/sgx/driver.c
> +++ b/arch/x86/kernel/cpu/sgx/driver.c
> @@ -150,8 +150,10 @@ int __init sgx_drv_init(void)
> u64 xfrm_mask;
> int ret;
>
> - if (!cpu_feature_enabled(X86_FEATURE_SGX_LC))
> + if (!cpu_feature_enabled(X86_FEATURE_SGX_LC)) {
> + pr_err("SGX disabled: SGX launch control is not available.\n");
> return -ENODEV;
> + }
>
> cpuid_count(SGX_CPUID, 0, &eax, &ebx, &ecx, &edx);
>
* Huang, Kai <kai.huang@intel.com> wrote:
> On Sun, 2025-03-09 at 18:22 +0100, Vladis Dronov wrote:
> > A kernel requires X86_FEATURE_SGX_LC to be able to create SGX enclaves.
>
> The kernel requires ...
>
> > There is quite a number of hardware which has X86_FEATURE_SGX but not
> > X86_FEATURE_SGX_LC. A kernel running on such a hardware does not create
> > /dev/sgx_enclave file silently. Explicitly warn if X86_FEATURE_SGX_LC
> > is not enabled to properly nofity a user about this condition.
> ^
> notify
>
> And I don't think "notify" is correct because the reality is the
> kernel only prints some error message so that the user can check and
> see when it wants.
>
> How about:
>
> Explicitly print error message if X86_FEATURE_SGX_LC is not present
> so that the users can be aware of this condition which results in SGX
> driver being disabled.
>
> >
> > The X86_FEATURE_SGX_LC is a CPU feature that enables LE hash MSRs to be
> > writable when running native enclaves, i.e. using a custom root key rather
> > than the Intel proprietary key for enclave signing.
>
> Using "root key" can be controversial. Let's just say "key" instead.
>
> And the X86_FEATURE_SGX_LC feature itself doesn't automatically enable LE MSRs
> to be writable. We still need to opt-in in the 'feature control' MSR.
Why would it be controversial?
> How about:
>
> The X86_FEATURE_SGX_LC, a.k.a. SGX Launch Control, is a CPU feature
> that enables LE (Launch Enclave) hash MSRs to be writable (with
> additional opt-in required in the 'feature control' MSR) when running
> enclaves, i.e., using a custom key rather than the Intel proprietary
> key for enclave signing.
> > Signed-off-by: Vladis Dronov <vdronov@redhat.com>
>
> I think this message will be useful for someone who knows SGX in
> general but doesn't know that Linux SGX driver requires the LE MSRs
> to be writable, thus requires the CPU supports SGX_LC feature bit.
>
> With the above addressed, feel free to add:
>
> Acked-by: Kai Huang <kai.huang@intel.com>
Thanks, I've edited the changelog to be a bit clearer.
I also added an error message when the driver fails to register, and
made all 3 failure error messages consistent and refer back to the
/dev/sgx_enclave device node name.
I also included part of this commit message note:
> > an out-of-commit-message note:
> >
> > I've hit this issue myself and have spent some time researching where is
> > my /dev/sgx_enclave file on an SGX-enabled hardware, so this is a bit
> > personal.
> >
> > Links related:
> > https://github.com/intel/linux-sgx/issues/837
> > https://patchwork.kernel.org/project/platform-driver-x86/patch/20180827185507.17087-3-jarkko.sakkinen@linux.intel.com/
Because this experience reflects arguably poor usability: people see
'SGX' in their /proc/cpuinfo file, think that their hardware is 'SGX
enabled' and are wondering why the hell the /dev/sgx_enclave device
node is not created, right?
I also Cc:-ed more SGX people.
See the full -v3 patch below.
Is the device node misnamed, should it be /dev/sgx_lc_enclave? Should
we hide the SGX feature bit from cpuinfo when SGX_LC is not present, so
that people don't go on a wild goose chase?
Thanks,
Ingo
======================================>
From: Vladis Dronov <vdronov@redhat.com>
Date: Sun, 9 Mar 2025 18:22:16 +0100
Subject: [PATCH] x86/sgx: Warn explicitly if X86_FEATURE_SGX_LC is not enabled
The kernel requires X86_FEATURE_SGX_LC to be able to create SGX enclaves,
not just X86_FEATURE_SGX.
There is quite a number of hardware which has X86_FEATURE_SGX but not
X86_FEATURE_SGX_LC. A kernel running on such hardware does not create
the /dev/sgx_enclave file and does so silently.
Explicitly warn if X86_FEATURE_SGX_LC is not enabled to properly notify
users that the kernel disabled the SGX driver.
The X86_FEATURE_SGX_LC, a.k.a. SGX Launch Control, is a CPU feature
that enables LE (Launch Enclave) hash MSRs to be writable (with
additional opt-in required in the 'feature control' MSR) when running
enclaves, i.e. using a custom root key rather than the Intel proprietary
key for enclave signing.
I've hit this issue myself and have spent some time researching where
my /dev/sgx_enclave file went on SGX-enabled hardware.
Related links:
https://github.com/intel/linux-sgx/issues/837
https://patchwork.kernel.org/project/platform-driver-x86/patch/20180827185507.17087-3-jarkko.sakkinen@linux.intel.com/
[ mingo: Made the error message a bit more verbose, and added other cases
where the kernel fails to create the /dev/sgx_enclave device node. ]
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Kai Huang <kai.huang@intel.com>
Cc: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: https://lore.kernel.org/r/20250309172215.21777-2-vdronov@redhat.com
---
arch/x86/kernel/cpu/sgx/driver.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/cpu/sgx/driver.c b/arch/x86/kernel/cpu/sgx/driver.c
index 22b65a5f5ec6..40c3347ac65d 100644
--- a/arch/x86/kernel/cpu/sgx/driver.c
+++ b/arch/x86/kernel/cpu/sgx/driver.c
@@ -150,13 +150,15 @@ int __init sgx_drv_init(void)
u64 xfrm_mask;
int ret;
- if (!cpu_feature_enabled(X86_FEATURE_SGX_LC))
+ if (!cpu_feature_enabled(X86_FEATURE_SGX_LC)) {
+ pr_err("SGX disabled: SGX launch control CPU feature is not available, /dev/sgx_enclave disabled.\n");
return -ENODEV;
+ }
cpuid_count(SGX_CPUID, 0, &eax, &ebx, &ecx, &edx);
if (!(eax & 1)) {
- pr_err("SGX disabled: SGX1 instruction support not available.\n");
+ pr_err("SGX disabled: SGX1 instruction support not available, /dev/sgx_enclave disabled.\n");
return -ENODEV;
}
@@ -173,8 +175,10 @@ int __init sgx_drv_init(void)
}
ret = misc_register(&sgx_dev_enclave);
- if (ret)
+ if (ret) {
+ pr_err("SGX disabled: Unable to register the /dev/sgx_enclave driver (%d).\n", ret);
return ret;
+ }
return 0;
}On Mon, 2025-03-10 at 09:42 +0100, Ingo Molnar wrote: > * Huang, Kai <kai.huang@intel.com> wrote: > > > On Sun, 2025-03-09 at 18:22 +0100, Vladis Dronov wrote: > > > A kernel requires X86_FEATURE_SGX_LC to be able to create SGX enclaves. > > > > The kernel requires ... > > > > > There is quite a number of hardware which has X86_FEATURE_SGX but not > > > X86_FEATURE_SGX_LC. A kernel running on such a hardware does not create > > > /dev/sgx_enclave file silently. Explicitly warn if X86_FEATURE_SGX_LC > > > is not enabled to properly nofity a user about this condition. > > ^ > > notify > > > > And I don't think "notify" is correct because the reality is the > > kernel only prints some error message so that the user can check and > > see when it wants. > > > > How about: > > > > Explicitly print error message if X86_FEATURE_SGX_LC is not present > > so that the users can be aware of this condition which results in SGX > > driver being disabled. > > > > > > > > The X86_FEATURE_SGX_LC is a CPU feature that enables LE hash MSRs to be > > > writable when running native enclaves, i.e. using a custom root key rather > > > than the Intel proprietary key for enclave signing. > > > > Using "root key" can be controversial. Let's just say "key" instead. > > > > And the X86_FEATURE_SGX_LC feature itself doesn't automatically enable LE MSRs > > to be writable. We still need to opt-in in the 'feature control' MSR. > > Why would it be controversial? If we are talking out from key derivation's perspective, I think the "root key" refers to something that sits at the bottom of the key hierarchy and is involved in the key derivation of other keys. If we are talking about asymmetric key signing and verification, then I think the "root key" means the private key of the last level of the certificate-chain. Here the key used to sign the enclave fits neither of above: It's not the root of any certificate chain. The MRSIGNER (the hash of the enclave signing key) is not involved in all SGX key derivations either (e.g., the derivation of REPORT_KEY doesn't use it, and the SEAL_KEY can choose to not use it). > > > How about: > > > > The X86_FEATURE_SGX_LC, a.k.a. SGX Launch Control, is a CPU feature > > that enables LE (Launch Enclave) hash MSRs to be writable (with > > additional opt-in required in the 'feature control' MSR) when running > > enclaves, i.e., using a custom key rather than the Intel proprietary > > key for enclave signing. > > > > > Signed-off-by: Vladis Dronov <vdronov@redhat.com> > > > > I think this message will be useful for someone who knows SGX in > > general but doesn't know that Linux SGX driver requires the LE MSRs > > to be writable, thus requires the CPU supports SGX_LC feature bit. > > > > With the above addressed, feel free to add: > > > > Acked-by: Kai Huang <kai.huang@intel.com> > > Thanks, I've edited the changelog to be a bit clearer. > > I also added an error message when the driver fails to register, and > made all 3 failure error messages consistent and refer back to the > /dev/sgx_enclave device node name. > > I also included part of this commit message note: > > > > an out-of-commit-message note: > > > > > > I've hit this issue myself and have spent some time researching where is > > > my /dev/sgx_enclave file on an SGX-enabled hardware, so this is a bit > > > personal. > > > > > > Links related: > > > https://github.com/intel/linux-sgx/issues/837 > > > https://patchwork.kernel.org/project/platform-driver-x86/patch/20180827185507.17087-3-jarkko.sakkinen@linux.intel.com/ > > Because this experience reflects arguably poor usability: people see > 'SGX' in their /proc/cpuinfo file, think that their hardware is 'SGX > enabled' and are wondering why the hell the /dev/sgx_enclave device > node is not created, right? Yes I believe so. > > I also Cc:-ed more SGX people. > > See the full -v3 patch below. > > Is the device node misnamed, should it be /dev/sgx_lc_enclave? > No. Form SGX hardware's perspective, LC (Launch Control) is a control mechanism to allow running 3rd party's Launch Enclave (LE), which is a special enclave used to control running other enclaves. Linux SGX driver doesn't distinguish whether the enclave is LE or not, it just treat all enclaves the same. So the name should be /dev/sgx_enclave. > Should > we hide the SGX feature bit from cpuinfo when SGX_LC is not present, so > that people don't go on a wild goose chase? No. KVM SGX virtualization can still work without the SGX_LC flag (only SGX flag is needed).
Hi, Jarkko, Kai, Thanks a ton for your suggestions and edits! Hi, Ingo, Thank you many tons for your help and attention to this small patch and a TIP submission! I wasn't expecting such an... immediate response to my small suggestion, honestly. Best regards, Vladis
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: 65be5c95d08eedda570a6c888a12384c77fe7614
Gitweb: https://git.kernel.org/tip/65be5c95d08eedda570a6c888a12384c77fe7614
Author: Vladis Dronov <vdronov@redhat.com>
AuthorDate: Sun, 09 Mar 2025 18:22:16 +01:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Mon, 10 Mar 2025 12:29:18 +01:00
x86/sgx: Warn explicitly if X86_FEATURE_SGX_LC is not enabled
The kernel requires X86_FEATURE_SGX_LC to be able to create SGX enclaves,
not just X86_FEATURE_SGX.
There is quite a number of hardware which has X86_FEATURE_SGX but not
X86_FEATURE_SGX_LC. A kernel running on such hardware does not create
the /dev/sgx_enclave file and does so silently.
Explicitly warn if X86_FEATURE_SGX_LC is not enabled to properly notify
users that the kernel disabled the SGX driver.
The X86_FEATURE_SGX_LC, a.k.a. SGX Launch Control, is a CPU feature
that enables LE (Launch Enclave) hash MSRs to be writable (with
additional opt-in required in the 'feature control' MSR) when running
enclaves, i.e. using a custom root key rather than the Intel proprietary
key for enclave signing.
I've hit this issue myself and have spent some time researching where
my /dev/sgx_enclave file went on SGX-enabled hardware.
Related links:
https://github.com/intel/linux-sgx/issues/837
https://patchwork.kernel.org/project/platform-driver-x86/patch/20180827185507.17087-3-jarkko.sakkinen@linux.intel.com/
[ mingo: Made the error message a bit more verbose, and added other cases
where the kernel fails to create the /dev/sgx_enclave device node. ]
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Kai Huang <kai.huang@intel.com>
Cc: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: https://lore.kernel.org/r/20250309172215.21777-2-vdronov@redhat.com
---
arch/x86/kernel/cpu/sgx/driver.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/cpu/sgx/driver.c b/arch/x86/kernel/cpu/sgx/driver.c
index 22b65a5..7f8d1e1 100644
--- a/arch/x86/kernel/cpu/sgx/driver.c
+++ b/arch/x86/kernel/cpu/sgx/driver.c
@@ -150,13 +150,15 @@ int __init sgx_drv_init(void)
u64 xfrm_mask;
int ret;
- if (!cpu_feature_enabled(X86_FEATURE_SGX_LC))
+ if (!cpu_feature_enabled(X86_FEATURE_SGX_LC)) {
+ pr_info("SGX disabled: SGX launch control CPU feature is not available, /dev/sgx_enclave disabled.\n");
return -ENODEV;
+ }
cpuid_count(SGX_CPUID, 0, &eax, &ebx, &ecx, &edx);
if (!(eax & 1)) {
- pr_err("SGX disabled: SGX1 instruction support not available.\n");
+ pr_info("SGX disabled: SGX1 instruction support not available, /dev/sgx_enclave disabled.\n");
return -ENODEV;
}
@@ -173,8 +175,10 @@ int __init sgx_drv_init(void)
}
ret = misc_register(&sgx_dev_enclave);
- if (ret)
+ if (ret) {
+ pr_info("SGX disabled: Unable to register the /dev/sgx_enclave driver (%d).\n", ret);
return ret;
+ }
return 0;
}The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: baf6a4fdb5ead6be10aa0a0e620d6078a669fc75
Gitweb: https://git.kernel.org/tip/baf6a4fdb5ead6be10aa0a0e620d6078a669fc75
Author: Vladis Dronov <vdronov@redhat.com>
AuthorDate: Sun, 09 Mar 2025 18:22:16 +01:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Mon, 10 Mar 2025 09:40:38 +01:00
x86/sgx: Warn explicitly if X86_FEATURE_SGX_LC is not enabled
The kernel requires X86_FEATURE_SGX_LC to be able to create SGX enclaves,
not just X86_FEATURE_SGX.
There is quite a number of hardware which has X86_FEATURE_SGX but not
X86_FEATURE_SGX_LC. A kernel running on such hardware does not create
the /dev/sgx_enclave file and does so silently.
Explicitly warn if X86_FEATURE_SGX_LC is not enabled to properly notify
users that the kernel disabled the SGX driver.
The X86_FEATURE_SGX_LC, a.k.a. SGX Launch Control, is a CPU feature
that enables LE (Launch Enclave) hash MSRs to be writable (with
additional opt-in required in the 'feature control' MSR) when running
enclaves, i.e. using a custom root key rather than the Intel proprietary
key for enclave signing.
I've hit this issue myself and have spent some time researching where
my /dev/sgx_enclave file went on SGX-enabled hardware.
Related links:
https://github.com/intel/linux-sgx/issues/837
https://patchwork.kernel.org/project/platform-driver-x86/patch/20180827185507.17087-3-jarkko.sakkinen@linux.intel.com/
[ mingo: Made the error message a bit more verbose, and added other cases
where the kernel fails to create the /dev/sgx_enclave device node. ]
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Kai Huang <kai.huang@intel.com>
Cc: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: https://lore.kernel.org/r/20250309172215.21777-2-vdronov@redhat.com
---
arch/x86/kernel/cpu/sgx/driver.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/cpu/sgx/driver.c b/arch/x86/kernel/cpu/sgx/driver.c
index 22b65a5..40c3347 100644
--- a/arch/x86/kernel/cpu/sgx/driver.c
+++ b/arch/x86/kernel/cpu/sgx/driver.c
@@ -150,13 +150,15 @@ int __init sgx_drv_init(void)
u64 xfrm_mask;
int ret;
- if (!cpu_feature_enabled(X86_FEATURE_SGX_LC))
+ if (!cpu_feature_enabled(X86_FEATURE_SGX_LC)) {
+ pr_err("SGX disabled: SGX launch control CPU feature is not available, /dev/sgx_enclave disabled.\n");
return -ENODEV;
+ }
cpuid_count(SGX_CPUID, 0, &eax, &ebx, &ecx, &edx);
if (!(eax & 1)) {
- pr_err("SGX disabled: SGX1 instruction support not available.\n");
+ pr_err("SGX disabled: SGX1 instruction support not available, /dev/sgx_enclave disabled.\n");
return -ENODEV;
}
@@ -173,8 +175,10 @@ int __init sgx_drv_init(void)
}
ret = misc_register(&sgx_dev_enclave);
- if (ret)
+ if (ret) {
+ pr_err("SGX disabled: Unable to register the /dev/sgx_enclave driver (%d).\n", ret);
return ret;
+ }
return 0;
}© 2016 - 2026 Red Hat, Inc.