Hi andrew:

 

   i find the place you said laste emai, it seems only xtensa and x84 arch supports the SMP mode, so take xtensa for exmaple.

it seems the mechanism you said in the laste email only effect when "CONFIG_TICKLESS_KERNEL" enabled.

if the macro CONFIG_TICKLESS_KERNEL not enabled,  the z_clock_announce still pased the 1 tick for each core, so the cur_tick would be doubled, where am i wrong?

 thanks for your kindly help.

static void ccompare_isr(void *arg)
{
    ARG_UNUSED(arg);

    k_spinlock_key_t key = k_spin_lock(&lock);
    u32_t curr = ccount();
    u32_t dticks = (curr - last_count) / CYC_PER_TICK;

    last_count += dticks * CYC_PER_TICK;

    if (!IS_ENABLED(CONFIG_TICKLESS_KERNEL) ||
        IS_ENABLED(CONFIG_QEMU_TICKLESS_WORKAROUND)) {
        u32_t next = last_count + CYC_PER_TICK;

        if ((s32_t)(next - curr) < MIN_DELAY) {
            next += CYC_PER_TICK;
        }
        set_ccompare(next);
    }

    k_spin_unlock(&lock, key);
    z_clock_announce(IS_ENABLED(CONFIG_TICKLESS_KERNEL) ? dticks : 1);
}

曹子龙

珠海全志科技股份有限公司      BU1-PSW

地址：广东省珠海市高新区唐家湾镇科技2路9号

TEL：13824125580

Email：caozilong@...

网址： http://www.allwinnertech.com

 

------------------------------------------------------------------

发件人：Andy Ross <andrew.j.ross@...>

发送时间：2019年8月23日(星期五) 23:35

收件人：曹子龙 <caozilong@...>; devel <devel@...>

主　题：Re: [Zephyr-devel] Is The tick handler "z_clock_announce" in SMP mode dupulicate caculated？

This is the responsibility of the timer driver.  The ticks announced needs to be globally correct.  The existing drivers do this by locking a "last count" state variable and updating it, so they see the updates made by the other cores.

Andy

On 8/23/2019 8:14 AM, "曹子龙 wrote:

Hi  friends:

    

  a puzzle in the timer tick interrupt handler in SMP mode.  look at below,  the SMP mult cores share the same "cur_tick" object to remeber the current time, each cpu would increment it when the tick hander  excutes on each CPU.

so, could this would accelerate the timer compare with the realworld?  for example, if 4cores  exist, the cur_tick would 4 times incmrent than the read world, i cant fingure out where am a wrong, so, could you figure me out?  thanks for your kinldy supply. 

void z_clock_announce(s32_t ticks)

{

#ifdef CONFIG_TIMESLICING

 z_time_slice(ticks);

#endif

 k_spinlock_key_t key = k_spin_lock(&timeout_lock);

 announce_remaining = ticks;

 while (first() != NULL && first()->dticks <= announce_remaining) {

  struct _timeout *t = first();

  int dt = t->dticks;

  curr_tick += dt;

  announce_remaining -= dt;

  t->dticks = 0;

  remove_timeout(t);

  k_spin_unlock(&timeout_lock, key);

  t->fn(t);

  key = k_spin_lock(&timeout_lock);

 }

 if (first() != NULL) {

  first()->dticks -= announce_remaining;

 }

 curr_tick += announce_remaining;

 announce_remaining = 0;

 z_clock_set_timeout(next_timeout(), false);

 k_spin_unlock(&timeout_lock, key);

}

曹子龙

珠海全志科技股份有限公司      BU1-PSW

地址：广东省珠海市高新区唐家湾镇科技2路9号

TEL：13824125580

Email：caozilong@...

网址： http://www.allwinnertech.com

 

Dear Madam,

I saw your video on the web related to Zephyr RTOS. Sorry to address you with the 'Mr' in my last email. I did not know you before. Really happy that Developer Advocate has very nicely replied to my query. I am very thankful. I really want to be expert in Zephyr RTOS. Hope i start of well. Waiting for your kind help despite of your busy schedule.

Best Regards

------------------------------------------------------------------

发件人：Andy Ross <andrew.j.ross@...>

发送时间：2019年8月23日(星期五) 23:35

收件人：曹子龙 <caozilong@...>; devel <devel@...>

主　题：Re: [Zephyr-devel] Is The tick handler "z_clock_announce" in SMP mode dupulicate caculated？

