From: Caleb Connolly <caleb.connolly@linaro.org>
To: Bjorn Andersson <quic_bjorande@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] soc: qcom: rmtfs: Support discarding guard pages
Date: Wed, 31 May 2023 01:08:29 +0100 [thread overview]
Message-ID: <e0d7021c-d6af-25df-5c90-3caec4bb83b7@linaro.org> (raw)
In-Reply-To: <20230530233643.4044823-3-quic_bjorande@quicinc.com>
On 31/05/2023 00:36, Bjorn Andersson wrote:
> In some configurations, the exact placement of the rmtfs shared memory
> region isn't so strict. The DeviceTree author can then choose to use the
> "size" property and rely on the OS for placement (in combination with
> "alloc-ranges", if desired).
>
> But on some platforms the rmtfs memory region may not be allocated
> adjacent to regions allocated by other clients. Add support for
> discarding the first and last 4k block in the region, if
> qcom,use-guard-pages is specified in DeviceTree.
Oh nice!
>
> Signed-off-by: Bjorn Andersson <quic_bjorande@quicinc.com>
> ---
>
> Changes since v1:
> - Drop the dma_alloc_coherent() based approach and just add support for
> the guard pages.
>
> drivers/soc/qcom/rmtfs_mem.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/soc/qcom/rmtfs_mem.c b/drivers/soc/qcom/rmtfs_mem.c
> index f83811f51175..28238974d913 100644
> --- a/drivers/soc/qcom/rmtfs_mem.c
> +++ b/drivers/soc/qcom/rmtfs_mem.c
> @@ -213,6 +213,16 @@ static int qcom_rmtfs_mem_probe(struct platform_device *pdev)
> goto put_device;
> }
>
> + /*
> + * If requested, discard the first and last 4k block in order to ensure
> + * that the rmtfs region isn't adjacent to other protected regions.
> + */
> + if (of_property_present(node, "qcom,use-guard-pages")) {
> + rmtfs_mem->addr += SZ_4K;
> + rmtfs_mem->base += SZ_4K;
> + rmtfs_mem->size -= 2 * SZ_4K;
> + }
> +
> cdev_init(&rmtfs_mem->cdev, &qcom_rmtfs_mem_fops);
> rmtfs_mem->cdev.owner = THIS_MODULE;
>
--
// Caleb (they/them)
next prev parent reply other threads:[~2023-05-31 0:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 23:36 [PATCH v2 0/3] soc: qcom: rmtfs: Support dynamic allocation Bjorn Andersson
2023-05-30 23:36 ` [PATCH v2 1/3] dt-bindings: reserved-memory: rmtfs: Allow guard pages Bjorn Andersson
2023-06-01 12:34 ` Stephan Gerhold
2023-06-04 10:25 ` Krzysztof Kozlowski
2023-05-30 23:36 ` [PATCH v2 2/3] soc: qcom: rmtfs: Support discarding " Bjorn Andersson
2023-05-31 0:08 ` Caleb Connolly [this message]
2023-05-31 0:09 ` Caleb Connolly
2023-06-01 12:26 ` Stephan Gerhold
2023-05-30 23:36 ` [PATCH v2 3/3] soc: qcom: rtmfs: Handle reserved-memory allocation issues Bjorn Andersson
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=e0d7021c-d6af-25df-5c90-3caec4bb83b7@linaro.org \
--to=caleb.connolly@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_bjorande@quicinc.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).