This repository was archived by the owner on Jan 27, 2026. It is now read-only.
x86/mtrr: Check if fixed-range MTRR exists in mtrr_save_fixed_ranges()#130
Open
jiaqingz-dev wants to merge 1 commit intoprojectceladon:celadon/u/mr0/masterfrom
Open
x86/mtrr: Check if fixed-range MTRR exists in mtrr_save_fixed_ranges()#130jiaqingz-dev wants to merge 1 commit intoprojectceladon:celadon/u/mr0/masterfrom
jiaqingz-dev wants to merge 1 commit intoprojectceladon:celadon/u/mr0/masterfrom
Conversation
sysopenci
added
Valid commit message
Pending Developer Approval
|
one of the dependent pr's program name is not compatable with other dependent prs, for more details please check tracked_on |
sysopenci
requested review from
JeevakaPrabu,
bpanda24,
dyang23,
feijiang1,
gkdeepa,
kaushlen,
sgnanase,
shyjumon-n,
xyzhao2018,
xzhan34 and
yaoxinshi-intel
|
one of the dependent pr's program name is not compatable with other dependent prs, for more details please check tracked_on |
dyang23
approved these changes
May 12, 2025
When suspending, save_processor_state() calls mtrr_save_fixed_ranges() to save fixed-range MTRRs. On platforms without fixed-range MTRRs, accessing these MSRs will trigger unchecked MSR access error. Make sure fixed-range MTRRs are supported before access to prevent such error. Since mtrr_state.have_fixed is only set when MTRRs are present and enabled, checking the CPU feature flag in mtrr_save_fixed_ranges() is unnecessary. Fixes: 3ebad59 ("[PATCH] x86: Save and restore the fixed-range MTRRs of the BSP when suspending") Tracked-On: OAM-132466 Signed-off-by: Jiaqing Zhao <jiaqing.zhao@intel.com>
xyzhao2018
approved these changes
May 13, 2025
sysopenci
added
Developer Approved
and removed
Pending Developer Approval
|
Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web for more details. |
|
FAILURE: Android CI has completed Engineering Build for this issue.Please check the linked Tracked-On issue/Android CI Web for more details. |
sysopenci
added
Engineering Build Failed
and removed
Engineering Build Not Started
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When suspending, save_processor_state() calls mtrr_save_fixed_ranges() to save fixed-range MTRRs. On platforms without fixed-range MTRRs, accessing these MSRs will trigger unchecked MSR access error. Make sure fixed-range MTRRs are supported before access to prevent such error.
Since mtrr_state.have_fixed is only set when MTRRs are present and enabled, checking the CPU feature flag in mtrr_save_fixed_ranges() is unnecessary.
Fixes: 3ebad59 ("[PATCH] x86: Save and restore the fixed-range MTRRs of the BSP when suspending")
Cc: stable@vger.kernel.org
Tracked-On: OAM-132466