From: Mike Lothian <mike@fireburn.co.uk>
To: "Christian König" <christian.koenig@amd.com>
Cc: dri-devel@lists.freedesktop.org,
Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>,
intel-gfx@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
matthew.auld@intel.com, alexander.deucher@amd.com
Subject: Re: [PATCH v12] drm/amdgpu: add drm buddy support to amdgpu
Date: Wed, 27 Apr 2022 12:55:19 +0100 [thread overview]
Message-ID: <CAHbf0-FMqAA3vWx_uRDYG_vr=FX+tFoLAL6BZLDe5upv7KJqrg@mail.gmail.com> (raw)
In-Reply-To: <c0facbf4-0e14-fde5-4334-499135a36f0c@amd.com>
On Tue, 26 Apr 2022 at 17:36, Christian König <christian.koenig@amd.com> wrote:
>
> 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?
-CONFIG_PCI_P2PDMA=y
+# CONFIG_PCI_P2PDMA is not set
If that's what you're meaning, then there's no difference, I'll upload
my dmesg to the gitlab issue
>
> Apart from that can you take a look Arun?
>
> Thanks,
> Christian.
WARNING: multiple messages have this Message-ID (diff)
From: Mike Lothian <mike@fireburn.co.uk>
To: "Christian König" <christian.koenig@amd.com>
Cc: dri-devel@lists.freedesktop.org,
Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>,
intel-gfx@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
matthew.auld@intel.com, alexander.deucher@amd.com
Subject: Re: [Intel-gfx] [PATCH v12] drm/amdgpu: add drm buddy support to amdgpu
Date: Wed, 27 Apr 2022 12:55:19 +0100 [thread overview]
Message-ID: <CAHbf0-FMqAA3vWx_uRDYG_vr=FX+tFoLAL6BZLDe5upv7KJqrg@mail.gmail.com> (raw)
In-Reply-To: <c0facbf4-0e14-fde5-4334-499135a36f0c@amd.com>
On Tue, 26 Apr 2022 at 17:36, Christian König <christian.koenig@amd.com> wrote:
>
> 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?
-CONFIG_PCI_P2PDMA=y
+# CONFIG_PCI_P2PDMA is not set
If that's what you're meaning, then there's no difference, I'll upload
my dmesg to the gitlab issue
>
> Apart from that can you take a look Arun?
>
> Thanks,
> Christian.
next prev parent reply other threads:[~2022-04-27 11:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 5:46 [PATCH v12] drm/amdgpu: add drm buddy support to amdgpu Arunpravin Paneer Selvam
2022-04-07 5:46 ` Arunpravin Paneer Selvam
2022-04-07 5:46 ` [Intel-gfx] " Arunpravin Paneer Selvam
2022-04-07 6:10 ` Christian König
2022-04-07 6:10 ` Christian König
2022-04-07 6:10 ` [Intel-gfx] " 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 ` [PATCH v12] drm/amdgpu: add drm buddy support to amdgpu Paul Menzel
2022-04-07 13:47 ` Paul Menzel
2022-04-07 13:47 ` [Intel-gfx] " Paul Menzel
2022-04-26 15:29 ` Mike Lothian
2022-04-26 15:29 ` [Intel-gfx] " Mike Lothian
2022-04-26 16:36 ` Christian König
2022-04-26 16:36 ` [Intel-gfx] " Christian König
2022-04-27 5:26 ` Paneer Selvam, Arunpravin
2022-04-27 5:26 ` [Intel-gfx] " Paneer Selvam, Arunpravin
2022-04-27 11:55 ` Mike Lothian [this message]
2022-04-27 11:55 ` Mike Lothian
2022-05-02 15:11 ` Mike Lothian
2022-05-02 15:11 ` [Intel-gfx] " Mike Lothian
2022-05-02 15:54 ` Arunpravin Paneer Selvam
2022-05-02 15:54 ` [Intel-gfx] " Arunpravin Paneer Selvam
2022-05-02 16:31 ` Mike Lothian
2022-05-02 16:31 ` [Intel-gfx] " Mike Lothian
2022-05-16 12:40 ` Mike Lothian
2022-05-16 12:40 ` [Intel-gfx] " Mike Lothian
2022-05-16 15:05 ` Alex Deucher
2022-05-16 15:05 ` [Intel-gfx] " Alex Deucher
2022-05-28 7:43 ` Paneer Selvam, Arunpravin
2022-05-28 7:43 ` [Intel-gfx] " Paneer Selvam, Arunpravin
2022-05-28 23:52 ` Mike Lothian
2022-05-28 23:52 ` Mike Lothian
2022-05-28 23:52 ` [Intel-gfx] " Mike Lothian
2022-05-30 6:02 ` Christian König
2022-05-30 6:02 ` Christian König
2022-06-23 11:15 ` Mike Lothian
2022-06-23 11:15 ` Mike Lothian
2022-06-23 11:15 ` [Intel-gfx] " 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='CAHbf0-FMqAA3vWx_uRDYG_vr=FX+tFoLAL6BZLDe5upv7KJqrg@mail.gmail.com' \
--to=mike@fireburn.co.uk \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.