Re: SMP boot sequence

2013-10-25 Thread Daniel Hellstrom
On 10/25/2013 02:40 PM, Sebastian Huber wrote: On 2013-10-25 14:23, Daniel Hellstrom wrote: Interrupts are enabled in _Thread_Handler() the first time. However on a SMP machine the secondary CPUs have enabled global CPU interrupt in order to receive IPIs during the boot sequence. This is a

Re: SMP boot sequence

2013-10-25 Thread Sebastian Huber
On 2013-10-25 14:23, Daniel Hellstrom wrote: Interrupts are enabled in _Thread_Handler() the first time. However on a SMP machine the secondary CPUs have enabled global CPU interrupt in order to receive IPIs during the boot sequence. This is a bug. Interrupts must be disabled during the low

Re: SMP boot sequence

2013-10-25 Thread Daniel Hellstrom
On 10/24/2013 04:08 PM, Sebastian Huber wrote: On 2013-10-24 15:42, Daniel Hellstrom wrote: I can see from the running on the LEON SMP hardware and analysing with GRMON that the init task is started and begins its execution on CPU1 before CPU0 (the booting CPU) has finished the RTEMS initializat

Re: SMP boot sequence

2013-10-25 Thread Chris Johns
On 25/10/2013 12:52 am, Joel Sherrill wrote: As you and I have discussed, there was an issue in that EVERY core was stepped up and all had to come to the same state. I know that we want to be able to run on a subset of CPU cores so this is undesirably rigid. Yes and statically controlling this

Re: SMP boot sequence

2013-10-24 Thread Sebastian Huber
On 2013-10-24 15:42, Daniel Hellstrom wrote: I can see from the running on the LEON SMP hardware and analysing with GRMON that the init task is started and begins its execution on CPU1 before CPU0 (the booting CPU) has finished the RTEMS initialization in boot_card(). This is only a problem if

Re: SMP boot sequence

2013-10-24 Thread Daniel Hellstrom
On 10/24/2013 03:52 PM, Joel Sherrill wrote: On 10/24/2013 8:42 AM, Daniel Hellstrom wrote: Hello, I can see from the running on the LEON SMP hardware and analysing with GRMON that the init task is started and begins its execution on CPU1 before CPU0 (the booting CPU) has finished the RTEMS i

Re: SMP boot sequence

2013-10-24 Thread Daniel Hellstrom
On 10/24/2013 03:50 PM, Sebastian Huber wrote: Hello Daniel, which RTEMS version do you use? Based on the d2c5bff7dc5a93d5369e83e5c412c3b424dee781 commit, I haven't rebased the last three weeks. Have this been fixed? Daniel ___ rtems-devel mailin

Re: SMP boot sequence

2013-10-24 Thread Joel Sherrill
On 10/24/2013 8:42 AM, Daniel Hellstrom wrote: > Hello, > > I can see from the running on the LEON SMP hardware and analysing with GRMON > that the init task is started and begins its execution on CPU1 before CPU0 > (the booting CPU) has finished the RTEMS > initialization in boot_card(). As I

Re: SMP boot sequence

2013-10-24 Thread Sebastian Huber
Hello Daniel, which RTEMS version do you use? -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Na

SMP boot sequence

2013-10-24 Thread Daniel Hellstrom
Hello, I can see from the running on the LEON SMP hardware and analysing with GRMON that the init task is started and begins its execution on CPU1 before CPU0 (the booting CPU) has finished the RTEMS initialization in boot_card(). As I understand the boot procedure of RTEMS global CPU interrupt