3 ms·

Easiest way to solve would be moving the process to BIG core on first use of unsupported feature.

• Symmetry 8y ago
  I'm far from an expert here but it sounds like you'd have to keep track of CPU extensions on a per core and per thread basis and I don't think most OSs actually do that.
  • aidenn0 8y ago
    Or just catch an illegal instruction trap and move the thread to a big core if it's on a little core.
    • jandrese 8y ago
      Or vice versa? The talk here was about how the specialized crypto hardware was only on the little core because it isn't necessary on the big one.
      • blattimwind 8y ago
        The Atom encryption engine stuff isn't in the micro-arch though. Afaik you'd use it via kernel APIs.
• brigade 8y ago
  That would still need kernel support, so apps will randomly crash if you aren't using the latest patches (spoiler: some people won't be) Really, it's just a bad idea overall to have usermode visible microarchitectural differences between cores, as Samsung keeps demonstrating with their Exynos chips.