From: Thomas Zimmermann <tzimmermann@suse.de>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
daniel@ffwll.ch, deller@gmx.de, javierm@redhat.com,
geert@linux-m68k.org, sam@ravnborg.org, kraxel@redhat.com,
ppaalanen@gmail.com
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [v3,4/5] fbdev: Improve performance of cfb_imageblit()
Date: Wed, 9 Mar 2022 09:22:32 +0100 [thread overview]
Message-ID: <a7c8ee6c-185e-916c-c92a-d3b3f4fd9135@suse.de> (raw)
In-Reply-To: <21110de8-d52a-e55e-8853-1f073c4ab969@samsung.com>
[-- Attachment #1.1: Type: text/plain, Size: 5244 bytes --]
Hi
Am 08.03.22 um 23:52 schrieb Marek Szyprowski:
> Hi Thomas,
>
> On 23.02.2022 20:38, Thomas Zimmermann wrote:
>> Improve the performance of cfb_imageblit() by manually unrolling
>> the inner blitting loop and moving some invariants out. The compiler
>> failed to do this automatically. This change keeps cfb_imageblit()
>> in sync with sys_imagebit().
>>
>> A microbenchmark measures the average number of CPU cycles
>> for cfb_imageblit() after a stabilizing period of a few minutes
>> (i7-4790, FullHD, simpledrm, kernel with debugging).
>>
>> cfb_imageblit(), new: 15724 cycles
>> cfb_imageblit(): old: 30566 cycles
>>
>> In the optimized case, cfb_imageblit() is now ~2x faster than before.
>>
>> v3:
>> * fix commit description (Pekka)
>>
>> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
>> Acked-by: Sam Ravnborg <sam@ravnborg.org>
>> Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
> This patch landed recently in linux next-20220308 as commit 0d03011894d2
> ("fbdev: Improve performance of cfb_imageblit()"). Sadly it causes a
> freeze after DRM and emulated fbdev initialization on various Samsung
> Exynos ARM 32bit based boards. This happens when kernel is compiled from
> exynos_defconfig. Surprisingly when kernel is compiled from
> multi_v7_defconfig all those boards boot fine, so this is a matter of
> one of the debugging options enabled in the exynos_defconfig. I will try
> to analyze this further and share the results. Reverting $subject on top
> of next-20220308 fixes the boot issue.
Thanks for reporting. I don't have the hardware to reproduce it and
there's no obvious difference to the original version. It's supposed to
be the same algorithm with a different implementation. Unless you can
figure out the issue, we can also revert the patch easily.
Best regards
Thomas
>> ---
>> drivers/video/fbdev/core/cfbimgblt.c | 51 +++++++++++++++++++++++-----
>> 1 file changed, 42 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/video/fbdev/core/cfbimgblt.c b/drivers/video/fbdev/core/cfbimgblt.c
>> index 01b01a279681..7361cfabdd85 100644
>> --- a/drivers/video/fbdev/core/cfbimgblt.c
>> +++ b/drivers/video/fbdev/core/cfbimgblt.c
>> @@ -218,23 +218,29 @@ static inline void fast_imageblit(const struct fb_image *image, struct fb_info *
>> {
>> u32 fgx = fgcolor, bgx = bgcolor, bpp = p->var.bits_per_pixel;
>> u32 ppw = 32/bpp, spitch = (image->width + 7)/8;
>> - u32 bit_mask, end_mask, eorx, shift;
>> + u32 bit_mask, eorx;
>> const char *s = image->data, *src;
>> u32 __iomem *dst;
>> const u32 *tab = NULL;
>> + size_t tablen;
>> + u32 colortab[16];
>> int i, j, k;
>>
>> switch (bpp) {
>> case 8:
>> tab = fb_be_math(p) ? cfb_tab8_be : cfb_tab8_le;
>> + tablen = 16;
>> break;
>> case 16:
>> tab = fb_be_math(p) ? cfb_tab16_be : cfb_tab16_le;
>> + tablen = 4;
>> break;
>> case 32:
>> - default:
>> tab = cfb_tab32;
>> + tablen = 2;
>> break;
>> + default:
>> + return;
>> }
>>
>> for (i = ppw-1; i--; ) {
>> @@ -248,15 +254,42 @@ static inline void fast_imageblit(const struct fb_image *image, struct fb_info *
>> eorx = fgx ^ bgx;
>> k = image->width/ppw;
>>
>> - for (i = image->height; i--; ) {
>> - dst = (u32 __iomem *) dst1, shift = 8; src = s;
>> + for (i = 0; i < tablen; ++i)
>> + colortab[i] = (tab[i] & eorx) ^ bgx;
>>
>> - for (j = k; j--; ) {
>> - shift -= ppw;
>> - end_mask = tab[(*src >> shift) & bit_mask];
>> - FB_WRITEL((end_mask & eorx)^bgx, dst++);
>> - if (!shift) { shift = 8; src++; }
>> + for (i = image->height; i--; ) {
>> + dst = (u32 __iomem *)dst1;
>> + src = s;
>> +
>> + switch (ppw) {
>> + case 4: /* 8 bpp */
>> + for (j = k; j; j -= 2, ++src) {
>> + FB_WRITEL(colortab[(*src >> 4) & bit_mask], dst++);
>> + FB_WRITEL(colortab[(*src >> 0) & bit_mask], dst++);
>> + }
>> + break;
>> + case 2: /* 16 bpp */
>> + for (j = k; j; j -= 4, ++src) {
>> + FB_WRITEL(colortab[(*src >> 6) & bit_mask], dst++);
>> + FB_WRITEL(colortab[(*src >> 4) & bit_mask], dst++);
>> + FB_WRITEL(colortab[(*src >> 2) & bit_mask], dst++);
>> + FB_WRITEL(colortab[(*src >> 0) & bit_mask], dst++);
>> + }
>> + break;
>> + case 1: /* 32 bpp */
>> + for (j = k; j; j -= 8, ++src) {
>> + FB_WRITEL(colortab[(*src >> 7) & bit_mask], dst++);
>> + FB_WRITEL(colortab[(*src >> 6) & bit_mask], dst++);
>> + FB_WRITEL(colortab[(*src >> 5) & bit_mask], dst++);
>> + FB_WRITEL(colortab[(*src >> 4) & bit_mask], dst++);
>> + FB_WRITEL(colortab[(*src >> 3) & bit_mask], dst++);
>> + FB_WRITEL(colortab[(*src >> 2) & bit_mask], dst++);
>> + FB_WRITEL(colortab[(*src >> 1) & bit_mask], dst++);
>> + FB_WRITEL(colortab[(*src >> 0) & bit_mask], dst++);
>> + }
>> + break;
>> }
>> +
>> dst1 += p->fix.line_length;
>> s += spitch;
>> }
>
> Best regards
--
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 --]
next prev parent reply other threads:[~2022-03-09 8:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 19:37 [PATCH v3 0/5] fbdev: Improve performance of fbdev console Thomas Zimmermann
2022-02-23 19:38 ` [PATCH v3 1/5] fbdev: Improve performance of sys_fillrect() Thomas Zimmermann
2022-02-23 19:38 ` [PATCH v3 2/5] fbdev: Improve performance of sys_imageblit() Thomas Zimmermann
2022-02-23 19:38 ` [PATCH v3 3/5] fbdev: Remove trailing whitespaces from cfbimgblt.c Thomas Zimmermann
2022-02-23 20:23 ` Sam Ravnborg
2022-02-24 8:22 ` Javier Martinez Canillas
2022-02-23 19:38 ` [PATCH v3 4/5] fbdev: Improve performance of cfb_imageblit() Thomas Zimmermann
2022-02-23 20:25 ` Sam Ravnborg
2022-02-24 9:02 ` Javier Martinez Canillas
2022-02-24 10:29 ` Sam Ravnborg
2022-02-24 10:31 ` Geert Uytterhoeven
2022-02-24 8:31 ` Javier Martinez Canillas
[not found] ` <CGME20220308225225eucas1p12fcdd6e5dc83308b19d51ad7b2a13141@eucas1p1.samsung.com>
2022-03-08 22:52 ` [v3,4/5] " Marek Szyprowski
2022-03-09 8:22 ` Thomas Zimmermann [this message]
2022-03-09 9:22 ` Marek Szyprowski
2022-03-09 10:39 ` Geert Uytterhoeven
2022-03-10 19:21 ` Thomas Zimmermann
2022-03-10 19:23 ` Geert Uytterhoeven
2022-03-13 19:23 ` Thomas Zimmermann
2022-03-24 19:11 ` [PATCH v3 4/5] " Guenter Roeck
2022-03-24 19:18 ` Thomas Zimmermann
2022-03-24 21:18 ` Guenter Roeck
2022-02-23 19:38 ` [PATCH v3 5/5] drm: Add TODO item for optimizing format helpers Thomas Zimmermann
2022-02-23 20:34 ` Sam Ravnborg
2022-02-24 8:39 ` Javier Martinez Canillas
2022-03-02 19:30 ` [PATCH v3 0/5] fbdev: Improve performance of fbdev console Thomas Zimmermann
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=a7c8ee6c-185e-916c-c92a-d3b3f4fd9135@suse.de \
--to=tzimmermann@suse.de \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=javierm@redhat.com \
--cc=kraxel@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=ppaalanen@gmail.com \
--cc=sam@ravnborg.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).