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>, Ard Biesheuvel <ardb@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Pavel Machek <pavel@kernel.org>,
Brian Gerst <brgerst@gmail.com>
Subject: [PATCH v2 2/4] x86/acpi/suspend: Remove segment reloads on resume
Date: Tue, 3 Feb 2026 12:58:19 -0500 [thread overview]
Message-ID: <20260203175821.511847-3-brgerst@gmail.com> (raw)
In-Reply-To: <20260203175821.511847-1-brgerst@gmail.com>
common_startup_64() has set the segments to usable values already, and
they will be restored later in restore_processor_state(). Remove the
redundant segment loads in wakeup_long64()..
Signed-off-by: Brian Gerst <brgerst@gmail.com>
---
arch/x86/kernel/acpi/wakeup_64.S | 6 ------
1 file changed, 6 deletions(-)
diff --git a/arch/x86/kernel/acpi/wakeup_64.S b/arch/x86/kernel/acpi/wakeup_64.S
index 3d56610f0108..099401ef2ea4 100644
--- a/arch/x86/kernel/acpi/wakeup_64.S
+++ b/arch/x86/kernel/acpi/wakeup_64.S
@@ -28,12 +28,6 @@ SYM_FUNC_START(wakeup_long64)
1:
jmp 1b
2:
- movw $__KERNEL_DS, %ax
- movw %ax, %ss
- movw %ax, %ds
- movw %ax, %es
- movw %ax, %fs
- movw %ax, %gs
movq saved_rsp(%rip), %rsp
movq saved_rbx(%rip), %rbx
--
2.52.0
next prev parent reply other threads:[~2026-02-03 17:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 17:58 [PATCH v2 0/4] x86 suspend cleanups Brian Gerst
2026-02-03 17:58 ` [PATCH v2 1/4] x86/acpi/suspend: Remove indirect jump Brian Gerst
2026-02-03 17:58 ` Brian Gerst [this message]
2026-02-03 17:58 ` [PATCH v2 3/4] x86/acpi/suspend: Clean up stack usage Brian Gerst
2026-02-03 17:58 ` [PATCH v2 4/4] x86/acpi/suspend: Remove redundant register saves Brian Gerst
2026-02-03 20:31 ` [PATCH v2 0/4] x86 suspend cleanups Rafael J. Wysocki
2026-02-04 9:47 ` Ard Biesheuvel
2026-02-07 18:04 ` Brian Gerst
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=20260203175821.511847-3-brgerst@gmail.com \
--to=brgerst@gmail.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pavel@kernel.org \
--cc=rafael@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
all inboxes | Powered by JetHome®