From: "Christian König" <ckoenig.leichtzumerken-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Trigger Huang <Trigger.Huang-5C7GfCeVMHo@public.gmane.org>,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/amdgpu: skip ring soft reset on SR-IOV VF
Date: Wed, 14 Nov 2018 11:24:05 +0100 [thread overview]
Message-ID: <af3c6113-4f06-2323-dace-2cee260bd9de@gmail.com> (raw)
In-Reply-To: <1542183804-3021-1-git-send-email-Trigger.Huang-5C7GfCeVMHo@public.gmane.org>
Am 14.11.18 um 09:23 schrieb Trigger Huang:
> When TDR happened on SR-IOV VF, the host Hypervisor may has already
> done the VF FLR, then, the re-initialization flow in KMD is a must.
> The same logic is in amdgpu_device_ip_check_soft_reset, too
NAK, this is only called in the timeout code path and not when the
Hypervisor signals a FLR.
Christian.
>
> Signed-off-by: Trigger Huang <Trigger.Huang@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c
> index 5b75bdc..14bd67a 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c
> @@ -397,6 +397,9 @@ bool amdgpu_ring_soft_recovery(struct amdgpu_ring *ring, unsigned int vmid,
> {
> ktime_t deadline = ktime_add_us(ktime_get(), 10000);
>
> + if (amdgpu_sriov_vf(ring->adev))
> + return false;
> +
> if (!ring->funcs->soft_recovery)
> return false;
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2018-11-14 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 8:23 [PATCH] drm/amdgpu: skip ring soft reset on SR-IOV VF Trigger Huang
[not found] ` <1542183804-3021-1-git-send-email-Trigger.Huang-5C7GfCeVMHo@public.gmane.org>
2018-11-14 10:24 ` Christian König [this message]
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=af3c6113-4f06-2323-dace-2cee260bd9de@gmail.com \
--to=ckoenig.leichtzumerken-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=Trigger.Huang-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=christian.koenig-5C7GfCeVMHo@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