mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Val Packett <val@packett.cool>
To: Jianping Li <jianping.li@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, ekansh.gupta@oss.qualcomm.com,
	quic_chennak@quicinc.com
Subject: Re: [PATCH v1] arm64: dts: qcom: talos: Make the ADSP remote heap no-map
Date: Wed, 14 Oct 2026 13:41:19 -0300	[thread overview]
Message-ID: <12d14e1d-8355-4b3b-9eef-bd5e90dfd19f@packett.cool> (raw)
In-Reply-To: <20261014083820.468-1-jianping.li@oss.qualcomm.com>

On 10/14/26 5:38 AM, Jianping Li wrote:

> The ADSP remote heap is declared as a reusable CMA pool. FastRPC
> assigns the entire region to the DSP through qcom_scm_assign_mem()
> during probe without allocating the pages from CMA. Consequently,
> the pages remain available for movable HLOS allocations even after
> HLOS access to the region has been revoked.
>
> On Talos, GPU stress testing triggers a synchronous external abort
> when zram accesses pages within the ADSP remote heap.
>
> Replace reusable with no-map to prevent the region from being reused
> for normal kernel allocations and exclude it from the kernel's
> standard memory mapping.
>
> Fixes: b0b51a5f1911f ("arm64: dts: qcom: talos: Add memory-region for audio PD")
> Link: https://lore.kernel.org/all/20260424-talosaudio-v3-1-9e2ad5d78a2e@oss.qualcomm.com/
> Signed-off-by: Jianping Li <jianping.li@oss.qualcomm.com>
> ---
>   arch/arm64/boot/dts/qcom/talos.dtsi | 2 +-

This also applies to: glymur, agatti, sm8250, kodiak, sm8750.. (at least 
those I've found by grepping for the adsp_rpc_remote_heap_mem label)

I've been hitting the SEA on a kodiak phone (sm7325-motorola-dubai) 
constantly with just light everyday usage:

Internal error: synchronous external abort: 0000000096000010 [#1]  SMP
CPU: 7 UID: 10000 PID: 26485 Comm: pool-24 Tainted: G   M    W         
7.3.0-rc6-next-20261009-uwu+ #167 PREEMPT(full)
Tainted: [M]=MACHINE_CHECK, [W]=WARN
Hardware name: motorola Motorola Edge 30 (Tianma)/Motorola Edge 30 
(Tianma), BIOS 2026.07-gca7686425f32-dirty 07/01/2026
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : clear_page+0x30/0x70
lr : prep_new_page+0x94/0x178 ...
Call trace:
  clear_page+0x30/0x70 (P)
  get_page_from_freelist+0x1bd8/0x1c00
  __alloc_frozen_pages_noprof+0x1cc/0x3f8
  alloc_pages_mpol+0x124/0x210
  vma_alloc_folio_noprof+0x124/0x200
  vma_alloc_zeroed_movable_folio+0x3c/0x50
  do_pte_missing+0x9e0/0xf80
  ...


This no-map does seem to fix it.


Thanks,
~val


      parent reply	other threads:[~2026-10-14 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  8:38 Jianping Li
2026-10-14  9:07 ` Konrad Dybcio
2026-10-14  9:10 ` Ekansh Gupta
2026-10-14 16:41 ` Val Packett [this message]

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=12d14e1d-8355-4b3b-9eef-bd5e90dfd19f@packett.cool \
    --to=val@packett.cool \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ekansh.gupta@oss.qualcomm.com \
    --cc=jianping.li@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_chennak@quicinc.com \
    --cc=robh@kernel.org \
    /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®