[comp.os.minix] Your message

mmdf@udel.UUCP (10/01/87)

Why is this in  kernel/main.c in function main()?

Code segment:

  /* Put a ptr to proc table in a known place so it can be found in
/dev/mem */
  set_vec( (BASE - 4)/4, proc, (phys_clicks) 0);

I see its putting a magic pointer in the top of the interrupt vector
table.
Using my hp1631 analyze, after booting, no one ever reads this magic
pointer.
I took out the code and nothing changes (the /usr/test package runs ok).

Any idea what's going on?  I didn't see any 1.2 diffs taking it out.
I'm somewhat concerned when it may bite me (although I don't see its
ever used by anyone).

(I'm currently moving the interrupt vector table into the kernel data
space on the ATs and using the idt of the 286 processor to change
tables.  This is in preparation for starting to run protected mode.  I'm
going to reprogram the 8259 interrupt controllers on the AT to run at
vectors 0x40-0x4f to get the hardware out of the way of the 286
exception handlers.)

marty
ARPA:	leisner.henr@xerox.com
GV:  leisner.henr
NS:  martin leisner:henr801c:xerox
UUCP: martyl@rocksvax.uucp

ast@star.UUCP (10/02/87)

In article <541@louie.udel.EDU> Leisner.Henr@xerox.com (marty) asks why
>  set_vec( (BASE - 4)/4, proc, (phys_clicks) 0);
is in kernel/main.c.

It was a hook in case somebody wanted to write ps(1).  That way ps
could find the proc table.
Andy Tanenbaum (ast@cs.vu.nl)