It's not, xlen is fixed on that core like most RISC-V cores.
> How does Linux handle this? Can you just run an executable and have it automatically scheduled onto whichever cores can execute it? Wouldn't the kernel itself have to be compiled for both architectures?
With asymmetric multiprocessing like you get with OpenAMP. The RV32 cores are more real time management cores. One core only has an MPU, no MMU. The other core doesn't even have that. So run something like freertos (or just a superloop) on those cores to babysit realtime tasks and either respond quicker and/or more deterministically than Linux can, or avoid waking up the Linux core.
If so, then that would be pretty awesome. I think that people have been trying to get real-time working on Raspberry Pis. It seems that they get kinda close, but never manage to get all the way.
Another "big-player" option is ST which has the STM32MP1[3], which features a single Cortex-A7 alongside a Cortex-M4.
[1]: https://www.nxp.com/products/processors-and-microcontrollers...
[2]: https://www.nxp.com/products/processors-and-microcontrollers...
[3]: https://www.st.com/en/microcontrollers-microprocessors/stm32...
Perhaps it's better with the newer BSPs on the 8, but I wouldn't be too quick to jump back into it.
But I imagine that the larger SoCs are a more complex beast where getting everything to play nice with upstream Linux would be a greater challenge.
It's just the coprocessor stuff they're weak on. It's easier to just link up to a Cortex-M3 offboard, but then again NXP has completely screwed up their supply chain and these parts are somewhat hard to get.
Cortex-R is also pretty common (R5 on Zynq-7000 and R7 on UltraScale MPSoC, for example)
This would seem to be what's happened here with Linux running on, and really only in charge of, a small portion of the SOC. https://www.usenix.org/conference/osdi21/presentation/fri-ke...
To paraphrase what he says at the end of the talk, it would be a great idea to think about the kind of OS which could take these three cores properly into account.
On Linux this is a module that exposes a character device with one off ioctls.
On Windows this a kernel mode driver that exposes a Device object with one off DeviceIoControls.
I really don't think the reputation is deserved in this case, both kernels added equivalent support for this workflow back in the 90s.
How does Linux handle this? Can you just run an executable and have it automatically scheduled onto whichever cores can execute it? Wouldn't the kernel itself have to be compiled for both architectures?
EDIT: Maybe I was overthinking this -- I found what looks like the devicetree file for the BL808, and it seems like only the single RV64 core is supported:
https://lore.kernel.org/lkml/20221127132448.4034-7-jszhang@k...