Forums - profiling on CDSP also create client on ADSP

1 post / 0 new
or Register
profiling on CDSP also create client on ADSP
lanxjian
Join Date: 7 Apr 22
Posts: 1
Posted: Thu, 2022-04-07 06:13
Top

Hi,

When I run " profiling -f noop -d 3 -n 1", I checked logs, not only CDSP client is created,  it also creates a client for ADSP, why would it happen?

Line 5: Jan 01 02:04:33.616                  qvm.516159..0                 slog   1234  [vdev-fastrpc-handler.c:59] virt_fastrpc_init: domain:3 pd:1 client:0 pid:798 tid:798 attrs:0x0
Line 80: Jan 01 02:04:33.639                  qvm.516159..0                 slog   1234  [vdev-fastrpc-handler.c:80] virt_fastrpc_init: domain:3 pd:1 client:0 pid:798 tid:798 ret:0
Line 1324: Jan 01 02:04:33.700                  qvm.516159..0                 slog   1234  [vdev-fastrpc-handler.c:59] virt_fastrpc_init: domain:0 pd:1 client:0 pid:798 tid:798 attrs:0x0
Line 1401: Jan 01 02:04:33.728                  qvm.516159..0                 slog   1234  [vdev-fastrpc-handler.c:80] virt_fastrpc_init: domain:0 pd:1 client:0 pid:798 tid:798 ret:0
Line 1682: Jan 01 02:04:33.736                  qvm.516159..0                 slog   1234  [vdev-fastrpc-handler.c:92] virt_fastrpc_deinit: domain:0 client:0 pid:798 tid:798
Line 1705: Jan 01 02:04:33.741                  qvm.516159..0                 slog   1234  [vdev-fastrpc-handler.c:97] virt_fastrpc_deinit: domain:0 client:0 pid:798 tid:798 ret:0
Line 1758: Jan 01 02:04:33.754                  qvm.516159..0                 slog   1234  [vdev-fastrpc-handler.c:92] virt_fastrpc_deinit: domain:3 client:0 pid:798 tid:798
Line 1782: Jan 01 02:04:33.758                  qvm.516159..0                 slog   1234  [vdev-fastrpc-handler.c:97] virt_fastrpc_deinit: domain:3 client:0 pid:798 tid:798 ret:0
 Full log is saved in \\lanxjian-gv\workspace2\tools\Hexagon_SDK\hexagon-sdk-4.2.0\examples\profiling\profiling_CDSP.txt
 

I tried "profiling -f noop -d 0 -n 1", it only creates a client on ADSP.

version : Hexagon SDK 4.2.0

  • Up0
  • Down0

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.