From: Jianping <jianping.li@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: srini@kernel.org, amahesh@qti.qualcomm.com, arnd@arndb.de,
Greg KH <gregkh@linuxfoundation.org>,
linux-arm-msm@vger.kernel.org, thierry.escande@linaro.org,
abelvesa@kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, quic_chennak@quicinc.com,
Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
Subject: Re: [PATCH v2 4/4] misc: fastrpc: Allocate entire reserved memory for Audio PD in probe
Date: Thu, 5 Feb 2026 17:02:35 +0800 [thread overview]
Message-ID: <b114f326-cbe3-4b05-8e6a-2d62636898c9@oss.qualcomm.com> (raw)
In-Reply-To: <pm7lequ6lqrgu3mloytfph5opz6aynaa4ag6uedc62fprpskoz@qqvonfthnk6n>
On 2/4/2026 5:19 AM, Dmitry Baryshkov wrote:
> On Mon, Feb 02, 2026 at 03:06:59PM +0800, Jianping wrote:
>>
>>
>> On 1/16/2026 4:49 AM, Dmitry Baryshkov wrote:
>>> On Thu, Jan 15, 2026 at 04:28:51PM +0800, Jianping Li wrote:
>>>> The entire reserved-memory region is now assigned to DSP VMIDs during
>>>> channel setup and stored in cctx->remote_heap. Memory is reclaimed in
>>>> rpmsg_remove by revoking DSP permissions and freeing the buffer, tying
>>>> heap lifecycle to the rpmsg channel.
>>>
>>>> @@ -1370,8 +1346,15 @@ static int fastrpc_init_create_static_process(struct fastrpc_user *fl,
>>>> args[1].length = inbuf.namelen;
>>>> args[1].fd = -1;
>>>> - pages[0].addr = fl->cctx->remote_heap->dma_addr;
>>>> - pages[0].size = fl->cctx->remote_heap->size;
>>>> + if (!fl->cctx->audio_init_mem) {
>>>> + pages[0].addr = fl->cctx->remote_heap->dma_addr;
>>>> + pages[0].size = fl->cctx->remote_heap->size;
>>>
>>> Do we need a flag? Can't we assume that remote_heap is always to be
>>> allocated to the PD?
>> We do need the audio_init_mem flag.
>> Once the PD starts and daemon takes the memory for the first time, PD will
>> start using the memory,
>> meanwhile, the daemon can be killed and restarted. In this case, the memory
>> is still with the PD and the next
>> daemon connection should not take any memory for the next request. This flag
>> is maintained to ensure that.
>> The memory needs to be resent only if Audio PD on DSP restarts(due to
>> PD-restart or Subsystem-restart)
>
> This needs to be explained in the changelog.
I will add it.
>
>>
>>>
>>>> + fl->cctx->audio_init_mem = true;
>
> What if there are two racing IOCTLs, trying to init AudioPD process?
There may be a chance that two threads enter ioctl at the same time, and
seeing that audio_init_mem is false causes it to send twice, so a
cctx->lock needs to be added here to ensure that two threads do not
enter simultaneously.
>
>>>> + inbuf.pageslen = 1;
>>>> + } else {
>>>> + pages[0].addr = 0;
>>>> + pages[0].size = 0;
>>>> + }
>>>> args[2].ptr = (u64)(uintptr_t) pages;
>>>> args[2].length = sizeof(*pages);
>
prev parent reply other threads:[~2026-02-05 9:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 8:28 [PATCH v2 0/4] Add missing bug fixes Jianping Li
2026-01-15 8:28 ` [PATCH v2 1/4] misc: fastrpc: Add NULL check to fastrpc_buf_free to prevent crash Jianping Li
2026-01-15 20:43 ` Dmitry Baryshkov
2026-02-02 6:33 ` Jianping
2026-01-16 14:49 ` Greg KH
2026-02-02 7:13 ` Jianping
2026-02-02 8:41 ` Greg KH
2026-02-03 11:00 ` Jianping
2026-02-03 12:08 ` Jianping
2026-02-03 21:32 ` Bjorn Andersson
2026-02-05 9:07 ` Jianping
2026-01-15 8:28 ` [PATCH v2 2/4] misc: fastrpc: Fix initial memory allocation for Audio PD memory pool Jianping Li
2026-01-15 20:45 ` Dmitry Baryshkov
2026-02-02 6:42 ` Jianping
2026-01-15 8:28 ` [PATCH v2 3/4] misc: fastrpc: Remove buffer from list prior to unmap operation Jianping Li
2026-01-15 20:47 ` Dmitry Baryshkov
2026-02-02 6:51 ` Jianping
2026-02-03 21:15 ` Dmitry Baryshkov
2026-02-05 9:00 ` Jianping
2026-01-15 8:28 ` [PATCH v2 4/4] misc: fastrpc: Allocate entire reserved memory for Audio PD in probe Jianping Li
2026-01-15 20:49 ` Dmitry Baryshkov
2026-02-02 7:06 ` Jianping
2026-02-03 21:19 ` Dmitry Baryshkov
2026-02-03 21:42 ` Bjorn Andersson
2026-02-05 9:04 ` Jianping
2026-02-05 9:02 ` Jianping [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=b114f326-cbe3-4b05-8e6a-2d62636898c9@oss.qualcomm.com \
--to=jianping.li@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=amahesh@qti.qualcomm.com \
--cc=arnd@arndb.de \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ekansh.gupta@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_chennak@quicinc.com \
--cc=srini@kernel.org \
--cc=thierry.escande@linaro.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®