AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Kuehling <felix.kuehling@amd.com>
To: Chengming Gui <Jack.Gui@amd.com>,
	amd-gfx@lists.freedesktop.org, Alexander.Deucher@amd.com
Cc: Tao.Zhou1@amd.com, Ray.Huang@amd.com, Guchun.Chen@amd.com,
	Hawking.Zhang@amd.com
Subject: Re: [PATCH v2] drm/amd/amdgpu: set the default value of noretry to 1 for some dGPUs
Date: Tue, 13 Oct 2020 11:32:08 -0400	[thread overview]
Message-ID: <63ca8d8a-3c0d-7512-e5d8-acb21368345a@amd.com> (raw)
In-Reply-To: <20201013151348.4382-1-Jack.Gui@amd.com>

Do you have more details about those test failures. In theory that test
should pass with noretry=0. If it fails, I'd rather look into the
problem than hiding it with a workaround.

Regards,
  Felix

Am 2020-10-13 um 11:13 a.m. schrieb Chengming Gui:
> noretry = 0 cause some dGPU's kfd page fault tests fail,
> so set noretry to 1 for these special ASICs:
> vega20/navi10/navi14/ARCTURUS
>
> v2:merge raven and default case due to the same setting
>
> Signed-off-by: Chengming Gui <Jack.Gui@amd.com>
> Change-Id: I3be70f463a49b0cd5c56456431d6c2cb98b13872
> ---
>  drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c | 24 ++++++++++++++++--------
>  1 file changed, 16 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c
> index 36604d751d62..3b7b9a5e9749 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c
> @@ -425,20 +425,28 @@ void amdgpu_gmc_noretry_set(struct amdgpu_device *adev)
>  	struct amdgpu_gmc *gmc = &adev->gmc;
>  
>  	switch (adev->asic_type) {
> -	case CHIP_RAVEN:
> -		/* Raven currently has issues with noretry
> -		 * regardless of what we decide for other
> -		 * asics, we should leave raven with
> -		 * noretry = 0 until we root cause the
> -		 * issues.
> +	case CHIP_VEGA20:
> +	case CHIP_NAVI10:
> +	case CHIP_NAVI14:
> +	case CHIP_ARCTURUS:
> +		/*
> +		 * noretry = 0 will cause kfd page fault tests fail
> +		 * for some ASICs, so set default to 1 for these ASICs.
>  		 */
>  		if (amdgpu_noretry == -1)
> -			gmc->noretry = 0;
> +			gmc->noretry = 1;
>  		else
>  			gmc->noretry = amdgpu_noretry;
>  		break;
> +	case CHIP_RAVEN:
>  	default:
> -		/* default this to 0 for now, but we may want
> +		/* Raven currently has issues with noretry
> +		 * regardless of what we decide for other
> +		 * asics, we should leave raven with
> +		 * noretry = 0 until we root cause the
> +		 * issues.
> +		 *
> +		 * default this to 0 for now, but we may want
>  		 * to change this in the future for certain
>  		 * GPUs as it can increase performance in
>  		 * certain cases.
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

           reply	other threads:[~2020-10-13 15:32 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20201013151348.4382-1-Jack.Gui@amd.com>]

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=63ca8d8a-3c0d-7512-e5d8-acb21368345a@amd.com \
    --to=felix.kuehling@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Guchun.Chen@amd.com \
    --cc=Hawking.Zhang@amd.com \
    --cc=Jack.Gui@amd.com \
    --cc=Ray.Huang@amd.com \
    --cc=Tao.Zhou1@amd.com \
    --cc=amd-gfx@lists.freedesktop.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