hi group,

Is it possible to get call grah using remote call profiler for a builtin
driver(e.g pci based ATA device)

thanking you,
karthik

RE: remote call profiler by gspil

gspil
Sat Oct 02 13:08:11 CDT 2004

You can profile any code except the kernel. The only issue with profiling
drivers is that you may miss initial data that occurs between the time your
driver starts profiling and the time CECAP connects to the device if the
data buffers overflow.

In PB 5.0 you will need to add one of the following flags to the driver and
rebuild it. You can do this by either editing the sources file manually or
adding it via the PB UI by selecting "settings" on the ATA project in the
FileView, go to "general", select "custom variables" and add the flags.

The following flag allows you to profile the time spent inside calls:
WINCECALLCAP=1

The following flag allows you to profile the time spent calling out to
other calls:
WINCEFASTCAP=1

In 4.1 or 4.2 you have to add the following to your sources file and
rebuild:

! IF "$(_TGTCPUFAMILY)"=="x86"
CFLAGS=$(CFLAGS) /Gh
! ELSE
CFLAGS=$(CFLAGS) /callcap
! ENDIF


# Pick one depending of what type of profiling you want
CFLAGS=$(CFLAGS) /callcap
or
CFLAGS=$(CFLAGS) /fastcap


TARGETLIBS=$(TARGETLIBS)
$(_COMMONOAKROOT)\lib\$(_TGTCPU)\$(WINCEDEBUG)\cecap.lib

Gabriel Spil
IDE Dev Lead