CP TRACE question....
Hi, gang. I have a question about the CP TRACE command.what are the ramifications, if any, on using the TRACE command to monitor and debug an application running in a virtual machine that has multiple virtual CPUs defined? The application is aware of the multiple virtual processors and can dispatch work on multiple processors at the same time. Does this configuration have any impact on the ability of the TRACE command to trap machine operations, set breakpoints, etc.? Thanks and have a good one. -- Dave Jones V/Soft www.vsoft-software.com Houston, TX 281.578.7544
Re: CP TRACE question....
On Thu, Oct 8, 2009 at 9:44 PM, Dave Jones d...@vsoft-software.com wrote: Does this configuration have any impact on the ability of the TRACE command to trap machine operations, set breakpoints, etc.? Did you remember to use CPU ALL to activate PER for all CPUs (unless you know where to look for it) Rob
Re: CP TRACE question....
On Thu, Oct 8, 2009 at 4:46 PM, Rob van der Heij rvdh...@gmail.com wrote: Did you remember to use CPU ALL to activate PER for all CPUs (unless you know where to look for it) Good point: CPU ALL TRACE ... (in case it wasn't obvious)
Re: CP TRACE question....
Thanks, Rob and PSso I need to issue the TRACE command like so: CPU ALL CMD TRACE ... . . . . . . . . . correct? Rob van der Heij wrote: On Thu, Oct 8, 2009 at 9:44 PM, Dave Jones d...@vsoft-software.com wrote: Does this configuration have any impact on the ability of the TRACE command to trap machine operations, set breakpoints, etc.? Did you remember to use CPU ALL to activate PER for all CPUs (unless you know where to look for it) Rob -- Dave Jones V/Soft www.vsoft-software.com Houston, TX 281.578.7544
Re: CP TRACE question....
On Thu, Oct 8, 2009 at 5:14 PM, Dave Jones d...@vsoft-software.com wrote: Thanks, Rob and PSso I need to issue the TRACE command like so: CPU ALL CMD TRACE ... . . . . . . . . . correct? The CMD is optional, but sure.
Re: CP TRACE question....
Excellent, PS; thanks a lot. P S wrote: On Thu, Oct 8, 2009 at 4:46 PM, Rob van der Heij rvdh...@gmail.com wrote: Did you remember to use CPU ALL to activate PER for all CPUs (unless you know where to look for it) Good point: CPU ALL TRACE ... (in case it wasn't obvious) -- Dave Jones V/Soft www.vsoft-software.com Houston, TX 281.578.7544
Re: CP TRACE question....
On Thu, Oct 8, 2009 at 11:14 PM, Dave Jones d...@vsoft-software.com wrote: CPU ALL CMD TRACE ... . . . . . . . . . Sure, the CMD is probably optional unless the CP command would look like a CPU address... (not in your case) I did not want to go into the commands because you just should be ware that this is per cpu (no 00D intended). The CPU ALL is only for the CPUs you had at that time (and may not even include the quiesced ones, dunno). Your haircut may also be seriously impacted when you forget this when the trace hits. Like display the registers of the default CPU when you try to understand the reason for the program check (iirc the command after the CMD option on the TRACE command itself does go for the right one). When you issue the commands by hand, the CPU command can be used to point to another CPU for the unqualified commands. Rob
