why my posts are not appearing on the discussion list?

[zhang jin]

i am reading minix3.1 text book, the save procedure in the book on page 712 tests
whether the caller enter the kernel for the first time (from user to kernel) or later
(from kernel to kernel).
on line 6638 jmp RETADR-P_STACKBASE(eax)

The RETADR = 24
P_STACKBASE = 0
eax is essentially esp before testing k_reenter for kernel stack switch
so this statement is essentially

jmp 24-0(esp)

how does this work? it looks rather odd to me

Code:

06613
06614 !*===========================================================================*
06615 !* save *
06616 !*===========================================================================*
06617 ! Save for protected mode.
06618 ! This is much simpler than for 8086 mode, because the stack already points
06619 ! into the process table, or has already been switched to the kernel stack.
06620
06621 .align 16
06622 save:
06623 cld ! set direction flag to a known value
06624 pushad ! save "general" registers
06625 o16 push ds ! save ds
06626 o16 push es ! save es
06627 o16 push fs ! save fs
06628 o16 push gs ! save gs
06629 mov dx, ss ! ss is kernel data segment
06630 mov ds, dx ! load rest of kernel segments
06631 mov es, dx ! kernel does not use fs, gs
06632 mov eax, esp ! prepare to return
06633 incb (_k_reenter) ! from -1 if not reentering
06634 jnz set_restart1 ! stack is already kernel stack
06635 mov esp, k_stktop
06636 push _restart ! build return address for int handler
06637 xor ebp, ebp ! for stacktrace
06638 jmp RETADR-P_STACKBASE(eax)
06639
06640 .align 4
06641 set_restart1:
06642 push restart1
06643 jmp RETADR-P_STACKBASE(eax)
06644

[stux...@gmail.com]

Hi, it seems that you're getting the groups confused.   This group is mainly for minix development (albeit development has long stalled).

You already posted this question on the minix3 group and answered there.  The link to that post is here:

• https://groups.google.com/g/minix3/c/xWw52HzNmKo

Please bookmark that post and please be mindful not to repeatedly post the same question as it can be disruptive.  You also posted another question another question here which has not been answered yet:

• https://groups.google.com/g/minix3/c/1vgvrqg_Pl4

Please understand that these are highly technical questions which may not have an expert available right away to respond.

-stux

[stux...@gmail.com]

Finally, I should mention that here is the link to the main minix3 group:

• https://groups.google.com/g/minix3

Please bookmark that as well since that is where most discussions occur.