This is the responsibility of the timer driver.  The ticks announced needs to be globally correct.  The existing drivers do this by locking a "last count" state variable and updating it, so they see the updates made by the other cores.

Andy

On 8/23/2019 8:14 AM, "曹子龙 wrote:

Hi  friends:

    

  a puzzle in the timer tick interrupt handler in SMP mode.  look at below,  the SMP mult cores share the same "cur_tick" object to remeber the current time, each cpu would increment it when the tick hander  excutes on each CPU.

so, could this would accelerate the timer compare with the realworld?  for example, if 4cores  exist, the cur_tick would 4 times incmrent than the read world, i cant fingure out where am a wrong, so, could you figure me out?  thanks for your kinldy supply. 

void z_clock_announce(s32_t ticks)

{

#ifdef CONFIG_TIMESLICING

 z_time_slice(ticks);

#endif

 k_spinlock_key_t key = k_spin_lock(&timeout_lock);

 announce_remaining = ticks;

 while (first() != NULL && first()->dticks <= announce_remaining) {

  struct _timeout *t = first();

  int dt = t->dticks;

  curr_tick += dt;

  announce_remaining -= dt;

  t->dticks = 0;

  remove_timeout(t);

  k_spin_unlock(&timeout_lock, key);

  t->fn(t);

  key = k_spin_lock(&timeout_lock);

 }

 if (first() != NULL) {

  first()->dticks -= announce_remaining;

 }

 curr_tick += announce_remaining;

 announce_remaining = 0;

 z_clock_set_timeout(next_timeout(), false);

 k_spin_unlock(&timeout_lock, key);

}

曹子龙

珠海全志科技股份有限公司      BU1-PSW

地址：广东省珠海市高新区唐家湾镇科技2路9号

TEL：13824125580

Email：caozilong@...

网址： http://www.allwinnertech.com

 

On 23 Aug 2019, at 16:32, Manu R <manu@...> wrote:

Thanks Anas, I should have been clearer in my question, apologies.

It looks like there is a 1.14.1 brewing, I presume that is bug fixes on the 1.14 release. When it is released, I will probably want that, but for now, the last released version is v1.14.0, is that correct?

Manu

On Fri, Aug 23, 2019 at 4:24 PM Nashif, Anas <anas.nashif@...> wrote:
v1.14-branch is the branch, all others are tags on the branch.



Anas





From: <devel@...> on behalf of Manu R <manu@...>
Date: Friday, 23 August 2019 at 18:38
To: "devel@..." <devel@...>
Subject: [Zephyr-devel] What branch should I be using for the 1.14 LTS release?



when I do a zephyr (v1.14-branch) $ git checkout v1.14<tab>
v1.14-branch v1.14.0 v1.14.0-rc1 v1.14.0-rc2 v1.14.0-rc3 v1.14.1-rc1



Thanks

Manu

------------------------------------------------------------------

发件人：Andy Ross <andrew.j.ross@...>

发送时间：2019年8月23日(星期五) 23:35

收件人：曹子龙 <caozilong@...>; devel <devel@...>

主　题：Re: [Zephyr-devel] Is The tick handler "z_clock_announce" in SMP mode dupulicate caculated？

This is the responsibility of the timer driver.  The ticks announced needs to be globally correct.  The existing drivers do this by locking a "last count" state variable and updating it, so they see the updates made by the other cores.

Andy

On 8/23/2019 8:14 AM, "曹子龙 wrote:

Hi  friends:

    

  a puzzle in the timer tick interrupt handler in SMP mode.  look at below,  the SMP mult cores share the same "cur_tick" object to remeber the current time, each cpu would increment it when the tick hander  excutes on each CPU.

so, could this would accelerate the timer compare with the realworld?  for example, if 4cores  exist, the cur_tick would 4 times incmrent than the read world, i cant fingure out where am a wrong, so, could you figure me out?  thanks for your kinldy supply. 

void z_clock_announce(s32_t ticks)

{

#ifdef CONFIG_TIMESLICING

 z_time_slice(ticks);

#endif

 k_spinlock_key_t key = k_spin_lock(&timeout_lock);

 announce_remaining = ticks;

 while (first() != NULL && first()->dticks <= announce_remaining) {

  struct _timeout *t = first();

  int dt = t->dticks;

  curr_tick += dt;

  announce_remaining -= dt;

  t->dticks = 0;

  remove_timeout(t);

  k_spin_unlock(&timeout_lock, key);

  t->fn(t);

  key = k_spin_lock(&timeout_lock);

 }

 if (first() != NULL) {

  first()->dticks -= announce_remaining;

 }

 curr_tick += announce_remaining;

 announce_remaining = 0;

 z_clock_set_timeout(next_timeout(), false);

 k_spin_unlock(&timeout_lock, key);

}

