AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Kuehling, Felix" <Felix.Kuehling-5C7GfCeVMHo@public.gmane.org>
To: "Grodzovsky,
	Andrey" <Andrey.Grodzovsky-5C7GfCeVMHo@public.gmane.org>,
	"Koenig,
	Christian" <Christian.Koenig-5C7GfCeVMHo@public.gmane.org>,
	"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Cc: "alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
	<alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"Zhang, Hawking" <Hawking.Zhang-5C7GfCeVMHo@public.gmane.org>
Subject: Re: [PATCH 1/2] dmr/amdgpu: Avoid HW GPU reset for RAS.
Date: Thu, 29 Aug 2019 19:09:29 +0000	[thread overview]
Message-ID: <f5c745ba-da46-d2b3-92eb-7aa91e520b5c@amd.com> (raw)
In-Reply-To: <2763a85d-cfd7-bf80-5d8b-3590cf35e6d0-5C7GfCeVMHo@public.gmane.org>

On 2019-08-29 1:21 p.m., Grodzovsky, Andrey wrote:
> On 8/29/19 12:18 PM, Kuehling, Felix wrote:
>> On 2019-08-29 10:08 a.m., Grodzovsky, Andrey wrote:
>>> Agree, the placement of amdgpu_amdkfd_pre/post _reset in
>>> amdgpu_device_lock/unlock_adev is a bit wierd.
>>>
>> amdgpu_device_reset_sriov already calls amdgpu_amdkfd_pre/post_reset
>> itself while it has exclusive access to the GPU.
> So in that case amdgpu_amdkfd_pre/post_reset gets called twice - once
> from amdgpu_device_lock/unlock_adev and second time from
> amdgpu_device_reset_sriov, no ? Why is it ?

No, it's not called twice because the bare metal case has conditions if 
(!amdgpu_sriov_vf(adev)). If you don't move the 
amdgpu_amdkfd_pre/post_reset calls into a bare-metal-specific code-path 
(such as amdgpu_do_asic_reset), you'll need to keep those conditions.


>
>
>> It would make sense to
>> move the same calls into amdgpu_do_asic_reset for the bare-metal case.
>
> Problem is i am skipping amdgpu_do_asic_reset totally in this case as
> there is no HW reset here so i will just extract it from
> amdgpu_device_lock/unlock_adev

OK.

Regards,
   Felix


>
> Andrey
>
>
>> Regards,
>>      Felix
>>
>>
>>> Andrey
>>>
>>> On 8/29/19 10:06 AM, Koenig, Christian wrote:
>>>>> Felix advised that the way to stop all KFD activity is simply to NOT
>>>>> call amdgpu_amdkfd_post_reset so that why I added this. Do you mean you
>>>>> prefer amdgpu_amdkfd_post_reset to be outside of amdgpu_device_unlock_adev ?
>>>> Yes, exactly. It doesn't seems to be related to the unlock operation in
>>>> the first place, but rather only signals the KFD that the reset is
>>>> completed.
>>>>
>>>> Christian.
>>>>
>>> _______________________________________________
>>> 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

  parent reply	other threads:[~2019-08-29 19:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 20:00 [PATCH 1/2] dmr/amdgpu: Avoid HW GPU reset for RAS Andrey Grodzovsky
     [not found] ` <1567022426-6612-1-git-send-email-andrey.grodzovsky-5C7GfCeVMHo@public.gmane.org>
2019-08-28 20:00   ` [PATCH 2/2] dmr/amdgpu: Add system auto reboot to RAS Andrey Grodzovsky
     [not found]     ` <1567022426-6612-2-git-send-email-andrey.grodzovsky-5C7GfCeVMHo@public.gmane.org>
2019-08-29  7:33       ` Christian König
2019-08-28 21:18   ` [PATCH 1/2] dmr/amdgpu: Avoid HW GPU reset for RAS Kuehling, Felix
     [not found]     ` <5cf4dfa5-705c-9c10-8ca1-bf9cc21c1529-5C7GfCeVMHo@public.gmane.org>
2019-08-28 21:30       ` Grodzovsky, Andrey
2019-08-29  7:30   ` Christian König
     [not found]     ` <85798da5-a4f1-28d3-c80f-9f262743cac9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-08-29 14:03       ` Grodzovsky, Andrey
     [not found]         ` <9a46188b-b528-0d1f-8c3f-b6ce5b73649f-5C7GfCeVMHo@public.gmane.org>
2019-08-29 14:06           ` Koenig, Christian
     [not found]             ` <8c2b0bf3-47ff-ea3b-a682-7ec76240be4d-5C7GfCeVMHo@public.gmane.org>
2019-08-29 14:08               ` Grodzovsky, Andrey
     [not found]                 ` <1444ae5f-0997-d1ce-3e1e-23fea8822c88-5C7GfCeVMHo@public.gmane.org>
2019-08-29 16:18                   ` Kuehling, Felix
     [not found]                     ` <3a39a720-ae2d-0019-aecc-422f0e3f27bb-5C7GfCeVMHo@public.gmane.org>
2019-08-29 17:21                       ` Grodzovsky, Andrey
     [not found]                         ` <2763a85d-cfd7-bf80-5d8b-3590cf35e6d0-5C7GfCeVMHo@public.gmane.org>
2019-08-29 19:09                           ` Kuehling, Felix [this message]
2019-08-29  7:56   ` Zhou1, Tao
     [not found]     ` <MN2PR12MB305484B7D854243654C06EBDB0A20-rweVpJHSKTqnT25eLM+iUQdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-08-29 14:19       ` Grodzovsky, Andrey

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=f5c745ba-da46-d2b3-92eb-7aa91e520b5c@amd.com \
    --to=felix.kuehling-5c7gfcevmho@public.gmane.org \
    --cc=Andrey.Grodzovsky-5C7GfCeVMHo@public.gmane.org \
    --cc=Christian.Koenig-5C7GfCeVMHo@public.gmane.org \
    --cc=Hawking.Zhang-5C7GfCeVMHo@public.gmane.org \
    --cc=alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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