I don't see why the loader (exec.c) couldn't be modified. It can determine
the executable's architecture when you run any ELF binary, so it seems
reasonable that it could also schedule which processor it executes on.
This might do strange things to the SMP code. In fact, it isn't even SMP
proper. It's more like having two totally separate processors sharing a
memory space and devices.
On Fri, 9 Apr 1999, Leslie F. Donaldson wrote:
> HEllo,
> I was reading the latest information about AMD's new K7 and there
> use of Digitals CPU interface and I considered the following:
>
> Take a dual CPU K7 motherboard and insert:
> - K7
> - 21264A Alpha.
>
> Then run Linux on the Alpha Cpu and patch the em86 code to run
> on the K7 treating it as a seperate device.
>
> Now I will admit I haven't gone looking through the kernel on this
> issue yet but It seems to me as long as the Alpha is in the primary
> CPU slot and You tell the kernel there is only one CPU it should boot
> and run. Then You would have to create a driver for the second CPU.
>
> In fact maybe VIA's bios could let you choose which CPU to make the primary one.
> Then You could boot the 21264A when you need to do real work and boot the K7
> to run the game launching OS.
>
> So what does anyone think?
>
> Leslie Donaldson
>
> -
> 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/
>
-- Bob
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin
Bob McElrath (rsmcelrath@students.wisc.edu) Univ. of Wisconsin at Madison
-
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/