From: Arthur Marsh <arthur.marsh@internode.on.net>
To: "Arunpravin Paneer Selvam" <arunpravin.paneerselvam@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Dave Airlie" <airlied@gmail.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
daniel.vetter@ffwll.ch, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [git pull] drm fixes for 6.1-rc1
Date: Tue, 18 Oct 2022 11:58:06 +1030 [thread overview]
Message-ID: <EE5085BD-98AF-452E-9AE3-4EA81E2A55E1@internode.on.net> (raw)
In-Reply-To: <f3a5b249-84d8-9ba3-9977-3557c82a7850@amd.com>
Thanks Arunpravin, your patch applied to the 6.1-rc1 code built a kernel that loaded the amdgpu module on my pc with Cape Verde GPU card with no problems.
Regards,
Arthur.
On 18 October 2022 7:10:45 am ACDT, Arunpravin Paneer Selvam <arunpravin.paneerselvam@amd.com> wrote:
>Hi Christian,
>
>Looks like we have to exit the loop if there are no blocks to compare.
>May be that's why the function returns false.
>
>@Arthur Marsh Could you please test the attached patch.
>
>Thanks,
>Arun
>
>On 10/17/2022 1:39 PM, Christian König wrote:
>> Am 17.10.22 um 10:01 schrieb Dave Airlie:
>>> On Mon, 17 Oct 2022 at 17:07, Christian König <christian.koenig@amd.com> wrote:
>>>> Hi Arun,
>>>>
>>>> the hw generation doesn't matter. This error message here:
>>>>
>>>> amdgpu: Move buffer fallback to memcpy unavailable
>>>>
>>>> indicates that the detection of linear buffers still doesn't work as
>>>> expected or that we have a bug somewhere else.
>>>>
>>>> Maybe the limiting when SDMA moves are not available isn't working
>>>> correctly?
>>> It is a CAPE_VERDE, so maybe something with the SI UVD memory limitations?
>>
>> Yeah, good point. Could be that we try to move something into the UVD memory window and that something isn't allocated linearly.
>>
>> Arun can you trace the allocation and make sure that all kernel allocations have the CONTIGUOUS flag set?
>>
>> Thanks,
>> Christian.
>>
>>>
>>> Dave.
>>
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
prev parent reply other threads:[~2022-10-18 1:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 0:29 [git pull] drm fixes for 6.1-rc1 Dave Airlie
2022-10-14 5:04 ` Linus Torvalds
2022-10-14 5:07 ` pr-tracker-bot
2022-10-16 8:08 ` Arthur Marsh
2022-10-16 21:44 ` Dave Airlie
2022-10-17 1:13 ` Arthur Marsh
2022-10-17 6:20 ` Christian König
2022-10-17 6:54 ` Arunpravin Paneer Selvam
2022-10-17 7:07 ` Christian König
2022-10-17 8:01 ` Dave Airlie
2022-10-17 8:09 ` Christian König
2022-10-17 20:40 ` Arunpravin Paneer Selvam
2022-10-18 1:28 ` Arthur Marsh [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=EE5085BD-98AF-452E-9AE3-4EA81E2A55E1@internode.on.net \
--to=arthur.marsh@internode.on.net \
--cc=Alexander.Deucher@amd.com \
--cc=airlied@gmail.com \
--cc=arunpravin.paneerselvam@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).