Daniel Huenig
|
AW: SystemProfiler View "Why Running" not working for SMP traces
|
Daniel Huenig
10/07/2009 9:24 AM
post39506
|
AW: SystemProfiler View "Why Running" not working for SMP traces
Hi,
I think the problem occurs when your selected event is not a "Running". While backtracing, the next "Running" will be
regarded as corresponding, but it might be on the "wrong" CPU. In consequence, the entire detection goes amiss.
I'm uploading a sample kev on /home/harman_ftp/Generic/IDE/
Try selecting
Event, Time, CPU, Owner, Type, Data
158954, 861ms 661us, 2, procnto-smp-instr (1) Thread 17 (17), MsgReplyv Exit, ret_val 0
"Why running" will get you to
Event, Time, CPU, Owner, Type, Data
158948, 861ms 652us, 1, devb-mmcsd (6) Thread 9 (9), Running, pid 6 tid 9 priority 10 policy 2 partition 4 sched_flags 0
which is the most recent "Running" event, but not on the same CPU.
Thanks,
Daniel
>-----Ursprüngliche Nachricht-----
>Von: David Cummings [mailto:community-noreply@qnx.com]
>Gesendet: Mittwoch, 7. Oktober 2009 14:52
>An: general-ide
>Betreff: Re: SystemProfiler View "Why Running" not working for
>SMP traces
>
>Hi HP,
>
>I've run through some quick test cases of the Why Running view
>using SMP traces and I am seeing reasonable results. The Why
>Running view was implemented with support for SMP but perhaps
>it is not correctly implemented for the scenarios in your
>trace. Could you please provide some concrete examples of
>where the Why Running view is not providing reasonable information?
>
>Thanks,
>David
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post39497
>
>
*******************************************
Harman Becker Automotive Systems GmbH
Management Board: Dr. Klaus Blickle (Chairman), Dr. Udo Hüls, Michael Mauser
Chairman of the Supervisory Board: Ansgar Rempp | Domicile: Karlsbad |
Local Court Mannheim: Register No. 361395
*******************************************
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat
sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail
. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have
received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying,
disclosure or distribution of the contents in this e-mail is strictly forbidden.
*******************************************
|
|
|