When would Apple silicons made natively support for OSes such as Linux? Apple seemlingly reluctant to release detailed technical reference manual for M-series SoCs, which makes running Linux natively on Apple silicon challenging.
Nope, mine runs on a native Linux box featuring Intel i7-1370P and 32GB RAM. Maybe Xilinx has some tuning which makes Yocto become slow at parsing the recipe dependency and the likes.
I've tried asking the Xilinx community, and got only a reply saying that there is a database in Yocto which limits the scalability.
Your scenario makes me suspecting that it is Xilinx flavored Yocto causing the problem. I think that removing some unused Xilinx-specific layers/recipes can reduce the prologue and epilogue execution time.
Out of curious, does BPF now capable of capturing all the context switch events such as CPU trap?
Also, if the overhead is negligible, maybe the author can try to merge this into mainline with the use of static key to make the incurred overhead switchable. In spite of the static key, the degree of the accompanied inteferences on cache and branch predictor might be an intriguing topic though.
In the near future, people can control appliances with purely their own consciousness, and the only prerequisite is that it requires a minimum consiciousness level, which is reachable for most of the human being. Lastly, we usually think that people living in the Stone age are primitive people. Are they?
I don't think that the vanilla scheduler would get abandoned, instead, it would then acts as a fallback scheduler when customized userspace scheduler crashed or getting an update and so on.
Wonder if it's hard to make it SMP, if too many places use something like #ifdef CONFIG_ARCH_IS_UM to tell whether it is single CPU, it might be hard.