Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] A question regarding starpu_fxt_autostart_profiling function

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] A question regarding starpu_fxt_autostart_profiling function


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@inria.fr>
  • To: Mirko Myllykoski <mirkom@cs.umu.se>
  • Cc: Starpu Devel <starpu-devel@lists.gforge.inria.fr>
  • Subject: Re: [Starpu-devel] A question regarding starpu_fxt_autostart_profiling function
  • Date: Tue, 29 Jan 2019 10:46:42 +0100
  • List-archive: <http://lists.gforge.inria.fr/pipermail/starpu-devel/>
  • List-id: "Developers list. For discussion of new features, code changes, etc." <starpu-devel.lists.gforge.inria.fr>
  • Organization: I am not organized

Mirko Myllykoski, le mar. 29 janv. 2019 10:24:36 +0100, a ecrit:
> I have situation where I am calling the starpu_init and starpu_shutdown
> functions several times. I would like to enable FxT traces during one of
> these init-shutdown pairs.
>
> I believe that the starpu_fxt_autostart_profiling function should do the
> trick:
>
> starpu_fxt_autostart_profiling(0);
> starpu_init(...);
> this_should_not_generate_traces();
> starpu_shutdown();
>
> starpu_fxt_autostart_profiling(1);
> starpu_init(...);
> this_should_generate_traces();
> starpu_shutdown();
>
> starpu_fxt_autostart_profiling(0);
> starpu_init(...);
> this_should_not_generate_traces();
> starpu_shutdown();
>
> Is this the correct way to use the function?

That should probably be it yes.

> The problems is that the last init-shutdown pair seems to overwrite the
> traces from the middle one.

I guess we just haven't taken care of fixing that use case yet.

Samuel




Archives gérées par MHonArc 2.6.19+.

Haut de le page