stephane eranian writes: > Unless you tell me that pc->index is marked invalid (0) when the > event is not scheduled. I don't see how you can avoid reading > the wrong value. I am assuming that is the event is not scheduled > lock remains constant.
That's what happens; when pc->index == 0, the event is not scheduled and the current count is in pc->offset. > Assuming the event is active when you enter the loop and you > read a value. How to get the timing information to scale the > count? At present you'd have to do a read(). It wouldn't be hard to add fields to mmapped page to enable the user program to compute up-to-date timing information from the TSC (x86) or timebase (powerpc) value. We'll do that. Paul. ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ perfmon2-devel mailing list perfmon2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
