Hello. Thanks for your report.

Thanks. Missed the lockless reader of the queue. Who is the lockless reader for spm_response_add() and spm_response_get()?

A secure partition may be reading from the queue from CPU1 at the same time as CPU0 pushes a new request. If this happens, it is needed that the stores are seen in the same order by all observers of the system.

Example comment 3

In T314#3758, @kennyliang-mtk wrote:

According to Hung-Te's comment,
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/860#message-233c99d5_765db5d9
I split the initial commit to several smaller patches.

According to Hung-Te's comment,
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/860#message-233c99d5_765db5d9
I split the initial commit to several smaller patches.

Hello kennyliang-mtk,

In T314#3510, @jts-arm wrote:

In T314#3507, @kennyliang-mtk wrote:

Excuse me, how do I link the commit,
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/860
to this task?

Hello kennyliang-mtk,
the link to the code review that you provided seems fine to me. Unless you had something more in mind?

John

In T314#3507, @kennyliang-mtk wrote:

Excuse me, how do I link the commit,
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/860
to this task?

Excuse me, how do I link the commit,
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/860
to this task?
Thanks.

Example comment 2

Example comment 1

comment 2

comment 1

Test TF-A tasks

Any thoughts on this? At the moment if I point potential members at git.trustedfirmware.org the 'no description'/'unnamed repository' labels are a bit off-putting.

Needs access to config files (I think). Feel free to reassign to whoever has access.