Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Mike Lothian <mike@fireburn.co.uk>,
	Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>
Cc: alexander.deucher@amd.com, intel-gfx@lists.freedesktop.org,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	matthew.auld@intel.com
Subject: Re: [Intel-gfx] [PATCH v12] drm/amdgpu: add drm buddy support to amdgpu
Date: Tue, 26 Apr 2022 18:36:12 +0200	[thread overview]
Message-ID: <c0facbf4-0e14-fde5-4334-499135a36f0c@amd.com> (raw)
In-Reply-To: <CAHbf0-H5uE4RtZwY0L8Wz0VG6QnU1+E3yhg3fDFVc3n__=nrNQ@mail.gmail.com>

Hi Mike,

sounds like somehow stitching together the SG table for PRIME doesn't 
work any more with this patch.

Can you try with P2P DMA disabled?

Apart from that can you take a look Arun?

Thanks,
Christian.

Am 26.04.22 um 17:29 schrieb Mike Lothian:
> Hi
>
> I'm having issues with this patch on my PRIME system and vulkan workloads
>
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fdrm%2Famd%2F-%2Fissues%2F1992&amp;data=05%7C01%7Cchristian.koenig%40amd.com%7Ce18d158769fc47b08ee708da27998e7e%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637865838441574170%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&amp;sdata=hQu67WrdUwZn6%2BdXziGz84nMGepI6%2FnlB8XFCFKCnpA%3D&amp;reserved=0
>
> Is there any chance you could take a look?
>
> Cheers
>
> Mike


  reply	other threads:[~2022-04-26 16:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  5:46 [Intel-gfx] [PATCH v12] drm/amdgpu: add drm buddy support to amdgpu Arunpravin Paneer Selvam
2022-04-07  6:10 ` Christian König
2022-04-07  6:22 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/amdgpu: add drm buddy support to amdgpu (rev3) Patchwork
2022-04-07 13:47 ` [Intel-gfx] [PATCH v12] drm/amdgpu: add drm buddy support to amdgpu Paul Menzel
2022-04-26 15:29 ` Mike Lothian
2022-04-26 16:36   ` Christian König [this message]
2022-04-27  5:26     ` Paneer Selvam, Arunpravin
2022-04-27 11:55     ` Mike Lothian
2022-05-02 15:11       ` Mike Lothian
2022-05-02 15:54         ` Arunpravin Paneer Selvam
2022-05-02 16:31           ` Mike Lothian
2022-05-16 12:40             ` Mike Lothian
2022-05-16 15:05               ` Alex Deucher
2022-05-28  7:43                 ` Paneer Selvam, Arunpravin
2022-05-28 23:52                   ` Mike Lothian
2022-06-23 11:15                     ` Mike Lothian

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=c0facbf4-0e14-fde5-4334-499135a36f0c@amd.com \
    --to=christian.koenig@amd.com \
    --cc=Arunpravin.PaneerSelvam@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=mike@fireburn.co.uk \
    /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