All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Kuehling <felix.kuehling@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>, Smith John <ls.cat.kth@gmail.com>
Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: [amdgpu] Compute kernels still run when the host process exit?
Date: Tue, 6 Apr 2021 11:35:39 -0400	[thread overview]
Message-ID: <af27e67f-24c7-3bc9-ef2f-12aeecbe11b2@amd.com> (raw)
In-Reply-To: <CADnq5_NF6=_cDEW8gxrbEd38EAxfh0y9je9+F7fXKV1Eojdqqg@mail.gmail.com>

Am 2021-04-01 um 2:22 p.m. schrieb Alex Deucher:
> On Thu, Apr 1, 2021 at 10:08 AM Smith John <ls.cat.kth@gmail.com> wrote:
>> Hi, when I killed an OpenCL host process, the kernels it launched were not terminated, and still run.
>>
>> My OpenCL runtime is AMDGPU-PRO 20.20. OS Ubuntu 18.04.5 with  Linux Kernel 5.4.53
>>
>> I was wondering if it was a bug or the driver did not implement this "watchdog" mechanism.
> In general, once you issue work on the GPU it has to run to
> completion.  It is not stopped if the application that issued it goes
> away.

If this is using KFD, we destroy user mode queues and free all the
process' memory at process termination. Because we support CWSR, we can
interrupt running shaders. Is this using the legacy OpenCL?

Regards,
  Felix


>
> Alex
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  reply	other threads:[~2021-04-06 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 14:07 [amdgpu] Compute kernels still run when the host process exit? Smith John
2021-04-01 18:22 ` Alex Deucher
2021-04-06 15:35   ` Felix Kuehling [this message]
2021-04-07  9:36   ` Christian König

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=af27e67f-24c7-3bc9-ef2f-12aeecbe11b2@amd.com \
    --to=felix.kuehling@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=ls.cat.kth@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.