linux-kernel - Re: [PATCH v3 2/2] firmware: qcom_scm: Support multiple waitq contexts

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] [day] [month] [year] [list]

Message-ID: <e466a2bd-c1a0-4a55-9d20-eb9e58427554@quicinc.com>
Date: Thu, 7 Nov 2024 10:53:11 +0530
From: Pavan Kondeti <quic_pkondeti@...cinc.com>
To: Unnathi Chalicheemala <quic_uchalich@...cinc.com>
CC: Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio
	<konradybcio@...nel.org>,
        <linux-arm-msm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <kernel@...cinc.com>
Subject: Re: [PATCH v3 2/2] firmware: qcom_scm: Support multiple waitq
 contexts

On Mon, Nov 04, 2024 at 08:20:56AM -0800, Unnathi Chalicheemala wrote:
>  
> +static int qcom_scm_query_waitq_count(void)
> +{
> +	int ret;
> +	struct qcom_scm_desc desc = {
> +		.svc = QCOM_SCM_SVC_WAITQ,
> +		.cmd = QCOM_SCM_WAITQ_GET_INFO,
> +		.owner = ARM_SMCCC_OWNER_SIP
> +	};
> +	struct qcom_scm_res res;
> +
> +	if (!__qcom_scm_is_call_available(__scm->dev, QCOM_SCM_SVC_WAITQ, QCOM_SCM_WAITQ_GET_INFO))
> +		return 1;
> +
> +	ret = qcom_scm_call_atomic(__scm->dev, &desc, &res);
> +	if (ret)
> +		return ret;
> +
> +	return res.result[0] & GENMASK(7, 0);
> +}

I see that this SCM call is same as what we called to get the IRQ, not
possible to populate all the waitq info at once and process/cache them
accordingly?

Thanks,
Pavan