Hi All,

I was wondering how folks are handling processor specifc implementations of their OS. There was a thread on the main forum which you may have read. Essentially I was poking for information on XMM registers and received some. However, I'd like to understand how others have approached this from an OS design perspective. There are other features besides the XMM registers (and associated opcodes) and am curious why/how people designed for them.

All thoughts welcomed!

I think its best to not use this type of reg in the OS its self, but use it in program that benefit from using them, they are simple to use and test for.
Dex4u test prog:


But that may just be me .

Yep, this is what Solar OS is doing too, but if you're multitasking (which I realize Dex OS isn't) that you'd want to ensure you are able to save all the states for all the registers and flags between swapping tasks. If a seperate task uses the FPU registers, you have to have a way to save that state so some other task doesn't trash the state of another task.

Nice CPUID BTW!

Do not be too sure, as i am thinking about using a form of virtualization to run lots of mini Dex4u images .

Off the top of my head, i would test at startup for what are available on the that processor and then uses some self modifying code ?.

Dex: get in touch with HyperVista about that

Yes i am hoping HyperVista will be of help, in point me in a good overall design .
But i need to finish some bits and bobs, before i get stuck in, then i go in info gathering mode, and HyperVista is top of that list .