Lines Matching refs:will
26 …) section discusses the state of our testing, as well as how this testing will be extended in futu…
78 …will still work. Implementations which only ever call PSA functions from a single thread, or which…
119 …y, with the same key identifier, only one thread can succeed - the others will return `PSA_ERROR_A…
123 …will be returned. If this code is returned, execution of the PSA subsystem must be stopped. All fu…
194 …te). Attempting to start using any key which is not a member of the union will result in a `PSA_ER…
198 …ation fails and this is the first failure within a function, the function will return `PSA_ERROR_S…
206 …ILLING`. If not found, it will see if there are any persistent keys loaded which do not have any r…
213 …at has been kicked out of a slot, the call to `psa_get_and_lock_key_slot` will see that the key is…
215 …slot` cannot find a suitable slot, the key cannot be loaded back in. This will lead to a `PSA_ERRO…
225 …y (the operations do not access the key slots again). The copy of the key will not be destroyed du…
231 …or" approach. The final thread to unregister from reading a destroyed key will automatically wipe …
255 …ts thread-safe. If multiple threads fail a test assert, the first failure will be reported with co…
292 …, we eventually aim to make the entirety of the PSA API thread-safe. This will build on the work t…
296 …med under any global mutex. One-shot operations and multi-part operations will each only hold the …
324 …* Multi-part operations will need to remain registered as readers of their key slot until their co…
325 …* The functionality where `psa_unregister_read` can wipe the key slot will need to be removed, slo…
333 …will require a status field protected by a global mutex. On entry, API calls would check the state…