Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bugfix][6.6]Hygon: Fix S4 kernel panic issue on HYGON psp #501

Conversation

wojiaohanliyang
Copy link

When running the kernel which is compiled with the config CONFIG_CRYPTO_DEV_CCP_DD=y, the S4 resume process will change the TMR region, but the CSV firmware still keeps TMR region information as before. This will lead to kernel PANIC when the system resumed from S4. To address this issue, we provide PM callbacks, the callbacks will be called during S4 and resume from S4.

hygon inclusion
category: bugfix
CVE: NA

---------------------------

When running the kernel which is compiled with the config
CONFIG_CRYPTO_DEV_CCP_DD=y, the S4 resume process will change the TMR
region, but the CSV firmware still keeps TMR region information as
before. This will lead to kernel PANIC when the system resumed from S4.
To address this issue, we provide PM callbacks, the callbacks will be
called during S4 and resume from S4.

Signed-off-by: baizhaowei <[email protected]>
Signed-off-by: hanliyang <[email protected]>
@deepin-ci-robot
Copy link

Hi @wojiaohanliyang. Thanks for your PR.

I'm waiting for a deepin-community member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@deepin-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mingcongbai for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@wojiaohanliyang
Copy link
Author

/retest

@Avenger-285714 Avenger-285714 merged commit 973eb41 into deepin-community:linux-6.6.y Nov 28, 2024
2 of 4 checks passed
@deepin-ci-robot
Copy link

@wojiaohanliyang: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants