Hi Krzysztof,

I'm assuming that you're referring to ARM Cortex-A? A patch recently landed to implement switch instead of swap: https://github.com/zephyrproject-rtos/zephyr/pull/27766. There is a GitHub enhancement for ARM64 SMP support https://github.com/zephyrproject-rtos/zephyr/issues/26952 but nobody is working on it AFAIK.

CPU affinity is currently implemented via the k_thread_cpu_mask_* APIs in include/kernel.h. So if you get SMP working on your arch the scheduling infrastructure is there.

This is just the first step, to fully implement SMP you'll need per-cpu variables, IPIs, some extra arch_* APIs implemented, etc. We don't have a porting guide for SMP yet, and having not done this myself I'm not quite an expert in this area but I would reach out to Andy Ross for general SMP enabling questions, and for ARM64 stuff I would coordinate with  Carlo Caione who has done much of the work so far.

We have SMP working on x86_64, ARC, and Xtensa so reviewing that may also be helpful.

HTH

Andrew

Hi everyone,

We are pleased to announce the release of Zephyr RTOS version 2.4.0!

Major enhancements with this release include:

• Introduced initial support for virtual memory management.
• Added Bluetooth host support for periodic advertisement and isochronous channels.
• Enabled the new TCP stack, TCP2, by default. This stack was introduced in Zephyr v2.1.0 to improve network protocol testability with open source tools.
• Introduced a new toolchain abstraction with initial implementations for GCC and LLVM/Clang, and groundwork for future support of commercial toolchains.
• Moved to using C99 integer types and deprecate Zephyr integer types. The Zephyr types can be enabled by Kconfig DEPRECATED_ZEPHYR_INT_TYPES option.

During this release cycle we also:

• Migrated to a new CI infrastructure.
• Started aggregating board farm test results from multiple companies.
• Agreed on a set of MISRA-based coding guidelines and a plan to implement them.
• Reduced a large backlog of low priority bugs.

The detailed release notes can be found here:

https://github.com/zephyrproject-rtos/zephyr/releases/tag/zephyr-v2.4.0

The next release, v2.5.0, is scheduled for January 29^th, 2021. We’ll select a release manager in the next few days. The merge window is now open!

Thank you to everyone that contributed features, documentation, testing, infrastructure, and bug fixes!

Maureen

Hi Maureen,

> The final release remains scheduled for 25 Sep.

I see that one of my PR has not been merged, because there was a merge conflict introduced due to another PR that was merged.

PR: https://github.com/zephyrproject-rtos/zephyr/pull/28089

This PR was submitted 19 days ago, covering a bug reported by a user. It has since not got reviews after repeated reminders to reviewers until “it's a big change that fixes one low priority bug. do we really need it?

“ and “it is this late in the release cycle…” decision being taken. (Discussions in #release slack channel)

There are 142 low priority bugs still open as mentioned in this email chain.

A bug is a bug, an assignee works on a fix during the release stabilization period.

Fix PR could be submitted by assignee before the next Release Candidate, these PR shall be merged else there is no point in classifying medium and low priority if the fixes are not merged because release criteria of < 150 low priority bugs is already met because of other PRs being closed.

There should be a RC4 considering that all medium and low priority bugs having a submitted PR that is passing CI gets reviews/approvals. These PRs can be omitted if there are pending change requests and it is decided to be removed from v2.4 milestone.

Regards,

Vinayak

Hi everyone,

The third release candidate for Zephyr v2.4.0 has been tagged (v2.4.0-rc3). The full release log can be found here:

https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.4.0-rc3

This is hopefully the last release candidate before we finalize the v2.4.0 release. We have satisfied release quality criteria [1] with the exception of one high priority bug. Current bug counts are:

    High: 1

    Medium: 18

    Low: 142

The outstanding high priority bug is to deprecate and remove old k_mem_pool/sys_mem_pool APIs [2]. The TSC decided this week that the PR fixing this bug [3] is too extensive to merge at this late stage of the release cycle. We have documented the mem_pool APIs as deprecated [4], but will wait until after the v2.4.0 release to tag them with the __deprecated attribute and fix in-tree uses, then remove the APIs completely in v2.6.0 LTS.

The purpose of this release candidate is to do one last round of QA testing and finalize release notes. I don’t plan to merge anything other than documentation unless QA testing reveals new bugs that cause us to no longer satisfy release quality criteria.

The final release remains scheduled for 25 Sep.

A big Thank You to everyone that contributed to this release so far, be it with code, reviews, documentation or any other type of contribution!

[1] https://docs.zephyrproject.org/latest/development_process/release_process.html#release-quality-criteria

[2] https://github.com/zephyrproject-rtos/zephyr/issues/24358

[3] https://github.com/zephyrproject-rtos/zephyr/pull/28611

[4] https://github.com/zephyrproject-rtos/zephyr/pull/28646

Maureen

Call for today’s Toolchain WG.

Agenda

• Updates:
• Toolchain related issues for 2.4
• Thomas: IAR: Updates ?
• Zephyr SDK.
• Milestones for 2.5 ?

Feel free to send a mail, if you would like additional topics to be discussed.

Best regards

Torsten T. Rasmussen           

Live meeting minutes: https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/edit#heading=h.x36xe8bnwr9r

________________________________________________________________________________

Join Microsoft Teams Meeting

+1 321-558-6518 United States, Orlando (Toll)

Conference ID: 682 738 030#

Local numbers | Reset PIN | Learn more about Teams | Meeting options

________________________________________________________________________________