mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Sui Jingfeng <15330273260@189.cn>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	suijingfeng <suijingfeng@loongson.cn>, liyi <liyi@loongson.cn>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/fbdev-generic: optimize out a redundant assignment clause
Date: Wed, 29 Mar 2023 11:09:13 +0200	[thread overview]
Message-ID: <6504a971-cf4b-ac35-4fe9-ee49b984b521@suse.de> (raw)
In-Reply-To: <a3370ae7-8c78-8170-f9c3-7f616a1fa382@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 2562 bytes --]



Am 29.03.23 um 11:04 schrieb Thomas Zimmermann:
> (cc'ing Lucas)
> 
> Hi
> 
> Am 25.03.23 um 08:46 schrieb Sui Jingfeng:
>>   The assignment already done in drm_client_buffer_vmap(),
>>   just trival clean, no functional change.
>>
>> Signed-off-by: Sui Jingfeng <15330273260@189.cn>
>> ---
>>   drivers/gpu/drm/drm_fbdev_generic.c | 5 ++---
>>   1 file changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_fbdev_generic.c 
>> b/drivers/gpu/drm/drm_fbdev_generic.c
>> index 4d6325e91565..1da48e71c7f1 100644
>> --- a/drivers/gpu/drm/drm_fbdev_generic.c
>> +++ b/drivers/gpu/drm/drm_fbdev_generic.c
>> @@ -282,7 +282,7 @@ static int drm_fbdev_damage_blit(struct 
>> drm_fb_helper *fb_helper,
>>                    struct drm_clip_rect *clip)
>>   {
>>       struct drm_client_buffer *buffer = fb_helper->buffer;
>> -    struct iosys_map map, dst;
>> +    struct iosys_map map;
>>       int ret;
>>       /*
>> @@ -302,8 +302,7 @@ static int drm_fbdev_damage_blit(struct 
>> drm_fb_helper *fb_helper,
>>       if (ret)
>>           goto out;
>> -    dst = map;
>> -    drm_fbdev_damage_blit_real(fb_helper, clip, &dst);
>> +    drm_fbdev_damage_blit_real(fb_helper, clip, &map);
> 
> I see what you're doing and it's probably correct in this case.
> 
> But there's a larger issue with this iosys interfaces. Sometimes the 
> address has to be modified (see calls of iosys_map_incr()). That can 
> prevent incorrect uses of the mapping in other places, especially in 

'prevent correct uses'

> unmap code.
> 
> I think it would make sense to consider a separate structure for the I/O 
> location. The buffer as a whole would still be represented by struct 
> iosys_map.  And that new structure, let's call it struct iosys_ptr, 
> would point to an actual location within the buffer's memory range. A 
> few locations and helpers would need changes, but there are not so many 
> callers that it's an issue.  This would also allow for a few debugging 
> tests that ensure that iosys_ptr always operates within the bounds of an 
> iosys_map.
> 
> I've long considered this idea, but there was no pressure to work on it. 
> Maybe now.
> 
> Best regards
> Thomas
> 
>>       drm_client_buffer_vunmap(buffer);
> 

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2023-03-29  9:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-25  7:46 Sui Jingfeng
2023-03-29  9:04 ` Thomas Zimmermann
2023-03-29  9:09   ` Thomas Zimmermann [this message]
2023-03-29 10:48   ` Sui Jingfeng
2023-03-30  4:17   ` Lucas De Marchi
2023-03-30  6:57     ` Thomas Zimmermann
2023-03-30  7:11       ` Lucas De Marchi
2023-03-30  7:17       ` Sui Jingfeng
2023-03-30  7:26         ` Thomas Zimmermann
2023-03-30  7:48           ` Sui Jingfeng
2023-03-31  3:47           ` Sui Jingfeng
2023-03-30  8:29       ` Sui Jingfeng
2023-03-30  9:01       ` Sui Jingfeng
2023-04-04  2:55   ` Sui Jingfeng

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=6504a971-cf4b-ac35-4fe9-ee49b984b521@suse.de \
    --to=tzimmermann@suse.de \
    --cc=15330273260@189.cn \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liyi@loongson.cn \
    --cc=lucas.demarchi@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=suijingfeng@loongson.cn \
    /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

all inboxes | Powered by JetHome®