From: Brian Gerst <brgerst@gmail.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Ingo Molnar <mingo@kernel.org>, "H . Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, Andy Lutomirski <luto@kernel.org>,
Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Brian Gerst <brgerst@gmail.com>,
Sohil Mehta <sohil.mehta@intel.com>
Subject: [PATCH v2 7/7] x86/syscall/32: Add comment to conditional
Date: Fri, 14 Mar 2025 11:12:20 -0400 [thread overview]
Message-ID: <20250314151220.862768-8-brgerst@gmail.com> (raw)
In-Reply-To: <20250314151220.862768-1-brgerst@gmail.com>
Add a CONFIG_X86_FRED comment, since this conditional is nested.
Signed-off-by: Brian Gerst <brgerst@gmail.com>
Suggested-by: Sohil Mehta <sohil.mehta@intel.com>
---
arch/x86/entry/syscall_32.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/x86/entry/syscall_32.c b/arch/x86/entry/syscall_32.c
index 993d72504fc5..2b15ea17bb7c 100644
--- a/arch/x86/entry/syscall_32.c
+++ b/arch/x86/entry/syscall_32.c
@@ -238,7 +238,8 @@ DEFINE_FREDENTRY_RAW(int80_emulation)
instrumentation_end();
syscall_exit_to_user_mode(regs);
}
-#endif
+#endif /* CONFIG_X86_FRED */
+
#else /* CONFIG_IA32_EMULATION */
/* Handles int $0x80 on a 32bit kernel */
--
2.48.1
next prev parent reply other threads:[~2025-03-14 15:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 15:12 [PATCH v2 0/7] x86/entry: Break up common.c Brian Gerst
2025-03-14 15:12 ` [PATCH v2 1/7] x86/xen: Move Xen upcall handler Brian Gerst
2025-03-14 15:16 ` Juergen Gross
2025-03-16 11:01 ` [tip: x86/cpu] " tip-bot2 for Brian Gerst
2025-03-19 11:03 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-14 15:12 ` [PATCH v2 2/7] x86/syscall/32: Move 32-bit syscall dispatch code Brian Gerst
2025-03-16 11:01 ` [tip: x86/cpu] " tip-bot2 for Brian Gerst
2025-03-19 11:03 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-14 15:12 ` [PATCH v2 3/7] x86/syscall/64: Move 64-bit " Brian Gerst
2025-03-16 11:01 ` [tip: x86/cpu] " tip-bot2 for Brian Gerst
2025-03-19 11:03 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-14 15:12 ` [PATCH v2 4/7] x86/syscall/x32: Move x32 syscall table Brian Gerst
2025-03-16 11:01 ` [tip: x86/cpu] " tip-bot2 for Brian Gerst
2025-03-19 11:03 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-14 15:12 ` [PATCH v2 5/7] x86/syscall: Move sys_ni_syscall() Brian Gerst
2025-03-16 11:01 ` [tip: x86/cpu] " tip-bot2 for Brian Gerst
2025-03-19 11:03 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-14 15:12 ` [PATCH v2 6/7] x86/syscall: Remove stray semicolons Brian Gerst
2025-03-16 11:01 ` [tip: x86/cpu] " tip-bot2 for Brian Gerst
2025-03-19 11:03 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-14 15:12 ` Brian Gerst [this message]
2025-03-14 17:19 ` [PATCH v2 7/7] x86/syscall/32: Add comment to conditional Sohil Mehta
2025-03-14 17:43 ` Brian Gerst
2025-03-14 18:30 ` H. Peter Anvin
2025-03-16 11:01 ` [tip: x86/cpu] " tip-bot2 for Brian Gerst
2025-03-19 11:03 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-14 17:22 ` [PATCH v2 0/7] x86/entry: Break up common.c Sohil Mehta
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=20250314151220.862768-8-brgerst@gmail.com \
--to=brgerst@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=sohil.mehta@intel.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