Lines Matching refs:API
3 Currently, PSA Crypto API calls in Mbed TLS releases are not thread-safe.
5 As of Mbed TLS 3.6, an MVP for making the [PSA Crypto key management API](https://arm-software.gith…
15 - Some multithreaded testing of the key management API has been added, this is outlined in [Testing…
19 The other functions in the PSA Crypto API are planned to be made thread-safe in future, but current…
33 …n make calls to the Crypto API in separate threads. In such an environment, concurrent calls are t…
45 We do not test or support calling other PSA API functions concurrently.
47 There is no busy-waiting in our implementation, every API call completes in a finite number of step…
90 Much like all other API calls, `psa_destroy_key` does not block indefinitely, and when `psa_destroy…
119 …oon as one thread returns from creating/loading a key via a key management API call the key can be…
263 Our tests currently only run on pthread, we hope to expand this in the future (our API already allo…
267 Currently, not every API call is tested, we also cannot feasibly test every combination of concurre…
275 * For every API call, have a test which runs multiple copies of the call simultaneously.
292 As explained previously, we eventually aim to make the entirety of the PSA API thread-safe. This wi…
329 … same operation is not invoked concurrently. This abides by the PSA Crypto API Specification ([PSA…
333 …rations will require a status field protected by a global mutex. On entry, API calls would check t…
353 2. Provide a new public API that drivers can safely call.
355 …ore when handling these calls. (Drivers are still allowed to call any core API that can't have a d…
357 The first is too restrictive, the second and the third would require making it a stable API, and wo…
363 …e a call to the core when handling a call that is on the non-thread-safe driver core API whitelist.