曹子龙

珠海全志科技股份有限公司      BU1-PSW

地址：广东省珠海市高新区唐家湾镇科技2路9号

TEL：13824125580

Email：caozilong@...

网址： http://www.allwinnertech.com

 

------------------------------------------------------------------
发件人：Andy Ross<andrew.j.ross@...>
日　期：2019年08月23日 23:32:07
收件人：曹子龙<caozilong@...>; devel<devel@...>
主　题：Re: [Zephyr-devel] Is The tick handler "z_clock_announce" in SMP mode dupulicate caculated？

This is the responsibility of the timer driver.  The ticks announced needs to be globally correct.  The existing drivers do this by locking a "last count" state variable and updating it, so they see the updates made by the other cores.

Andy

On 8/23/2019 8:14 AM, "曹子龙 wrote:

Hi  friends:

    

  a puzzle in the timer tick interrupt handler in SMP mode.  look at below,  the SMP mult cores share the same "cur_tick" object to remeber the current time, each cpu would increment it when the tick hander  excutes on each CPU.

so, could this would accelerate the timer compare with the realworld?  for example, if 4cores  exist, the cur_tick would 4 times incmrent than the read world, i cant fingure out where am a wrong, so, could you figure me out?  thanks for your kinldy supply. 

void z_clock_announce(s32_t ticks)

{

#ifdef CONFIG_TIMESLICING

 z_time_slice(ticks);

#endif

 k_spinlock_key_t key = k_spin_lock(&timeout_lock);

 announce_remaining = ticks;

 while (first() != NULL && first()->dticks <= announce_remaining) {

  struct _timeout *t = first();

  int dt = t->dticks;

  curr_tick += dt;

  announce_remaining -= dt;

  t->dticks = 0;

  remove_timeout(t);

  k_spin_unlock(&timeout_lock, key);

  t->fn(t);

  key = k_spin_lock(&timeout_lock);

 }

 if (first() != NULL) {

  first()->dticks -= announce_remaining;

 }

 curr_tick += announce_remaining;

 announce_remaining = 0;

 z_clock_set_timeout(next_timeout(), false);

 k_spin_unlock(&timeout_lock, key);

}

曹子龙

珠海全志科技股份有限公司      BU1-PSW

地址：广东省珠海市高新区唐家湾镇科技2路9号

TEL：13824125580

Email：caozilong@...

网址： http://www.allwinnertech.com

 

Hi  friends:

    

  a puzzle in the timer tick interrupt handler in SMP mode.  look at below,  the SMP mult cores share the same "cur_tick" object to remeber the current time, each cpu would increment it when the tick hander  excutes on each CPU.

so, could this would accelerate the timer compare with the realworld?  for example, if 4cores  exist, the cur_tick would 4 times incmrent than the read world, i cant fingure out where am a wrong, so, could you figure me out?  thanks for your kinldy supply. 

void z_clock_announce(s32_t ticks)

{

#ifdef CONFIG_TIMESLICING

 z_time_slice(ticks);

#endif

 k_spinlock_key_t key = k_spin_lock(&timeout_lock);

 announce_remaining = ticks;

 while (first() != NULL && first()->dticks <= announce_remaining) {

  struct _timeout *t = first();

  int dt = t->dticks;

  curr_tick += dt;

  announce_remaining -= dt;

  t->dticks = 0;

  remove_timeout(t);

  k_spin_unlock(&timeout_lock, key);

  t->fn(t);

  key = k_spin_lock(&timeout_lock);

 }

 if (first() != NULL) {

  first()->dticks -= announce_remaining;

 }

 curr_tick += announce_remaining;

 announce_remaining = 0;

 z_clock_set_timeout(next_timeout(), false);

 k_spin_unlock(&timeout_lock, key);

}

曹子龙

珠海全志科技股份有限公司      BU1-PSW

地址：广东省珠海市高新区唐家湾镇科技2路9号

TEL：13824125580

Email：caozilong@...

网址： http://www.allwinnertech.com