linux-kernel - Re: [PATCH v8 4/5] soc: qcom: add pd-mapper implementation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Fri, 7 Jun 2024 17:45:38 -0700
From: Chris Lew <quic_clew@...cinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
        Bjorn Andersson
	<andersson@...nel.org>,
        Konrad Dybcio <konrad.dybcio@...aro.org>,
        Sibi Sankar
	<quic_sibis@...cinc.com>,
        Mathieu Poirier <mathieu.poirier@...aro.org>
CC: <linux-arm-msm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-remoteproc@...r.kernel.org>,
        Johan Hovold <johan+linaro@...nel.org>,
        Xilin Wu <wuxilin123@...il.com>,
        Bryan O'Donoghue
	<bryan.odonoghue@...aro.org>,
        Steev Klimaszewski <steev@...i.org>,
        "Alexey
 Minnekhanov" <alexeymin@...tmarketos.org>
Subject: Re: [PATCH v8 4/5] soc: qcom: add pd-mapper implementation



On 5/11/2024 2:56 PM, Dmitry Baryshkov wrote:
> Existing userspace protection domain mapper implementation has several
> issue. It doesn't play well with CONFIG_EXTRA_FIRMWARE, it doesn't
> reread JSON files if firmware location is changed (or if firmware was
> not available at the time pd-mapper was started but the corresponding
> directory is mounted later), etc.
> 
> Provide in-kernel service implementing protection domain mapping
> required to work with several services, which are provided by the DSP
> firmware.
> 
> This module is loaded automatically by the remoteproc drivers when
> necessary via the symbol dependency. It uses a root node to match a
> protection domains map for a particular board. It is not possible to
> implement it as a 'driver' as there is no corresponding device.
> 
> Tested-by: Steev Klimaszewski <steev@...i.org>
> Tested-by: Alexey Minnekhanov <alexeymin@...tmarketos.org>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
> ---
>   drivers/soc/qcom/Kconfig          |  11 +
>   drivers/soc/qcom/Makefile         |   1 +
>   drivers/soc/qcom/pdr_internal.h   |  14 +
>   drivers/soc/qcom/qcom_pd_mapper.c | 676 ++++++++++++++++++++++++++++++++++++++
>   drivers/soc/qcom/qcom_pdr_msg.c   |  34 ++
>   5 files changed, 736 insertions(+)
> 

Reviewed-by: Chris Lew <quic_clew@...cinc.com>