From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [RFC/RFT] -cip-rt kernels for review/testing
Date: Sun, 23 Jun 2019 22:37:04 +0200 [thread overview]
Message-ID: <20190623203704.GA12734@amd> (raw)
Hi!
I played a bit with -rt kernels, and here are the results.
v4.19.50-rt22-cip3-rebase was reasonably easy to do, as -cip1 was
empty. v4.4.179-rt181-cip34-rebase was more interesting.
Trees are at kernel.org:
https://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-cip.git/log/?h=v4.4.179-rt181-cip34-rebase
https://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-cip.git/log/?h=v4.19.50-rt22-cip3-rebase
Basically untested. Could I ask for reviews and testing?
I know that full preemption does not work on x86-32. I sent
"PREEMPT_RT_FULL on x86-32 machine" mail to the lists
I don't know how to release useful non-rebasing trees. Is someone
using those?
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190623/bb4ed075/attachment.sig>
next reply other threads:[~2019-06-23 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 20:37 Pavel Machek [this message]
2019-06-24 6:28 ` [cip-dev] [RFC/RFT] -cip-rt kernels for review/testing Jan Kiszka
2019-06-28 8:27 ` Daniel Wagner
2019-07-23 12:15 ` Pavel Machek
2019-07-25 8:37 ` Daniel Wagner
2019-06-25 3:55 ` SZ Lin (林上智)
2019-06-28 12:59 ` [cip-dev] [ANNOUNCE] v4.19.50-cip3-rt1 Pavel Machek
2019-06-28 15:45 ` Jan Kiszka
2019-07-04 18:20 ` Pavel Machek
2019-07-05 8:44 ` Jan Kiszka
2019-07-04 18:29 ` Pavel Machek
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=20190623203704.GA12734@amd \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox