mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Xin Li (Intel)" <xin@zytor.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Cc: rafael@kernel.org, pavel@kernel.org, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	x86@kernel.org, luto@kernel.org, brgerst@gmail.com,
	jgross@suse.com, torvalds@linux-foundation.org,
	xi.pardee@intel.com, todd.e.brandt@intel.com, xin@zytor.com
Subject: Re: [PATCH v2 1/1] x86/fred: Fix system hang during S4 resume with FRED enabled
Date: Tue, 01 Apr 2025 07:39:56 -0700	[thread overview]
Message-ID: <2C7E3D1D-0391-43DF-8D72-02C4C742573F@zytor.com> (raw)
In-Reply-To: <20250401075728.3626147-1-xin@zytor.com>

On April 1, 2025 12:57:27 AM PDT, "Xin Li (Intel)" <xin@zytor.com> wrote:
>Upon a wakeup from S4, the restore kernel starts and initializes the
>FRED MSRs as needed from its perspective.  It then loads a hibernation
>image, including the image kernel, and attempts to load image pages
>directly into their original page frames used before hibernation unless
>those frames are currently in use.  Once all pages are moved to their
>original locations, it jumps to a "trampoline" page in the image kernel.
>
>At this point, the image kernel takes control, but the FRED MSRs still
>contain values set by the restore kernel, which may differ from those
>set by the image kernel before hibernation.  Therefore, the image kernel
>must ensure the FRED MSRs have the same values as before hibernation.
>Since these values depend only on the location of the kernel text and
>data, they can be recomputed from scratch.
>
>Reported-by: Xi Pardee <xi.pardee@intel.com>
>Reported-by: Todd Brandt <todd.e.brandt@intel.com>
>Suggested-by: H. Peter Anvin (Intel) <hpa@zytor.com>
>Signed-off-by: Xin Li (Intel) <xin@zytor.com>
>Tested-by: Todd Brandt <todd.e.brandt@intel.com>
>Cc: Andy Lutomirski <luto@kernel.org>
>Cc: Brian Gerst <brgerst@gmail.com>
>Cc: Juergen Gross <jgross@suse.com>
>Cc: Linus Torvalds <torvalds@linux-foundation.org>
>Cc: stable@vger.kernel.org # 6.9+
>---
>
>Change in v2:
>* Rewrite the change log and in-code comments based on Rafael's feedback.
>---
> arch/x86/power/cpu.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
>diff --git a/arch/x86/power/cpu.c b/arch/x86/power/cpu.c
>index 63230ff8cf4f..08e76a5ca155 100644
>--- a/arch/x86/power/cpu.c
>+++ b/arch/x86/power/cpu.c
>@@ -27,6 +27,7 @@
> #include <asm/mmu_context.h>
> #include <asm/cpu_device_id.h>
> #include <asm/microcode.h>
>+#include <asm/fred.h>
> 
> #ifdef CONFIG_X86_32
> __visible unsigned long saved_context_ebx;
>@@ -231,6 +232,19 @@ static void notrace __restore_processor_state(struct saved_context *ctxt)
> 	 */
> #ifdef CONFIG_X86_64
> 	wrmsrl(MSR_GS_BASE, ctxt->kernelmode_gs_base);
>+
>+	/*
>+	 * Reinitialize FRED to ensure the FRED MSRs contain the same values
>+	 * as before hibernation.
>+	 *
>+	 * Note, the setup of FRED RSPs requires access to percpu data
>+	 * structures.  Therefore, FRED reinitialization can only occur after
>+	 * the percpu access pointer (i.e., MSR_GS_BASE) is restored.
>+	 */
>+	if (ctxt->cr4 & X86_CR4_FRED) {
>+		cpu_init_fred_exceptions();
>+		cpu_init_fred_rsps();
>+	}
> #else
> 	loadsegment(fs, __KERNEL_PERCPU);
> #endif
>
>base-commit: 535bd326c5657fe570f41b1f76941e449d9e2062

Reviewed-by: H. Peter Anvin (Intel) <hpa@zytor.com>

  parent reply	other threads:[~2025-04-01 14:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01  7:57 Xin Li (Intel)
2025-04-01 11:51 ` Rafael J. Wysocki
2025-04-01 14:39 ` H. Peter Anvin [this message]
2025-04-01 20:41 ` [tip: x86/urgent] " tip-bot2 for Xin Li (Intel)

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=2C7E3D1D-0391-43DF-8D72-02C4C742573F@zytor.com \
    --to=hpa@zytor.com \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=pavel@kernel.org \
    --cc=rafael@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=todd.e.brandt@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    --cc=xi.pardee@intel.com \
    --cc=xin@zytor.com \
    /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®