From: Luben Tuikov <luben.tuikov@amd.com>
To: Felix Kuehling <felix.kuehling@amd.com>,
Kent Russell <kent.russell@amd.com>,
amd-gfx@lists.freedesktop.org
Cc: Mukul Joshi <Mukul.Joshi@amd.com>
Subject: Re: [PATCH 3/3] drm/amdgpu: Implement bad_page_threshold = -2 case
Date: Wed, 20 Oct 2021 18:01:01 -0400 [thread overview]
Message-ID: <311fd85f-b3ab-377f-c98b-858b3afa6af3@amd.com> (raw)
In-Reply-To: <42f538e2-22b7-7a74-7212-a6063694164b@amd.com>
On 2021-10-20 17:54, Felix Kuehling wrote:
> On 2021-10-20 12:35 p.m., Kent Russell wrote:
>> If the bad_page_threshold kernel parameter is set to -2,
>> continue to post the GPU. Print a warning to dmesg that this action has
>> been done, and that page retirement will obviously not work for said GPU
> I'd squash patch 2 and 3. The squashed patch is
>
> Acked-by: Felix Kuehling <Felix.Kuehling@amd.com>
I was just thinking the same thing. Keep the title and text of patch 2 and add the description of 3 to 2. With that done:
Reviewed-by: Luben Tuikov <luben.tuikov@amd.com>
Regards,
Luben
>
>
>> Cc: Luben Tuikov <luben.tuikov@amd.com>
>> Cc: Mukul Joshi <Mukul.Joshi@amd.com>
>> Signed-off-by: Kent Russell <kent.russell@amd.com>
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_ras_eeprom.c | 13 +++++++++----
>> 1 file changed, 9 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ras_eeprom.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ras_eeprom.c
>> index 1ede0f0d6f55..31852330c1db 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ras_eeprom.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ras_eeprom.c
>> @@ -1115,11 +1115,16 @@ int amdgpu_ras_eeprom_init(struct amdgpu_ras_eeprom_control *control,
>> res = amdgpu_ras_eeprom_correct_header_tag(control,
>> RAS_TABLE_HDR_VAL);
>> } else {
>> - *exceed_err_limit = true;
>> - dev_err(adev->dev,
>> - "RAS records:%d exceed threshold:%d, "
>> - "GPU will not be initialized. Replace this GPU or increase the threshold",
>> + dev_err(adev->dev, "RAS records:%d exceed threshold:%d",
>> control->ras_num_recs, ras->bad_page_cnt_threshold);
>> + if (amdgpu_bad_page_threshold == -2) {
>> + dev_warn(adev->dev, "GPU will be initialized due to bad_page_threshold = -2.");
>> + dev_warn(adev->dev, "Page retirement will not work for this GPU in this state.");
>> + res = 0;
>> + } else {
>> + *exceed_err_limit = true;
>> + dev_err(adev->dev, "GPU will not be initialized. Replace this GPU or increase the threshold.");
>> + }
>> }
>> } else {
>> DRM_INFO("Creating a new EEPROM table");
next prev parent reply other threads:[~2021-10-20 22:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 16:35 [PATCH 1/3] drm/amdgpu: Warn when bad pages approaches 90% threshold Kent Russell
2021-10-20 16:35 ` [PATCH 2/3] drm/amdgpu: Add kernel parameter support for ignoring bad page threshold Kent Russell
2021-10-20 16:35 ` [PATCH 3/3] drm/amdgpu: Implement bad_page_threshold = -2 case Kent Russell
2021-10-20 21:54 ` Felix Kuehling
2021-10-20 22:01 ` Luben Tuikov [this message]
2021-10-21 13:57 ` Russell, Kent
2021-10-21 5:24 ` Lazar, Lijo
2021-10-21 13:56 ` Russell, Kent
2021-10-22 11:26 ` Lazar, Lijo
2021-10-20 21:47 ` [PATCH 1/3] drm/amdgpu: Warn when bad pages approaches 90% threshold Luben Tuikov
2021-10-21 14:04 ` Russell, Kent
2021-10-20 21:50 ` Felix Kuehling
2021-10-20 22:09 ` Luben Tuikov
2021-10-20 22:31 ` Felix Kuehling
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=311fd85f-b3ab-377f-c98b-858b3afa6af3@amd.com \
--to=luben.tuikov@amd.com \
--cc=Mukul.Joshi@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=felix.kuehling@amd.com \
--cc=kent.russell@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox