Re: memory operation operand len
"Stanislav" <[email protected]>
| Newsgroups | gmane.comp.emulators.bochs.devel |
|---|---|
| Message-ID | <[email protected]> |
By reading the class bxInstruction_c you cannot know a thing, especially because some instructions access memory multiple times (FXSAVE, REP MOVS) or access variable amount of bytes (VMASKMOV). I am not talking about many memory access cases which not related to any instruction (page walks, descriptors reads and other system stuff). Also before the memory access actually happen an instruction might fault so the memory access won't happen. But what do you want to do ? Might be I can help ... If you searching to lock memory before memory access happens you can look for BX_NOTIFY_LIN_MEMORY_ACCESS and BX_NOTIFY_PHY_MEMORY_ACCESS all around the code. Stanislav -----Original Message----- From: Xin Tong [mailto:[email protected]] Sent: Friday, October 19, 2012 9:06 PM To: [email protected] Subject: [Bochs-developers] memory operation operand len what is the best way to figure out the length of the memory a memory operation is going to access in BOCHS ? I read the class bxInstruction_c. it does not seem to provide anything to do that ? Xin ---------------------------------------------------------------------------- -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ bochs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bochs-developers ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct