AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: David Rosca <david.rosca@amd.com>,
	Philipp Stanner <phasta@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>,
	Matthew Brost <matthew.brost@intel.com>
Cc: amd-gfx@lists.freedesktop.org,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"Prosyak, Vitaly" <Vitaly.Prosyak@amd.com>
Subject: Re: [PATCH] drm/sched: Avoid killing entity last used by parent on child SIGKILL
Date: Fri, 10 Oct 2025 14:28:12 +0200	[thread overview]
Message-ID: <4cc2b216-e778-4b4e-bd13-01af0ded5427@amd.com> (raw)
In-Reply-To: <14de5473-534c-4294-bb1d-41d1a43fb46d@amd.com>

David any objections that I take this patch and make the necessary modifications?

People are pinging me about the problem.

Regards,
Christian.

On 09.10.25 17:04, Christian König wrote:
> FYI
> 
> On 09.10.25 09:01, Christian König wrote:
>> On 02.10.25 17:05, David Rosca wrote:
>>> drm_sched_entity_flush should only kill the entity if the current
>>> process is the last user of the entity. The last_user is only set
>>> when adding new job, so entities that had no jobs submitted to them
>>> have NULL last_user and would always be killed.
>>> Another issue is setting last_user to NULL from drm_sched_entity_flush,
>>> which causes subsequent calls to kill the entity.
>>>
>>> Signed-off-by: David Rosca <david.rosca@amd.com>
>>> Fixes: 51564e9f06f0 ("drm/amdgpu: Avoid extra evict-restore process.")
>>
>> Good catch, but in general please CC the relevant maintainers and mailing lists for scheduler patches.
>>
>>> ---
>>>  drivers/gpu/drm/scheduler/sched_entity.c | 5 ++---
>>>  1 file changed, 2 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/scheduler/sched_entity.c b/drivers/gpu/drm/scheduler/sched_entity.c
>>> index 8867b95ab089..a325e4a59990 100644
>>> --- a/drivers/gpu/drm/scheduler/sched_entity.c
>>> +++ b/drivers/gpu/drm/scheduler/sched_entity.c
>>> @@ -70,6 +70,7 @@ int drm_sched_entity_init(struct drm_sched_entity *entity,
>>>  	entity->guilty = guilty;
>>>  	entity->num_sched_list = num_sched_list;
>>>  	entity->priority = priority;
>>> +	entity->last_user = current->group_leader;
>>>  	/*
>>>  	 * It's perfectly valid to initialize an entity without having a valid
>>>  	 * scheduler attached. It's just not valid to use the scheduler before it
>>> @@ -278,7 +279,6 @@ static void drm_sched_entity_kill(struct drm_sched_entity *entity)
>>>  long drm_sched_entity_flush(struct drm_sched_entity *entity, long timeout)
>>>  {
>>>  	struct drm_gpu_scheduler *sched;
>>> -	struct task_struct *last_user;
>>>  	long ret = timeout;
>>>  
>>>  	if (!entity->rq)
>>> @@ -301,8 +301,7 @@ long drm_sched_entity_flush(struct drm_sched_entity *entity, long timeout)
>>>  	}
>>>  
>>>  	/* For killed process disable any more IBs enqueue right now */
>>> -	last_user = cmpxchg(&entity->last_user, current->group_leader, NULL);
>>> -	if ((!last_user || last_user == current->group_leader) &&
>>> +	if (entity->last_user == current->group_leader &&
>>
>> You still need the cmpxchg() here or otherwise drm_sched_entity_kill() would run multiple times.
>>
>> Regards,
>> Christian.
>>
>>>  	    (current->flags & PF_EXITING) && (current->exit_code == SIGKILL))
>>>  		drm_sched_entity_kill(entity);
>>>  
>>
> 


  reply	other threads:[~2025-10-10 12:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 15:05 [PATCH] drm/sched: Avoid killing entity last used by parent on child SIGKILL David Rosca
2025-10-09  7:01 ` Christian König
2025-10-09 15:04   ` Christian König
2025-10-10 12:28     ` Christian König [this message]
2025-10-10 12:48       ` David Rosca

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=4cc2b216-e778-4b4e-bd13-01af0ded5427@amd.com \
    --to=christian.koenig@amd.com \
    --cc=Vitaly.Prosyak@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dakr@kernel.org \
    --cc=david.rosca@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=phasta@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox