Jens Nerche wrote: > > I just remember, someone would write a GUI for plex86. Seems, > this project sleeps, no? > Well, with or without this GUI it would be nice to get some > more information about the running monitor. We can provide > this information via /proc-fs, or we drop our /proc-subtree > and and provide all via GUI. Last way is better for porting, > and the only info in /proc is the number of reflected > interrupts for now. This number and some other such as > memory consumption for guest, monitor, SBE and so on, > found dangerous instructions could go into a frame of the > GUI. > Cool for debugging would be a suspend/resume mechanims > (should be easy to implement, we only don't switch to monitor > if we've our time slice) and view/change guest memory. My idea is to define another packet type in the interface between user/kernel-module, and pass back whatever statistics we want via that packet. Or perhaps several packet types if we want various categories of info. This way, one standard mechanism for retrieving, and the user code is free to display this however it wants (GUI/log-file,...). > Sorry for only give some ideas and code them not myself, > I've to write text for my master theses now... Ideas are always welcome. But man, everyone around me is getting Phd and Master's degrees. I feel so inadequate. :^) -Kevin
