AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Kuehling <felix.kuehling@amd.com>
To: Ramesh Errabolu <Ramesh.Errabolu@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/amdgpu: Inform if PCIe based P2P links are not available
Date: Wed, 6 Nov 2024 18:26:59 -0500	[thread overview]
Message-ID: <0150ce95-709a-4a25-a376-c82b2b312ca4@amd.com> (raw)
In-Reply-To: <20241106225429.347179-1-Ramesh.Errabolu@amd.com>

On 2024-11-06 17:54, Ramesh Errabolu wrote:
> Raise an info message in kernel log if PCIe root complex
> determines that a AMD GPU device D<i> cannot have P2P
> communication with another AMD GPU device D<j>
> 
> Signed-off-by: Ramesh Errabolu <Ramesh.Errabolu@amd.com>
> ---
>  drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> index 230c24638a34..76182d5c719d 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> @@ -6222,6 +6222,9 @@ bool amdgpu_device_is_peer_accessible(struct amdgpu_device *adev,
>  	bool p2p_access =
>  		!adev->gmc.xgmi.connected_to_cpu &&
>  		!(pci_p2pdma_distance(adev->pdev, peer_adev->dev, false) < 0);
> +	if (!p2p_access)
> +		dev_info(adev->dev, "has no link with Peer device: %s\n",
> +			pci_name(peer_adev->pdev));

Please clarify the message to say "PCIe P2P access from peer device %s is not supported by the chipset". And "peer" should not be capitalized. With that fixed, the patch is

Reviewed-by: Felix Kuehling <felix.kuehling@amd.com>

>  
>  	bool is_large_bar = adev->gmc.visible_vram_size &&
>  		adev->gmc.real_vram_size == adev->gmc.visible_vram_size;

      reply	other threads:[~2024-11-06 23:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06 22:54 [PATCH v3] drm/amdgpu: Inform if PCIe based P2P links are not available Ramesh Errabolu
2024-11-06 23:26 ` Felix Kuehling [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=0150ce95-709a-4a25-a376-c82b2b312ca4@amd.com \
    --to=felix.kuehling@amd.com \
    --cc=Ramesh.Errabolu@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