linux-kernel - Re: [PATCH 4/5] firmware: arm_scmi: smc transport supports multi-message pool

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]

Message-ID: <20201008211116.l6gbym2ypb6lzlo7@bogus>
Date:   Thu, 8 Oct 2020 22:11:16 +0100
From:   Sudeep Holla <sudeep.holla@....com>
To:     Etienne Carriere <etienne.carriere@...aro.org>
Cc:     linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        Cristian Marussi <cristian.marussi@....com>,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Souvik Chakravarty <Souvik.Chakravarty@....com>,
        Peng Fan <peng.fan@....com>
Subject: Re: [PATCH 4/5] firmware: arm_scmi: smc transport supports
 multi-message pool

On Thu, Oct 08, 2020 at 04:37:21PM +0200, Etienne Carriere wrote:
> There is no reason for the smc transport to restrict itself to a 1
> message pool. More can be allocated, messages are copied from/to the
> shared memory only on SMC exit/entry hence SCMI driver can play with
> several messages.
> 
> Use value of 20 to mimic mailbox transport implementation.

What is the need to mimic ?

> Any high value could fit. This should be something configurable.

Why not 10 or 100 ? I see any value other than 1 is useless as we lock
the channel in send_message and we don't maintain a queue like mailbox.

-- 
Regards,
Sudeep