public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: pavel@ucw.cz (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [OBSOLETE?] CONFIG_PREEMPT_RT_FULL config parameter in 4.19?!
Date: Fri, 19 Jul 2019 15:59:32 +0200	[thread overview]
Message-ID: <20190719135932.GA23951@amd> (raw)
In-Reply-To: <CAEss1E+HzuGDxBCww0dkShV6Wqe-cnSpxCuM_kiq=0TtXOjo-A@mail.gmail.com>

Hi!

> I started my own investigation about RT kernels, namely 4.19. I
> proceed very carefully over the kernel config parameters... BUt the
> last one I inspected today got me nowhere!?
> 
> Seems, that the following config parameters are obsolete in 4.19:
> CONFIG_PREEMPT_RT_FULL
> 
> This one (CONFIG_PREEMPT_RT_FULL) is still present in 4.4 .
> 
> [vuser at fedora30-ssd kernel-config]$ cat CONFIG-4.4.120-rt-bbb | grep PREEMPT
> CONFIG_PREEMPT_RCU=y
> CONFIG_PREEMPT=y
> CONFIG_PREEMPT_RT_BASE=y
> CONFIG_HAVE_PREEMPT_LAZY=y
> CONFIG_PREEMPT_LAZY=y
> # CONFIG_PREEMPT_NONE is not set
> # CONFIG_PREEMPT_VOLUNTARY is not set
> # CONFIG_PREEMPT__LL is not set
> # CONFIG_PREEMPT_RTB is not set
> CONFIG_PREEMPT_RT_FULL=y <<======= Obsolete in 4.19 ?
> CONFIG_PREEMPT_COUNT=y
> CONFIG_DEBUG_PREEMPT=y
> [vuser at fedora30-ssd kernel-config]$
> 
> What I should do to maintain RT-kernel-4.19? It is obvious, I must/need to set:
> CONFIG_PREEMPT=y

Are you sure you have your kernel patched with -rt patches?
CONFIG_PREEMPT_RT_FULL=y was still needed in 4.19, AFAICT.

Note that not every piece of hardware has suitable characteristics for
realtime / low latencies.

Best regards,
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- 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/20190719/72b0ce91/attachment-0001.sig>

  parent reply	other threads:[~2019-07-19 13:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19 13:31 [cip-dev] [OBSOLETE?] CONFIG_PREEMPT_RT_FULL config parameter in 4.19?! Zoran S
2019-07-19 13:58 ` Ben Hutchings
2019-07-19 17:58   ` Zoran S
2019-07-19 18:11     ` Ben Hutchings
2019-07-19 19:03       ` Zoran S
2019-07-19 19:08         ` Daniel Wagner
2019-07-19 13:59 ` Pavel Machek [this message]
2019-07-19 18:05   ` Zoran S

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=20190719135932.GA23951@amd \
    --to=pavel@ucw.cz \
    --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