From: Ingo Molnar <mingo@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
"Xin Li (Intel)" <xin@zytor.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, pavel@kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, xi.pardee@intel.com, todd.e.brandt@intel.com
Subject: Re: [PATCH v1 1/1] x86/fred: Fix system hang during S4 resume with FRED enabled
Date: Tue, 1 Apr 2025 10:22:53 +0200 [thread overview]
Message-ID: <Z-uiXfz1nOP7jGQv@gmail.com> (raw)
In-Reply-To: <148C8753-8972-4970-8951-E2D1CB26D8B0@zytor.com>
* H. Peter Anvin <hpa@zytor.com> wrote:
> Just to make it clear: the patch is correct, the shortcoming is in
> the description.
>
> I would say that Xin's description, although perhaps excessively
> brief, is correct from the *hardware* point of view, whereas Rafael
> adds the much needed *software* perspective.
This part of the -v1 patch was a bit misleading to me:
>> Due to changes in the kernel text and data mappings, the FRED MSRs
>> must be reinitialized.
... as it suggests that the FRED MSRs will change from before the
suspend - while they don't.
What this sentence meant is that FRED MSRs set up by the intermediate
*kexec kernel* are incorrect and must be reinitialized again to
reconstruct the pre-hibernation state. Ie. there's 3 FRED setup states:
pre-S4, kexec and post-S4, where pre-S4 == post-S4. Right?
I think the description and comments in the -v2 patch are better in
this regard.
Thanks,
Ingo
next prev parent reply other threads:[~2025-04-01 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 6:25 [PATCH v1 1/1] x86/fred: Fix system hang during S4 resume with FRED enabled Xin Li (Intel)
2025-03-31 12:36 ` [tip: x86/urgent] " tip-bot2 for Xin Li (Intel)
2025-03-31 15:30 ` [PATCH v1 1/1] " Rafael J. Wysocki
2025-03-31 16:19 ` Ingo Molnar
2025-03-31 20:03 ` H. Peter Anvin
2025-03-31 20:25 ` Rafael J. Wysocki
2025-04-01 8:22 ` Ingo Molnar [this message]
2025-04-01 6:34 ` Xin Li
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=Z-uiXfz1nOP7jGQv@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.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=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