Bootviz provides information about the time spent by a driver in
initializing its device. My guess is that the profiling done here is similar
to most other profiling patterns, viz., sampling the eip at regular
intervals and then checking address against module load address. Am I
correct?
The reason I m asking this is because I cross checked the %cpu utuilization
of my driver using Bootviz and VTune and they are ridiculously different,
something like Bootviz saying 1.3 (s) and VTune (5.0 though)saying 0.13
(s). Am I missing something here?
thanks
banks
To answer my own naive question ( should have read the docs first ):
Looks like the driver delay is the start and end time for the power IRP.
Thats no good, what about preemption? Disk reads are totally suspect on S3
resume because of the spin up time. So say a driver queues a disk read
request ahead of me and that hogs up the time. That time willbe added to my
driver too, or surely I am missing a fundamental part here?
thanks
banks
“bank kus” wrote in message news:xxxxx@ntdev…
> Bootviz provides information about the time spent by a driver in
> initializing its device. My guess is that the profiling done here is
> similar to most other profiling patterns, viz., sampling the eip at
> regular intervals and then checking address against module load address.
> Am I correct?
>
> The reason I m asking this is because I cross checked the %cpu
> utuilization of my driver using Bootviz and VTune and they are
> ridiculously different, something like Bootviz saying 1.3 (s) and VTune
> (5.0 though)saying 0.13 (s). Am I missing something here?
>
> thanks
> banks
>
>
>