Re: wortel problems

[Johan Rydberg]

Espen Skoglund <address@hidden> wrote:

: > s0: Alloc pool:
: > s0:  0x00000000-0x00003fff   0x00034001 (kernel)
: > s0:  0x00005000-0x000c2fff   0x00034001 (kernel)
: > s0:  0x00100000-0x00180fff   0x00034001 (kernel)
: > s0:  0x00216000-0x00216fff   0x000bc001 (root server)
: > s0:  0x00290000-0x002ccfff   0x000bc001 (root server)
: > s0:  0x00300000-0x00309fff   0x000bc001 (root server)
: > s0:  0x00350000-0x00356fff   0x000bc001 (root server)
: 
: The pool doesn't look very sane to me.  Where is sigma0's memory? 

Good question.  It's covered by 
 
  s0:  0x00100000-0x00180fff   0x00034001 (kernel)

But I really don't know why it shows up as kernel memory.

: I assume that this is the page table of the destination space, right?

Yes.

: It seems that you are observing some "interesting" behaviour here?  Is
: it possible for me to try this setup so that I can try to figure out
: what is going on?

I've written a test case that triggers the problem.  The problem, for
you, I guess is that it uses hurd-l4/libl4  headers.  And the PowerPC
patches to laden+wortel hasn't yet been applied.

Maybe it would be easier for you to just look at the test case, and 
write one of your own using "your" headers and libraries.  What it
does it simply requests any page of size (1 << 24) from sigma0.

-- 
Johan Rydberg, Free Software Developer, Sweden
http://rtmk.sf.net | http://www.nongnu.org/guss/

Playing Money Mark Diggla & C.O. - Goodness Gracious (Super Clean

test-sigma0.c
Description: Binary data