From: Fino Meng <fino.meng@linux.intel.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai@xenomai.org
Subject: Re: Kernel 5.4 status
Date: Mon, 26 Oct 2020 16:23:52 +0800 [thread overview]
Message-ID: <20201026082352.GB17437@linux.intel.com> (raw)
In-Reply-To: <d0dbd921-5127-0acc-a1df-ab5b173b7b00@siemens.com>
On Mon, Oct 26, 2020 at 08:54:54AM +0100, Jan Kiszka via Xenomai wrote:
> Hi all,
>
> a brief update on the porting status to 5.4:
>
> - new noarch ipipe/master is ready:
>
> https://gitlab.denx.de/Xenomai/ipipe-noarch/-/commits/ipipe/master
>
> I've regenerated the queue from Fino's work, reviewing conflict
> resolutions once again. No issues found, well done! I've only done a
> few cleanups and added missing patches from the latest 4.19-noarch.
>
> This should now be a reasonable baseline for porting other archs.
>
> - x86 5.4 branch is also ready:
>
> https://gitlab.denx.de/Xenomai/ipipe-x86/-/commits/ipipe-x86-5.4.y
>
> Here I added the FPU changes, fixing the hard-irqs mask leak and
> hardening an additionally needed path (fpu__clear). I've also done a
> full merge conflict review, and I think I found and fixed issues in
> the kvm code. Still untested, though. I've cleaned up the GTOD update.
> I furthermore fixed missing hard-irqs reenabling in some page-fault
> paths. And added latest x86 patches from 4.19.
>
> - Xenomai next is almost ready:
>
> https://gitlab.denx.de/Xenomai/xenomai/-/commits/next
>
> RTnet and Analogy are not building ATM. That still breaks CI. But the
> result is otherwise working fine, at least in QEMU/KVM. More tests
> welcome!
>
> Jan
>
Thanks Jan, and great team work! We really need Xenomai on newest Linux
kenrel, not only used as bare metal, also working as RTVM in ACRN. We
will contribute more on Xenomai and Dovetail.
BR fino
> --
> Siemens AG, T RDA IOT
> Corporate Competence Center Embedded Linux
>
next prev parent reply other threads:[~2020-10-26 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 7:54 Kernel 5.4 status Jan Kiszka
2020-10-26 8:23 ` Fino Meng [this message]
2020-10-26 13:45 ` Greg Gallagher
2020-10-27 1:32 ` chensong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201026082352.GB17437@linux.intel.com \
--to=fino.meng@linux.intel.com \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.