4 ms·
No they usually pair different architectures and it will crash if the OS doesn't catch and handle the invalid instruction error the CPU will throw. https://med
by AnotherGoodName 6y ago
No they usually pair different architectures and it will crash if the OS doesn't catch and handle the invalid instruction error the CPU will throw.
https://medium.com/@jaddr2line/a-big-little-problem-a-tale-of-big-little-gone-wrong-e7778ce744bb https://medium.com/@jaddr2line/a-big-little-problem-a-tale-o...
- johntb86 6y agoThat's not usual, that's just Samsung's incompetence.
- deleted 6y ago[deleted]
- brigade 6y agoAs mentioned in your link, that's ultimately against ARM's requirements for big.LITTLE and was due to buggy Samsung patches. A fixed kernel only exposes the subset of features available on all CPUs.
- deleted 6y ago[deleted]
- est31 6y agoHow does the scheduler know which process will use CPU instructions that the small cores don't support? Will it just try it out and then move the process to the higher support core if it detects an error?
- AnotherGoodName 6y ago>How does the scheduler know which process will use CPU instructions that the small cores don't support? I don't see that as required? If you catch the illegal instruction signal that CPUs throw you can just run it on the other CPU since the instruction counter would not have incremented. There's a delay in the catch and retry on the other CPU but i don't see the big deal here?
- mtklein 6y agoI once ran into the same sort of issue with this very chip, in that the little A55 cores supported half-float compute, while the big Mongoose cores didn't. Seriously a pain.