Tom Rini 233fda6af6 Merge patch series "Uthreads"
Jerome Forissier <jerome.forissier@linaro.org> says:

This series introduces threads and uses them to improve the performance
of the USB bus scanning code and to implement background jobs in the
shell via two new commands: 'spawn' and 'wait'.

The threading framework is called 'uthread' and is inspired from the
barebox threads [2]. setjmp() and longjmp() are used to save and
restore contexts, as well as a non-standard extension called initjmp().
This new function is added in several patches, one for each
architecture that supports HAVE_SETJMP. A new symbol is defined:
HAVE_INITJMP. Two tests, one for initjmp() and one for the uthread
scheduling, are added to the lib suite.

After introducing threads and making schedule() and udelay() a thread
re-scheduling point, the USB stack initialization is modified to benefit
from concurrency when UTHREAD is enabled, where uthreads are used in
usb_init() to initialize and scan multiple busses at the same time.
The code was tested on arm64 and arm QEMU with 4 simulated XHCI buses
and some devices. On this platform the USB scan takes 2.2 s instead of
5.6 s. Tested on i.MX93 EVK with two USB hubs, one ethernet adapter and
one webcam on each, "usb start" takes 2.4 s instead of 4.6 s.

Finally, the spawn and wait commands are introduced, allowing the use of
threads from the shell. Tested on the i.MX93 EVK with a spinning HDD
connected to USB1 and the network connected to ENET1. The USB plus DHCP
init sequence "spawn usb start; spawn dhcp; wait" takes 4.5 seconds
instead of 8 seconds for "usb start; dhcp".

[1] https://patchwork.ozlabs.org/project/uboot/list/?series=446674
[2] https://github.com/barebox/barebox/blob/master/common/bthread.c

Link: https://lore.kernel.org/r/20250418141114.2056981-1-jerome.forissier@linaro.org
2025-04-23 13:21:39 -06:00
..
2025-02-11 20:12:36 -06:00
2024-10-17 03:12:47 +02:00
2025-01-22 15:58:03 -06:00
2025-04-22 15:08:47 -06:00
2024-07-29 15:01:04 -06:00
2024-10-24 11:20:58 -06:00
2024-08-26 14:05:38 -06:00
2025-04-03 11:43:22 -06:00
2024-07-29 15:01:04 -06:00
2025-03-24 08:51:34 -03:00
2024-11-20 17:57:58 +01:00
2024-07-29 15:01:04 -06:00
2025-01-05 02:30:49 +01:00
2024-06-14 12:59:07 -06:00
2024-07-29 15:01:04 -06:00
2025-03-07 11:50:22 -06:00
2024-09-24 13:41:20 -06:00
2025-02-05 16:22:55 +01:00
2025-04-02 20:00:59 -06:00
2024-07-29 15:01:04 -06:00
2024-07-29 15:01:04 -06:00
2024-07-29 15:01:04 -06:00
2024-07-29 15:01:04 -06:00
2024-08-13 06:23:15 +02:00
2025-03-10 07:41:16 +01:00
2024-12-31 10:58:30 -06:00
2025-01-26 11:06:56 +01:00
2025-04-03 11:41:54 -06:00
2024-07-29 15:01:04 -06:00
2025-04-03 16:54:49 -06:00
2024-11-04 16:41:38 -06:00
2024-07-29 15:01:04 -06:00
2025-03-11 23:06:18 +01:00
2024-07-29 15:01:04 -06:00
2024-10-24 11:21:48 -06:00
2024-07-29 15:01:04 -06:00
2024-07-29 15:01:04 -06:00
2024-11-25 23:07:37 -03:00
2024-09-30 17:48:12 -06:00
2024-11-20 17:57:58 +01:00
2025-03-19 03:38:51 +01:00
2024-09-12 17:35:37 +02:00
2025-04-10 20:55:53 -06:00
2025-01-14 14:29:29 -06:00
2024-07-29 15:01:04 -06:00
2025-04-16 19:57:19 -06:00
2025-02-28 08:41:54 -06:00
2024-07-29 15:01:04 -06:00
2025-02-11 20:10:58 -06:00
2025-01-07 15:45:51 +02:00
2025-01-01 10:40:33 -06:00
2024-07-29 15:01:04 -06:00
2024-07-29 15:01:04 -06:00
2025-04-23 13:19:44 -06:00
2025-02-03 16:01:36 -06:00
2024-11-13 08:14:23 -06:00
2024-07-29 15:01:04 -06:00