> They definitely could have made avx512 instructions trigger a switch to p-cores Not really, no. OS-level schedulers are complicated as is with only P vs E cores to worry about, let alone having to dynamically move…
ACHI (which is how SATA is exposed) doesn't change any of this. The only thing that is affected is how the loaded OS has to talk to the disk controller. The real thing that loses space is the BPB (a 60 bytes or so,…
The screenshot of their bootloader (https://exectos.eu.org/images/exectos/xtldr_boot_menu.png) bears striking resemblance to GRUB, as well.
Can you show a source for this claim? There exists this codepath in adp_open: int adp_open(struct inode *inode, struct file *filp) { if (current->comm[0] == 'X') return -EBUSY; return drm_open(inode, filp); } but: (a)…
Can you provide any citations for this (extraordinary, if true) claim? My knowledge of operating systems (which is based on experience in designing toy ones, but also studying other operating systems) suggests this is…
> But understand that modern CPUs have hyperthreading, meaning more than one independent thread of execution. I know. But spinning up threads in an infinite loop is going to get code running on all threads (and indeed,…
> Or maybe I'm all wrong. I'm not an OS dev, so please someone correct me. Nope, you are completl right! A while (true) might slow down the system, but even that is not necessarily the case: I wrote a program to test…
> They definitely could have made avx512 instructions trigger a switch to p-cores Not really, no. OS-level schedulers are complicated as is with only P vs E cores to worry about, let alone having to dynamically move…
ACHI (which is how SATA is exposed) doesn't change any of this. The only thing that is affected is how the loaded OS has to talk to the disk controller. The real thing that loses space is the BPB (a 60 bytes or so,…
The screenshot of their bootloader (https://exectos.eu.org/images/exectos/xtldr_boot_menu.png) bears striking resemblance to GRUB, as well.
Can you show a source for this claim? There exists this codepath in adp_open: int adp_open(struct inode *inode, struct file *filp) { if (current->comm[0] == 'X') return -EBUSY; return drm_open(inode, filp); } but: (a)…
Can you provide any citations for this (extraordinary, if true) claim? My knowledge of operating systems (which is based on experience in designing toy ones, but also studying other operating systems) suggests this is…
> But understand that modern CPUs have hyperthreading, meaning more than one independent thread of execution. I know. But spinning up threads in an infinite loop is going to get code running on all threads (and indeed,…
> Or maybe I'm all wrong. I'm not an OS dev, so please someone correct me. Nope, you are completl right! A while (true) might slow down the system, but even that is not necessarily the case: I wrote a program to test…