[libcamera-devel] [PATCH 3/3] libcamera: ipa_manager: Allow forcing IPA module isolation

Kieran Bingham kieran.bingham at ideasonboard.com
Mon Jul 12 09:55:01 CEST 2021


Hi Laurent,

On 12/07/2021 00:15, Laurent Pinchart wrote:
> For test purpose it's useful to run open-source IPA modules in
> isolation. This can already be done by deleting the corresponding
> signature file, but that method can be inconvenient. Add a way to force
> IPA module isolation through a new LIBCAMERA_IPA_FORCE_ISOLATION
> environment variable.
> 
> Signed-off-by: Laurent Pinchart <laurent.pinchart at ideasonboard.com>
> ---
>  Documentation/environment_variables.rst | 5 +++++
>  src/libcamera/ipa_manager.cpp           | 8 ++++++++
>  2 files changed, 13 insertions(+)
> 
> diff --git a/Documentation/environment_variables.rst b/Documentation/environment_variables.rst
> index d392fd26b87a..1e85befd538a 100644
> --- a/Documentation/environment_variables.rst
> +++ b/Documentation/environment_variables.rst
> @@ -24,6 +24,11 @@ LIBCAMERA_IPA_CONFIG_PATH
>  
>     Example value: ``${HOME}/.libcamera/share/ipa:/opt/libcamera/vendor/share/ipa``
>  
> +LIBCAMERA_IPA_FORCE_ISOLATION
> +   When set to a non-empty string, force process isolation of all IPA modules.
> +
> +   Example value: ``1``
> +
>  LIBCAMERA_IPA_MODULE_PATH
>     Define custom search locations for IPA modules (`more <IPA module_>`__).
>  
> diff --git a/src/libcamera/ipa_manager.cpp b/src/libcamera/ipa_manager.cpp
> index 9533c8fadea6..028b2ce21779 100644
> --- a/src/libcamera/ipa_manager.cpp
> +++ b/src/libcamera/ipa_manager.cpp
> @@ -276,6 +276,14 @@ IPAModule *IPAManager::module(PipelineHandler *pipe, uint32_t minVersion,
>  bool IPAManager::isSignatureValid([[maybe_unused]] IPAModule *ipa) const
>  {
>  #if HAVE_IPA_PUBKEY
> +	char *force = utils::secure_getenv("LIBCAMERA_IPA_FORCE_ISOLATION");
> +	if (force && force[0] != '\0') {

We're getting this pattern a lot. I wonder if we should have
utils::secure_getenv return null if env[0] == '\0' to simplify the code.

Or otherwise, have an isSet() wrapper.

But anyway, that's not required here.

I suspect that the users of this env won't extend beyond developers and
tests, but I think even just for testing that provides a very valid use
case here, as we'll be able to create comparable tests using the same
IPA but for both isolated, and non-isolated cases.

Reviewed-by: Kieran Bingham <kieran.bingham at ideasonboard.com>


> +		LOG(IPAManager, Debug)
> +			<< "Isolation of IPA module " << ipa->path()
> +			<< " forced through environment variable";
> +		return false;
> +	}
> +
>  	File file{ ipa->path() };
>  	if (!file.open(File::ReadOnly))
>  		return false;
> 


More information about the libcamera-devel mailing list