2006-06-12 15:22:12 +00:00
|
|
|
/*
|
|
|
|
* p->mem:
|
|
|
|
* text
|
|
|
|
* original data and bss
|
|
|
|
* fixed-size stack
|
|
|
|
* expandable heap
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* segments in proc->gdt
|
|
|
|
*/
|
|
|
|
#define SEG_KCODE 1 // kernel code
|
|
|
|
#define SEG_KDATA 2 // kernel data+stack
|
|
|
|
#define SEG_UCODE 3
|
|
|
|
#define SEG_UDATA 4
|
|
|
|
#define SEG_TSS 5 // this process's task state
|
|
|
|
#define NSEGS 6
|
|
|
|
|
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 01:07:40 +00:00
|
|
|
struct jmpbuf {
|
|
|
|
// saved registers for kernel context switches
|
|
|
|
// don't need to save all the fs etc. registers because
|
|
|
|
// they are constant across kernel contexts
|
|
|
|
// save all the regular registers so we don't care which are caller save
|
|
|
|
// don't save eax because that's the return register
|
2006-07-16 15:41:47 +00:00
|
|
|
// layout known to setjmp.S
|
|
|
|
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 01:07:40 +00:00
|
|
|
};
|
|
|
|
|
2006-08-16 01:56:00 +00:00
|
|
|
enum proc_state { UNUSED, EMBRYO, SLEEPING, RUNNABLE, RUNNING, ZOMBIE };
|
2006-07-12 01:48:35 +00:00
|
|
|
|
2006-06-12 15:22:12 +00:00
|
|
|
struct proc{
|
2006-08-29 21:35:30 +00:00
|
|
|
char *mem; // start of process's memory (a kernel address)
|
|
|
|
uint sz; // user memory size
|
|
|
|
char *kstack; // kernel stack
|
2006-07-12 01:48:35 +00:00
|
|
|
enum proc_state state;
|
2006-06-15 19:58:01 +00:00
|
|
|
int pid;
|
|
|
|
int ppid;
|
|
|
|
void *chan; // sleep
|
2006-07-11 17:39:45 +00:00
|
|
|
int killed;
|
2006-06-27 14:35:53 +00:00
|
|
|
struct fd *fds[NOFILE];
|
2006-08-15 15:53:46 +00:00
|
|
|
struct inode *cwd;
|
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 01:07:40 +00:00
|
|
|
struct jmpbuf jmpbuf;
|
2006-07-17 01:58:13 +00:00
|
|
|
struct trapframe *tf; // points into kstack, used to find user regs
|
2006-06-12 15:22:12 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
extern struct proc proc[];
|
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 01:07:40 +00:00
|
|
|
extern struct proc *curproc[NCPU]; // can be NULL if no proc running.
|
2006-07-01 21:26:01 +00:00
|
|
|
|
|
|
|
#define MPSTACK 512
|
|
|
|
|
|
|
|
struct cpu {
|
2006-07-20 09:07:53 +00:00
|
|
|
uchar apicid; // Local APIC ID
|
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 01:07:40 +00:00
|
|
|
struct jmpbuf jmpbuf;
|
2006-08-15 22:18:20 +00:00
|
|
|
struct taskstate ts; // only to give cpu address of kernel stack
|
|
|
|
struct segdesc gdt[NSEGS];
|
2006-08-08 19:58:06 +00:00
|
|
|
char mpstack[MPSTACK]; // per-cpu start-up stack
|
|
|
|
volatile int booted;
|
2006-07-16 01:15:28 +00:00
|
|
|
int nlock; // # of locks currently held
|
2006-07-01 21:26:01 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
extern struct cpu cpus[NCPU];
|
|
|
|
extern int ncpu;
|