LKML Archive on
help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <>
To: Thomas Gleixner <>
Cc: LKML <>,
	linux-rt-users <>,
	Steven Rostedt <>
Subject: [ANNOUNCE] v5.0.3-rt1
Date: Wed, 20 Mar 2019 18:15:12 +0100	[thread overview]
Message-ID: <> (raw)

Dear RT folks!

I'm pleased to announce the v5.0.3-rt1 patch set. 

Changes since v4.19.25-rt16:

  - rebase to v5.0

  - Several ARM architectures have a so called "boot_lock" in their SMP
    bring up code. In previous releases the boot_lock was converted to
    to a raw_spinlock in order to get in working on -RT. As of v5.0 only the
    bits for the `versatile' platform have been applied upstream and I
    dropped the patch entirely.
    The other platforms were rejected because they were doing it wrong by
    using such a lock. The omap2 and sti platform were converted to other
    mechanism as part of the discussion. Others (like i.MX) were never
    using such a lock.
    There are still a few platforms using such a lock. If you are
    affected you would to convince the platform maintainer to remove the
    lock from the SMP code.

  - Applied John Ogness' prinkt rework. One visible change is the
    output during boot. Under the hood and for RT: By default, output
    that is created at KERN_WARN[0] or higher is printed immediately if the
    console supports "atomic" print (currently the 8250 driver does).
    This output is printed immediately (and visible) even from IRQ-off
    or preempt-disabled regions which wasn't the case earlier. This will
    raise the latency at run-time *but* there should be no WARNING,
    ERROR or PANIC messages at run-time on a fully working system.
    Messages with lower severity are printed "later" by a kthread.

    [0] default message level, default_message_loglevel, second field in

  - Applied "restore FPU on return to userland" series. This only
    applies to x86. This change makes repeated kernel_fpu_begin() +
    kernel_fpu_end() cheap.

  - I tried to include some BH related rework but it is not yet in
    reasonable shape. I will probably revisit this during the v5.0

Known issues
     - A warning triggered in "rcu_note_context_switch" originated from
       SyS_timer_gettime(). The issue was always there, it is now
       visible. Reported by Grygorii Strashko and Daniel Wagner.

     - rcutorture is currently broken on -RT. Reported by Juri Lelli.

You can get this release via the git tree at:

    git:// v5.0.3-rt1

The RT patch against v5.0.3 can be found here:

The split quilt queue is available at:


             reply	other threads:[~2019-03-20 17:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20 17:15 Sebastian Andrzej Siewior [this message]
2019-03-22 18:52 ` Julien Grall
2019-03-25  8:13   ` John Ogness
2019-03-25 10:18     ` Julien Grall
2019-03-25 10:34       ` John Ogness
2019-03-26 10:26         ` Julien Grall
2019-03-26 16:04           ` John Ogness
2019-03-27 18:33 ` [PATCH 1/4] printk: An all-in-one commit to fix build failures Sebastian Andrzej Siewior
2019-03-27 18:33   ` [PATCH 2/4] powerpc/stackprotector: work around stack-guard init from atomic Sebastian Andrzej Siewior
2019-05-10 21:46     ` Steven Rostedt
2019-03-27 18:33   ` [PATCH 3/4] powerpc/pseries/iommu: Use a locallock instead local_irq_save() Sebastian Andrzej Siewior
2019-03-27 18:33   ` [PATCH 4/4] powerpc: reshuffle TIF bits Sebastian Andrzej Siewior

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: [ANNOUNCE] v5.0.3-rt1' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).