Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
alexfru wrote:It shouldn't be much different from how you implement regular IPC and synchronization primitives. Send a message and block until reception of a response. Or block while waiting for an event which your v86 code will fire when done. That sort of stuff.
While you could do all v86 stuff in the context of the calling thread without IPC and additional thread/processes, you probably shouldn't or shouldn't rush into it. Unless you're certain there isn't going to be any kind of race condition between multiple v86 tasks, accessing shared resources, perform everything in a single 86 task and serialize accesses to it.
Okay. Yes I thought running the VM86 in its own process was the best solution, like this the process that wants to access the BIOS function doesn't crash if the VM86 process messes around.
alexfru wrote:Btw, is it expected to look like Malevich's black square?
Yes for sure, I wanted to reflect a little art in my works. I think OSdeving is an art just like painting, though it may not be that visually appealing.
