On Thu, Jul 12, 2012 at 12:56 PM, Addison Mayberry <[email protected]>wrote:
> Greetings, > I'm trying to pass some relevant information about the status of the guest > OS to MARSS. While reading through ptlcalls.h, I noticed that the CPUID > instruction is used for a similar purpose in that code. I discovered a > comment saying: > > "The 0x4xxxxxxx CPUID index range has been architecturally reserved > specifically for user defined purposes like this" > > I just want to be completely clear so I don't damage the validity of my > simulation. Does this mean that I can implement further "special values" > that MARSS checks for on a CPUID instruction, so long as they're in the > specified range, and it won't alter the operation of my SUT? > > CPUID is used to identify presence of MARSS and also returns the MMIO starting address to communicate between MARSS and VM. So you can use standard ptlcall like facility to communicate between VM and simulator. This wont break any simulation validity. - Avadh > Thanks for any help. > Sincerely, > Addison > > ______________________________**_________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected].**edu <[email protected]> > https://www.cs.binghamton.edu/**mailman/listinfo/marss86-devel<https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel> >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
