dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: "Chen Li" <chenli@uniontech.com>,
	"Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 2/2] radeon: use memcpy_to/fromio for UVD fw upload
Date: Fri, 4 Jun 2021 10:31:28 +0200	[thread overview]
Message-ID: <7bf7e03a-4733-bf66-4a81-ac712582539c@amd.com> (raw)
In-Reply-To: <875yyuc9tt.wl-chenli@uniontech.com>



Am 04.06.21 um 10:28 schrieb Chen Li:
> On Fri, 04 Jun 2021 16:08:26 +0800,
> Christian König wrote:
>>
>>
>> Am 04.06.21 um 09:53 schrieb Chen Li:
>>> I met a gpu addr bug recently and the kernel log
>>> tells me the pc is memcpy/memset and link register is
>>> radeon_uvd_resume.
>>>
>>> As we know, in some architectures, optimized memcpy/memset
>>> may not work well on device memory. Trival memcpy_toio/memset_io
>>> can fix this problem.
>>>
>>> BTW, amdgpu has already done it in:
>>> commit ba0b2275a678 ("drm/amdgpu: use memcpy_to/fromio for UVD fw upload"),
>>> that's why it has no this issue on the same gpu and platform.
>>>
>>> Signed-off-by: Chen Li <chenli@uniontech.com>
>>> ---
>>>    drivers/gpu/drm/radeon/radeon_uvd.c | 6 ++++--
>>>    1 file changed, 4 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/radeon/radeon_uvd.c b/drivers/gpu/drm/radeon/radeon_uvd.c
>>> index 85a1f2c31749..55abf9a9623b 100644
>>> --- a/drivers/gpu/drm/radeon/radeon_uvd.c
>>> +++ b/drivers/gpu/drm/radeon/radeon_uvd.c
>>> @@ -288,7 +288,9 @@ int radeon_uvd_resume(struct radeon_device *rdev)
>>>    	if (rdev->uvd.vcpu_bo == NULL)
>>>    		return -EINVAL;
>>>    -	memcpy(rdev->uvd.cpu_addr, rdev->uvd_fw->data, rdev->uvd_fw->size);
>>> +	memcpy_toio((void __iomem *)rdev->uvd.cpu_addr,
>>> +				rdev->uvd_fw->data,
>>> +				rdev->uvd_fw->size);
>> The coding style still looks wrong here, e.g. it is indented to far to the right
>> and data/size can be on one line.
> It's really werid that the patch before being replyed has not this coding style issue and do always indent the same with previous memcpy(in all of v1, v2 and v3),
> you can check at https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.kernel.org%2Fproject%2Fdri-devel%2Fpatch%2F87im2ufhyz.wl-chenli%40uniontech.com%2F&amp;data=04%7C01%7Cchristian.koenig%40amd.com%7C3faf061c19b54a68e72508d92732cd5e%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637583921450406148%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=b0726ORwyeLQsKVzqjfZEMaU4Vi543szpFYoHekPMIU%3D&amp;reserved=0 Cannot figure out what happened, sorry.
>
> I'll take merge them in single line in the next series, thanks.

It's not much of an issue, just make sure that checkpatch.pl doesn't 
complain.

Christian.

>> Apart from that the patch is Reviewed-by: Christian König
>> <christian.koenig@amd.com>
>>
>> Regards,
>> Christian.
>>
>>>      	size = radeon_bo_size(rdev->uvd.vcpu_bo);
>>>    	size -= rdev->uvd_fw->size;
>>> @@ -296,7 +298,7 @@ int radeon_uvd_resume(struct radeon_device *rdev)
>>>    	ptr = rdev->uvd.cpu_addr;
>>>    	ptr += rdev->uvd_fw->size;
>>>    -	memset(ptr, 0, size);
>>> +	memset_io((void __iomem *)ptr, 0, size);
>>>      	return 0;
>>>    }
>>
>>
>


  reply	other threads:[~2021-06-04  8:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  5:35 [PATCH] radeon: use memcpy_to/fromio for UVD fw upload Chen Li
2021-06-03 19:21 ` Alex Deucher
2021-06-04  3:00   ` [PATCH v2 0/2] " Chen Li
2021-06-04  3:02 ` [PATCH v2 1/2] radeon: fix coding issues reported from sparse Chen Li
2021-06-04  7:14   ` Christian König
2021-06-04  3:04 ` [PATCH v2 2/2] radeon: use memcpy_to/fromio for UVD fw upload Chen Li
2021-06-04  7:18   ` Christian König
2021-06-04  7:50     ` [PATCH v3 0/2] " Chen Li
2021-06-04  7:52     ` [PATCH v3 1/2] radeon: fix coding issues reported from sparse Chen Li
2021-06-04  7:53     ` [PATCH v3 2/2] radeon: use memcpy_to/fromio for UVD fw upload Chen Li
2021-06-04  8:08       ` Christian König
2021-06-04  8:28         ` Chen Li
2021-06-04  8:31           ` Christian König [this message]
2021-06-04  8:37             ` Chen Li
2021-06-04  8:38         ` [PATCH v4 0/2] " Chen Li
2021-06-04  8:40         ` [PATCH v4 1/2] radeon: fix coding issues reported from sparse Chen Li
2021-06-04 17:19           ` Alex Deucher
2021-06-04  8:43         ` [PATCH v4 2/2] radeon: use memcpy_to/fromio for UVD fw upload Chen Li
2021-06-04  8:47           ` Christian König
2021-06-04 17:21           ` Alex Deucher

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=7bf7e03a-4733-bf66-4a81-ac712582539c@amd.com \
    --to=christian.koenig@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=chenli@uniontech.com \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=dri-devel@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;
as well as URLs for NNTP newsgroup(s).