Maciej W. Rozycki wrote: > On Tue, 28 Oct 2008, Ralf Baechle wrote: > >> Another thing I noticed is that we don't use write_c0_ebase(), so the >> firmware better setup this correctly or we crash and burn. We better >> should initialize that right ... > > Well, your version still does not do it... > > Maciej >From an Octeon perspective, we'd prefer that the kernel not touch ebase as we set it in the bootloader. The bootloader sets the proper value based on the number of kernels being loaded and which cores the kernel is loaded on. This allows some interesting things, like running 16 kernels each on a different CPU. Although 16 kernels is just a toy project, we have a number of customers that run two kernels. They choose which cores the kernels run on dynamically at boot time. Chad
