2006-09-07 16:12:30 +02:00
|
|
|
// Segments in proc->gdt
|
|
|
|
#define SEG_KCODE 1 // kernel code
|
|
|
|
#define SEG_KDATA 2 // kernel data+stack
|
2006-06-12 17:22:12 +02:00
|
|
|
#define SEG_UCODE 3
|
|
|
|
#define SEG_UDATA 4
|
2006-09-07 16:12:30 +02:00
|
|
|
#define SEG_TSS 5 // this process's task state
|
2006-09-06 19:50:20 +02:00
|
|
|
#define NSEGS 6
|
2006-06-12 17:22:12 +02:00
|
|
|
|
2006-09-07 16:12:30 +02:00
|
|
|
// Saved registers for kernel context switches.
|
|
|
|
// Don't need to save all the %fs etc. segment registers,
|
|
|
|
// because they are constant across kernel contexts.
|
|
|
|
// Save all the regular registers so we don't need to care
|
|
|
|
// which are caller save.
|
|
|
|
// Don't save %eax, because that's the return register.
|
|
|
|
// The layout of jmpbuf is known to setjmp.S.
|
Changes to allow use of native x86 ELF compilers, which on my
Linux 2.4 box using gcc 3.4.6 don't seem to follow the same
conventions as the i386-jos-elf-gcc compilers.
Can run make 'TOOLPREFIX=' or edit the Makefile.
curproc[cpu()] can now be NULL, indicating that no proc is running.
This seemed safer to me than having curproc[0] and curproc[1]
both pointing at proc[0] potentially.
The old implementation of swtch depended on the stack frame layout
used inside swtch being okay to return from on the other stack
(exactly the V6 you are not expected to understand this).
It also could be called in two contexts: at boot time, to schedule
the very first process, and later, on behalf of a process, to sleep
or schedule some other process.
I split this into two functions: scheduler and swtch.
The scheduler is now a separate never-returning function, invoked
by each cpu once set up. The scheduler looks like:
scheduler() {
setjmp(cpu.context);
pick proc to schedule
blah blah blah
longjmp(proc.context)
}
The new swtch is intended to be called only when curproc[cpu()] is not NULL,
that is, only on behalf of a user proc. It does:
swtch() {
if(setjmp(proc.context) == 0)
longjmp(cpu.context)
}
to save the current proc context and then jump over to the scheduler,
running on the cpu stack.
Similarly the system call stubs are now in assembly in usys.S to avoid
needing to know the details of stack frame layout used by the compiler.
Also various changes in the debugging prints.
2006-07-11 03:07:40 +02:00
|
|
|
struct jmpbuf {
|
2006-07-16 17:41:47 +02:00
|
|
|
int ebx;
|
|
|
|
int ecx;
|
|
|
|
int edx;
|
|
|
|
int esi;
|
|
|
|
int edi;
|
|
|
|
int esp;
|
|
|
|
int ebp;
|
|
|
|
int eip;
|
Changes to allow use of native x86 ELF compilers, which on my
Linux 2.4 box using gcc 3.4.6 don't seem to follow the same
conventions as the i386-jos-elf-gcc compilers.
Can run make 'TOOLPREFIX=' or edit the Makefile.
curproc[cpu()] can now be NULL, indicating that no proc is running.
This seemed safer to me than having curproc[0] and curproc[1]
both pointing at proc[0] potentially.
The old implementation of swtch depended on the stack frame layout
used inside swtch being okay to return from on the other stack
(exactly the V6 you are not expected to understand this).
It also could be called in two contexts: at boot time, to schedule
the very first process, and later, on behalf of a process, to sleep
or schedule some other process.
I split this into two functions: scheduler and swtch.
The scheduler is now a separate never-returning function, invoked
by each cpu once set up. The scheduler looks like:
scheduler() {
setjmp(cpu.context);
pick proc to schedule
blah blah blah
longjmp(proc.context)
}
The new swtch is intended to be called only when curproc[cpu()] is not NULL,
that is, only on behalf of a user proc. It does:
swtch() {
if(setjmp(proc.context) == 0)
longjmp(cpu.context)
}
to save the current proc context and then jump over to the scheduler,
running on the cpu stack.
Similarly the system call stubs are now in assembly in usys.S to avoid
needing to know the details of stack frame layout used by the compiler.
Also various changes in the debugging prints.
2006-07-11 03:07:40 +02:00
|
|
|
};
|
|
|
|
|
2006-08-16 03:56:00 +02:00
|
|
|
enum proc_state { UNUSED, EMBRYO, SLEEPING, RUNNABLE, RUNNING, ZOMBIE };
|
2006-07-12 03:48:35 +02:00
|
|
|
|
2006-09-07 16:12:30 +02:00
|
|
|
// Per-process state
|
|
|
|
struct proc {
|
|
|
|
char *mem; // Start of process memory (kernel address)
|
|
|
|
uint sz; // Size of process memory (bytes)
|
|
|
|
char *kstack; // Bottom of kernel stack for this process
|
|
|
|
enum proc_state state; // Process state
|
|
|
|
int pid; // Process ID
|
|
|
|
int ppid; // Parent pid
|
|
|
|
void *chan; // If non-zero, sleeping on chan
|
|
|
|
int killed; // If non-zero, have been killed
|
|
|
|
struct file *ofile[NOFILE]; // Open files
|
|
|
|
struct inode *cwd; // Current directory
|
|
|
|
struct jmpbuf jmpbuf; // Jump here to run process
|
|
|
|
struct trapframe *tf; // Trap frame for current interrupt
|
2006-06-12 17:22:12 +02:00
|
|
|
};
|
|
|
|
|
2006-09-07 16:12:30 +02:00
|
|
|
// Process memory is laid out contiguously:
|
|
|
|
// text
|
|
|
|
// original data and bss
|
|
|
|
// fixed-size stack
|
|
|
|
// expandable heap
|
|
|
|
|
2006-06-12 17:22:12 +02:00
|
|
|
extern struct proc proc[];
|
2006-09-07 16:12:30 +02:00
|
|
|
extern struct proc *curproc[NCPU]; // Current (running) process per CPU
|
2006-07-01 23:26:01 +02:00
|
|
|
|
|
|
|
#define MPSTACK 512
|
|
|
|
|
2006-09-07 16:12:30 +02:00
|
|
|
// Per-CPU state
|
2006-07-01 23:26:01 +02:00
|
|
|
struct cpu {
|
2006-09-07 16:12:30 +02:00
|
|
|
uchar apicid; // Local APIC ID
|
|
|
|
struct jmpbuf jmpbuf; // Jump here to enter scheduler
|
|
|
|
struct taskstate ts; // Used by x86 to find stack for interrupt
|
|
|
|
struct segdesc gdt[NSEGS]; // x86 global descriptor table
|
|
|
|
char mpstack[MPSTACK]; // Per-CPU startup stack
|
|
|
|
volatile int booted; // Has the CPU started?
|
|
|
|
int nlock; // Number of locks currently held
|
2006-07-01 23:26:01 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
extern struct cpu cpus[NCPU];
|
|
|
|
extern int ncpu;
|