[seL4] Re: memory zero'ing

RISC-V (32-bit), no L2 cache. All of user-space shares 1 ASID. On Fri, Mar 10, 2023 at 4:23 PM Indan Zupancic wrote: > Hello, > > On 2023-03-11 10:56, Sam Leffler via Devel wrote: > > I've got a stress test that forces lots of memory recycling by > > creating, > > running & tearing down applicat

[seL4] Re: memory zero'ing

Hello, On 2023-03-11 10:56, Sam Leffler via Devel wrote: I've got a stress test that forces lots of memory recycling by creating, running & tearing down applications. I repeatedly see a particular point in the test (after memory starts being recycled) where an app gets an instruction fault. Na

[seL4] Re: memory zero'ing

On Fri, Mar 10, 2023 at 3:55 PM Gerwin Klein wrote: > > > On 11 Mar 2023, at 09:19, Sam Leffler via Devel > wrote: > > I'm chasing an issue that looks like retype'd memory has nonsense data. If > I read the kernel code correctly it looks like the object returned by an > seL4_UntypeRetype syscall

[seL4] Re: memory zero'ing

On Fri, Mar 10, 2023 at 3:28 PM Kent Mcleod wrote: > > > On Sat, 11 Mar 2023, 09:40 Sam Leffler via Devel, > wrote: > >> I'm chasing an issue that looks like retype'd memory has nonsense data. If >> I read the kernel code correctly it looks like the object returned by an >> seL4_UntypeRetype sys

[seL4] Re: memory zero'ing

On 11 Mar 2023, at 09:19, Sam Leffler via Devel wrote: I'm chasing an issue that looks like retype'd memory has nonsense data. If I read the kernel code correctly it looks like the object returned by an seL4_UntypeRetype syscall should be zero'd (looks to happen when an untyped memory object i

[seL4] Re: memory zero'ing

On Sat, 11 Mar 2023, 09:40 Sam Leffler via Devel, wrote: > I'm chasing an issue that looks like retype'd memory has nonsense data. If > I read the kernel code correctly it looks like the object returned by an > seL4_UntypeRetype syscall should be zero'd (looks to happen when an untyped > memory o

[seL4] memory zero'ing

I'm chasing an issue that looks like retype'd memory has nonsense data. If I read the kernel code correctly it looks like the object returned by an seL4_UntypeRetype syscall should be zero'd (looks to happen when an untyped memory object is reset here