Re: memcpy_cpu on 64bit arm

2023-01-24 Thread Michael Grunditz
> I have rebased my code to git level and into a separate tree now. > Can I have the start file , crt0.s , in my tree? I still need register > clearing. > > I will put in on github asap. I have based it on Alllwinner , so I > need to remove the allwinner file and (not exactly necessary for first >

Re: memcpy_cpu on 64bit arm

2023-01-24 Thread Michael Grunditz
On Tue, 24 Jan 2023 at 09:48, Norman Feske wrote: > > Hi Michael, > > > About the blitting: > > I will do benchmarks with and without clipping/flushing. > > for such microbenchmarking, let me point you to the GENODE_LOG_TSC > utility [1], which makes this dead easy. > > [1] https://genodians.org/n

Re: memcpy_cpu on 64bit arm

2023-01-24 Thread Norman Feske
Hi Michael, About the blitting: I will do benchmarks with and without clipping/flushing. for such microbenchmarking, let me point you to the GENODE_LOG_TSC utility [1], which makes this dead easy. [1] https://genodians.org/nfeske/2021-04-07-performance Cheers Norman -- Dr.-Ing. Norman Fes

Re: memcpy_cpu on 64bit arm

2023-01-24 Thread Michael Grunditz
On Tue, 24 Jan 2023 at 08:21, Christian Helmuth wrote: > > Hello, > > On Mon, Jan 23, 2023 at 15:56:48 CET, Michael Grunditz wrote: > > On Mon, 23 Jan 2023 at 14:15, Michael Grunditz > > wrote: > > > Anyway init crashes somewhere. > > > > > > 2043 MiB RAM and 64533 caps assigned to init > > > no

Re: memcpy_cpu on 64bit arm

2023-01-23 Thread Christian Helmuth
Hello, On Mon, Jan 23, 2023 at 15:56:48 CET, Michael Grunditz wrote: > On Mon, 23 Jan 2023 at 14:15, Michael Grunditz > wrote: > > Anyway init crashes somewhere. > > > > 2043 MiB RAM and 64533 caps assigned to init > > no RM attachment (READ pf_addr=0x81 pf_ip=0x9f3f4 from pager_object: > > pd='

Re: memcpy_cpu on 64bit arm

2023-01-23 Thread Michael Grunditz
On Mon, 23 Jan 2023 at 14:15, Michael Grunditz wrote: > > > I have something that seems to work, even though I get a crash from > > test-log that I haven't solved. > > It could be because the .S file is built in every component. So the > > question is, where do I put it!?! > > It needs to live in

Re: memcpy_cpu on 64bit arm

2023-01-23 Thread Michael Grunditz
> I have something that seems to work, even though I get a crash from > test-log that I haven't solved. > It could be because the .S file is built in every component. So the > question is, where do I put it!?! > It needs to live in "base", I guess. But I don't know how. The rest of > the system doe

Re: memcpy_cpu on 64bit arm

2023-01-23 Thread Michael Grunditz
On Fri, 20 Jan 2023 at 20:15, Michael Grunditz wrote: > > > There is no particular reason why the implementation is (i.e. "was") > > empty. You can find a recent commit on the staging branch that applies a > > few obvious optimisations to all architectures, though: > > https://github.com/genodelab

Re: memcpy_cpu on 64bit arm

2023-01-20 Thread Michael Grunditz
> There is no particular reason why the implementation is (i.e. "was") > empty. You can find a recent commit on the staging branch that applies a > few obvious optimisations to all architectures, though: > https://github.com/genodelabs/genode/commit/4d06661d7c3f7b798ec8228f04983bd4ae7cddcf > Is the

Re: memcpy_cpu on 64bit arm

2023-01-20 Thread Johannes Schlatow
Hi Michael, On Fri, 20 Jan 2023 16:40:10 +0100 Michael Grunditz wrote: > Hello, > > Is there any particular reason why it is empty? > My rect copy to fb in riscos uses neon. It is > a speed gain of about 40% compared to word/long word > copy from c. But I don't know how much it affects Genode.

memcpy_cpu on 64bit arm

2023-01-20 Thread Michael Grunditz
Hello, Is there any particular reason why it is empty? My rect copy to fb in riscos uses neon. It is a speed gain of about 40% compared to word/long word copy from c. But I don't know how much it affects Genode. It seems like it ends up in /* eight bytes chunks */ but isn't that a byte copy? I h