From: Bryan O'Donoghue <bod@kernel.org>
To: Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Vishnu Reddy <busanna.reddy@oss.qualcomm.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Vishnu Reddy <quic_bvisredd@quicinc.com>
Subject: Re: [PATCH v3 0/6] media: iris: prepare support for video codecs on Qcom vpu4 platform
Date: Thu, 20 Nov 2025 09:49:19 +0000 [thread overview]
Message-ID: <e01513fb-8ed8-4d4b-9111-bbf8ac4cce89@kernel.org> (raw)
In-Reply-To: <be157faa-b062-4726-83e2-ffdeaf792b50@oss.qualcomm.com>
On 12/11/2025 05:09, Vikash Garodia wrote:
>> One additional bonus is that fluster runs several process in parallel
>> by default, catching issues caused by several decode threads running
>> in parallel.
>>
> multi process issue is due to below [1] (tried it on lemans). Due to
> higher concurrency, we can see that the DMA buffer is mapped into
> un-addressable range (0-0x25800000) i.e 0x24b00000, and leading to
> global fault. This was the reason i was keeping 2 memory-region in
> kaanapali binding, to restrict certain ranges of IOVA.
If that is currently true then we should restrict concurrent sessions
entirely unless/until it can be safely supported.
---
bod
next prev parent reply other threads:[~2025-11-20 9:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 9:49 [PATCH v3 0/6] media: iris: prepare support for video codecs on Qcom vpu4 platform Vikash Garodia
2025-11-07 9:49 ` [PATCH v3 1/6] media: iris: Add support for multiple clock sources Vikash Garodia
2025-11-07 9:49 ` [PATCH v3 2/6] media: iris: Add support for multiple TZ content protection(CP) configs Vikash Garodia
2025-11-07 9:49 ` [PATCH v3 3/6] media: iris: Introduce buffer size calculations for vpu4 Vikash Garodia
2025-11-07 9:49 ` [PATCH v3 4/6] media: iris: Move vpu register defines to common header file Vikash Garodia
2025-11-07 9:49 ` [PATCH v3 5/6] media: iris: Move vpu35 specific api to common to use for vpu4 Vikash Garodia
2025-11-07 9:49 ` [PATCH v3 6/6] media: iris: Introduce vpu ops for vpu4 with necessary hooks Vikash Garodia
2025-12-06 23:04 ` Bryan O'Donoghue
2025-12-09 9:02 ` Vikash Garodia
2025-11-11 10:38 ` [PATCH v3 0/6] media: iris: prepare support for video codecs on Qcom vpu4 platform Dmitry Baryshkov
2025-11-11 12:43 ` Vikash Garodia
2025-11-11 13:39 ` Dmitry Baryshkov
2025-11-12 5:09 ` Vikash Garodia
2025-11-19 9:08 ` Dmitry Baryshkov
2025-11-20 9:49 ` Bryan O'Donoghue [this message]
2025-11-21 11:03 ` Vikash Garodia
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=e01513fb-8ed8-4d4b-9111-bbf8ac4cce89@kernel.org \
--to=bod@kernel.org \
--cc=abhinav.kumar@linux.dev \
--cc=bryan.odonoghue@linaro.org \
--cc=busanna.reddy@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=quic_bvisredd@quicinc.com \
--cc=robh@kernel.org \
--cc=vikash.garodia@oss.qualcomm.com \
/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;
as well as URLs for NNTP newsgroup(s).