From: Thomas Huth <thuth@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: slof@lists.ozlabs.org, nikunj@linux.vnet.ibm.com, aik@ozlabs.ru,
linuxppc-dev@lists.ozlabs.org, gkurz@linux.vnet.ibm.com
Subject: Re: [SLOF PATCH 1/2] fbuffer: Improve invert-region helper
Date: Tue, 28 Jul 2015 23:00:49 +0200 [thread overview]
Message-ID: <55B7ED81.3080103@redhat.com> (raw)
In-Reply-To: <20150728170416.GB28839@gate.crashing.org>
Hi Segher,
On 28/07/15 19:04, Segher Boessenkool wrote:
> On Tue, Jul 28, 2015 at 12:19:54PM +0200, Thomas Huth wrote:
>> : invert-region ( addr len -- )
>> - 0 ?DO dup dup rb@ -1 xor swap rb! 1+ LOOP drop
>> -;
>> -
>> -: invert-region-x ( addr len -- )
>> - /x / 0 ?DO dup dup rx@ -1 xor swap rx! xa1+ LOOP drop
>> + 2dup or 7 and CASE
>> + 0 OF 3 rshift 0 ?DO dup dup rx@ -1 xor swap rx! xa1+ LOOP ENDOF
>> + 2 OF 1 rshift 0 ?DO dup dup rw@ -1 xor swap rw! wa1+ LOOP ENDOF
>> + 4 OF 2 rshift 0 ?DO dup dup rl@ -1 xor swap rl! la1+ LOOP ENDOF
>> + 6 OF 1 rshift 0 ?DO dup dup rw@ -1 xor swap rw! wa1+ LOOP ENDOF
>> + dup OF 0 ?DO dup dup rb@ -1 xor swap rb! 1+ LOOP ENDOF
>> + ENDCASE
>> + drop
>> ;
>
> Can you access device memory as 64 bits for all supported devices?
Yes, should be fine since 64 bit access was already used in the original
code, see fb8-invert-screen in
https://github.com/aik/SLOF/commit/99c534ecc7a8566bd9ca6346915d9ac1bfacae1e
> You can get a bigger speedup by writing some of the core blitting
> functions in C, btw.
Well, the above code is for js2x only ... so this is likely not worth
the effort anymore. The code for qemu-spapr calls into a hypercall
already, so this is already accelerated.
> A small simplification:
>
> 2dup or 7 and CASE
> 0 OF 3 rshift 0 ?DO dup dup rx@ -1 xor swap rx! xa1+ LOOP ENDOF
> 4 OF 2 rshift 0 ?DO dup dup rl@ -1 xor swap rl! la1+ LOOP ENDOF
> 3 and
> 2 OF 1 rshift 0 ?DO dup dup rw@ -1 xor swap rw! wa1+ LOOP ENDOF
> dup OF 0 ?DO dup dup rb@ -1 xor swap rb! 1+ LOOP ENDOF
> ENDCASE
Ok, nice idea, makes sense! I'll include it in v2 (after waiting a little
bit to see if there's other feedback)
> If this code is often called unaligned, it makes more sense to special-
> case the begin and end probably.
It's only used for drawing the cursor, so it always should be aligned.
Thomas
next prev parent reply other threads:[~2015-07-28 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 10:19 [SLOF PATCH 0/2] fbuffer: Improve the speed of the cursor drawing Thomas Huth
2015-07-28 10:19 ` [SLOF PATCH 1/2] fbuffer: Improve invert-region helper Thomas Huth
2015-07-28 17:04 ` Segher Boessenkool
2015-07-28 21:00 ` Thomas Huth [this message]
2015-07-28 10:19 ` [SLOF PATCH 2/2] fbuffer: Use a smaller cursor Thomas Huth
2015-07-29 3:05 ` Alexey Kardashevskiy
2015-07-29 3:42 ` [SLOF] " Segher Boessenkool
2015-07-29 6:03 ` Thomas Huth
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=55B7ED81.3080103@redhat.com \
--to=thuth@redhat.com \
--cc=aik@ozlabs.ru \
--cc=gkurz@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nikunj@linux.vnet.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=slof@lists.ozlabs.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 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.