Hey folks,
So Sam and I are at the point now where we're attempting to get our
untrusted user threads running in a different scheduling domain, and it's
not exactly clear how this is supposed to work in terms of enabling more
than one domain in the kernel.
So far, I've set KernelNumDomains to 2 in the easy-settings.cmake for our
project, but unless I provide a separate implementation of
kernel/config/default_domain.c by overriding KernelDomainSchedule, the
resulting kernel will only think it has one domain and only ever schedule
domain 0 for execution.
Are we expected to override the default_domain.c file with our own in the
project, like sel4test seems to do?
Thanks!
--
June Tate-Gans
Software Engineer
