Re: [Gems-users] patch PC / patch NPC message

[lyen@xxxxxxxxxxx]

Hi Vince:

  This message is printed out every time Opal's retirement check of
register values and control state disagrees with the values as indicated
by the in-order Simics execution.  Basically the first hex value is what
Opal thinks is the correct PC and NPC, and the actual correct PC and NPC
value pairs are the second hex values in the corresponding lines.

   I have noticed this happening alot when running Ocean, but the most
important stat to note is the final "Total percentage correct" as
printed out in the .opal file after the simulation ends.  If this
percentage is unusually low there may be something wrong with Opal.

   If you do not care for the patch messages simply comment them out,
since it is used for user-notification purposes.

   Luke


> Hello
>
> I am running GEMS simulating Solaris 9 and running the splash2 benchmark
> FFT on a 4-processor simulation.
>
> After the end of the benchmark run (which I am watching for with the
> simics "con0.break" command)  I get a never-ending stream of
>
>  patch  PC: 0x1082610 0x10825f8
>  patch  NPC: 0x1082614 0x1082610
>
> messages, creating a huge log file until I end it with control-C.
>
> What does this mean?  I went to the source code but it wasn't really
> obvious what this message is trying to convey...
>
> Vince
>
>
>
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>