Skip to content

QCLINUX: firmware: qcom: memory_dump_v2: assign dump table region to non-secure world - #80

Merged
Tingwei Zhang (quic-tingweiz) merged 1 commit into
qualcomm-linux:resolute-qcom-develfrom
jiegan0107:resolute-qcom-devel
Sep 29, 2026
Merged

Tingwei Zhang (quic-tingweiz) merged 1 commit into
qualcomm-linux:resolute-qcom-develfrom
jiegan0107:resolute-qcom-devel

Conversation

@jiegan0107

Copy link
Copy Markdown

Add assign_dump_table_region() to notify TZ that the memory dump table region should be made accessible to AOP.

@jiegan0107

Copy link
Copy Markdown
Author
  1. Why do we need this change?
    Fix the access permission issue of the HLOS dump table on Hamoa

  2. Was it merged on qcom-next, qcom-6.18 or upstream Kernel?
    Merged on qcom-next. Ongoing on qcom-6.18

  3. Was it verified with Ubuntu Kernel? What is the test case that is verified?
    Fully validated. With the fix change, the HLOS dump table is working well.
    Test case: manually trigger a crash to collect the crashdump to verify the change.

  4. If it's required, please rebase the PR since we have rebased on Canonical x05 release.
    Rebased on latest tip.

…non-secure world

Add assign_dump_table_region() to notify TZ that the memory dump table
region should be made accessible to AOP, via a self-contained SCM SMC
call (QCOM_SCM_SVC_UTIL / QCOM_SCM_UTIL_DUMP_TABLE_ASSIGN). The SMC
convention probe (__get_convention()) and dispatch helper are kept
local to this driver rather than exported from qcom_scm, since only
the register-argument SMC path is needed here.

Wire it into mem_dump_alloc(), falling back to the IMEM-based dump
table registration path if the SCM call fails.

signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
@quic-tingweiz
Tingwei Zhang (quic-tingweiz) merged commit 18bc3cd into qualcomm-linux:resolute-qcom-devel Sep 29, 2026
14 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants