> ah ok, so the kernel only ran on one CPU, but processes could run on
> both. i had thought that this was due to a global kernel lock, not
> interrupts.. by what mechanism can the kernel on cpu#0 schedule a
> task to run on cpu#1?
>
> Hopefully widely available K7 SMP systems will accelerate development
> of EV6 SMP and help the 21264 out aswell.
no.. You misunderstand.
In unix the kernel runs in process context.. So the kernel ran on both
cpus, but two copies of the kernel could not run at one (except when doing
some trivial things). All the int's were processes by cpu0.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/