FLOSS virtualization hacker, occasional brewer

  • 3 Posts
  • 145 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle


  • Alex@lemmy.mltoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    19
    ·
    11 days ago

    It depends what they want to do. They can fork and take on the burden of maintaining the whole tree in which case good luck with that, linux is too much of a fire hose to enable a 3rd party to assemble something similar making different choices about what they merge. Otherwise they can maintain a re-based fork that tracks the Torvalds tree and then congratulations you’ve just invented a feature tree that can do contribution with extra steps.








  • What do people expect? Those servers aren’t free to run and they’re is only so much VC money to burn. That said I wouldn’t pay the various subscription levels that are currently being asked for. I pay for API use which is basically pay as you go. It also makes you think “does this task really need the non-free tier to complete?”.






  • QEMU is always going to focus on emulation fidelity first and there are few shortcuts. With floating point the differences aren’t generally in the numbers but in how the NaNs and other edge cases are handled. If you want to execute FP heavy code you should be cross compiling anyway.






  • Pretty much. From v8.0 onwards all the extra features are indicated by id flags. Stuff that is relevant to kernel mode will generally be automatically handled by the kernel patching itself on booting up and in user space some libraries will select appropriately accelerated functions when the ISA extensions are probed. There are a bunch off advisory instructions encoded in the hint space that will be effectively NOPs on older hardware but will enhance execution if run on newer hardware.

    If you want to play with newer instructions have a look at QEMUs “max” CPU.