From: Luben Tuikov <luben.tuikov@amd.com>
To: Andrey Grodzovsky <andrey.grodzovsky@amd.com>,
amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com, nirmodas@amd.com,
christian.koenig@amd.com, Dennis.Li@amd.com
Subject: Re: [PATCH v3 7/8] drm/amdgpu: Disable DPC for XGMI for now.
Date: Mon, 31 Aug 2020 17:09:48 -0400 [thread overview]
Message-ID: <7518f239-e1bf-f46d-fe88-8920c60ca25d@amd.com> (raw)
In-Reply-To: <1598889049-28321-8-git-send-email-andrey.grodzovsky@amd.com>
On 2020-08-31 11:50 a.m., Andrey Grodzovsky wrote:
> XGMI support is more complicated then single device support as
Typo: "then" --> "than".
> questions of synchronization between the device recovering from
> PCI error and other members of the hive is required.
Typo: "is" --> "are", as the subject of this long sentence changes
from "XGMI support" to "questions", which is plural: "questions ... _are_ required."
Regards,
Luben
> Leaving this for next round.
>
> Signed-off-by: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> index b31868a..fe720c2 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> @@ -4781,6 +4781,11 @@ pci_ers_result_t amdgpu_pci_error_detected(struct pci_dev *pdev, pci_channel_sta
>
> DRM_INFO("PCI error: detected callback, state(%d)!!\n", state);
>
> + if (adev->gmc.xgmi.num_physical_nodes > 1) {
> + DRM_WARN("No support for XGMI hive yet...");
> + return PCI_ERS_RESULT_DISCONNECT;
> + }
> +
> switch (state) {
> case pci_channel_io_normal:
> return PCI_ERS_RESULT_CAN_RECOVER;
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2020-08-31 21:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 15:50 [PATCH v3 0/8] Implement PCI Error Recovery on Navi12 Andrey Grodzovsky
2020-08-31 15:50 ` [PATCH v3 1/8] drm/amdgpu: Implement DPC recovery Andrey Grodzovsky
2020-08-31 20:28 ` Luben Tuikov
2020-08-31 20:47 ` Luben Tuikov
2020-08-31 15:50 ` [PATCH v3 2/8] drm/amdgpu: Avoid accessing HW when suspending SW state Andrey Grodzovsky
2020-08-31 15:50 ` [PATCH v3 3/8] drm/amdgpu: Block all job scheduling activity during DPC recovery Andrey Grodzovsky
2020-08-31 21:00 ` Luben Tuikov
2020-08-31 22:04 ` Andrey Grodzovsky
2020-08-31 15:50 ` [PATCH v3 4/8] drm/amdgpu: Fix SMU error failure Andrey Grodzovsky
2020-08-31 15:50 ` [PATCH v3 5/8] drm/amdgpu: Fix consecutive DPC recovery failures Andrey Grodzovsky
2020-08-31 21:05 ` Luben Tuikov
2020-08-31 15:50 ` [PATCH v3 6/8] drm/amdgpu: Trim amdgpu_pci_slot_reset by reusing code Andrey Grodzovsky
2020-08-31 15:50 ` [PATCH v3 7/8] drm/amdgpu: Disable DPC for XGMI for now Andrey Grodzovsky
2020-08-31 21:09 ` Luben Tuikov [this message]
2020-08-31 15:50 ` [PATCH v3 8/8] drm/amdgpu: Minor checkpatch fix Andrey Grodzovsky
2020-08-31 16:47 ` [PATCH v3 0/8] Implement PCI Error Recovery on Navi12 Nirmoy
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=7518f239-e1bf-f46d-fe88-8920c60ca25d@amd.com \
--to=luben.tuikov@amd.com \
--cc=Dennis.Li@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrey.grodzovsky@amd.com \
--cc=christian.koenig@amd.com \
--cc=nirmodas@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