diff --git a/debian/changelog b/debian/changelog index 78999bf15..61fc4025e 100644 --- a/debian/changelog +++ b/debian/changelog @@ -469,6 +469,7 @@ linux (4.19.127-1) UNRELEASED; urgency=medium * nfsd: apply umask on fs without ACL support (Closes: #962254) * [rt] Update to 4.19.120-rt52 * [rt] Update to 4.19.124-rt53 + * [rt] Update to 4.19.127-rt55 -- Salvatore Bonaccorso Wed, 13 May 2020 17:44:43 +0200 diff --git a/debian/patches-rt/0001-ARM-at91-add-TCB-registers-definitions.patch b/debian/patches-rt/0001-ARM-at91-add-TCB-registers-definitions.patch index d1b91d90e..608006640 100644 --- a/debian/patches-rt/0001-ARM-at91-add-TCB-registers-definitions.patch +++ b/debian/patches-rt/0001-ARM-at91-add-TCB-registers-definitions.patch @@ -1,9 +1,9 @@ -From 4f310e18bbb62e33196484e72d1a7d0416189d63 Mon Sep 17 00:00:00 2001 -Message-Id: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 07cd0dbc80b976663c80755496a03f288decfe5a Mon Sep 17 00:00:00 2001 +Message-Id: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:18 +0200 -Subject: [PATCH 001/327] ARM: at91: add TCB registers definitions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 001/330] ARM: at91: add TCB registers definitions +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Add registers and bits definitions for the timer counter blocks found on Atmel ARM SoCs. diff --git a/debian/patches-rt/0002-clocksource-drivers-Add-a-new-driver-for-the-Atmel-A.patch b/debian/patches-rt/0002-clocksource-drivers-Add-a-new-driver-for-the-Atmel-A.patch index 9a566add3..754662878 100644 --- a/debian/patches-rt/0002-clocksource-drivers-Add-a-new-driver-for-the-Atmel-A.patch +++ b/debian/patches-rt/0002-clocksource-drivers-Add-a-new-driver-for-the-Atmel-A.patch @@ -1,12 +1,12 @@ -From e255d2aa2e1906721ff1c5570d33884cd2fec55f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 3a7e05ef840a3ba6b67e57c983330a57fd7a6e65 Mon Sep 17 00:00:00 2001 +Message-Id: <3a7e05ef840a3ba6b67e57c983330a57fd7a6e65.1592846146.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:19 +0200 -Subject: [PATCH 002/327] clocksource/drivers: Add a new driver for the Atmel +Subject: [PATCH 002/330] clocksource/drivers: Add a new driver for the Atmel ARM TC blocks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Add a driver for the Atmel Timer Counter Blocks. This driver provides a clocksource and two clockevent devices. diff --git a/debian/patches-rt/0003-clocksource-drivers-timer-atmel-tcb-add-clockevent-d.patch b/debian/patches-rt/0003-clocksource-drivers-timer-atmel-tcb-add-clockevent-d.patch index 74a4efdf5..ea5489041 100644 --- a/debian/patches-rt/0003-clocksource-drivers-timer-atmel-tcb-add-clockevent-d.patch +++ b/debian/patches-rt/0003-clocksource-drivers-timer-atmel-tcb-add-clockevent-d.patch @@ -1,12 +1,12 @@ -From 1eb3e20b534521ca26b7f0bac47a840640ddab9b Mon Sep 17 00:00:00 2001 -Message-Id: <1eb3e20b534521ca26b7f0bac47a840640ddab9b.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d6eb03e5f67486085de39ec702182866ffdced2b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:20 +0200 -Subject: [PATCH 003/327] clocksource/drivers: timer-atmel-tcb: add clockevent +Subject: [PATCH 003/330] clocksource/drivers: timer-atmel-tcb: add clockevent device on separate channel -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Add an other clockevent device that uses a separate TCB channel when available. diff --git a/debian/patches-rt/0004-clocksource-drivers-atmel-pit-make-option-silent.patch b/debian/patches-rt/0004-clocksource-drivers-atmel-pit-make-option-silent.patch index 4192305d1..5fc03f9b7 100644 --- a/debian/patches-rt/0004-clocksource-drivers-atmel-pit-make-option-silent.patch +++ b/debian/patches-rt/0004-clocksource-drivers-atmel-pit-make-option-silent.patch @@ -1,11 +1,11 @@ -From 1fd848b0c640a606d536a935016238ba6e26e84e Mon Sep 17 00:00:00 2001 -Message-Id: <1fd848b0c640a606d536a935016238ba6e26e84e.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From a6a73dbfa9364e274c53e48d7688f6e8ec5590e4 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:21 +0200 -Subject: [PATCH 004/327] clocksource/drivers: atmel-pit: make option silent -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 004/330] clocksource/drivers: atmel-pit: make option silent +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz To conform with the other option, make the ATMEL_PIT option silent so it can be selected from the platform diff --git a/debian/patches-rt/0005-ARM-at91-Implement-clocksource-selection.patch b/debian/patches-rt/0005-ARM-at91-Implement-clocksource-selection.patch index 2ff94818a..f842553bf 100644 --- a/debian/patches-rt/0005-ARM-at91-Implement-clocksource-selection.patch +++ b/debian/patches-rt/0005-ARM-at91-Implement-clocksource-selection.patch @@ -1,11 +1,11 @@ -From b18d5a54259f5181ff68dd524e0d39022a454b62 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From df1a4ba0a8f32ea01c78c697ec86f13cce3ef643 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:22 +0200 -Subject: [PATCH 005/327] ARM: at91: Implement clocksource selection -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 005/330] ARM: at91: Implement clocksource selection +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Allow selecting and unselecting the PIT clocksource driver so it doesn't have to be compile when unused. diff --git a/debian/patches-rt/0006-ARM-configs-at91-use-new-TCB-timer-driver.patch b/debian/patches-rt/0006-ARM-configs-at91-use-new-TCB-timer-driver.patch index 8fdd796bf..ae0080c76 100644 --- a/debian/patches-rt/0006-ARM-configs-at91-use-new-TCB-timer-driver.patch +++ b/debian/patches-rt/0006-ARM-configs-at91-use-new-TCB-timer-driver.patch @@ -1,11 +1,11 @@ -From dbab7bb656e42051b6f7866ab056b683d6bedd58 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From dcb2bbcbb30d20da84674245778e0331a11506db Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:23 +0200 -Subject: [PATCH 006/327] ARM: configs: at91: use new TCB timer driver -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 006/330] ARM: configs: at91: use new TCB timer driver +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Unselecting ATMEL_TCLIB switches the TCB timer driver from tcb_clksrc to timer-atmel-tcb. diff --git a/debian/patches-rt/0007-ARM-configs-at91-unselect-PIT.patch b/debian/patches-rt/0007-ARM-configs-at91-unselect-PIT.patch index c5f23537b..91398ac6e 100644 --- a/debian/patches-rt/0007-ARM-configs-at91-unselect-PIT.patch +++ b/debian/patches-rt/0007-ARM-configs-at91-unselect-PIT.patch @@ -1,11 +1,11 @@ -From 9154d0d7c52c6357fc510b50289fc4613f0915fa Mon Sep 17 00:00:00 2001 -Message-Id: <9154d0d7c52c6357fc510b50289fc4613f0915fa.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 53515792129df60191ffab76cbcb7e98acbfb445 Mon Sep 17 00:00:00 2001 +Message-Id: <53515792129df60191ffab76cbcb7e98acbfb445.1592846146.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:24 +0200 -Subject: [PATCH 007/327] ARM: configs: at91: unselect PIT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 007/330] ARM: configs: at91: unselect PIT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The PIT is not required anymore to successfully boot and may actually harm in case preempt-rt is used because the PIT interrupt is shared. diff --git a/debian/patches-rt/0008-irqchip-gic-v3-its-Move-pending-table-allocation-to-.patch b/debian/patches-rt/0008-irqchip-gic-v3-its-Move-pending-table-allocation-to-.patch index 342196ece..b7f4354ee 100644 --- a/debian/patches-rt/0008-irqchip-gic-v3-its-Move-pending-table-allocation-to-.patch +++ b/debian/patches-rt/0008-irqchip-gic-v3-its-Move-pending-table-allocation-to-.patch @@ -1,12 +1,12 @@ -From 1ae7995f17f7d1635b4070389a1091a9444b19ac Mon Sep 17 00:00:00 2001 -Message-Id: <1ae7995f17f7d1635b4070389a1091a9444b19ac.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 63a0ba1dbc5b216456c687723511cf8e3c4c5cf7 Mon Sep 17 00:00:00 2001 +Message-Id: <63a0ba1dbc5b216456c687723511cf8e3c4c5cf7.1592846146.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Marc Zyngier Date: Fri, 27 Jul 2018 13:38:54 +0100 -Subject: [PATCH 008/327] irqchip/gic-v3-its: Move pending table allocation to +Subject: [PATCH 008/330] irqchip/gic-v3-its: Move pending table allocation to init time -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Signed-off-by: Marc Zyngier Signed-off-by: Sebastian Andrzej Siewior diff --git a/debian/patches-rt/0009-kthread-convert-worker-lock-to-raw-spinlock.patch b/debian/patches-rt/0009-kthread-convert-worker-lock-to-raw-spinlock.patch index 0def24b88..74053e536 100644 --- a/debian/patches-rt/0009-kthread-convert-worker-lock-to-raw-spinlock.patch +++ b/debian/patches-rt/0009-kthread-convert-worker-lock-to-raw-spinlock.patch @@ -1,11 +1,11 @@ -From 57ff6e8d36212caf843344a17c6a1e8a1704d3b7 Mon Sep 17 00:00:00 2001 -Message-Id: <57ff6e8d36212caf843344a17c6a1e8a1704d3b7.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 2b88f6517aa1aae701189bc677e368206ec2dfaa Mon Sep 17 00:00:00 2001 +Message-Id: <2b88f6517aa1aae701189bc677e368206ec2dfaa.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Julia Cartwright Date: Fri, 28 Sep 2018 21:03:51 +0000 -Subject: [PATCH 009/327] kthread: convert worker lock to raw spinlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 009/330] kthread: convert worker lock to raw spinlock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz In order to enable the queuing of kthread work items from hardirq context even when PREEMPT_RT_FULL is enabled, convert the worker diff --git a/debian/patches-rt/0010-crypto-caam-qi-simplify-CGR-allocation-freeing.patch b/debian/patches-rt/0010-crypto-caam-qi-simplify-CGR-allocation-freeing.patch index c4dd44278..ddfd3a17b 100644 --- a/debian/patches-rt/0010-crypto-caam-qi-simplify-CGR-allocation-freeing.patch +++ b/debian/patches-rt/0010-crypto-caam-qi-simplify-CGR-allocation-freeing.patch @@ -1,14 +1,14 @@ -From 48610c50b1eff4d562b785d41ad6baae1f9f311f Mon Sep 17 00:00:00 2001 -Message-Id: <48610c50b1eff4d562b785d41ad6baae1f9f311f.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From ece8b73ec8e440bd4a31c3e365262f6f77321377 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: =?UTF-8?q?Horia=20Geant=C4=83?= Date: Mon, 8 Oct 2018 14:09:37 +0300 -Subject: [PATCH 010/327] crypto: caam/qi - simplify CGR allocation, freeing +Subject: [PATCH 010/330] crypto: caam/qi - simplify CGR allocation, freeing MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [Upstream commit 29e83c757006fd751966bdc53392bb22d74179c6] diff --git a/debian/patches-rt/0011-sched-fair-Robustify-CFS-bandwidth-timer-locking.patch b/debian/patches-rt/0011-sched-fair-Robustify-CFS-bandwidth-timer-locking.patch index b93c4227b..408d15142 100644 --- a/debian/patches-rt/0011-sched-fair-Robustify-CFS-bandwidth-timer-locking.patch +++ b/debian/patches-rt/0011-sched-fair-Robustify-CFS-bandwidth-timer-locking.patch @@ -1,11 +1,11 @@ -From 6b25155aabb22bf66e94098b75e72bc8df337351 Mon Sep 17 00:00:00 2001 -Message-Id: <6b25155aabb22bf66e94098b75e72bc8df337351.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 523d1d6151bf8e68c3a6f27bfa42f3166966a8c7 Mon Sep 17 00:00:00 2001 +Message-Id: <523d1d6151bf8e68c3a6f27bfa42f3166966a8c7.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 7 Jan 2019 13:52:31 +0100 -Subject: [PATCH 011/327] sched/fair: Robustify CFS-bandwidth timer locking -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 011/330] sched/fair: Robustify CFS-bandwidth timer locking +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Traditionally hrtimer callbacks were run with IRQs disabled, but with the introduction of HRTIMER_MODE_SOFT it is possible they run from diff --git a/debian/patches-rt/0012-arm-Convert-arm-boot_lock-to-raw.patch b/debian/patches-rt/0012-arm-Convert-arm-boot_lock-to-raw.patch index 447a14326..3c68906ec 100644 --- a/debian/patches-rt/0012-arm-Convert-arm-boot_lock-to-raw.patch +++ b/debian/patches-rt/0012-arm-Convert-arm-boot_lock-to-raw.patch @@ -1,11 +1,11 @@ -From 404266779320e3b3e55c3f87b1f83e2e5ee671b8 Mon Sep 17 00:00:00 2001 -Message-Id: <404266779320e3b3e55c3f87b1f83e2e5ee671b8.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From b5330f7774aae315712657ef2004c84d1085246d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Frank Rowand Date: Mon, 19 Sep 2011 14:51:14 -0700 -Subject: [PATCH 012/327] arm: Convert arm boot_lock to raw -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 012/330] arm: Convert arm boot_lock to raw +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The arm boot_lock is used by the secondary processor startup code. The locking task is the idle thread, which has idle->sched_class == &idle_sched_class. diff --git a/debian/patches-rt/0013-x86-ioapic-Don-t-let-setaffinity-unmask-threaded-EOI.patch b/debian/patches-rt/0013-x86-ioapic-Don-t-let-setaffinity-unmask-threaded-EOI.patch index cb61d3620..478bb2a06 100644 --- a/debian/patches-rt/0013-x86-ioapic-Don-t-let-setaffinity-unmask-threaded-EOI.patch +++ b/debian/patches-rt/0013-x86-ioapic-Don-t-let-setaffinity-unmask-threaded-EOI.patch @@ -1,12 +1,12 @@ -From 963d7de788ad8f43cc5332a1921be8b5c205b36b Mon Sep 17 00:00:00 2001 -Message-Id: <963d7de788ad8f43cc5332a1921be8b5c205b36b.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 9fc24b69a709c6f6dffa94b71a56c271dd6211c0 Mon Sep 17 00:00:00 2001 +Message-Id: <9fc24b69a709c6f6dffa94b71a56c271dd6211c0.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 17 Jul 2018 18:25:31 +0200 -Subject: [PATCH 013/327] x86/ioapic: Don't let setaffinity unmask threaded EOI +Subject: [PATCH 013/330] x86/ioapic: Don't let setaffinity unmask threaded EOI interrupt too early -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz There is an issue with threaded interrupts which are marked ONESHOT and using the fasteoi handler. diff --git a/debian/patches-rt/0014-cgroup-use-irqsave-in-cgroup_rstat_flush_locked.patch b/debian/patches-rt/0014-cgroup-use-irqsave-in-cgroup_rstat_flush_locked.patch index 62ce999a6..cc6a1ff9c 100644 --- a/debian/patches-rt/0014-cgroup-use-irqsave-in-cgroup_rstat_flush_locked.patch +++ b/debian/patches-rt/0014-cgroup-use-irqsave-in-cgroup_rstat_flush_locked.patch @@ -1,11 +1,11 @@ -From d08761b3bc9c131e839d1ef186515fabf2f43812 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 4a35b70a502fad9d53627081bf02ba98ed08ae4e Mon Sep 17 00:00:00 2001 +Message-Id: <4a35b70a502fad9d53627081bf02ba98ed08ae4e.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 3 Jul 2018 18:19:48 +0200 -Subject: [PATCH 014/327] cgroup: use irqsave in cgroup_rstat_flush_locked() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 014/330] cgroup: use irqsave in cgroup_rstat_flush_locked() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz All callers of cgroup_rstat_flush_locked() acquire cgroup_rstat_lock either with spin_lock_irq() or spin_lock_irqsave(). @@ -25,10 +25,10 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/kernel/cgroup/rstat.c b/kernel/cgroup/rstat.c -index bb95a35e8c2d..3266a9781b4e 100644 +index d0ed410b4127..3c949c46c6b3 100644 --- a/kernel/cgroup/rstat.c +++ b/kernel/cgroup/rstat.c -@@ -159,8 +159,9 @@ static void cgroup_rstat_flush_locked(struct cgroup *cgrp, bool may_sleep) +@@ -149,8 +149,9 @@ static void cgroup_rstat_flush_locked(struct cgroup *cgrp, bool may_sleep) raw_spinlock_t *cpu_lock = per_cpu_ptr(&cgroup_rstat_cpu_lock, cpu); struct cgroup *pos = NULL; @@ -39,7 +39,7 @@ index bb95a35e8c2d..3266a9781b4e 100644 while ((pos = cgroup_rstat_cpu_pop_updated(pos, cgrp, cpu))) { struct cgroup_subsys_state *css; -@@ -172,7 +173,7 @@ static void cgroup_rstat_flush_locked(struct cgroup *cgrp, bool may_sleep) +@@ -162,7 +163,7 @@ static void cgroup_rstat_flush_locked(struct cgroup *cgrp, bool may_sleep) css->ss->css_rstat_flush(css, cpu); rcu_read_unlock(); } diff --git a/debian/patches-rt/0015-fscache-initialize-cookie-hash-table-raw-spinlocks.patch b/debian/patches-rt/0015-fscache-initialize-cookie-hash-table-raw-spinlocks.patch index f7988dcc2..0ef74583e 100644 --- a/debian/patches-rt/0015-fscache-initialize-cookie-hash-table-raw-spinlocks.patch +++ b/debian/patches-rt/0015-fscache-initialize-cookie-hash-table-raw-spinlocks.patch @@ -1,11 +1,11 @@ -From 133c250518b207fed8973a6b6af5b60712bcc73a Mon Sep 17 00:00:00 2001 -Message-Id: <133c250518b207fed8973a6b6af5b60712bcc73a.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From a2f42d911a79b4a69a234abb2540b7e45e136358 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Clark Williams Date: Tue, 3 Jul 2018 13:34:30 -0500 -Subject: [PATCH 015/327] fscache: initialize cookie hash table raw spinlocks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 015/330] fscache: initialize cookie hash table raw spinlocks +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The fscache cookie mechanism uses a hash table of hlist_bl_head structures. The PREEMPT_RT patcheset adds a raw spinlock to this structure and so on PREEMPT_RT diff --git a/debian/patches-rt/0016-Drivers-hv-vmbus-include-header-for-get_irq_regs.patch b/debian/patches-rt/0016-Drivers-hv-vmbus-include-header-for-get_irq_regs.patch index 63a3f4b39..405516b68 100644 --- a/debian/patches-rt/0016-Drivers-hv-vmbus-include-header-for-get_irq_regs.patch +++ b/debian/patches-rt/0016-Drivers-hv-vmbus-include-header-for-get_irq_regs.patch @@ -1,14 +1,14 @@ -From d6e772d4b5a7e8136969acc1fdd0fa85b000fe12 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From ed83918632048e1a2aaeef2357ac17050d4c0897 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 29 Aug 2018 21:59:04 +0200 -Subject: [PATCH 016/327] Drivers: hv: vmbus: include header for get_irq_regs() +Subject: [PATCH 016/330] Drivers: hv: vmbus: include header for get_irq_regs() MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz On !RT the header file get_irq_regs() gets pulled in via other header files. On RT it does not and the build fails: diff --git a/debian/patches-rt/0017-percpu-include-irqflags.h-for-raw_local_irq_save.patch b/debian/patches-rt/0017-percpu-include-irqflags.h-for-raw_local_irq_save.patch index 01b7ac6d7..5d572b544 100644 --- a/debian/patches-rt/0017-percpu-include-irqflags.h-for-raw_local_irq_save.patch +++ b/debian/patches-rt/0017-percpu-include-irqflags.h-for-raw_local_irq_save.patch @@ -1,11 +1,11 @@ -From a7569b22f3f504f5437cf35486d263269e69fe82 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 67955e639b641e0d236cb72fbfb78d513f815ce4 Mon Sep 17 00:00:00 2001 +Message-Id: <67955e639b641e0d236cb72fbfb78d513f815ce4.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 11 Oct 2018 16:39:59 +0200 -Subject: [PATCH 017/327] percpu: include irqflags.h for raw_local_irq_save() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 017/330] percpu: include irqflags.h for raw_local_irq_save() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The header percpu.h header file is using raw_local_irq_save() but does not include irqflags.h for its definition. It compiles because the diff --git a/debian/patches-rt/0018-efi-Allow-efi-runtime.patch b/debian/patches-rt/0018-efi-Allow-efi-runtime.patch index b4e44b643..ce6ede502 100644 --- a/debian/patches-rt/0018-efi-Allow-efi-runtime.patch +++ b/debian/patches-rt/0018-efi-Allow-efi-runtime.patch @@ -1,11 +1,11 @@ -From 1687401d2d9cf76ef1bc95b39c9436df2b1dc5cb Mon Sep 17 00:00:00 2001 -Message-Id: <1687401d2d9cf76ef1bc95b39c9436df2b1dc5cb.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 87a59b5dfefbfe6ef7dbf349b524e3fb175f10bc Mon Sep 17 00:00:00 2001 +Message-Id: <87a59b5dfefbfe6ef7dbf349b524e3fb175f10bc.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 15:06:10 +0200 -Subject: [PATCH 018/327] efi: Allow efi=runtime -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 018/330] efi: Allow efi=runtime +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz In case the option "efi=noruntime" is default at built-time, the user could overwrite its sate by `efi=runtime' and allow it again. diff --git a/debian/patches-rt/0019-x86-efi-drop-task_lock-from-efi_switch_mm.patch b/debian/patches-rt/0019-x86-efi-drop-task_lock-from-efi_switch_mm.patch index c5ef9d3b5..84b83ae72 100644 --- a/debian/patches-rt/0019-x86-efi-drop-task_lock-from-efi_switch_mm.patch +++ b/debian/patches-rt/0019-x86-efi-drop-task_lock-from-efi_switch_mm.patch @@ -1,11 +1,11 @@ -From 6f9e192258cc14e3ad3b988e93f3557e222a56fd Mon Sep 17 00:00:00 2001 -Message-Id: <6f9e192258cc14e3ad3b988e93f3557e222a56fd.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From f58b1dce5d7d97bb8d531d1fd82229f63d9f365f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 24 Jul 2018 14:48:55 +0200 -Subject: [PATCH 019/327] x86/efi: drop task_lock() from efi_switch_mm() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 019/330] x86/efi: drop task_lock() from efi_switch_mm() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz efi_switch_mm() is a wrapper around switch_mm() which saves current's ->active_mm, sets the requests mm as ->active_mm and invokes diff --git a/debian/patches-rt/0020-arm64-KVM-compute_layout-before-altenates-are-applie.patch b/debian/patches-rt/0020-arm64-KVM-compute_layout-before-altenates-are-applie.patch index 65d653ad0..8469b4d65 100644 --- a/debian/patches-rt/0020-arm64-KVM-compute_layout-before-altenates-are-applie.patch +++ b/debian/patches-rt/0020-arm64-KVM-compute_layout-before-altenates-are-applie.patch @@ -1,12 +1,12 @@ -From 1558047d61e27b21f0d85ed68cfaf00ee2fcd9f8 Mon Sep 17 00:00:00 2001 -Message-Id: <1558047d61e27b21f0d85ed68cfaf00ee2fcd9f8.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From cee4251021086c8806b95fe27a3587c416343b27 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 09:13:42 +0200 -Subject: [PATCH 020/327] arm64: KVM: compute_layout before altenates are +Subject: [PATCH 020/330] arm64: KVM: compute_layout before altenates are applied -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz compute_layout() is invoked as part of an alternative fixup under stop_machine() and needs a sleeping lock as part of get_random_long(). diff --git a/debian/patches-rt/0021-of-allocate-free-phandle-cache-outside-of-the-devtre.patch b/debian/patches-rt/0021-of-allocate-free-phandle-cache-outside-of-the-devtre.patch index 91ad50fd3..e7ea3f6d4 100644 --- a/debian/patches-rt/0021-of-allocate-free-phandle-cache-outside-of-the-devtre.patch +++ b/debian/patches-rt/0021-of-allocate-free-phandle-cache-outside-of-the-devtre.patch @@ -1,12 +1,12 @@ -From 1db75db4b2bf05b9e72d82a8c67014c5ebe68277 Mon Sep 17 00:00:00 2001 -Message-Id: <1db75db4b2bf05b9e72d82a8c67014c5ebe68277.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8231839ea6b5b1d00e3c51e5a95fc05fad1e4b3d Mon Sep 17 00:00:00 2001 +Message-Id: <8231839ea6b5b1d00e3c51e5a95fc05fad1e4b3d.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 31 Aug 2018 14:16:30 +0200 -Subject: [PATCH 021/327] of: allocate / free phandle cache outside of the +Subject: [PATCH 021/330] of: allocate / free phandle cache outside of the devtree_lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The phandle cache code allocates memory while holding devtree_lock which is a raw_spinlock_t. Memory allocation (and free()) is not possible on diff --git a/debian/patches-rt/0022-mm-kasan-make-quarantine_lock-a-raw_spinlock_t.patch b/debian/patches-rt/0022-mm-kasan-make-quarantine_lock-a-raw_spinlock_t.patch index a66010ac2..67fc888c6 100644 --- a/debian/patches-rt/0022-mm-kasan-make-quarantine_lock-a-raw_spinlock_t.patch +++ b/debian/patches-rt/0022-mm-kasan-make-quarantine_lock-a-raw_spinlock_t.patch @@ -1,11 +1,11 @@ -From d48a743e6790c2b04b2aded80a118472a82252e8 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From ddfc22e4646ebd7625c8406cee2c82dc9e706eeb Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Clark Williams Date: Tue, 18 Sep 2018 10:29:31 -0500 -Subject: [PATCH 022/327] mm/kasan: make quarantine_lock a raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 022/330] mm/kasan: make quarantine_lock a raw_spinlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The static lock quarantine_lock is used in quarantine.c to protect the quarantine queue datastructures. It is taken inside quarantine queue diff --git a/debian/patches-rt/0023-EXP-rcu-Revert-expedited-GP-parallelization-cleverne.patch b/debian/patches-rt/0023-EXP-rcu-Revert-expedited-GP-parallelization-cleverne.patch index 70f359a08..d58d6ce33 100644 --- a/debian/patches-rt/0023-EXP-rcu-Revert-expedited-GP-parallelization-cleverne.patch +++ b/debian/patches-rt/0023-EXP-rcu-Revert-expedited-GP-parallelization-cleverne.patch @@ -1,12 +1,12 @@ -From 90ec710ee45bcaa48b73ef6865fbfd5d6aaffcc4 Mon Sep 17 00:00:00 2001 -Message-Id: <90ec710ee45bcaa48b73ef6865fbfd5d6aaffcc4.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 663ee9b36ce5702a7109f98003e5ac144c147ce8 Mon Sep 17 00:00:00 2001 +Message-Id: <663ee9b36ce5702a7109f98003e5ac144c147ce8.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Mon, 29 Oct 2018 11:53:01 +0100 -Subject: [PATCH 023/327] EXP rcu: Revert expedited GP parallelization +Subject: [PATCH 023/330] EXP rcu: Revert expedited GP parallelization cleverness -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz (Commit 258ba8e089db23f760139266c232f01bad73f85c from linux-rcu) diff --git a/debian/patches-rt/0024-kmemleak-Turn-kmemleak_lock-to-raw-spinlock-on-RT.patch b/debian/patches-rt/0024-kmemleak-Turn-kmemleak_lock-to-raw-spinlock-on-RT.patch index 7f9af1f4a..57e0156b2 100644 --- a/debian/patches-rt/0024-kmemleak-Turn-kmemleak_lock-to-raw-spinlock-on-RT.patch +++ b/debian/patches-rt/0024-kmemleak-Turn-kmemleak_lock-to-raw-spinlock-on-RT.patch @@ -1,14 +1,14 @@ -From a2642ecac08a5ee9ac4ea60bed4017aee8b24311 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 4b563ec476c710e76b14442995b3bc33a0080378 Mon Sep 17 00:00:00 2001 +Message-Id: <4b563ec476c710e76b14442995b3bc33a0080378.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: He Zhe Date: Wed, 19 Dec 2018 16:30:57 +0100 -Subject: [PATCH 024/327] kmemleak: Turn kmemleak_lock to raw spinlock on RT +Subject: [PATCH 024/330] kmemleak: Turn kmemleak_lock to raw spinlock on RT MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz kmemleak_lock, as a rwlock on RT, can possibly be held in atomic context and causes the follow BUG. diff --git a/debian/patches-rt/0025-NFSv4-replace-seqcount_t-with-a-seqlock_t.patch b/debian/patches-rt/0025-NFSv4-replace-seqcount_t-with-a-seqlock_t.patch index e1360d8d6..b940c21d2 100644 --- a/debian/patches-rt/0025-NFSv4-replace-seqcount_t-with-a-seqlock_t.patch +++ b/debian/patches-rt/0025-NFSv4-replace-seqcount_t-with-a-seqlock_t.patch @@ -1,11 +1,11 @@ -From 20a77d5d5ac10b654a565988835117a28aeb0af1 Mon Sep 17 00:00:00 2001 -Message-Id: <20a77d5d5ac10b654a565988835117a28aeb0af1.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 7b19ab6d7165436a3b6f7d398b04fe5b3c43f1b8 Mon Sep 17 00:00:00 2001 +Message-Id: <7b19ab6d7165436a3b6f7d398b04fe5b3c43f1b8.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 28 Oct 2016 23:05:11 +0200 -Subject: [PATCH 025/327] NFSv4: replace seqcount_t with a seqlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 025/330] NFSv4: replace seqcount_t with a seqlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The raw_write_seqcount_begin() in nfs4_reclaim_open_state() bugs me because it maps to preempt_disable() in -RT which I can't have at this diff --git a/debian/patches-rt/0026-kernel-sched-Provide-a-pointer-to-the-valid-CPU-mask.patch b/debian/patches-rt/0026-kernel-sched-Provide-a-pointer-to-the-valid-CPU-mask.patch index 54652ce8a..1cea55bcb 100644 --- a/debian/patches-rt/0026-kernel-sched-Provide-a-pointer-to-the-valid-CPU-mask.patch +++ b/debian/patches-rt/0026-kernel-sched-Provide-a-pointer-to-the-valid-CPU-mask.patch @@ -1,15 +1,15 @@ -From c440d254bb20fa3d293214b24f7ec84e751996e5 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From b2bcf442a6169f3511183be2d5add38de01e7122 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 4 Apr 2017 12:50:16 +0200 -Subject: [PATCH 026/327] kernel: sched: Provide a pointer to the valid CPU +Subject: [PATCH 026/330] kernel: sched: Provide a pointer to the valid CPU mask MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz In commit 4b53a3412d66 ("sched/core: Remove the tsk_nr_cpus_allowed() wrapper") the tsk_nr_cpus_allowed() wrapper was removed. There was not diff --git a/debian/patches-rt/0027-kernel-sched-core-add-migrate_disable.patch b/debian/patches-rt/0027-kernel-sched-core-add-migrate_disable.patch index 02f7c2bb1..c8550fd6c 100644 --- a/debian/patches-rt/0027-kernel-sched-core-add-migrate_disable.patch +++ b/debian/patches-rt/0027-kernel-sched-core-add-migrate_disable.patch @@ -1,11 +1,11 @@ -From 478a0edd893bd9a88dba5a9c184b1e05cde79f97 Mon Sep 17 00:00:00 2001 -Message-Id: <478a0edd893bd9a88dba5a9c184b1e05cde79f97.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From bc21ea67b9b00e94aab5f17c15e4ebfc04c16d32 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Sat, 27 May 2017 19:02:06 +0200 -Subject: [PATCH 027/327] kernel/sched/core: add migrate_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 027/330] kernel/sched/core: add migrate_disable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz --- include/linux/preempt.h | 23 +++++++ diff --git a/debian/patches-rt/0028-sched-migrate_disable-Add-export_symbol_gpl-for-__mi.patch b/debian/patches-rt/0028-sched-migrate_disable-Add-export_symbol_gpl-for-__mi.patch index 345678259..d753dc3bb 100644 --- a/debian/patches-rt/0028-sched-migrate_disable-Add-export_symbol_gpl-for-__mi.patch +++ b/debian/patches-rt/0028-sched-migrate_disable-Add-export_symbol_gpl-for-__mi.patch @@ -1,12 +1,12 @@ -From 1e2b24fdfb06ea49b4b86e3e09ff185a298ece74 Mon Sep 17 00:00:00 2001 -Message-Id: <1e2b24fdfb06ea49b4b86e3e09ff185a298ece74.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 7c2d3cd530fafd2579f51fdf728efac5efa06e64 Mon Sep 17 00:00:00 2001 +Message-Id: <7c2d3cd530fafd2579f51fdf728efac5efa06e64.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 9 Oct 2018 17:34:50 +0200 -Subject: [PATCH 028/327] sched/migrate_disable: Add export_symbol_gpl for +Subject: [PATCH 028/330] sched/migrate_disable: Add export_symbol_gpl for __migrate_disabled -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Jonathan reported that lttng/modules can't use __migrate_disabled(). This function is only used by sched/core itself and the tracing diff --git a/debian/patches-rt/0029-arm-at91-do-not-disable-enable-clocks-in-a-row.patch b/debian/patches-rt/0029-arm-at91-do-not-disable-enable-clocks-in-a-row.patch index 9f7de4777..1b22ac8b2 100644 --- a/debian/patches-rt/0029-arm-at91-do-not-disable-enable-clocks-in-a-row.patch +++ b/debian/patches-rt/0029-arm-at91-do-not-disable-enable-clocks-in-a-row.patch @@ -1,11 +1,11 @@ -From 948aa294f96cc352c3ad40f35e68c281e56477c5 Mon Sep 17 00:00:00 2001 -Message-Id: <948aa294f96cc352c3ad40f35e68c281e56477c5.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From df993c27894ef5e6222614263a3bb50325e7beea Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 9 Mar 2016 10:51:06 +0100 -Subject: [PATCH 029/327] arm: at91: do not disable/enable clocks in a row -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 029/330] arm: at91: do not disable/enable clocks in a row +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Currently the driver will disable the clock and enable it one line later if it is switching from periodic mode into one shot. diff --git a/debian/patches-rt/0030-clocksource-TCLIB-Allow-higher-clock-rates-for-clock.patch b/debian/patches-rt/0030-clocksource-TCLIB-Allow-higher-clock-rates-for-clock.patch index 18ebfda31..fabf55a72 100644 --- a/debian/patches-rt/0030-clocksource-TCLIB-Allow-higher-clock-rates-for-clock.patch +++ b/debian/patches-rt/0030-clocksource-TCLIB-Allow-higher-clock-rates-for-clock.patch @@ -1,15 +1,15 @@ -From f5979da3eb2684a8d5e90c62b35496090139a187 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 98324319b88d92e82e7dca6c9fce5fef5f1ad6cd Mon Sep 17 00:00:00 2001 +Message-Id: <98324319b88d92e82e7dca6c9fce5fef5f1ad6cd.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Benedikt Spranger Date: Mon, 8 Mar 2010 18:57:04 +0100 -Subject: [PATCH 030/327] clocksource: TCLIB: Allow higher clock rates for +Subject: [PATCH 030/330] clocksource: TCLIB: Allow higher clock rates for clock events MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz As default the TCLIB uses the 32KiHz base clock rate for clock events. Add a compile time selection to allow higher clock resulution. diff --git a/debian/patches-rt/0031-timekeeping-Split-jiffies-seqlock.patch b/debian/patches-rt/0031-timekeeping-Split-jiffies-seqlock.patch index 87c7aadf7..da17c939f 100644 --- a/debian/patches-rt/0031-timekeeping-Split-jiffies-seqlock.patch +++ b/debian/patches-rt/0031-timekeeping-Split-jiffies-seqlock.patch @@ -1,11 +1,11 @@ -From bb11ff748a6fc0e34d9ef98873b5d41c2a02fe49 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From f9064a5ac7a8b372cc7c41f6664d3cd0d652c72a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 14 Feb 2013 22:36:59 +0100 -Subject: [PATCH 031/327] timekeeping: Split jiffies seqlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 031/330] timekeeping: Split jiffies seqlock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Replace jiffies_lock seqlock with a simple seqcounter and a rawlock so it can be taken in atomic context on RT. diff --git a/debian/patches-rt/0032-signal-Revert-ptrace-preempt-magic.patch b/debian/patches-rt/0032-signal-Revert-ptrace-preempt-magic.patch index a505fa3ce..7df600e74 100644 --- a/debian/patches-rt/0032-signal-Revert-ptrace-preempt-magic.patch +++ b/debian/patches-rt/0032-signal-Revert-ptrace-preempt-magic.patch @@ -1,11 +1,11 @@ -From b73180a75e9c692a7b8fb11703db34fce450aea5 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 63bd6f12bf459b90a60d42a1a1934428b56703b2 Mon Sep 17 00:00:00 2001 +Message-Id: <63bd6f12bf459b90a60d42a1a1934428b56703b2.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 21 Sep 2011 19:57:12 +0200 -Subject: [PATCH 032/327] signal: Revert ptrace preempt magic -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 032/330] signal: Revert ptrace preempt magic +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Upstream commit '53da1d9456fe7f8 fix ptrace slowness' is nothing more than a bandaid around the ptrace design trainwreck. It's not a diff --git a/debian/patches-rt/0033-net-sched-Use-msleep-instead-of-yield.patch b/debian/patches-rt/0033-net-sched-Use-msleep-instead-of-yield.patch index 044da086c..8d99b90dc 100644 --- a/debian/patches-rt/0033-net-sched-Use-msleep-instead-of-yield.patch +++ b/debian/patches-rt/0033-net-sched-Use-msleep-instead-of-yield.patch @@ -1,11 +1,11 @@ -From 42aa735468326ce67ba5401ecf20d408df54b572 Mon Sep 17 00:00:00 2001 -Message-Id: <42aa735468326ce67ba5401ecf20d408df54b572.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8d8fd79497b0a37bd55eef0dc21ad274d3cbf8c4 Mon Sep 17 00:00:00 2001 +Message-Id: <8d8fd79497b0a37bd55eef0dc21ad274d3cbf8c4.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Marc Kleine-Budde Date: Wed, 5 Mar 2014 00:49:47 +0100 -Subject: [PATCH 033/327] net: sched: Use msleep() instead of yield() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 033/330] net: sched: Use msleep() instead of yield() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz On PREEMPT_RT enabled systems the interrupt handler run as threads at prio 50 (by default). If a high priority userspace process tries to shut down a busy diff --git a/debian/patches-rt/0034-dm-rq-remove-BUG_ON-irqs_disabled-check.patch b/debian/patches-rt/0034-dm-rq-remove-BUG_ON-irqs_disabled-check.patch index 483a4347b..163136edd 100644 --- a/debian/patches-rt/0034-dm-rq-remove-BUG_ON-irqs_disabled-check.patch +++ b/debian/patches-rt/0034-dm-rq-remove-BUG_ON-irqs_disabled-check.patch @@ -1,11 +1,11 @@ -From ebb8984e99bee2c99680926ef817db3c129f91da Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8a0b137903b17bfba32e5879cb82453cce87bce8 Mon Sep 17 00:00:00 2001 +Message-Id: <8a0b137903b17bfba32e5879cb82453cce87bce8.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 27 Mar 2018 16:24:15 +0200 -Subject: [PATCH 034/327] dm rq: remove BUG_ON(!irqs_disabled) check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 034/330] dm rq: remove BUG_ON(!irqs_disabled) check +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz In commit 052189a2ec95 ("dm: remove superfluous irq disablement in dm_request_fn") the spin_lock_irq() was replaced with spin_lock() + a diff --git a/debian/patches-rt/0035-usb-do-no-disable-interrupts-in-giveback.patch b/debian/patches-rt/0035-usb-do-no-disable-interrupts-in-giveback.patch index 8e6f9c39e..46d0faf15 100644 --- a/debian/patches-rt/0035-usb-do-no-disable-interrupts-in-giveback.patch +++ b/debian/patches-rt/0035-usb-do-no-disable-interrupts-in-giveback.patch @@ -1,11 +1,11 @@ -From a8d9dfb357e884ef3275e7062783f015f53565d0 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From c42d9f8ff6e816c7b9505c5619db2ea2d116f9c3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 8 Nov 2013 17:34:54 +0100 -Subject: [PATCH 035/327] usb: do no disable interrupts in giveback -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 035/330] usb: do no disable interrupts in giveback +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Since commit 94dfd7ed ("USB: HCD: support giveback of URB in tasklet context") the USB code disables interrupts before invoking the complete diff --git a/debian/patches-rt/0036-rt-Provide-PREEMPT_RT_BASE-config-switch.patch b/debian/patches-rt/0036-rt-Provide-PREEMPT_RT_BASE-config-switch.patch index 7500c7704..9c454dd5c 100644 --- a/debian/patches-rt/0036-rt-Provide-PREEMPT_RT_BASE-config-switch.patch +++ b/debian/patches-rt/0036-rt-Provide-PREEMPT_RT_BASE-config-switch.patch @@ -1,11 +1,11 @@ -From 18d84e2e4e3fe6697f24db1b3b71f5d5d66cba83 Mon Sep 17 00:00:00 2001 -Message-Id: <18d84e2e4e3fe6697f24db1b3b71f5d5d66cba83.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 9bbb97fd14d7adf24e33fd132dc90363ee9b0eb9 Mon Sep 17 00:00:00 2001 +Message-Id: <9bbb97fd14d7adf24e33fd132dc90363ee9b0eb9.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 17 Jun 2011 12:39:57 +0200 -Subject: [PATCH 036/327] rt: Provide PREEMPT_RT_BASE config switch -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 036/330] rt: Provide PREEMPT_RT_BASE config switch +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Introduce PREEMPT_RT_BASE which enables parts of PREEMPT_RT_FULL. Forces interrupt threading and enables some of the RT diff --git a/debian/patches-rt/0037-cpumask-Disable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch b/debian/patches-rt/0037-cpumask-Disable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch index 5957aebc6..6860e28d9 100644 --- a/debian/patches-rt/0037-cpumask-Disable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch +++ b/debian/patches-rt/0037-cpumask-Disable-CONFIG_CPUMASK_OFFSTACK-for-RT.patch @@ -1,11 +1,11 @@ -From c3a80fee57f43808e1308ad27b6dd334ace98e2b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 23ecea24e7a8967b7aa41cbbc2bdc68e5488da3b Mon Sep 17 00:00:00 2001 +Message-Id: <23ecea24e7a8967b7aa41cbbc2bdc68e5488da3b.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 14 Dec 2011 01:03:49 +0100 -Subject: [PATCH 037/327] cpumask: Disable CONFIG_CPUMASK_OFFSTACK for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 037/330] cpumask: Disable CONFIG_CPUMASK_OFFSTACK for RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz There are "valid" GFP_ATOMIC allocations such as diff --git a/debian/patches-rt/0038-jump-label-disable-if-stop_machine-is-used.patch b/debian/patches-rt/0038-jump-label-disable-if-stop_machine-is-used.patch index 6f2faabc7..048725a4e 100644 --- a/debian/patches-rt/0038-jump-label-disable-if-stop_machine-is-used.patch +++ b/debian/patches-rt/0038-jump-label-disable-if-stop_machine-is-used.patch @@ -1,11 +1,11 @@ -From e78cbc1a8d62397f7983179aa9ab1dda8b44c6b3 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 1ece596541b3a857f449f35acb8f31bb59e9f84a Mon Sep 17 00:00:00 2001 +Message-Id: <1ece596541b3a857f449f35acb8f31bb59e9f84a.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 8 Jul 2015 17:14:48 +0200 -Subject: [PATCH 038/327] jump-label: disable if stop_machine() is used -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 038/330] jump-label: disable if stop_machine() is used +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Some architectures are using stop_machine() while switching the opcode which leads to latency spikes. diff --git a/debian/patches-rt/0039-kconfig-Disable-config-options-which-are-not-RT-comp.patch b/debian/patches-rt/0039-kconfig-Disable-config-options-which-are-not-RT-comp.patch index 0134c1b00..963dd50bc 100644 --- a/debian/patches-rt/0039-kconfig-Disable-config-options-which-are-not-RT-comp.patch +++ b/debian/patches-rt/0039-kconfig-Disable-config-options-which-are-not-RT-comp.patch @@ -1,12 +1,12 @@ -From 7f3631443b247633a6ad805dcc6c602975362f79 Mon Sep 17 00:00:00 2001 -Message-Id: <7f3631443b247633a6ad805dcc6c602975362f79.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 523f4d05d6acc578a3270548ea5d6dc58f76faeb Mon Sep 17 00:00:00 2001 +Message-Id: <523f4d05d6acc578a3270548ea5d6dc58f76faeb.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 24 Jul 2011 12:11:43 +0200 -Subject: [PATCH 039/327] kconfig: Disable config options which are not RT +Subject: [PATCH 039/330] kconfig: Disable config options which are not RT compatible -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Disable stuff which is known to have issues on RT diff --git a/debian/patches-rt/0040-lockdep-disable-self-test.patch b/debian/patches-rt/0040-lockdep-disable-self-test.patch index 7ba48725e..6d593442e 100644 --- a/debian/patches-rt/0040-lockdep-disable-self-test.patch +++ b/debian/patches-rt/0040-lockdep-disable-self-test.patch @@ -1,14 +1,14 @@ -From 310b37d29f13519e002722ddf05335d39b763f1c Mon Sep 17 00:00:00 2001 -Message-Id: <310b37d29f13519e002722ddf05335d39b763f1c.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8dea7bc14458299afacd76fa1f347ffdeabe829a Mon Sep 17 00:00:00 2001 +Message-Id: <8dea7bc14458299afacd76fa1f347ffdeabe829a.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 17 Oct 2017 16:36:18 +0200 -Subject: [PATCH 040/327] lockdep: disable self-test +Subject: [PATCH 040/330] lockdep: disable self-test MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The self-test wasn't always 100% accurate for RT. We disabled a few tests which failed because they had a different semantic for RT. Some diff --git a/debian/patches-rt/0041-mm-Allow-only-slub-on-RT.patch b/debian/patches-rt/0041-mm-Allow-only-slub-on-RT.patch index 315894dbf..c1d4afa99 100644 --- a/debian/patches-rt/0041-mm-Allow-only-slub-on-RT.patch +++ b/debian/patches-rt/0041-mm-Allow-only-slub-on-RT.patch @@ -1,11 +1,11 @@ -From b2dedc8d0f5404d57c89027effe1b8b96348c29a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 2f7534e810d4069b5ce3ccb730b0873917ca7832 Mon Sep 17 00:00:00 2001 +Message-Id: <2f7534e810d4069b5ce3ccb730b0873917ca7832.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:44:03 -0500 -Subject: [PATCH 041/327] mm: Allow only slub on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 041/330] mm: Allow only slub on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Disable SLAB and SLOB on -RT. Only SLUB is adopted to -RT needs. diff --git a/debian/patches-rt/0042-locking-Disable-spin-on-owner-for-RT.patch b/debian/patches-rt/0042-locking-Disable-spin-on-owner-for-RT.patch index 8cf15c67c..4f0817761 100644 --- a/debian/patches-rt/0042-locking-Disable-spin-on-owner-for-RT.patch +++ b/debian/patches-rt/0042-locking-Disable-spin-on-owner-for-RT.patch @@ -1,14 +1,14 @@ -From a647dc8ee4cd8e98063ad658821a7b8a3bb1b200 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 9117450a92f0382c88bb580ec82d02af1e7ef4cf Mon Sep 17 00:00:00 2001 +Message-Id: <9117450a92f0382c88bb580ec82d02af1e7ef4cf.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:51:45 +0200 -Subject: [PATCH 042/327] locking: Disable spin on owner for RT +Subject: [PATCH 042/330] locking: Disable spin on owner for RT MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Drop spin on owner for mutex / rwsem. We are most likely not using it but… diff --git a/debian/patches-rt/0043-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch b/debian/patches-rt/0043-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch index 6ab9114cd..750393f76 100644 --- a/debian/patches-rt/0043-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch +++ b/debian/patches-rt/0043-rcu-Disable-RCU_FAST_NO_HZ-on-RT.patch @@ -1,11 +1,11 @@ -From ff9a18b1372ece9b57258b3fbef3fa9d41f92176 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 7cd88e0bc8f5e84d50b8c030c559e2f15453cf0a Mon Sep 17 00:00:00 2001 +Message-Id: <7cd88e0bc8f5e84d50b8c030c559e2f15453cf0a.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 28 Oct 2012 13:26:09 +0000 -Subject: [PATCH 043/327] rcu: Disable RCU_FAST_NO_HZ on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 043/330] rcu: Disable RCU_FAST_NO_HZ on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz This uses a timer_list timer from the irq disabled guts of the idle code. Disable it for now to prevent wreckage. diff --git a/debian/patches-rt/0044-rcu-make-RCU_BOOST-default-on-RT.patch b/debian/patches-rt/0044-rcu-make-RCU_BOOST-default-on-RT.patch index 7d6ce6c00..83de0b98d 100644 --- a/debian/patches-rt/0044-rcu-make-RCU_BOOST-default-on-RT.patch +++ b/debian/patches-rt/0044-rcu-make-RCU_BOOST-default-on-RT.patch @@ -1,11 +1,11 @@ -From e59c75bdefea320550c0b6e2894ea07404710779 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5e2789c8f2577b965b4850c91839a3e680ce301d Mon Sep 17 00:00:00 2001 +Message-Id: <5e2789c8f2577b965b4850c91839a3e680ce301d.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Mar 2014 20:19:05 +0100 -Subject: [PATCH 044/327] rcu: make RCU_BOOST default on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 044/330] rcu: make RCU_BOOST default on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Since it is no longer invoked from the softirq people run into OOM more often if the priority of the RCU thread is too low. Making boosting diff --git a/debian/patches-rt/0045-sched-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch b/debian/patches-rt/0045-sched-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch index 39533b728..d1f7aaea3 100644 --- a/debian/patches-rt/0045-sched-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch +++ b/debian/patches-rt/0045-sched-Disable-CONFIG_RT_GROUP_SCHED-on-RT.patch @@ -1,11 +1,11 @@ -From 070e82edd6b754089e847b8055bf7b81f3a84509 Mon Sep 17 00:00:00 2001 -Message-Id: <070e82edd6b754089e847b8055bf7b81f3a84509.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 91af26714b8fb61247dde6420eaf9fc3329fda2e Mon Sep 17 00:00:00 2001 +Message-Id: <91af26714b8fb61247dde6420eaf9fc3329fda2e.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:03:52 +0200 -Subject: [PATCH 045/327] sched: Disable CONFIG_RT_GROUP_SCHED on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 045/330] sched: Disable CONFIG_RT_GROUP_SCHED on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Carsten reported problems when running: diff --git a/debian/patches-rt/0046-net-core-disable-NET_RX_BUSY_POLL.patch b/debian/patches-rt/0046-net-core-disable-NET_RX_BUSY_POLL.patch index 33a9b4782..c91c76193 100644 --- a/debian/patches-rt/0046-net-core-disable-NET_RX_BUSY_POLL.patch +++ b/debian/patches-rt/0046-net-core-disable-NET_RX_BUSY_POLL.patch @@ -1,14 +1,14 @@ -From 0bc8851b10d0cacf55d80a873579f56adeeb7f46 Mon Sep 17 00:00:00 2001 -Message-Id: <0bc8851b10d0cacf55d80a873579f56adeeb7f46.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From fba0603919c5cd1dd19338e31cd405204034e64f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Sat, 27 May 2017 19:02:06 +0200 -Subject: [PATCH 046/327] net/core: disable NET_RX_BUSY_POLL +Subject: [PATCH 046/330] net/core: disable NET_RX_BUSY_POLL MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz sk_busy_loop() does preempt_disable() followed by a few operations which can take sleeping locks and may get long. diff --git a/debian/patches-rt/0047-arm-disable-NEON-in-kernel-mode.patch b/debian/patches-rt/0047-arm-disable-NEON-in-kernel-mode.patch index 4f5ad4ea4..38fa4a247 100644 --- a/debian/patches-rt/0047-arm-disable-NEON-in-kernel-mode.patch +++ b/debian/patches-rt/0047-arm-disable-NEON-in-kernel-mode.patch @@ -1,11 +1,11 @@ -From b143a53bf840ab206ea9ecb9c878b2f7d6d4a794 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From e0099a0cce872afef4d3276a40c9e70daee9c123 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 1 Dec 2017 10:42:03 +0100 -Subject: [PATCH 047/327] arm*: disable NEON in kernel mode -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 047/330] arm*: disable NEON in kernel mode +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz NEON in kernel mode is used by the crypto algorithms and raid6 code. While the raid6 code looks okay, the crypto algorithms do not: NEON diff --git a/debian/patches-rt/0048-powerpc-Use-generic-rwsem-on-RT.patch b/debian/patches-rt/0048-powerpc-Use-generic-rwsem-on-RT.patch index 0b47514cc..989d6fdde 100644 --- a/debian/patches-rt/0048-powerpc-Use-generic-rwsem-on-RT.patch +++ b/debian/patches-rt/0048-powerpc-Use-generic-rwsem-on-RT.patch @@ -1,11 +1,11 @@ -From 42399a14ed658b9c71ed3ebb65611fa610dbdbb4 Mon Sep 17 00:00:00 2001 -Message-Id: <42399a14ed658b9c71ed3ebb65611fa610dbdbb4.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From ec7330e84b7bbcb8457fd00e0587bfca8d4c91c3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 048/327] powerpc: Use generic rwsem on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 048/330] powerpc: Use generic rwsem on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Use generic code which uses rtmutex @@ -15,7 +15,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig -index 6f475dc5829b..3d5c86336072 100644 +index f38d153d2586..53fa972c2548 100644 --- a/arch/powerpc/Kconfig +++ b/arch/powerpc/Kconfig @@ -105,10 +105,11 @@ config LOCKDEP_SUPPORT diff --git a/debian/patches-rt/0049-powerpc-kvm-Disable-in-kernel-MPIC-emulation-for-PRE.patch b/debian/patches-rt/0049-powerpc-kvm-Disable-in-kernel-MPIC-emulation-for-PRE.patch index 072eba8b6..f956c5f05 100644 --- a/debian/patches-rt/0049-powerpc-kvm-Disable-in-kernel-MPIC-emulation-for-PRE.patch +++ b/debian/patches-rt/0049-powerpc-kvm-Disable-in-kernel-MPIC-emulation-for-PRE.patch @@ -1,12 +1,12 @@ -From a8e752a32eca81f368f6310b6773d1a065261602 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 87606cf3013d6722b78e6ddd779dd1e92eb8ceca Mon Sep 17 00:00:00 2001 +Message-Id: <87606cf3013d6722b78e6ddd779dd1e92eb8ceca.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Bogdan Purcareata Date: Fri, 24 Apr 2015 15:53:13 +0000 -Subject: [PATCH 049/327] powerpc/kvm: Disable in-kernel MPIC emulation for +Subject: [PATCH 049/330] powerpc/kvm: Disable in-kernel MPIC emulation for PREEMPT_RT_FULL -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz While converting the openpic emulation code to use a raw_spinlock_t enables guests to run on RT, there's still a performance issue. For interrupts sent in diff --git a/debian/patches-rt/0050-powerpc-Disable-highmem-on-RT.patch b/debian/patches-rt/0050-powerpc-Disable-highmem-on-RT.patch index 6bc9568ef..36fdda128 100644 --- a/debian/patches-rt/0050-powerpc-Disable-highmem-on-RT.patch +++ b/debian/patches-rt/0050-powerpc-Disable-highmem-on-RT.patch @@ -1,11 +1,11 @@ -From 167f4d2530f40f270c7e70ba2b7be61f74976957 Mon Sep 17 00:00:00 2001 -Message-Id: <167f4d2530f40f270c7e70ba2b7be61f74976957.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From f1b2a43b677f6cb695ba312e57de2a0c09b98412 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:08:34 +0200 -Subject: [PATCH 050/327] powerpc: Disable highmem on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 050/330] powerpc: Disable highmem on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The current highmem handling on -RT is not compatible and needs fixups. @@ -15,7 +15,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig -index 3d5c86336072..1b332f69dd36 100644 +index 53fa972c2548..8455293d1435 100644 --- a/arch/powerpc/Kconfig +++ b/arch/powerpc/Kconfig @@ -399,7 +399,7 @@ menu "Kernel options" diff --git a/debian/patches-rt/0051-mips-Disable-highmem-on-RT.patch b/debian/patches-rt/0051-mips-Disable-highmem-on-RT.patch index f0691ad06..8bce83c39 100644 --- a/debian/patches-rt/0051-mips-Disable-highmem-on-RT.patch +++ b/debian/patches-rt/0051-mips-Disable-highmem-on-RT.patch @@ -1,11 +1,11 @@ -From 1dc7f900c6d3b7d90320643829fd8b7ab4e8bd37 Mon Sep 17 00:00:00 2001 -Message-Id: <1dc7f900c6d3b7d90320643829fd8b7ab4e8bd37.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From e3fafbcb7f57fe9b2a70fd821d7a3499f7164ebf Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:10:12 +0200 -Subject: [PATCH 051/327] mips: Disable highmem on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 051/330] mips: Disable highmem on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The current highmem handling on -RT is not compatible and needs fixups. diff --git a/debian/patches-rt/0052-x86-Use-generic-rwsem_spinlocks-on-rt.patch b/debian/patches-rt/0052-x86-Use-generic-rwsem_spinlocks-on-rt.patch index d422cf24c..94a467ab1 100644 --- a/debian/patches-rt/0052-x86-Use-generic-rwsem_spinlocks-on-rt.patch +++ b/debian/patches-rt/0052-x86-Use-generic-rwsem_spinlocks-on-rt.patch @@ -1,11 +1,11 @@ -From 57c434a742802b917adb2b24b7be6ea2fed8bed5 Mon Sep 17 00:00:00 2001 -Message-Id: <57c434a742802b917adb2b24b7be6ea2fed8bed5.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From e2affe0d3ea6818a9df69ff68211bed0fd505b2c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 26 Jul 2009 02:21:32 +0200 -Subject: [PATCH 052/327] x86: Use generic rwsem_spinlocks on -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 052/330] x86: Use generic rwsem_spinlocks on -rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Simplifies the separation of anon_rw_semaphores and rw_semaphores for -rt. diff --git a/debian/patches-rt/0053-leds-trigger-disable-CPU-trigger-on-RT.patch b/debian/patches-rt/0053-leds-trigger-disable-CPU-trigger-on-RT.patch index 5ad2238a7..a8a08a2c9 100644 --- a/debian/patches-rt/0053-leds-trigger-disable-CPU-trigger-on-RT.patch +++ b/debian/patches-rt/0053-leds-trigger-disable-CPU-trigger-on-RT.patch @@ -1,11 +1,11 @@ -From a2821c225889984e47e9d362bd8f209f24676b0e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 049a5cd3a17958b2c72a457e21d7e32d8acf6845 Mon Sep 17 00:00:00 2001 +Message-Id: <049a5cd3a17958b2c72a457e21d7e32d8acf6845.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 23 Jan 2014 14:45:59 +0100 -Subject: [PATCH 053/327] leds: trigger: disable CPU trigger on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 053/330] leds: trigger: disable CPU trigger on -RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz as it triggers: |CPU: 0 PID: 0 Comm: swapper Not tainted 3.12.8-rt10 #141 diff --git a/debian/patches-rt/0054-cpufreq-drop-K8-s-driver-from-beeing-selected.patch b/debian/patches-rt/0054-cpufreq-drop-K8-s-driver-from-beeing-selected.patch index a02415897..30d435a11 100644 --- a/debian/patches-rt/0054-cpufreq-drop-K8-s-driver-from-beeing-selected.patch +++ b/debian/patches-rt/0054-cpufreq-drop-K8-s-driver-from-beeing-selected.patch @@ -1,11 +1,11 @@ -From 744458e6f2c0b9a78d6beca68296280083dab626 Mon Sep 17 00:00:00 2001 -Message-Id: <744458e6f2c0b9a78d6beca68296280083dab626.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8dc4f59d3d6db08c4b9ab5723d95e3542eaac829 Mon Sep 17 00:00:00 2001 +Message-Id: <8dc4f59d3d6db08c4b9ab5723d95e3542eaac829.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 9 Apr 2015 15:23:01 +0200 -Subject: [PATCH 054/327] cpufreq: drop K8's driver from beeing selected -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 054/330] cpufreq: drop K8's driver from beeing selected +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Ralf posted a picture of a backtrace from diff --git a/debian/patches-rt/0055-md-disable-bcache.patch b/debian/patches-rt/0055-md-disable-bcache.patch index 71cba47eb..1fb18ad38 100644 --- a/debian/patches-rt/0055-md-disable-bcache.patch +++ b/debian/patches-rt/0055-md-disable-bcache.patch @@ -1,14 +1,14 @@ -From 99ec29dde2efbd67eba447615b20f6419f10d75f Mon Sep 17 00:00:00 2001 -Message-Id: <99ec29dde2efbd67eba447615b20f6419f10d75f.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 3ea96f7ad4ba1ee631264d36a1aef047d0c69224 Mon Sep 17 00:00:00 2001 +Message-Id: <3ea96f7ad4ba1ee631264d36a1aef047d0c69224.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Aug 2013 11:48:57 +0200 -Subject: [PATCH 055/327] md: disable bcache +Subject: [PATCH 055/330] md: disable bcache MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz It uses anon semaphores |drivers/md/bcache/request.c: In function ‘cached_dev_write_complete’: diff --git a/debian/patches-rt/0056-efi-Disable-runtime-services-on-RT.patch b/debian/patches-rt/0056-efi-Disable-runtime-services-on-RT.patch index fc0ebb121..3cfa41d38 100644 --- a/debian/patches-rt/0056-efi-Disable-runtime-services-on-RT.patch +++ b/debian/patches-rt/0056-efi-Disable-runtime-services-on-RT.patch @@ -1,11 +1,11 @@ -From a50bf762b1437509176fa702d694be0540874d32 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 43b593bfaeee4443e7148f10440e6a1bfc23b488 Mon Sep 17 00:00:00 2001 +Message-Id: <43b593bfaeee4443e7148f10440e6a1bfc23b488.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 15:03:16 +0200 -Subject: [PATCH 056/327] efi: Disable runtime services on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 056/330] efi: Disable runtime services on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Based on meassurements the EFI functions get_variable / get_next_variable take up to 2us which looks okay. diff --git a/debian/patches-rt/0057-printk-Add-a-printk-kill-switch.patch b/debian/patches-rt/0057-printk-Add-a-printk-kill-switch.patch index e28ed008e..3ae611503 100644 --- a/debian/patches-rt/0057-printk-Add-a-printk-kill-switch.patch +++ b/debian/patches-rt/0057-printk-Add-a-printk-kill-switch.patch @@ -1,11 +1,11 @@ -From 46e48c644bd5f997e868fa0d6f39da7378cdaa38 Mon Sep 17 00:00:00 2001 -Message-Id: <46e48c644bd5f997e868fa0d6f39da7378cdaa38.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From be673afc886a3182fc5b0c8db43a81da033c8f0d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 22 Jul 2011 17:58:40 +0200 -Subject: [PATCH 057/327] printk: Add a printk kill switch -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 057/330] printk: Add a printk kill switch +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Add a prinkt-kill-switch. This is used from (NMI) watchdog to ensure that it does not dead-lock with the early printk code. diff --git a/debian/patches-rt/0058-printk-Add-force_early_printk-boot-param-to-help-wit.patch b/debian/patches-rt/0058-printk-Add-force_early_printk-boot-param-to-help-wit.patch index 4f47a4c4f..bfea3d9fd 100644 --- a/debian/patches-rt/0058-printk-Add-force_early_printk-boot-param-to-help-wit.patch +++ b/debian/patches-rt/0058-printk-Add-force_early_printk-boot-param-to-help-wit.patch @@ -1,12 +1,12 @@ -From 5ba31ca9469e52e6d4478fee90d733f9c1634dcd Mon Sep 17 00:00:00 2001 -Message-Id: <5ba31ca9469e52e6d4478fee90d733f9c1634dcd.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From b257f7a21e7846cefc9954c981ff6d79f6700fb4 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Peter Zijlstra Date: Fri, 2 Sep 2011 14:41:29 +0200 -Subject: [PATCH 058/327] printk: Add "force_early_printk" boot param to help +Subject: [PATCH 058/330] printk: Add "force_early_printk" boot param to help with debugging -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Gives me an option to screw printk and actually see what the machine says. diff --git a/debian/patches-rt/0059-preempt-Provide-preempt_-_-no-rt-variants.patch b/debian/patches-rt/0059-preempt-Provide-preempt_-_-no-rt-variants.patch index f46d1a4bf..174fa4f5b 100644 --- a/debian/patches-rt/0059-preempt-Provide-preempt_-_-no-rt-variants.patch +++ b/debian/patches-rt/0059-preempt-Provide-preempt_-_-no-rt-variants.patch @@ -1,11 +1,11 @@ -From 3d6a4436d485a01571ba80494daf1958a6ceff63 Mon Sep 17 00:00:00 2001 -Message-Id: <3d6a4436d485a01571ba80494daf1958a6ceff63.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 80491e850b7b96971c05fdf86426877c9d1304e9 Mon Sep 17 00:00:00 2001 +Message-Id: <80491e850b7b96971c05fdf86426877c9d1304e9.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 24 Jul 2009 12:38:56 +0200 -Subject: [PATCH 059/327] preempt: Provide preempt_*_(no)rt variants -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 059/330] preempt: Provide preempt_*_(no)rt variants +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz RT needs a few preempt_disable/enable points which are not necessary otherwise. Implement variants to avoid #ifdeffery. diff --git a/debian/patches-rt/0060-futex-workaround-migrate_disable-enable-in-different.patch b/debian/patches-rt/0060-futex-workaround-migrate_disable-enable-in-different.patch index d03093c85..929e5b912 100644 --- a/debian/patches-rt/0060-futex-workaround-migrate_disable-enable-in-different.patch +++ b/debian/patches-rt/0060-futex-workaround-migrate_disable-enable-in-different.patch @@ -1,12 +1,12 @@ -From f1cfb83a92f79961e79a25067ecbb45b019a45a1 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d6a9cdf745cd79634b4581276a1fff7570beb85c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 8 Mar 2017 14:23:35 +0100 -Subject: [PATCH 060/327] futex: workaround migrate_disable/enable in different +Subject: [PATCH 060/330] futex: workaround migrate_disable/enable in different context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz migrate_disable()/migrate_enable() takes a different path in atomic() vs !atomic() context. These little hacks ensure that we don't underflow / overflow diff --git a/debian/patches-rt/0061-rt-Add-local-irq-locks.patch b/debian/patches-rt/0061-rt-Add-local-irq-locks.patch index 6cfef7ef3..a1d41ca42 100644 --- a/debian/patches-rt/0061-rt-Add-local-irq-locks.patch +++ b/debian/patches-rt/0061-rt-Add-local-irq-locks.patch @@ -1,11 +1,11 @@ -From e49cf3c5cbf9c7bd3530ce2adaa3ffa845e13f12 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5b7e7169be4389cda315a618a77fec0b378095ca Mon Sep 17 00:00:00 2001 +Message-Id: <5b7e7169be4389cda315a618a77fec0b378095ca.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 20 Jun 2011 09:03:47 +0200 -Subject: [PATCH 061/327] rt: Add local irq locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 061/330] rt: Add local irq locks +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Introduce locallock. For !RT this maps to preempt_disable()/ local_irq_disable() so there is not much that changes. For RT this will diff --git a/debian/patches-rt/0062-locallock-provide-get-put-_locked_ptr-variants.patch b/debian/patches-rt/0062-locallock-provide-get-put-_locked_ptr-variants.patch index 8c12743cf..1e551615e 100644 --- a/debian/patches-rt/0062-locallock-provide-get-put-_locked_ptr-variants.patch +++ b/debian/patches-rt/0062-locallock-provide-get-put-_locked_ptr-variants.patch @@ -1,11 +1,11 @@ -From 9c5aa6fb6aded4fa1e63dc3ea5b5341447272009 Mon Sep 17 00:00:00 2001 -Message-Id: <9c5aa6fb6aded4fa1e63dc3ea5b5341447272009.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 29cd5fd02b7f0dbdcdf3398745fb90248bae6a11 Mon Sep 17 00:00:00 2001 +Message-Id: <29cd5fd02b7f0dbdcdf3398745fb90248bae6a11.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Julia Cartwright Date: Mon, 7 May 2018 08:58:56 -0500 -Subject: [PATCH 062/327] locallock: provide {get,put}_locked_ptr() variants -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 062/330] locallock: provide {get,put}_locked_ptr() variants +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Provide a set of locallocked accessors for pointers to per-CPU data; this is useful for dynamically-allocated per-CPU regions, for example. diff --git a/debian/patches-rt/0063-mm-scatterlist-Do-not-disable-irqs-on-RT.patch b/debian/patches-rt/0063-mm-scatterlist-Do-not-disable-irqs-on-RT.patch index 57dcaf145..e69695076 100644 --- a/debian/patches-rt/0063-mm-scatterlist-Do-not-disable-irqs-on-RT.patch +++ b/debian/patches-rt/0063-mm-scatterlist-Do-not-disable-irqs-on-RT.patch @@ -1,11 +1,11 @@ -From 0b3ba0e63efc0ff3698c93ccea1b057c1c3c3c8c Mon Sep 17 00:00:00 2001 -Message-Id: <0b3ba0e63efc0ff3698c93ccea1b057c1c3c3c8c.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d8c286fb8afb9a25878451e26616b96f9bf2b38e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 3 Jul 2009 08:44:34 -0500 -Subject: [PATCH 063/327] mm/scatterlist: Do not disable irqs on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 063/330] mm/scatterlist: Do not disable irqs on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz For -RT it is enough to keep pagefault disabled (which is currently handled by kmap_atomic()). diff --git a/debian/patches-rt/0064-signal-x86-Delay-calling-signals-in-atomic.patch b/debian/patches-rt/0064-signal-x86-Delay-calling-signals-in-atomic.patch index c4f9c4c0f..7e999bdd6 100644 --- a/debian/patches-rt/0064-signal-x86-Delay-calling-signals-in-atomic.patch +++ b/debian/patches-rt/0064-signal-x86-Delay-calling-signals-in-atomic.patch @@ -1,11 +1,11 @@ -From 2c40a53ef74493c310549cef2af63ae00de88f54 Mon Sep 17 00:00:00 2001 -Message-Id: <2c40a53ef74493c310549cef2af63ae00de88f54.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 6fe95ca706326c7519412c75e10c7d70713424cb Mon Sep 17 00:00:00 2001 +Message-Id: <6fe95ca706326c7519412c75e10c7d70713424cb.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Oleg Nesterov Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 064/327] signal/x86: Delay calling signals in atomic -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 064/330] signal/x86: Delay calling signals in atomic +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz On x86_64 we must disable preemption before we enable interrupts for stack faults, int3 and debugging, because the current task is using diff --git a/debian/patches-rt/0065-x86-signal-delay-calling-signals-on-32bit.patch b/debian/patches-rt/0065-x86-signal-delay-calling-signals-on-32bit.patch index a3bbeb3d8..26c63187c 100644 --- a/debian/patches-rt/0065-x86-signal-delay-calling-signals-on-32bit.patch +++ b/debian/patches-rt/0065-x86-signal-delay-calling-signals-on-32bit.patch @@ -1,11 +1,11 @@ -From eb7f3125c3a4fa024505a05e41fcfcca6f484171 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 58212e94797862f347a83da1c62d6dbf644c28b8 Mon Sep 17 00:00:00 2001 +Message-Id: <58212e94797862f347a83da1c62d6dbf644c28b8.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Yang Shi Date: Thu, 10 Dec 2015 10:58:51 -0800 -Subject: [PATCH 065/327] x86/signal: delay calling signals on 32bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 065/330] x86/signal: delay calling signals on 32bit +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz When running some ptrace single step tests on x86-32 machine, the below problem is triggered: diff --git a/debian/patches-rt/0066-buffer_head-Replace-bh_uptodate_lock-for-rt.patch b/debian/patches-rt/0066-buffer_head-Replace-bh_uptodate_lock-for-rt.patch index c83f38dd4..a3517fab2 100644 --- a/debian/patches-rt/0066-buffer_head-Replace-bh_uptodate_lock-for-rt.patch +++ b/debian/patches-rt/0066-buffer_head-Replace-bh_uptodate_lock-for-rt.patch @@ -1,11 +1,11 @@ -From c482d938dd8d53d5dd3876957a4964f18b102a66 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 2c8893c469811fe57a6ccb47cd67600bf510dcdc Mon Sep 17 00:00:00 2001 +Message-Id: <2c8893c469811fe57a6ccb47cd67600bf510dcdc.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 18 Mar 2011 09:18:52 +0100 -Subject: [PATCH 066/327] buffer_head: Replace bh_uptodate_lock for -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 066/330] buffer_head: Replace bh_uptodate_lock for -rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Wrap the bit_spin_lock calls into a separate inline and add the RT replacements with a real spinlock. diff --git a/debian/patches-rt/0067-fs-jbd-jbd2-Make-state-lock-and-journal-head-lock-rt.patch b/debian/patches-rt/0067-fs-jbd-jbd2-Make-state-lock-and-journal-head-lock-rt.patch index 48ebdfe20..07c85a2a1 100644 --- a/debian/patches-rt/0067-fs-jbd-jbd2-Make-state-lock-and-journal-head-lock-rt.patch +++ b/debian/patches-rt/0067-fs-jbd-jbd2-Make-state-lock-and-journal-head-lock-rt.patch @@ -1,12 +1,12 @@ -From 9c5c5f4f8fcf4dbf8c30dac97256c4025048780d Mon Sep 17 00:00:00 2001 -Message-Id: <9c5c5f4f8fcf4dbf8c30dac97256c4025048780d.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 3cc11354713594d4fb2664a7fb4cb59872176ed0 Mon Sep 17 00:00:00 2001 +Message-Id: <3cc11354713594d4fb2664a7fb4cb59872176ed0.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 18 Mar 2011 10:11:25 +0100 -Subject: [PATCH 067/327] fs: jbd/jbd2: Make state lock and journal head lock +Subject: [PATCH 067/330] fs: jbd/jbd2: Make state lock and journal head lock rt safe -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz bit_spin_locks break under RT. diff --git a/debian/patches-rt/0068-list_bl-Make-list-head-locking-RT-safe.patch b/debian/patches-rt/0068-list_bl-Make-list-head-locking-RT-safe.patch index 637e13575..9241aee2c 100644 --- a/debian/patches-rt/0068-list_bl-Make-list-head-locking-RT-safe.patch +++ b/debian/patches-rt/0068-list_bl-Make-list-head-locking-RT-safe.patch @@ -1,11 +1,11 @@ -From 0909d9250b379740656baff6f1fdb5f5673aab67 Mon Sep 17 00:00:00 2001 -Message-Id: <0909d9250b379740656baff6f1fdb5f5673aab67.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d7dbda4307c7d2330cf192e6d04d34f788dfbdea Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Paul Gortmaker Date: Fri, 21 Jun 2013 15:07:25 -0400 -Subject: [PATCH 068/327] list_bl: Make list head locking RT safe -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 068/330] list_bl: Make list head locking RT safe +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz As per changes in include/linux/jbd_common.h for avoiding the bit_spin_locks on RT ("fs: jbd/jbd2: Make state lock and journal diff --git a/debian/patches-rt/0069-list_bl-fixup-bogus-lockdep-warning.patch b/debian/patches-rt/0069-list_bl-fixup-bogus-lockdep-warning.patch index 8e0d49a93..52eae2fb0 100644 --- a/debian/patches-rt/0069-list_bl-fixup-bogus-lockdep-warning.patch +++ b/debian/patches-rt/0069-list_bl-fixup-bogus-lockdep-warning.patch @@ -1,11 +1,11 @@ -From c4e0f18722acf2edc69eb96130f868e6c6788940 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 546e11e3b7d198f31697e3d37f91f7d13691a5e9 Mon Sep 17 00:00:00 2001 +Message-Id: <546e11e3b7d198f31697e3d37f91f7d13691a5e9.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 31 Mar 2016 00:04:25 -0500 -Subject: [PATCH 069/327] list_bl: fixup bogus lockdep warning -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 069/330] list_bl: fixup bogus lockdep warning +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz At first glance, the use of 'static inline' seems appropriate for INIT_HLIST_BL_HEAD(). diff --git a/debian/patches-rt/0070-genirq-Disable-irqpoll-on-rt.patch b/debian/patches-rt/0070-genirq-Disable-irqpoll-on-rt.patch index 5844c88da..2e8d93235 100644 --- a/debian/patches-rt/0070-genirq-Disable-irqpoll-on-rt.patch +++ b/debian/patches-rt/0070-genirq-Disable-irqpoll-on-rt.patch @@ -1,11 +1,11 @@ -From f4e96b7117d9532078b14d66d22deb81c27a6059 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 58fdb46a53ff73cd5b4c8142eff4acb4799ae34b Mon Sep 17 00:00:00 2001 +Message-Id: <58fdb46a53ff73cd5b4c8142eff4acb4799ae34b.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:57 -0500 -Subject: [PATCH 070/327] genirq: Disable irqpoll on -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 070/330] genirq: Disable irqpoll on -rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Creates long latencies for no value diff --git a/debian/patches-rt/0071-genirq-Force-interrupt-thread-on-RT.patch b/debian/patches-rt/0071-genirq-Force-interrupt-thread-on-RT.patch index 0eaa3b4eb..9e017b8d5 100644 --- a/debian/patches-rt/0071-genirq-Force-interrupt-thread-on-RT.patch +++ b/debian/patches-rt/0071-genirq-Force-interrupt-thread-on-RT.patch @@ -1,11 +1,11 @@ -From 3e051aa90e4544659fb2dc14bbd65d9009783051 Mon Sep 17 00:00:00 2001 -Message-Id: <3e051aa90e4544659fb2dc14bbd65d9009783051.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From e6e7eb166022fa841ca4b929eb6bc22951a46275 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 3 Apr 2011 11:57:29 +0200 -Subject: [PATCH 071/327] genirq: Force interrupt thread on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 071/330] genirq: Force interrupt thread on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Force threaded_irqs and optimize the code (force_irqthreads) in regard to this. diff --git a/debian/patches-rt/0072-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch b/debian/patches-rt/0072-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch index 3d195d63d..681095559 100644 --- a/debian/patches-rt/0072-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch +++ b/debian/patches-rt/0072-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch @@ -1,12 +1,12 @@ -From 3a3f3413b2b150857c43187c4181949a65c09d6b Mon Sep 17 00:00:00 2001 -Message-Id: <3a3f3413b2b150857c43187c4181949a65c09d6b.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 021d0c4398f9f1d303211609224bcc816a76ec03 Mon Sep 17 00:00:00 2001 +Message-Id: <021d0c4398f9f1d303211609224bcc816a76ec03.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 28 May 2018 15:24:20 +0200 -Subject: [PATCH 072/327] Split IRQ-off and zone->lock while freeing pages from +Subject: [PATCH 072/330] Split IRQ-off and zone->lock while freeing pages from PCP list #1 -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Split the IRQ-off section while accessing the PCP list from zone->lock while freeing pages. diff --git a/debian/patches-rt/0073-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch b/debian/patches-rt/0073-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch index fbbe3a416..2fc5f76dd 100644 --- a/debian/patches-rt/0073-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch +++ b/debian/patches-rt/0073-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch @@ -1,12 +1,12 @@ -From 7b7dde90646c316e1fc54ee2de83ecbb83663772 Mon Sep 17 00:00:00 2001 -Message-Id: <7b7dde90646c316e1fc54ee2de83ecbb83663772.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 377595cd119888aa39bd32ee3c2ae94341f8b596 Mon Sep 17 00:00:00 2001 +Message-Id: <377595cd119888aa39bd32ee3c2ae94341f8b596.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 28 May 2018 15:24:21 +0200 -Subject: [PATCH 073/327] Split IRQ-off and zone->lock while freeing pages from +Subject: [PATCH 073/330] Split IRQ-off and zone->lock while freeing pages from PCP list #2 -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Split the IRQ-off section while accessing the PCP list from zone->lock while freeing pages. diff --git a/debian/patches-rt/0074-mm-SLxB-change-list_lock-to-raw_spinlock_t.patch b/debian/patches-rt/0074-mm-SLxB-change-list_lock-to-raw_spinlock_t.patch index 5ead99f78..8ef57bacf 100644 --- a/debian/patches-rt/0074-mm-SLxB-change-list_lock-to-raw_spinlock_t.patch +++ b/debian/patches-rt/0074-mm-SLxB-change-list_lock-to-raw_spinlock_t.patch @@ -1,11 +1,11 @@ -From fa057a8cd66ac953640cc16e35915d8afe3a6465 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 39ebbedf9476b543cc534b642872b6467de93810 Mon Sep 17 00:00:00 2001 +Message-Id: <39ebbedf9476b543cc534b642872b6467de93810.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 28 May 2018 15:24:22 +0200 -Subject: [PATCH 074/327] mm/SLxB: change list_lock to raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 074/330] mm/SLxB: change list_lock to raw_spinlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The list_lock is used with used with IRQs off on RT. Make it a raw_spinlock_t otherwise the interrupts won't be disabled on -RT. The locking rules remain diff --git a/debian/patches-rt/0075-mm-SLUB-delay-giving-back-empty-slubs-to-IRQ-enabled.patch b/debian/patches-rt/0075-mm-SLUB-delay-giving-back-empty-slubs-to-IRQ-enabled.patch index ea1ab87fb..f228eeb39 100644 --- a/debian/patches-rt/0075-mm-SLUB-delay-giving-back-empty-slubs-to-IRQ-enabled.patch +++ b/debian/patches-rt/0075-mm-SLUB-delay-giving-back-empty-slubs-to-IRQ-enabled.patch @@ -1,12 +1,12 @@ -From 4d6fc2ed37bb9bf82d3fa7f7a1056969914ea7d9 Mon Sep 17 00:00:00 2001 -Message-Id: <4d6fc2ed37bb9bf82d3fa7f7a1056969914ea7d9.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 7b367dfb1943353fa3ba380009621330359ebb3e Mon Sep 17 00:00:00 2001 +Message-Id: <7b367dfb1943353fa3ba380009621330359ebb3e.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 21 Jun 2018 17:29:19 +0200 -Subject: [PATCH 075/327] mm/SLUB: delay giving back empty slubs to IRQ enabled +Subject: [PATCH 075/330] mm/SLUB: delay giving back empty slubs to IRQ enabled regions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz __free_slab() is invoked with disabled interrupts which increases the irq-off time while __free_pages() is doing the work. diff --git a/debian/patches-rt/0076-mm-page_alloc-rt-friendly-per-cpu-pages.patch b/debian/patches-rt/0076-mm-page_alloc-rt-friendly-per-cpu-pages.patch index 1ab2c4d68..54848eda5 100644 --- a/debian/patches-rt/0076-mm-page_alloc-rt-friendly-per-cpu-pages.patch +++ b/debian/patches-rt/0076-mm-page_alloc-rt-friendly-per-cpu-pages.patch @@ -1,11 +1,11 @@ -From 4de498e282c6832127555daa53cf0f14d33561e6 Mon Sep 17 00:00:00 2001 -Message-Id: <4de498e282c6832127555daa53cf0f14d33561e6.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From abda1f47485a78498dde5581c2b61f1f22454778 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:37 -0500 -Subject: [PATCH 076/327] mm: page_alloc: rt-friendly per-cpu pages -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 076/330] mm: page_alloc: rt-friendly per-cpu pages +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz rt-friendly per-cpu pages: convert the irqs-off per-cpu locking method into a preemptible, explicit-per-cpu-locks method. diff --git a/debian/patches-rt/0077-mm-swap-Convert-to-percpu-locked.patch b/debian/patches-rt/0077-mm-swap-Convert-to-percpu-locked.patch index 67a67f2c2..9444791c2 100644 --- a/debian/patches-rt/0077-mm-swap-Convert-to-percpu-locked.patch +++ b/debian/patches-rt/0077-mm-swap-Convert-to-percpu-locked.patch @@ -1,11 +1,11 @@ -From 10d21f8e8a36ebe0763b204d827259c8a249de7f Mon Sep 17 00:00:00 2001 -Message-Id: <10d21f8e8a36ebe0763b204d827259c8a249de7f.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d054e1f303f7a4661d16389108b38a84aa85f441 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:51 -0500 -Subject: [PATCH 077/327] mm/swap: Convert to percpu locked -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 077/330] mm/swap: Convert to percpu locked +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Replace global locks (get_cpu + local_irq_save) with "local_locks()". Currently there is one of for "rotate" and one for "swap". diff --git a/debian/patches-rt/0078-mm-perform-lru_add_drain_all-remotely.patch b/debian/patches-rt/0078-mm-perform-lru_add_drain_all-remotely.patch index 3b1bfb1d9..af5e358de 100644 --- a/debian/patches-rt/0078-mm-perform-lru_add_drain_all-remotely.patch +++ b/debian/patches-rt/0078-mm-perform-lru_add_drain_all-remotely.patch @@ -1,11 +1,11 @@ -From fdeb720879c14d725ec3d401960fa2ca0f479ebe Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From a8db797e3972c746f7642b6b73bca01fdde9ec4a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Luiz Capitulino Date: Fri, 27 May 2016 15:03:28 +0200 -Subject: [PATCH 078/327] mm: perform lru_add_drain_all() remotely -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 078/330] mm: perform lru_add_drain_all() remotely +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz lru_add_drain_all() works by scheduling lru_add_drain_cpu() to run on all CPUs that have non-empty LRU pagevecs and then waiting for diff --git a/debian/patches-rt/0079-mm-vmstat-Protect-per-cpu-variables-with-preempt-dis.patch b/debian/patches-rt/0079-mm-vmstat-Protect-per-cpu-variables-with-preempt-dis.patch index 687315cab..6b1d2ec2a 100644 --- a/debian/patches-rt/0079-mm-vmstat-Protect-per-cpu-variables-with-preempt-dis.patch +++ b/debian/patches-rt/0079-mm-vmstat-Protect-per-cpu-variables-with-preempt-dis.patch @@ -1,12 +1,12 @@ -From dffe1cb4045c66c67368b11f369e5bb5f26a1f81 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 2eb1b2f89292a0e3d57b1f13b86752834510784e Mon Sep 17 00:00:00 2001 +Message-Id: <2eb1b2f89292a0e3d57b1f13b86752834510784e.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:30:13 -0500 -Subject: [PATCH 079/327] mm/vmstat: Protect per cpu variables with preempt +Subject: [PATCH 079/330] mm/vmstat: Protect per cpu variables with preempt disable on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Disable preemption on -RT for the vmstat code. On vanila the code runs in IRQ-off regions while on -RT it is not. "preempt_disable" ensures that the diff --git a/debian/patches-rt/0080-ARM-Initialize-split-page-table-locks-for-vector-pag.patch b/debian/patches-rt/0080-ARM-Initialize-split-page-table-locks-for-vector-pag.patch index d63b73d97..61248fb78 100644 --- a/debian/patches-rt/0080-ARM-Initialize-split-page-table-locks-for-vector-pag.patch +++ b/debian/patches-rt/0080-ARM-Initialize-split-page-table-locks-for-vector-pag.patch @@ -1,12 +1,12 @@ -From aeffc8a19ecbfab057793781f8a25041af504a83 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 9204f20ab0da124e60ac40e30f4221b66ee0eb61 Mon Sep 17 00:00:00 2001 +Message-Id: <9204f20ab0da124e60ac40e30f4221b66ee0eb61.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Frank Rowand Date: Sat, 1 Oct 2011 18:58:13 -0700 -Subject: [PATCH 080/327] ARM: Initialize split page table locks for vector +Subject: [PATCH 080/330] ARM: Initialize split page table locks for vector page -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Without this patch, ARM can not use SPLIT_PTLOCK_CPUS if PREEMPT_RT_FULL=y because vectors_user_mapping() creates a diff --git a/debian/patches-rt/0081-mm-Enable-SLUB-for-RT.patch b/debian/patches-rt/0081-mm-Enable-SLUB-for-RT.patch index ec16c21fd..c15129f08 100644 --- a/debian/patches-rt/0081-mm-Enable-SLUB-for-RT.patch +++ b/debian/patches-rt/0081-mm-Enable-SLUB-for-RT.patch @@ -1,11 +1,11 @@ -From 6e8c5a61ab832ba68d9935c4f02adcb7a30d7a94 Mon Sep 17 00:00:00 2001 -Message-Id: <6e8c5a61ab832ba68d9935c4f02adcb7a30d7a94.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 94db5b5c0cfd8c5e5afbb9d61349434df1eda3dc Mon Sep 17 00:00:00 2001 +Message-Id: <94db5b5c0cfd8c5e5afbb9d61349434df1eda3dc.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 25 Oct 2012 10:32:35 +0100 -Subject: [PATCH 081/327] mm: Enable SLUB for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 081/330] mm: Enable SLUB for RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Avoid the memory allocation in IRQ section diff --git a/debian/patches-rt/0082-slub-Enable-irqs-for-__GFP_WAIT.patch b/debian/patches-rt/0082-slub-Enable-irqs-for-__GFP_WAIT.patch index 898939340..da1cf22ca 100644 --- a/debian/patches-rt/0082-slub-Enable-irqs-for-__GFP_WAIT.patch +++ b/debian/patches-rt/0082-slub-Enable-irqs-for-__GFP_WAIT.patch @@ -1,11 +1,11 @@ -From 8f6fd4e0cc2883e6382583e41d27d3d6d040192b Mon Sep 17 00:00:00 2001 -Message-Id: <8f6fd4e0cc2883e6382583e41d27d3d6d040192b.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From cdb48077b31503604eace5c253d95af45d57fb7f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 9 Jan 2013 12:08:15 +0100 -Subject: [PATCH 082/327] slub: Enable irqs for __GFP_WAIT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 082/330] slub: Enable irqs for __GFP_WAIT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz SYSTEM_RUNNING might be too late for enabling interrupts. Allocations with GFP_WAIT can happen before that. So use this as an indicator. diff --git a/debian/patches-rt/0083-slub-Disable-SLUB_CPU_PARTIAL.patch b/debian/patches-rt/0083-slub-Disable-SLUB_CPU_PARTIAL.patch index 18efeb664..653f36a34 100644 --- a/debian/patches-rt/0083-slub-Disable-SLUB_CPU_PARTIAL.patch +++ b/debian/patches-rt/0083-slub-Disable-SLUB_CPU_PARTIAL.patch @@ -1,11 +1,11 @@ -From 843e5b1d54daef194395fd4369cb1ec54262ef2b Mon Sep 17 00:00:00 2001 -Message-Id: <843e5b1d54daef194395fd4369cb1ec54262ef2b.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 65cd4aa9dd745640a6c1fd4f2aeb930f5743b578 Mon Sep 17 00:00:00 2001 +Message-Id: <65cd4aa9dd745640a6c1fd4f2aeb930f5743b578.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 15 Apr 2015 19:00:47 +0200 -Subject: [PATCH 083/327] slub: Disable SLUB_CPU_PARTIAL -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 083/330] slub: Disable SLUB_CPU_PARTIAL +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:915 |in_atomic(): 1, irqs_disabled(): 0, pid: 87, name: rcuop/7 diff --git a/debian/patches-rt/0084-mm-memcontrol-Don-t-call-schedule_work_on-in-preempt.patch b/debian/patches-rt/0084-mm-memcontrol-Don-t-call-schedule_work_on-in-preempt.patch index 6e9ef850f..ab8675094 100644 --- a/debian/patches-rt/0084-mm-memcontrol-Don-t-call-schedule_work_on-in-preempt.patch +++ b/debian/patches-rt/0084-mm-memcontrol-Don-t-call-schedule_work_on-in-preempt.patch @@ -1,12 +1,12 @@ -From 3e9c12c78200b760c00837854fd6d37028b2f543 Mon Sep 17 00:00:00 2001 -Message-Id: <3e9c12c78200b760c00837854fd6d37028b2f543.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d01df1ad64744dc92dd654ff0012eda4c068dad7 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Yang Shi Date: Wed, 30 Oct 2013 11:48:33 -0700 -Subject: [PATCH 084/327] mm/memcontrol: Don't call schedule_work_on in +Subject: [PATCH 084/330] mm/memcontrol: Don't call schedule_work_on in preemption disabled context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The following trace is triggered when running ltp oom test cases: diff --git a/debian/patches-rt/0085-mm-memcontrol-Replace-local_irq_disable-with-local-l.patch b/debian/patches-rt/0085-mm-memcontrol-Replace-local_irq_disable-with-local-l.patch index cabbca4e2..0b74083df 100644 --- a/debian/patches-rt/0085-mm-memcontrol-Replace-local_irq_disable-with-local-l.patch +++ b/debian/patches-rt/0085-mm-memcontrol-Replace-local_irq_disable-with-local-l.patch @@ -1,12 +1,12 @@ -From 91616d29c2d084ab75578112ead5001d6080f166 Mon Sep 17 00:00:00 2001 -Message-Id: <91616d29c2d084ab75578112ead5001d6080f166.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 77ce783710c1173421fac0625b9717d0fe6bd861 Mon Sep 17 00:00:00 2001 +Message-Id: <77ce783710c1173421fac0625b9717d0fe6bd861.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 28 Jan 2015 17:14:16 +0100 -Subject: [PATCH 085/327] mm/memcontrol: Replace local_irq_disable with local +Subject: [PATCH 085/330] mm/memcontrol: Replace local_irq_disable with local locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz There are a few local_irq_disable() which then take sleeping locks. This patch converts them local locks. diff --git a/debian/patches-rt/0086-mm-zsmalloc-copy-with-get_cpu_var-and-locking.patch b/debian/patches-rt/0086-mm-zsmalloc-copy-with-get_cpu_var-and-locking.patch index 65a6bb0ed..d242544f8 100644 --- a/debian/patches-rt/0086-mm-zsmalloc-copy-with-get_cpu_var-and-locking.patch +++ b/debian/patches-rt/0086-mm-zsmalloc-copy-with-get_cpu_var-and-locking.patch @@ -1,11 +1,11 @@ -From c088f5ac3869d9017ee3cfd6e3e635b739f29b9a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From bd0237a4fed1901b2c73f6f2657cb517bfca624b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Mike Galbraith Date: Tue, 22 Mar 2016 11:16:09 +0100 -Subject: [PATCH 086/327] mm/zsmalloc: copy with get_cpu_var() and locking -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 086/330] mm/zsmalloc: copy with get_cpu_var() and locking +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz get_cpu_var() disables preemption and triggers a might_sleep() splat later. This is replaced with get_locked_var(). diff --git a/debian/patches-rt/0087-x86-mm-pat-disable-preemption-__split_large_page-aft.patch b/debian/patches-rt/0087-x86-mm-pat-disable-preemption-__split_large_page-aft.patch index 6b9620516..34b676ee7 100644 --- a/debian/patches-rt/0087-x86-mm-pat-disable-preemption-__split_large_page-aft.patch +++ b/debian/patches-rt/0087-x86-mm-pat-disable-preemption-__split_large_page-aft.patch @@ -1,12 +1,12 @@ -From 10058ab5044aa42d8a446f23dbf389501fe42659 Mon Sep 17 00:00:00 2001 -Message-Id: <10058ab5044aa42d8a446f23dbf389501fe42659.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 16770986d54d3c32d2b8ae4a60b34203c0653de1 Mon Sep 17 00:00:00 2001 +Message-Id: <16770986d54d3c32d2b8ae4a60b34203c0653de1.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 11 Dec 2018 21:53:43 +0100 -Subject: [PATCH 087/327] x86/mm/pat: disable preemption __split_large_page() +Subject: [PATCH 087/330] x86/mm/pat: disable preemption __split_large_page() after spin_lock() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Commit "x86/mm/pat: Disable preemption around __flush_tlb_all()" added a warning if __flush_tlb_all() is invoked in preemptible context. On !RT diff --git a/debian/patches-rt/0088-radix-tree-use-local-locks.patch b/debian/patches-rt/0088-radix-tree-use-local-locks.patch index 891d1243e..07bdba5c5 100644 --- a/debian/patches-rt/0088-radix-tree-use-local-locks.patch +++ b/debian/patches-rt/0088-radix-tree-use-local-locks.patch @@ -1,11 +1,11 @@ -From 53285f0d22a166ed75e6783eff8da4a278d77baf Mon Sep 17 00:00:00 2001 -Message-Id: <53285f0d22a166ed75e6783eff8da4a278d77baf.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 86f0fd23813b5e4d76e213f0720df690840d9fb4 Mon Sep 17 00:00:00 2001 +Message-Id: <86f0fd23813b5e4d76e213f0720df690840d9fb4.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 25 Jan 2017 16:34:27 +0100 -Subject: [PATCH 088/327] radix-tree: use local locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 088/330] radix-tree: use local locks +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The preload functionality uses per-CPU variables and preempt-disable to ensure that it does not switch CPUs during its usage. This patch adds diff --git a/debian/patches-rt/0089-timers-Prepare-for-full-preemption.patch b/debian/patches-rt/0089-timers-Prepare-for-full-preemption.patch index 01f89e776..3c340add4 100644 --- a/debian/patches-rt/0089-timers-Prepare-for-full-preemption.patch +++ b/debian/patches-rt/0089-timers-Prepare-for-full-preemption.patch @@ -1,11 +1,11 @@ -From 48cd286fdd0d9f93477f3a3243bf27c30531c995 Mon Sep 17 00:00:00 2001 -Message-Id: <48cd286fdd0d9f93477f3a3243bf27c30531c995.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 6da3c3ca1b06ab37552a67701decb91ef244b889 Mon Sep 17 00:00:00 2001 +Message-Id: <6da3c3ca1b06ab37552a67701decb91ef244b889.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:34 -0500 -Subject: [PATCH 089/327] timers: Prepare for full preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 089/330] timers: Prepare for full preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz When softirqs can be preempted we need to make sure that cancelling the timer from the active thread can not deadlock vs. a running timer diff --git a/debian/patches-rt/0090-x86-kvm-Require-const-tsc-for-RT.patch b/debian/patches-rt/0090-x86-kvm-Require-const-tsc-for-RT.patch index c320eb99c..eb541953b 100644 --- a/debian/patches-rt/0090-x86-kvm-Require-const-tsc-for-RT.patch +++ b/debian/patches-rt/0090-x86-kvm-Require-const-tsc-for-RT.patch @@ -1,11 +1,11 @@ -From f6c3ce2272c7ebee850197cd4744deea0ade3851 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8df6f704e04eac71d8ff66069f9b932baedda922 Mon Sep 17 00:00:00 2001 +Message-Id: <8df6f704e04eac71d8ff66069f9b932baedda922.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 6 Nov 2011 12:26:18 +0100 -Subject: [PATCH 090/327] x86: kvm Require const tsc for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 090/330] x86: kvm Require const tsc for RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Non constant TSC is a nightmare on bare metal already, but with virtualization it becomes a complete disaster because the workarounds diff --git a/debian/patches-rt/0091-pci-switchtec-Don-t-use-completion-s-wait-queue.patch b/debian/patches-rt/0091-pci-switchtec-Don-t-use-completion-s-wait-queue.patch index d9677e4f2..916126dfd 100644 --- a/debian/patches-rt/0091-pci-switchtec-Don-t-use-completion-s-wait-queue.patch +++ b/debian/patches-rt/0091-pci-switchtec-Don-t-use-completion-s-wait-queue.patch @@ -1,11 +1,11 @@ -From 66114e344899bf9406fdb9c868239f2c3c3339ea Mon Sep 17 00:00:00 2001 -Message-Id: <66114e344899bf9406fdb9c868239f2c3c3339ea.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d162010e64fe7d5f653343131c52c4d28be04b8e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 4 Oct 2017 10:24:23 +0200 -Subject: [PATCH 091/327] pci/switchtec: Don't use completion's wait queue -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 091/330] pci/switchtec: Don't use completion's wait queue +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The poll callback is using completion's wait_queue_head_t member and puts it in poll_wait() so the poll() caller gets a wakeup after command diff --git a/debian/patches-rt/0092-wait.h-include-atomic.h.patch b/debian/patches-rt/0092-wait.h-include-atomic.h.patch index 2ef611a47..4ff716d5b 100644 --- a/debian/patches-rt/0092-wait.h-include-atomic.h.patch +++ b/debian/patches-rt/0092-wait.h-include-atomic.h.patch @@ -1,14 +1,14 @@ -From 41af71c175d23fa802fba4537a43b0af5a2700c3 Mon Sep 17 00:00:00 2001 -Message-Id: <41af71c175d23fa802fba4537a43b0af5a2700c3.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 53c3e1b86c8c364ff7eb2216997392eba50deb86 Mon Sep 17 00:00:00 2001 +Message-Id: <53c3e1b86c8c364ff7eb2216997392eba50deb86.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 28 Oct 2013 12:19:57 +0100 -Subject: [PATCH 092/327] wait.h: include atomic.h +Subject: [PATCH 092/330] wait.h: include atomic.h MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz | CC init/main.o |In file included from include/linux/mmzone.h:9:0, diff --git a/debian/patches-rt/0093-work-simple-Simple-work-queue-implemenation.patch b/debian/patches-rt/0093-work-simple-Simple-work-queue-implemenation.patch index ec5055248..32bc41b4d 100644 --- a/debian/patches-rt/0093-work-simple-Simple-work-queue-implemenation.patch +++ b/debian/patches-rt/0093-work-simple-Simple-work-queue-implemenation.patch @@ -1,11 +1,11 @@ -From d017a1556dd43a1b3784e918d26490349760d104 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 08ed3c311776de6b7d8600d89e3524938e03707f Mon Sep 17 00:00:00 2001 +Message-Id: <08ed3c311776de6b7d8600d89e3524938e03707f.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Daniel Wagner Date: Fri, 11 Jul 2014 15:26:11 +0200 -Subject: [PATCH 093/327] work-simple: Simple work queue implemenation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 093/330] work-simple: Simple work queue implemenation +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Provides a framework for enqueuing callbacks from irq context PREEMPT_RT_FULL safe. The callbacks are executed in kthread context. diff --git a/debian/patches-rt/0094-work-simple-drop-a-shit-statement-in-SWORK_EVENT_PEN.patch b/debian/patches-rt/0094-work-simple-drop-a-shit-statement-in-SWORK_EVENT_PEN.patch index 9a1fd0aef..cb7a4ad06 100644 --- a/debian/patches-rt/0094-work-simple-drop-a-shit-statement-in-SWORK_EVENT_PEN.patch +++ b/debian/patches-rt/0094-work-simple-drop-a-shit-statement-in-SWORK_EVENT_PEN.patch @@ -1,12 +1,12 @@ -From 242c094d4338111ace88909588c33688966aa416 Mon Sep 17 00:00:00 2001 -Message-Id: <242c094d4338111ace88909588c33688966aa416.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d64bfa33220ec37825bf56b524ca8ec253853395 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 10 Sep 2018 18:00:31 +0200 -Subject: [PATCH 094/327] work-simple: drop a shit statement in +Subject: [PATCH 094/330] work-simple: drop a shit statement in SWORK_EVENT_PENDING -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Dan Carpenter reported | smatch warnings: diff --git a/debian/patches-rt/0095-completion-Use-simple-wait-queues.patch b/debian/patches-rt/0095-completion-Use-simple-wait-queues.patch index d22359710..f961449e6 100644 --- a/debian/patches-rt/0095-completion-Use-simple-wait-queues.patch +++ b/debian/patches-rt/0095-completion-Use-simple-wait-queues.patch @@ -1,11 +1,11 @@ -From cec9bf06d5bcc8203e45e2f4fe388ec2e1f03e3c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5b88f91e4d8bd0abaed34ac96c9a50b0792882ae Mon Sep 17 00:00:00 2001 +Message-Id: <5b88f91e4d8bd0abaed34ac96c9a50b0792882ae.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 11 Jan 2013 11:23:51 +0100 -Subject: [PATCH 095/327] completion: Use simple wait queues -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 095/330] completion: Use simple wait queues +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Completions have no long lasting callbacks and therefor do not need the complex waitqueue variant. Use simple waitqueues which reduces the @@ -71,7 +71,7 @@ index 11a501d0664c..1fe8a1b359d6 100644 destroy_workqueue(ffs->io_completion_wq); kfree(ffs->dev_name); diff --git a/drivers/usb/gadget/legacy/inode.c b/drivers/usb/gadget/legacy/inode.c -index 37ca0e669bd8..56a16587b221 100644 +index 25d417ad9000..c5c11ff634b5 100644 --- a/drivers/usb/gadget/legacy/inode.c +++ b/drivers/usb/gadget/legacy/inode.c @@ -343,7 +343,7 @@ ep_io (struct ep_data *epdata, void *buf, unsigned len) diff --git a/debian/patches-rt/0096-fs-aio-simple-simple-work.patch b/debian/patches-rt/0096-fs-aio-simple-simple-work.patch index 68deb42bb..848077526 100644 --- a/debian/patches-rt/0096-fs-aio-simple-simple-work.patch +++ b/debian/patches-rt/0096-fs-aio-simple-simple-work.patch @@ -1,11 +1,11 @@ -From a3585f91ee1ccd096183305b2b26a3f9b23de582 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d6441914ec3b4e35345aa572a92feb01a525bcb0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Feb 2015 18:49:10 +0100 -Subject: [PATCH 096/327] fs/aio: simple simple work -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 096/330] fs/aio: simple simple work +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:768 |in_atomic(): 1, irqs_disabled(): 0, pid: 26, name: rcuos/2 diff --git a/debian/patches-rt/0097-time-hrtimer-avoid-schedule_work-with-interrupts-dis.patch b/debian/patches-rt/0097-time-hrtimer-avoid-schedule_work-with-interrupts-dis.patch index 0d4d065f6..4fe00dc94 100644 --- a/debian/patches-rt/0097-time-hrtimer-avoid-schedule_work-with-interrupts-dis.patch +++ b/debian/patches-rt/0097-time-hrtimer-avoid-schedule_work-with-interrupts-dis.patch @@ -1,12 +1,12 @@ -From 562153f05c52b64eb1fbb1d914c4d13c8970e1d9 Mon Sep 17 00:00:00 2001 -Message-Id: <562153f05c52b64eb1fbb1d914c4d13c8970e1d9.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From aa69306fb5d82a03cd997a6703e819353f8160d0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 15 Nov 2017 17:29:51 +0100 -Subject: [PATCH 097/327] time/hrtimer: avoid schedule_work() with interrupts +Subject: [PATCH 097/330] time/hrtimer: avoid schedule_work() with interrupts disabled -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The NOHZ code tries to schedule a workqueue with interrupts disabled. Since this does not work -RT I am switching it to swork instead. diff --git a/debian/patches-rt/0098-hrtimer-consolidate-hrtimer_init-hrtimer_init_sleepe.patch b/debian/patches-rt/0098-hrtimer-consolidate-hrtimer_init-hrtimer_init_sleepe.patch index 028ea91b4..aa3be9035 100644 --- a/debian/patches-rt/0098-hrtimer-consolidate-hrtimer_init-hrtimer_init_sleepe.patch +++ b/debian/patches-rt/0098-hrtimer-consolidate-hrtimer_init-hrtimer_init_sleepe.patch @@ -1,12 +1,12 @@ -From 9d881c5e2519bd672c3a549e82cfee2bc16ee600 Mon Sep 17 00:00:00 2001 -Message-Id: <9d881c5e2519bd672c3a549e82cfee2bc16ee600.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 6baf45cf7600734706bc0491ef07c82537459f6a Mon Sep 17 00:00:00 2001 +Message-Id: <6baf45cf7600734706bc0491ef07c82537459f6a.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 3 Jul 2018 11:25:41 +0200 -Subject: [PATCH 098/327] hrtimer: consolidate hrtimer_init() + +Subject: [PATCH 098/330] hrtimer: consolidate hrtimer_init() + hrtimer_init_sleeper() calls -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz hrtimer_init_sleeper() calls require a prior initialisation of the hrtimer object with hrtimer_init(). Lets make the initialisation of diff --git a/debian/patches-rt/0099-hrtimers-Prepare-full-preemption.patch b/debian/patches-rt/0099-hrtimers-Prepare-full-preemption.patch index 637b7fa0f..ca83729b6 100644 --- a/debian/patches-rt/0099-hrtimers-Prepare-full-preemption.patch +++ b/debian/patches-rt/0099-hrtimers-Prepare-full-preemption.patch @@ -1,11 +1,11 @@ -From 6704bcf1fe74cbf53686910ac00916d3a43bfb8b Mon Sep 17 00:00:00 2001 -Message-Id: <6704bcf1fe74cbf53686910ac00916d3a43bfb8b.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From c345c877f92b8c7976387fc239f175e11e40c644 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:34 -0500 -Subject: [PATCH 099/327] hrtimers: Prepare full preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 099/330] hrtimers: Prepare full preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Make cancellation of a running callback in softirq context safe against preemption. diff --git a/debian/patches-rt/0100-hrtimer-by-timers-by-default-into-the-softirq-contex.patch b/debian/patches-rt/0100-hrtimer-by-timers-by-default-into-the-softirq-contex.patch index 71b259986..9843110fa 100644 --- a/debian/patches-rt/0100-hrtimer-by-timers-by-default-into-the-softirq-contex.patch +++ b/debian/patches-rt/0100-hrtimer-by-timers-by-default-into-the-softirq-contex.patch @@ -1,12 +1,12 @@ -From 4a9fa2b1406ed2f87ad332819a38ffd70f85d9c7 Mon Sep 17 00:00:00 2001 -Message-Id: <4a9fa2b1406ed2f87ad332819a38ffd70f85d9c7.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 77dee9ee16bb3b5fe1fb2798f86a011a04428821 Mon Sep 17 00:00:00 2001 +Message-Id: <77dee9ee16bb3b5fe1fb2798f86a011a04428821.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 3 Jul 2009 08:44:31 -0500 -Subject: [PATCH 100/327] hrtimer: by timers by default into the softirq +Subject: [PATCH 100/330] hrtimer: by timers by default into the softirq context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz We can't have hrtimers callbacks running in hardirq context on RT. Therefore the timers are deferred to the softirq context by default. diff --git a/debian/patches-rt/0101-sched-fair-Make-the-hrtimers-non-hard-again.patch b/debian/patches-rt/0101-sched-fair-Make-the-hrtimers-non-hard-again.patch index edea39b02..df462b1c0 100644 --- a/debian/patches-rt/0101-sched-fair-Make-the-hrtimers-non-hard-again.patch +++ b/debian/patches-rt/0101-sched-fair-Make-the-hrtimers-non-hard-again.patch @@ -1,11 +1,11 @@ -From 082e4884cb260e9f3cbe76aafdfd47a8b484835c Mon Sep 17 00:00:00 2001 -Message-Id: <082e4884cb260e9f3cbe76aafdfd47a8b484835c.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From b2f6295389d39c26d8cfa3280dfd28aee4e86da0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 8 Jan 2019 12:31:06 +0100 -Subject: [PATCH 101/327] sched/fair: Make the hrtimers non-hard again -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 101/330] sched/fair: Make the hrtimers non-hard again +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Since commit "sched/fair: Robustify CFS-bandwidth timer locking" both hrtimer can run in softirq context because now interrupts are disabled diff --git a/debian/patches-rt/0102-hrtimer-Move-schedule_work-call-to-helper-thread.patch b/debian/patches-rt/0102-hrtimer-Move-schedule_work-call-to-helper-thread.patch index 84865f51e..cabccd12b 100644 --- a/debian/patches-rt/0102-hrtimer-Move-schedule_work-call-to-helper-thread.patch +++ b/debian/patches-rt/0102-hrtimer-Move-schedule_work-call-to-helper-thread.patch @@ -1,11 +1,11 @@ -From 86188a58273ca07bdbc3b7bb9d9ce78806103282 Mon Sep 17 00:00:00 2001 -Message-Id: <86188a58273ca07bdbc3b7bb9d9ce78806103282.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d49e5f82ce97ab7def9c08a828d4fca4d96ea540 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Yang Shi Date: Mon, 16 Sep 2013 14:09:19 -0700 -Subject: [PATCH 102/327] hrtimer: Move schedule_work call to helper thread -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 102/330] hrtimer: Move schedule_work call to helper thread +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz When run ltp leapsec_timer test, the following call trace is caught: diff --git a/debian/patches-rt/0103-hrtimer-move-state-change-before-hrtimer_cancel-in-d.patch b/debian/patches-rt/0103-hrtimer-move-state-change-before-hrtimer_cancel-in-d.patch index 50b471d33..daeef4d55 100644 --- a/debian/patches-rt/0103-hrtimer-move-state-change-before-hrtimer_cancel-in-d.patch +++ b/debian/patches-rt/0103-hrtimer-move-state-change-before-hrtimer_cancel-in-d.patch @@ -1,12 +1,12 @@ -From b0dd1e5d1587db55eb0310f7efa3a684ded20dc8 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8764dfa5aa683087cc0a49bdaa9adc6aa6bf36ad Mon Sep 17 00:00:00 2001 +Message-Id: <8764dfa5aa683087cc0a49bdaa9adc6aa6bf36ad.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 6 Dec 2018 10:15:13 +0100 -Subject: [PATCH 103/327] hrtimer: move state change before hrtimer_cancel in +Subject: [PATCH 103/330] hrtimer: move state change before hrtimer_cancel in do_nanosleep() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz There is a small window between setting t->task to NULL and waking the task up (which would set TASK_RUNNING). So the timer would fire, run and diff --git a/debian/patches-rt/0104-posix-timers-Thread-posix-cpu-timers-on-rt.patch b/debian/patches-rt/0104-posix-timers-Thread-posix-cpu-timers-on-rt.patch index 9ed99a1eb..f4a180198 100644 --- a/debian/patches-rt/0104-posix-timers-Thread-posix-cpu-timers-on-rt.patch +++ b/debian/patches-rt/0104-posix-timers-Thread-posix-cpu-timers-on-rt.patch @@ -1,11 +1,11 @@ -From 047a6b7143ebeb532949745b679055929b22140e Mon Sep 17 00:00:00 2001 -Message-Id: <047a6b7143ebeb532949745b679055929b22140e.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 3f690131ebcac46f3552283e10b2bd60beceecd6 Mon Sep 17 00:00:00 2001 +Message-Id: <3f690131ebcac46f3552283e10b2bd60beceecd6.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: John Stultz Date: Fri, 3 Jul 2009 08:29:58 -0500 -Subject: [PATCH 104/327] posix-timers: Thread posix-cpu-timers on -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 104/330] posix-timers: Thread posix-cpu-timers on -rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz posix-cpu-timer code takes non -rt safe locks in hard irq context. Move it to a thread. diff --git a/debian/patches-rt/0105-sched-Move-task_struct-cleanup-to-RCU.patch b/debian/patches-rt/0105-sched-Move-task_struct-cleanup-to-RCU.patch index fa29e99cb..a02293304 100644 --- a/debian/patches-rt/0105-sched-Move-task_struct-cleanup-to-RCU.patch +++ b/debian/patches-rt/0105-sched-Move-task_struct-cleanup-to-RCU.patch @@ -1,11 +1,11 @@ -From 482785c06adadbb608860d8c2d7353b4a51598ed Mon Sep 17 00:00:00 2001 -Message-Id: <482785c06adadbb608860d8c2d7353b4a51598ed.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 13d5f9e40172286d31f8920528f5a37a6208068c Mon Sep 17 00:00:00 2001 +Message-Id: <13d5f9e40172286d31f8920528f5a37a6208068c.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 31 May 2011 16:59:16 +0200 -Subject: [PATCH 105/327] sched: Move task_struct cleanup to RCU -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 105/330] sched: Move task_struct cleanup to RCU +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz __put_task_struct() does quite some expensive work. We don't want to burden random tasks with that. diff --git a/debian/patches-rt/0106-sched-Limit-the-number-of-task-migrations-per-batch.patch b/debian/patches-rt/0106-sched-Limit-the-number-of-task-migrations-per-batch.patch index 0c33def36..39d2f69f9 100644 --- a/debian/patches-rt/0106-sched-Limit-the-number-of-task-migrations-per-batch.patch +++ b/debian/patches-rt/0106-sched-Limit-the-number-of-task-migrations-per-batch.patch @@ -1,11 +1,11 @@ -From 780fc1971a74db9cc19b39a38aa1e51b669732d5 Mon Sep 17 00:00:00 2001 -Message-Id: <780fc1971a74db9cc19b39a38aa1e51b669732d5.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 377f1de1f1aa4bbd7afa40c6d4262eae1780b84b Mon Sep 17 00:00:00 2001 +Message-Id: <377f1de1f1aa4bbd7afa40c6d4262eae1780b84b.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 6 Jun 2011 12:12:51 +0200 -Subject: [PATCH 106/327] sched: Limit the number of task migrations per batch -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 106/330] sched: Limit the number of task migrations per batch +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Put an upper limit on the number of tasks which are migrated per batch to avoid large latencies. diff --git a/debian/patches-rt/0107-sched-Move-mmdrop-to-RCU-on-RT.patch b/debian/patches-rt/0107-sched-Move-mmdrop-to-RCU-on-RT.patch index c66e63b03..df908443d 100644 --- a/debian/patches-rt/0107-sched-Move-mmdrop-to-RCU-on-RT.patch +++ b/debian/patches-rt/0107-sched-Move-mmdrop-to-RCU-on-RT.patch @@ -1,11 +1,11 @@ -From 0bc84183d2823067f63028f0b91562beeea3457f Mon Sep 17 00:00:00 2001 -Message-Id: <0bc84183d2823067f63028f0b91562beeea3457f.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 3691a6aac0ee8777a3ebd30b1dcfbfc3b254af9b Mon Sep 17 00:00:00 2001 +Message-Id: <3691a6aac0ee8777a3ebd30b1dcfbfc3b254af9b.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 6 Jun 2011 12:20:33 +0200 -Subject: [PATCH 107/327] sched: Move mmdrop to RCU on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 107/330] sched: Move mmdrop to RCU on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Takes sleeping locks and calls into the memory allocator, so nothing we want to do in task switch and oder atomic contexts. diff --git a/debian/patches-rt/0108-kernel-sched-move-stack-kprobe-clean-up-to-__put_tas.patch b/debian/patches-rt/0108-kernel-sched-move-stack-kprobe-clean-up-to-__put_tas.patch index 01dee5048..d49b5ce4d 100644 --- a/debian/patches-rt/0108-kernel-sched-move-stack-kprobe-clean-up-to-__put_tas.patch +++ b/debian/patches-rt/0108-kernel-sched-move-stack-kprobe-clean-up-to-__put_tas.patch @@ -1,12 +1,12 @@ -From 61acabdefbe52dea4b27dacace8e566ebce5398d Mon Sep 17 00:00:00 2001 -Message-Id: <61acabdefbe52dea4b27dacace8e566ebce5398d.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8b0464e028d5ed9a0c1f88c889ddcd0822df72b8 Mon Sep 17 00:00:00 2001 +Message-Id: <8b0464e028d5ed9a0c1f88c889ddcd0822df72b8.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 21 Nov 2016 19:31:08 +0100 -Subject: [PATCH 108/327] kernel/sched: move stack + kprobe clean up to +Subject: [PATCH 108/330] kernel/sched: move stack + kprobe clean up to __put_task_struct() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz There is no need to free the stack before the task struct (except for reasons mentioned in commit 68f24b08ee89 ("sched/core: Free the stack early if diff --git a/debian/patches-rt/0109-sched-Add-saved_state-for-tasks-blocked-on-sleeping-.patch b/debian/patches-rt/0109-sched-Add-saved_state-for-tasks-blocked-on-sleeping-.patch index ee0c35911..a81e7b5f1 100644 --- a/debian/patches-rt/0109-sched-Add-saved_state-for-tasks-blocked-on-sleeping-.patch +++ b/debian/patches-rt/0109-sched-Add-saved_state-for-tasks-blocked-on-sleeping-.patch @@ -1,12 +1,12 @@ -From 74b050b3c0f543c3697cb8a4d1f5095fd0922ef6 Mon Sep 17 00:00:00 2001 -Message-Id: <74b050b3c0f543c3697cb8a4d1f5095fd0922ef6.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From fbc8583b80053646d79cb11b49a44ac16f30a7f1 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 25 Jun 2011 09:21:04 +0200 -Subject: [PATCH 109/327] sched: Add saved_state for tasks blocked on sleeping +Subject: [PATCH 109/330] sched: Add saved_state for tasks blocked on sleeping locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Spinlocks are state preserving in !RT. RT changes the state when a task gets blocked on a lock. So we need to remember the state before diff --git a/debian/patches-rt/0110-sched-Do-not-account-rcu_preempt_depth-on-RT-in-migh.patch b/debian/patches-rt/0110-sched-Do-not-account-rcu_preempt_depth-on-RT-in-migh.patch index f5ed27cf7..65e7c4560 100644 --- a/debian/patches-rt/0110-sched-Do-not-account-rcu_preempt_depth-on-RT-in-migh.patch +++ b/debian/patches-rt/0110-sched-Do-not-account-rcu_preempt_depth-on-RT-in-migh.patch @@ -1,12 +1,12 @@ -From 22065d3d9cb2d816e6f264c6886ef292115a89f0 Mon Sep 17 00:00:00 2001 -Message-Id: <22065d3d9cb2d816e6f264c6886ef292115a89f0.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d8dbc6b79d4ddd01f7c17fe56f38a31657f3971c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 7 Jun 2011 09:19:06 +0200 -Subject: [PATCH 110/327] sched: Do not account rcu_preempt_depth on RT in +Subject: [PATCH 110/330] sched: Do not account rcu_preempt_depth on RT in might_sleep() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz RT changes the rcu_preempt_depth semantics, so we cannot check for it in might_sleep(). diff --git a/debian/patches-rt/0111-sched-Use-the-proper-LOCK_OFFSET-for-cond_resched.patch b/debian/patches-rt/0111-sched-Use-the-proper-LOCK_OFFSET-for-cond_resched.patch index b7fc56bdf..766a38daf 100644 --- a/debian/patches-rt/0111-sched-Use-the-proper-LOCK_OFFSET-for-cond_resched.patch +++ b/debian/patches-rt/0111-sched-Use-the-proper-LOCK_OFFSET-for-cond_resched.patch @@ -1,11 +1,11 @@ -From 8765e86a1108396b938c68d33ca50ca039f51e1c Mon Sep 17 00:00:00 2001 -Message-Id: <8765e86a1108396b938c68d33ca50ca039f51e1c.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 39a6634075bf2d2269ccaabe49eb73b4cbae4c46 Mon Sep 17 00:00:00 2001 +Message-Id: <39a6634075bf2d2269ccaabe49eb73b4cbae4c46.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 22:51:33 +0200 -Subject: [PATCH 111/327] sched: Use the proper LOCK_OFFSET for cond_resched() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 111/330] sched: Use the proper LOCK_OFFSET for cond_resched() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz RT does not increment preempt count when a 'sleeping' spinlock is locked. Update PREEMPT_LOCK_OFFSET for that case. diff --git a/debian/patches-rt/0112-sched-Disable-TTWU_QUEUE-on-RT.patch b/debian/patches-rt/0112-sched-Disable-TTWU_QUEUE-on-RT.patch index e8e91b3c5..2f31937da 100644 --- a/debian/patches-rt/0112-sched-Disable-TTWU_QUEUE-on-RT.patch +++ b/debian/patches-rt/0112-sched-Disable-TTWU_QUEUE-on-RT.patch @@ -1,11 +1,11 @@ -From 47079ff574adc786f3fa7e05ecb95d66381e94cb Mon Sep 17 00:00:00 2001 -Message-Id: <47079ff574adc786f3fa7e05ecb95d66381e94cb.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5effa31e35d987848f4b459f305ad7dc1b61cd48 Mon Sep 17 00:00:00 2001 +Message-Id: <5effa31e35d987848f4b459f305ad7dc1b61cd48.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 13 Sep 2011 16:42:35 +0200 -Subject: [PATCH 112/327] sched: Disable TTWU_QUEUE on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 112/330] sched: Disable TTWU_QUEUE on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The queued remote wakeup mechanism can introduce rather large latencies if the number of migrated tasks is high. Disable it for RT. diff --git a/debian/patches-rt/0113-sched-workqueue-Only-wake-up-idle-workers-if-not-blo.patch b/debian/patches-rt/0113-sched-workqueue-Only-wake-up-idle-workers-if-not-blo.patch index 0b89b1024..733a57dbd 100644 --- a/debian/patches-rt/0113-sched-workqueue-Only-wake-up-idle-workers-if-not-blo.patch +++ b/debian/patches-rt/0113-sched-workqueue-Only-wake-up-idle-workers-if-not-blo.patch @@ -1,12 +1,12 @@ -From 1079c23476ecb96b3ff4b06b739a909880f1d562 Mon Sep 17 00:00:00 2001 -Message-Id: <1079c23476ecb96b3ff4b06b739a909880f1d562.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From c6c2b9b244badb5d0cad014f0e5ff7db89e43ffb Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Steven Rostedt Date: Mon, 18 Mar 2013 15:12:49 -0400 -Subject: [PATCH 113/327] sched/workqueue: Only wake up idle workers if not +Subject: [PATCH 113/330] sched/workqueue: Only wake up idle workers if not blocked on sleeping spin lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz In -rt, most spin_locks() turn into mutexes. One of these spin_lock conversions is performed on the workqueue gcwq->lock. When the idle diff --git a/debian/patches-rt/0114-rt-Increase-decrease-the-nr-of-migratory-tasks-when-.patch b/debian/patches-rt/0114-rt-Increase-decrease-the-nr-of-migratory-tasks-when-.patch index f4b69c002..46d1a9914 100644 --- a/debian/patches-rt/0114-rt-Increase-decrease-the-nr-of-migratory-tasks-when-.patch +++ b/debian/patches-rt/0114-rt-Increase-decrease-the-nr-of-migratory-tasks-when-.patch @@ -1,12 +1,12 @@ -From 38752bfbbf290971b71dd215cdab8efc6072bc43 Mon Sep 17 00:00:00 2001 -Message-Id: <38752bfbbf290971b71dd215cdab8efc6072bc43.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 51581e70171fc658c9d84e6bcbf4f165888c3602 Mon Sep 17 00:00:00 2001 +Message-Id: <51581e70171fc658c9d84e6bcbf4f165888c3602.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Daniel Bristot de Oliveira Date: Mon, 26 Jun 2017 17:07:15 +0200 -Subject: [PATCH 114/327] rt: Increase/decrease the nr of migratory tasks when +Subject: [PATCH 114/330] rt: Increase/decrease the nr of migratory tasks when enabling/disabling migration -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz There is a problem in the migrate_disable()/enable() implementation regarding the number of migratory tasks in the rt/dl RQs. The problem diff --git a/debian/patches-rt/0115-hotplug-Lightweight-get-online-cpus.patch b/debian/patches-rt/0115-hotplug-Lightweight-get-online-cpus.patch index b1ccab832..68c201287 100644 --- a/debian/patches-rt/0115-hotplug-Lightweight-get-online-cpus.patch +++ b/debian/patches-rt/0115-hotplug-Lightweight-get-online-cpus.patch @@ -1,11 +1,11 @@ -From a424e8aaf3de1c9c7ba828e6187a9395a05065fd Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 760fbae52ee672d35a40f60ad9b510f1f7ef686d Mon Sep 17 00:00:00 2001 +Message-Id: <760fbae52ee672d35a40f60ad9b510f1f7ef686d.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 15 Jun 2011 12:36:06 +0200 -Subject: [PATCH 115/327] hotplug: Lightweight get online cpus -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 115/330] hotplug: Lightweight get online cpus +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz get_online_cpus() is a heavy weight function which involves a global mutex. migrate_disable() wants a simpler construct which prevents only diff --git a/debian/patches-rt/0116-trace-Add-migrate-disabled-counter-to-tracing-output.patch b/debian/patches-rt/0116-trace-Add-migrate-disabled-counter-to-tracing-output.patch index 34d0fd542..a8dce3b92 100644 --- a/debian/patches-rt/0116-trace-Add-migrate-disabled-counter-to-tracing-output.patch +++ b/debian/patches-rt/0116-trace-Add-migrate-disabled-counter-to-tracing-output.patch @@ -1,11 +1,11 @@ -From c95438ace7d6cf226cf7d7bd6fb278f4c044abf4 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 7499455407bb0dbe20122d70909f1500c1004d14 Mon Sep 17 00:00:00 2001 +Message-Id: <7499455407bb0dbe20122d70909f1500c1004d14.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:56:42 +0200 -Subject: [PATCH 116/327] trace: Add migrate-disabled counter to tracing output -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 116/330] trace: Add migrate-disabled counter to tracing output +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Signed-off-by: Thomas Gleixner --- diff --git a/debian/patches-rt/0117-lockdep-Make-it-RT-aware.patch b/debian/patches-rt/0117-lockdep-Make-it-RT-aware.patch index 289cb13ef..17420d668 100644 --- a/debian/patches-rt/0117-lockdep-Make-it-RT-aware.patch +++ b/debian/patches-rt/0117-lockdep-Make-it-RT-aware.patch @@ -1,11 +1,11 @@ -From e30444a619dcdef52eae15a74928847c44ac84e8 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 6b13a5f0f483a4be1ea620a8681b2c3ad1068a53 Mon Sep 17 00:00:00 2001 +Message-Id: <6b13a5f0f483a4be1ea620a8681b2c3ad1068a53.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 18:51:23 +0200 -Subject: [PATCH 117/327] lockdep: Make it RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 117/330] lockdep: Make it RT aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz teach lockdep that we don't really do softirqs on -RT. diff --git a/debian/patches-rt/0118-tasklet-Prevent-tasklets-from-going-into-infinite-sp.patch b/debian/patches-rt/0118-tasklet-Prevent-tasklets-from-going-into-infinite-sp.patch index 4eea5b4f4..cce48e81e 100644 --- a/debian/patches-rt/0118-tasklet-Prevent-tasklets-from-going-into-infinite-sp.patch +++ b/debian/patches-rt/0118-tasklet-Prevent-tasklets-from-going-into-infinite-sp.patch @@ -1,12 +1,12 @@ -From ed95e55ce0acccaeb09908df0d79e91e88dc5046 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From f32e8b7b0f6569d517f577809cb9172aebe83064 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Ingo Molnar Date: Tue, 29 Nov 2011 20:18:22 -0500 -Subject: [PATCH 118/327] tasklet: Prevent tasklets from going into infinite +Subject: [PATCH 118/330] tasklet: Prevent tasklets from going into infinite spin in RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz When CONFIG_PREEMPT_RT_FULL is enabled, tasklets run as threads, and spinlocks turn are mutexes. But this can cause issues with diff --git a/debian/patches-rt/0119-softirq-Check-preemption-after-reenabling-interrupts.patch b/debian/patches-rt/0119-softirq-Check-preemption-after-reenabling-interrupts.patch index 7e35f7450..6f781cbc9 100644 --- a/debian/patches-rt/0119-softirq-Check-preemption-after-reenabling-interrupts.patch +++ b/debian/patches-rt/0119-softirq-Check-preemption-after-reenabling-interrupts.patch @@ -1,11 +1,11 @@ -From 3ad88e385b601fecc0834625ca606f3b417ac848 Mon Sep 17 00:00:00 2001 -Message-Id: <3ad88e385b601fecc0834625ca606f3b417ac848.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 48694ef24846509a7675309ef30fca17b76fcb07 Mon Sep 17 00:00:00 2001 +Message-Id: <48694ef24846509a7675309ef30fca17b76fcb07.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 13 Nov 2011 17:17:09 +0100 -Subject: [PATCH 119/327] softirq: Check preemption after reenabling interrupts -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 119/330] softirq: Check preemption after reenabling interrupts +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz raise_softirq_irqoff() disables interrupts and wakes the softirq daemon, but after reenabling interrupts there is no preemption check, @@ -120,7 +120,7 @@ index 86a709954f5a..9c069ef83d6d 100644 return 0; } diff --git a/net/core/dev.c b/net/core/dev.c -index 9ccc14200b80..a109f1acd3a0 100644 +index 50498a75c04b..0e4cff101523 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -2727,6 +2727,7 @@ static void __netif_reschedule(struct Qdisc *q) @@ -147,7 +147,7 @@ index 9ccc14200b80..a109f1acd3a0 100644 atomic_long_inc(&skb->dev->rx_dropped); kfree_skb(skb); -@@ -5804,12 +5807,14 @@ static void net_rps_action_and_irq_enable(struct softnet_data *sd) +@@ -5814,12 +5817,14 @@ static void net_rps_action_and_irq_enable(struct softnet_data *sd) sd->rps_ipi_list = NULL; local_irq_enable(); @@ -162,7 +162,7 @@ index 9ccc14200b80..a109f1acd3a0 100644 } static bool sd_has_rps_ipi_waiting(struct softnet_data *sd) -@@ -5887,6 +5892,7 @@ void __napi_schedule(struct napi_struct *n) +@@ -5897,6 +5902,7 @@ void __napi_schedule(struct napi_struct *n) local_irq_save(flags); ____napi_schedule(this_cpu_ptr(&softnet_data), n); local_irq_restore(flags); @@ -170,7 +170,7 @@ index 9ccc14200b80..a109f1acd3a0 100644 } EXPORT_SYMBOL(__napi_schedule); -@@ -9491,6 +9497,7 @@ static int dev_cpu_dead(unsigned int oldcpu) +@@ -9501,6 +9507,7 @@ static int dev_cpu_dead(unsigned int oldcpu) raise_softirq_irqoff(NET_TX_SOFTIRQ); local_irq_enable(); diff --git a/debian/patches-rt/0120-softirq-Disable-softirq-stacks-for-RT.patch b/debian/patches-rt/0120-softirq-Disable-softirq-stacks-for-RT.patch index 90810a65a..778487530 100644 --- a/debian/patches-rt/0120-softirq-Disable-softirq-stacks-for-RT.patch +++ b/debian/patches-rt/0120-softirq-Disable-softirq-stacks-for-RT.patch @@ -1,11 +1,11 @@ -From 767694c66ee6736de1aadbda3d762e54b2a6e7f5 Mon Sep 17 00:00:00 2001 -Message-Id: <767694c66ee6736de1aadbda3d762e54b2a6e7f5.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 17760159c08298032722aec1863b38e4e9d7c8df Mon Sep 17 00:00:00 2001 +Message-Id: <17760159c08298032722aec1863b38e4e9d7c8df.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 13:59:17 +0200 -Subject: [PATCH 120/327] softirq: Disable softirq stacks for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 120/330] softirq: Disable softirq stacks for RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Disable extra stacks for softirqs. We want to preempt softirqs and having them on special IRQ-stack does not make this easier. diff --git a/debian/patches-rt/0121-softirq-Split-softirq-locks.patch b/debian/patches-rt/0121-softirq-Split-softirq-locks.patch index c34c7c221..e1358992c 100644 --- a/debian/patches-rt/0121-softirq-Split-softirq-locks.patch +++ b/debian/patches-rt/0121-softirq-Split-softirq-locks.patch @@ -1,11 +1,11 @@ -From af59f89abaf51d204fd877dd5585b1505a6b2e36 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 7ffb028cfaf7252d1b4485546feefed68498c041 Mon Sep 17 00:00:00 2001 +Message-Id: <7ffb028cfaf7252d1b4485546feefed68498c041.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 4 Oct 2012 14:20:47 +0100 -Subject: [PATCH 121/327] softirq: Split softirq locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 121/330] softirq: Split softirq locks +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The 3.x RT series removed the split softirq implementation in favour of pushing softirq processing into the context of the thread which diff --git a/debian/patches-rt/0122-net-core-use-local_bh_disable-in-netif_rx_ni.patch b/debian/patches-rt/0122-net-core-use-local_bh_disable-in-netif_rx_ni.patch index 1feb6fd60..a604d382c 100644 --- a/debian/patches-rt/0122-net-core-use-local_bh_disable-in-netif_rx_ni.patch +++ b/debian/patches-rt/0122-net-core-use-local_bh_disable-in-netif_rx_ni.patch @@ -1,11 +1,11 @@ -From 9337b7f3c247191beaf253453652d4c026ec6e44 Mon Sep 17 00:00:00 2001 -Message-Id: <9337b7f3c247191beaf253453652d4c026ec6e44.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From c86a807b0ba3c42e49539839c06055e81dc1f8c5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 16 Jun 2017 19:03:16 +0200 -Subject: [PATCH 122/327] net/core: use local_bh_disable() in netif_rx_ni() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 122/330] net/core: use local_bh_disable() in netif_rx_ni() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz In 2004 netif_rx_ni() gained a preempt_disable() section around netif_rx() and its do_softirq() + testing for it. The do_softirq() part @@ -22,7 +22,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/net/core/dev.c b/net/core/dev.c -index a109f1acd3a0..c5901d343d0a 100644 +index 0e4cff101523..d4b73961f54b 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -4532,11 +4532,9 @@ int netif_rx_ni(struct sk_buff *skb) diff --git a/debian/patches-rt/0123-genirq-Allow-disabling-of-softirq-processing-in-irq-.patch b/debian/patches-rt/0123-genirq-Allow-disabling-of-softirq-processing-in-irq-.patch index cdd11f2a7..4a835594b 100644 --- a/debian/patches-rt/0123-genirq-Allow-disabling-of-softirq-processing-in-irq-.patch +++ b/debian/patches-rt/0123-genirq-Allow-disabling-of-softirq-processing-in-irq-.patch @@ -1,12 +1,12 @@ -From 5ffe6d5cdde4354111d57c27d3e3414a81d2635a Mon Sep 17 00:00:00 2001 -Message-Id: <5ffe6d5cdde4354111d57c27d3e3414a81d2635a.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 9a7d0a7baf8fdc58ae85f28aa8ddc11e725e9506 Mon Sep 17 00:00:00 2001 +Message-Id: <9a7d0a7baf8fdc58ae85f28aa8ddc11e725e9506.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 31 Jan 2012 13:01:27 +0100 -Subject: [PATCH 123/327] genirq: Allow disabling of softirq processing in irq +Subject: [PATCH 123/330] genirq: Allow disabling of softirq processing in irq thread context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The processing of softirqs in irq thread context is a performance gain for the non-rt workloads of a system, but it's counterproductive for diff --git a/debian/patches-rt/0124-softirq-split-timer-softirqs-out-of-ksoftirqd.patch b/debian/patches-rt/0124-softirq-split-timer-softirqs-out-of-ksoftirqd.patch index 7d75494d8..7c027fec7 100644 --- a/debian/patches-rt/0124-softirq-split-timer-softirqs-out-of-ksoftirqd.patch +++ b/debian/patches-rt/0124-softirq-split-timer-softirqs-out-of-ksoftirqd.patch @@ -1,11 +1,11 @@ -From 6dcb9e9c52f4e07e1362815f990938c459b2ab6a Mon Sep 17 00:00:00 2001 -Message-Id: <6dcb9e9c52f4e07e1362815f990938c459b2ab6a.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 37c06241be6216ceae2fe1bc4680b979adfedc9e Mon Sep 17 00:00:00 2001 +Message-Id: <37c06241be6216ceae2fe1bc4680b979adfedc9e.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 20 Jan 2016 16:34:17 +0100 -Subject: [PATCH 124/327] softirq: split timer softirqs out of ksoftirqd -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 124/330] softirq: split timer softirqs out of ksoftirqd +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The softirqd runs in -RT with SCHED_FIFO (prio 1) and deals mostly with timer wakeup which can not happen in hardirq context. The prio has been diff --git a/debian/patches-rt/0125-softirq-Avoid-local_softirq_pending-messages-if-ksof.patch b/debian/patches-rt/0125-softirq-Avoid-local_softirq_pending-messages-if-ksof.patch index 6a10dc009..eee1b3468 100644 --- a/debian/patches-rt/0125-softirq-Avoid-local_softirq_pending-messages-if-ksof.patch +++ b/debian/patches-rt/0125-softirq-Avoid-local_softirq_pending-messages-if-ksof.patch @@ -1,12 +1,12 @@ -From 4523d3e64f8b575b704a3daa83f3d41273dcb01d Mon Sep 17 00:00:00 2001 -Message-Id: <4523d3e64f8b575b704a3daa83f3d41273dcb01d.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8d8149c8babe49e42b6924b72fec5c341ce59609 Mon Sep 17 00:00:00 2001 +Message-Id: <8d8149c8babe49e42b6924b72fec5c341ce59609.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 18 Feb 2019 13:19:59 +0100 -Subject: [PATCH 125/327] softirq: Avoid "local_softirq_pending" messages if +Subject: [PATCH 125/330] softirq: Avoid "local_softirq_pending" messages if ksoftirqd is blocked -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz If the ksoftirqd thread has a softirq pending and is blocked on the `local_softirq_locks' lock then softirq_check_pending_idle() won't diff --git a/debian/patches-rt/0126-softirq-Avoid-local_softirq_pending-messages-if-task.patch b/debian/patches-rt/0126-softirq-Avoid-local_softirq_pending-messages-if-task.patch index 669ba0383..eaad82232 100644 --- a/debian/patches-rt/0126-softirq-Avoid-local_softirq_pending-messages-if-task.patch +++ b/debian/patches-rt/0126-softirq-Avoid-local_softirq_pending-messages-if-task.patch @@ -1,12 +1,12 @@ -From 811833713342f2b67a0b3ebff0f0d54f51f4e9ac Mon Sep 17 00:00:00 2001 -Message-Id: <811833713342f2b67a0b3ebff0f0d54f51f4e9ac.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From bd0ec3ed10c820a977c548af017f27c3c8516d09 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Feb 2019 16:49:29 +0100 -Subject: [PATCH 126/327] softirq: Avoid "local_softirq_pending" messages if +Subject: [PATCH 126/330] softirq: Avoid "local_softirq_pending" messages if task is in cpu_chill() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz If the softirq thread enters cpu_chill() then ->state is UNINTERRUPTIBLE and has no ->pi_blocked_on set and so its mask is not taken into account. diff --git a/debian/patches-rt/0127-rtmutex-trylock-is-okay-on-RT.patch b/debian/patches-rt/0127-rtmutex-trylock-is-okay-on-RT.patch index 71a11c01a..d4ce76963 100644 --- a/debian/patches-rt/0127-rtmutex-trylock-is-okay-on-RT.patch +++ b/debian/patches-rt/0127-rtmutex-trylock-is-okay-on-RT.patch @@ -1,11 +1,11 @@ -From 8819d5254b9159cea9ec9ea4264bea714c7803ac Mon Sep 17 00:00:00 2001 -Message-Id: <8819d5254b9159cea9ec9ea4264bea714c7803ac.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 6fd6ead7c002cc211af77ed296eb8076cc06189e Mon Sep 17 00:00:00 2001 +Message-Id: <6fd6ead7c002cc211af77ed296eb8076cc06189e.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 2 Dec 2015 11:34:07 +0100 -Subject: [PATCH 127/327] rtmutex: trylock is okay on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 127/330] rtmutex: trylock is okay on -RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz non-RT kernel could deadlock on rt_mutex_trylock() in softirq context. On -RT we don't run softirqs in IRQ context but in thread context so it is diff --git a/debian/patches-rt/0128-fs-nfs-turn-rmdir_sem-into-a-semaphore.patch b/debian/patches-rt/0128-fs-nfs-turn-rmdir_sem-into-a-semaphore.patch index 39f66bb4d..fd205a047 100644 --- a/debian/patches-rt/0128-fs-nfs-turn-rmdir_sem-into-a-semaphore.patch +++ b/debian/patches-rt/0128-fs-nfs-turn-rmdir_sem-into-a-semaphore.patch @@ -1,11 +1,11 @@ -From b45dbe89d1137c827c0b880c66f70070832367be Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From aa209e69997c5d05c47950bbf360bb3b36c56d4e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 15 Sep 2016 10:51:27 +0200 -Subject: [PATCH 128/327] fs/nfs: turn rmdir_sem into a semaphore -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 128/330] fs/nfs: turn rmdir_sem into a semaphore +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The RW semaphore had a reader side which used the _non_owner version because it most likely took the reader lock in one thread and released it diff --git a/debian/patches-rt/0129-rtmutex-Handle-the-various-new-futex-race-conditions.patch b/debian/patches-rt/0129-rtmutex-Handle-the-various-new-futex-race-conditions.patch index 9bcf4cade..0420c6dd5 100644 --- a/debian/patches-rt/0129-rtmutex-Handle-the-various-new-futex-race-conditions.patch +++ b/debian/patches-rt/0129-rtmutex-Handle-the-various-new-futex-race-conditions.patch @@ -1,11 +1,11 @@ -From 2452172b06a4c1ffb9a56eab07ae75372dc8ff0a Mon Sep 17 00:00:00 2001 -Message-Id: <2452172b06a4c1ffb9a56eab07ae75372dc8ff0a.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From dd0fd98a2b04d787c2bc1703d840f725950efb44 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 10 Jun 2011 11:04:15 +0200 -Subject: [PATCH 129/327] rtmutex: Handle the various new futex race conditions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 129/330] rtmutex: Handle the various new futex race conditions +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz RT opens a few new interesting race conditions in the rtmutex/futex combo due to futex hash bucket lock being a 'sleeping' spinlock and diff --git a/debian/patches-rt/0130-futex-Fix-bug-on-when-a-requeued-RT-task-times-out.patch b/debian/patches-rt/0130-futex-Fix-bug-on-when-a-requeued-RT-task-times-out.patch index 0035da9fe..4d06f51f5 100644 --- a/debian/patches-rt/0130-futex-Fix-bug-on-when-a-requeued-RT-task-times-out.patch +++ b/debian/patches-rt/0130-futex-Fix-bug-on-when-a-requeued-RT-task-times-out.patch @@ -1,11 +1,11 @@ -From 3b55384877a6b66992f53ca48b2e0c7b52aadcfe Mon Sep 17 00:00:00 2001 -Message-Id: <3b55384877a6b66992f53ca48b2e0c7b52aadcfe.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 1ac7fd9c7790dcd9a56dd4f5ee7c475334325588 Mon Sep 17 00:00:00 2001 +Message-Id: <1ac7fd9c7790dcd9a56dd4f5ee7c475334325588.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Steven Rostedt Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 130/327] futex: Fix bug on when a requeued RT task times out -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 130/330] futex: Fix bug on when a requeued RT task times out +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Requeue with timeout causes a bug with PREEMPT_RT_FULL. diff --git a/debian/patches-rt/0131-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch b/debian/patches-rt/0131-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch index 0d824ed16..a5b8476ba 100644 --- a/debian/patches-rt/0131-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch +++ b/debian/patches-rt/0131-futex-Ensure-lock-unlock-symetry-versus-pi_lock-and-.patch @@ -1,12 +1,12 @@ -From f8fdcafd3749db21474404cec4f42cbb6054768b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 9717072ba19978a6d8e38adb0d29c4e4f13fe5d5 Mon Sep 17 00:00:00 2001 +Message-Id: <9717072ba19978a6d8e38adb0d29c4e4f13fe5d5.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 1 Mar 2013 11:17:42 +0100 -Subject: [PATCH 131/327] futex: Ensure lock/unlock symetry versus pi_lock and +Subject: [PATCH 131/330] futex: Ensure lock/unlock symetry versus pi_lock and hash bucket lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz In exit_pi_state_list() we have the following locking construct: diff --git a/debian/patches-rt/0132-pid.h-include-atomic.h.patch b/debian/patches-rt/0132-pid.h-include-atomic.h.patch index ea0ddbda2..17b123565 100644 --- a/debian/patches-rt/0132-pid.h-include-atomic.h.patch +++ b/debian/patches-rt/0132-pid.h-include-atomic.h.patch @@ -1,11 +1,11 @@ -From 99aaad0ea9ee23d0ba791e1b17c351d4475c7c75 Mon Sep 17 00:00:00 2001 -Message-Id: <99aaad0ea9ee23d0ba791e1b17c351d4475c7c75.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d53b2ae993127a1b0d8ef29d0f3e2bfa6be672e2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Grygorii Strashko Date: Tue, 21 Jul 2015 19:43:56 +0300 -Subject: [PATCH 132/327] pid.h: include atomic.h -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 132/330] pid.h: include atomic.h +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz This patch fixes build error: CC kernel/pid_namespace.o diff --git a/debian/patches-rt/0133-arm-include-definition-for-cpumask_t.patch b/debian/patches-rt/0133-arm-include-definition-for-cpumask_t.patch index cde24f20f..9dc5fc9f3 100644 --- a/debian/patches-rt/0133-arm-include-definition-for-cpumask_t.patch +++ b/debian/patches-rt/0133-arm-include-definition-for-cpumask_t.patch @@ -1,11 +1,11 @@ -From c5159232b8108e74f309eddc832a043de0fc7e8a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 12acd35cb03c39a70b0114789cd0a9157f1ce48c Mon Sep 17 00:00:00 2001 +Message-Id: <12acd35cb03c39a70b0114789cd0a9157f1ce48c.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 22 Dec 2016 17:28:33 +0100 -Subject: [PATCH 133/327] arm: include definition for cpumask_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 133/330] arm: include definition for cpumask_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz This definition gets pulled in by other files. With the (later) split of RCU and spinlock.h it won't compile anymore. diff --git a/debian/patches-rt/0134-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch b/debian/patches-rt/0134-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch index 1aefe36e7..e31a634ec 100644 --- a/debian/patches-rt/0134-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch +++ b/debian/patches-rt/0134-locking-locktorture-Do-NOT-include-rwlock.h-directly.patch @@ -1,12 +1,12 @@ -From 4e55e676e90ed8345b4fc9e75ab2cbc9d292f2d4 Mon Sep 17 00:00:00 2001 -Message-Id: <4e55e676e90ed8345b4fc9e75ab2cbc9d292f2d4.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 71a35e0dd13879ed7303889af99754de08462969 Mon Sep 17 00:00:00 2001 +Message-Id: <71a35e0dd13879ed7303889af99754de08462969.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: "Wolfgang M. Reimer" Date: Tue, 21 Jul 2015 16:20:07 +0200 -Subject: [PATCH 134/327] locking: locktorture: Do NOT include rwlock.h +Subject: [PATCH 134/330] locking: locktorture: Do NOT include rwlock.h directly -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Including rwlock.h directly will cause kernel builds to fail if CONFIG_PREEMPT_RT_FULL is defined. The correct header file diff --git a/debian/patches-rt/0135-rtmutex-Add-rtmutex_lock_killable.patch b/debian/patches-rt/0135-rtmutex-Add-rtmutex_lock_killable.patch index e8b9567cf..4a55cc854 100644 --- a/debian/patches-rt/0135-rtmutex-Add-rtmutex_lock_killable.patch +++ b/debian/patches-rt/0135-rtmutex-Add-rtmutex_lock_killable.patch @@ -1,11 +1,11 @@ -From 1fcf466693d2f41fd5d9b2fa2af5e46e3901b2d8 Mon Sep 17 00:00:00 2001 -Message-Id: <1fcf466693d2f41fd5d9b2fa2af5e46e3901b2d8.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 3d8af4d515592cffd67fdcf39d35c64e7e83598c Mon Sep 17 00:00:00 2001 +Message-Id: <3d8af4d515592cffd67fdcf39d35c64e7e83598c.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 9 Jun 2011 11:43:52 +0200 -Subject: [PATCH 135/327] rtmutex: Add rtmutex_lock_killable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 135/330] rtmutex: Add rtmutex_lock_killable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Add "killable" type to rtmutex. We need this since rtmutex are used as "normal" mutexes which do use this type. diff --git a/debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch b/debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch index 634e0c87c..22b626d58 100644 --- a/debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch +++ b/debian/patches-rt/0136-rtmutex-Make-lock_killable-work.patch @@ -1,11 +1,11 @@ -From 99945d091d2189172b6395360f5e370724c862f0 Mon Sep 17 00:00:00 2001 -Message-Id: <99945d091d2189172b6395360f5e370724c862f0.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 069a09db29e6f1567519760e1d1b148c8dad75cb Mon Sep 17 00:00:00 2001 +Message-Id: <069a09db29e6f1567519760e1d1b148c8dad75cb.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 1 Apr 2017 12:50:59 +0200 -Subject: [PATCH 136/327] rtmutex: Make lock_killable work -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 136/330] rtmutex: Make lock_killable work +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Locking an rt mutex killable does not work because signal handling is restricted to TASK_INTERRUPTIBLE. diff --git a/debian/patches-rt/0137-spinlock-Split-the-lock-types-header.patch b/debian/patches-rt/0137-spinlock-Split-the-lock-types-header.patch index cbb4abbb6..81910ed6f 100644 --- a/debian/patches-rt/0137-spinlock-Split-the-lock-types-header.patch +++ b/debian/patches-rt/0137-spinlock-Split-the-lock-types-header.patch @@ -1,11 +1,11 @@ -From 419a199f135bbfdb6babdc8693434e9260c7ef5d Mon Sep 17 00:00:00 2001 -Message-Id: <419a199f135bbfdb6babdc8693434e9260c7ef5d.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5e42d3cb61508547d068d8bac88f4edf22de19f6 Mon Sep 17 00:00:00 2001 +Message-Id: <5e42d3cb61508547d068d8bac88f4edf22de19f6.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 19:34:01 +0200 -Subject: [PATCH 137/327] spinlock: Split the lock types header -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 137/330] spinlock: Split the lock types header +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Split raw_spinlock into its own file and the remaining spinlock_t into its own non-RT header. The non-RT header will be replaced later by sleeping diff --git a/debian/patches-rt/0138-rtmutex-Avoid-include-hell.patch b/debian/patches-rt/0138-rtmutex-Avoid-include-hell.patch index 1ada7eccf..428f569f6 100644 --- a/debian/patches-rt/0138-rtmutex-Avoid-include-hell.patch +++ b/debian/patches-rt/0138-rtmutex-Avoid-include-hell.patch @@ -1,11 +1,11 @@ -From a04a2be015aeb1c6cccfbdca788ddc4658d9af50 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From a55de65b25a8e9ebae2b0aeb91a2ed3772a5320d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 20:06:39 +0200 -Subject: [PATCH 138/327] rtmutex: Avoid include hell -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 138/330] rtmutex: Avoid include hell +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Include only the required raw types. This avoids pulling in the complete spinlock header which in turn requires rtmutex.h at some point. diff --git a/debian/patches-rt/0139-rbtree-don-t-include-the-rcu-header.patch b/debian/patches-rt/0139-rbtree-don-t-include-the-rcu-header.patch index 7879977f4..d58a0d834 100644 --- a/debian/patches-rt/0139-rbtree-don-t-include-the-rcu-header.patch +++ b/debian/patches-rt/0139-rbtree-don-t-include-the-rcu-header.patch @@ -1,14 +1,14 @@ -From e24a2c30abba20d2f2378c2a0725f77fbc4c6191 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From cdcb915e9a0890f1dd0cd2968b110e0db62bbdb3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 16:56:02 +0100 -Subject: [PATCH 139/327] rbtree: don't include the rcu header +Subject: [PATCH 139/330] rbtree: don't include the rcu header MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The RCU header pulls in spinlock.h and fails due not yet defined types: diff --git a/debian/patches-rt/0140-rtmutex-Provide-rt_mutex_slowlock_locked.patch b/debian/patches-rt/0140-rtmutex-Provide-rt_mutex_slowlock_locked.patch index 75ce7edae..7372753cf 100644 --- a/debian/patches-rt/0140-rtmutex-Provide-rt_mutex_slowlock_locked.patch +++ b/debian/patches-rt/0140-rtmutex-Provide-rt_mutex_slowlock_locked.patch @@ -1,11 +1,11 @@ -From 944062c039ea5cc645bb32d2d1ca8c583087e0b0 Mon Sep 17 00:00:00 2001 -Message-Id: <944062c039ea5cc645bb32d2d1ca8c583087e0b0.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From f50980e9779c472c8dcbb529d66ab12804fe53e7 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 16:14:22 +0200 -Subject: [PATCH 140/327] rtmutex: Provide rt_mutex_slowlock_locked() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 140/330] rtmutex: Provide rt_mutex_slowlock_locked() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz This is the inner-part of rt_mutex_slowlock(), required for rwsem-rt. diff --git a/debian/patches-rt/0141-rtmutex-export-lockdep-less-version-of-rt_mutex-s-lo.patch b/debian/patches-rt/0141-rtmutex-export-lockdep-less-version-of-rt_mutex-s-lo.patch index f8b4d0db3..b865cc367 100644 --- a/debian/patches-rt/0141-rtmutex-export-lockdep-less-version-of-rt_mutex-s-lo.patch +++ b/debian/patches-rt/0141-rtmutex-export-lockdep-less-version-of-rt_mutex-s-lo.patch @@ -1,12 +1,12 @@ -From a6f62ff143ee1407a1fd4f17d7d95dd73bc45ee2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d98c7d8371e95d28a96e6b0364cf896cd2de136f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 16:36:39 +0200 -Subject: [PATCH 141/327] rtmutex: export lockdep-less version of rt_mutex's +Subject: [PATCH 141/330] rtmutex: export lockdep-less version of rt_mutex's lock, trylock and unlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Required for lock implementation ontop of rtmutex. diff --git a/debian/patches-rt/0142-rtmutex-add-sleeping-lock-implementation.patch b/debian/patches-rt/0142-rtmutex-add-sleeping-lock-implementation.patch index dbf0fdfa6..dd25625fb 100644 --- a/debian/patches-rt/0142-rtmutex-add-sleeping-lock-implementation.patch +++ b/debian/patches-rt/0142-rtmutex-add-sleeping-lock-implementation.patch @@ -1,11 +1,11 @@ -From 30ba1f06e982c90f79a5349c832a69449244f5a2 Mon Sep 17 00:00:00 2001 -Message-Id: <30ba1f06e982c90f79a5349c832a69449244f5a2.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5a8fdc747b99a39b46eed22131df058553387e29 Mon Sep 17 00:00:00 2001 +Message-Id: <5a8fdc747b99a39b46eed22131df058553387e29.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:11:19 +0200 -Subject: [PATCH 142/327] rtmutex: add sleeping lock implementation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 142/330] rtmutex: add sleeping lock implementation +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Signed-off-by: Thomas Gleixner Signed-off-by: Sebastian Andrzej Siewior diff --git a/debian/patches-rt/0143-rtmutex-add-mutex-implementation-based-on-rtmutex.patch b/debian/patches-rt/0143-rtmutex-add-mutex-implementation-based-on-rtmutex.patch index 3b0595f5c..779dddeb7 100644 --- a/debian/patches-rt/0143-rtmutex-add-mutex-implementation-based-on-rtmutex.patch +++ b/debian/patches-rt/0143-rtmutex-add-mutex-implementation-based-on-rtmutex.patch @@ -1,11 +1,11 @@ -From 5a720d4f3dcb7f6d30270451d89fe7ae1059cc43 Mon Sep 17 00:00:00 2001 -Message-Id: <5a720d4f3dcb7f6d30270451d89fe7ae1059cc43.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d8cee7c6cad728b4488fc439220a0675a61827d9 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:17:03 +0200 -Subject: [PATCH 143/327] rtmutex: add mutex implementation based on rtmutex -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 143/330] rtmutex: add mutex implementation based on rtmutex +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Signed-off-by: Thomas Gleixner Signed-off-by: Sebastian Andrzej Siewior diff --git a/debian/patches-rt/0144-rtmutex-add-rwsem-implementation-based-on-rtmutex.patch b/debian/patches-rt/0144-rtmutex-add-rwsem-implementation-based-on-rtmutex.patch index 4fbf99098..0629553f1 100644 --- a/debian/patches-rt/0144-rtmutex-add-rwsem-implementation-based-on-rtmutex.patch +++ b/debian/patches-rt/0144-rtmutex-add-rwsem-implementation-based-on-rtmutex.patch @@ -1,11 +1,11 @@ -From 849650b8a4b915fa073d9dd0b07c6b2f706cb11d Mon Sep 17 00:00:00 2001 -Message-Id: <849650b8a4b915fa073d9dd0b07c6b2f706cb11d.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 477c61540feebd0f5b6e684894284cc78fed4ae9 Mon Sep 17 00:00:00 2001 +Message-Id: <477c61540feebd0f5b6e684894284cc78fed4ae9.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:28:34 +0200 -Subject: [PATCH 144/327] rtmutex: add rwsem implementation based on rtmutex -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 144/330] rtmutex: add rwsem implementation based on rtmutex +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The RT specific R/W semaphore implementation restricts the number of readers to one because a writer cannot block on multiple readers and inherit its diff --git a/debian/patches-rt/0145-rtmutex-add-rwlock-implementation-based-on-rtmutex.patch b/debian/patches-rt/0145-rtmutex-add-rwlock-implementation-based-on-rtmutex.patch index be5c7728b..738f34f5b 100644 --- a/debian/patches-rt/0145-rtmutex-add-rwlock-implementation-based-on-rtmutex.patch +++ b/debian/patches-rt/0145-rtmutex-add-rwlock-implementation-based-on-rtmutex.patch @@ -1,11 +1,11 @@ -From f64d066192e1ef0987e3ef08ea17f9ebdd93dad4 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 4bd45517f2813803b7157c7b176e41c704a7737e Mon Sep 17 00:00:00 2001 +Message-Id: <4bd45517f2813803b7157c7b176e41c704a7737e.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:18:06 +0200 -Subject: [PATCH 145/327] rtmutex: add rwlock implementation based on rtmutex -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 145/330] rtmutex: add rwlock implementation based on rtmutex +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The implementation is bias-based, similar to the rwsem implementation. diff --git a/debian/patches-rt/0146-rtmutex-rwlock-preserve-state-like-a-sleeping-lock.patch b/debian/patches-rt/0146-rtmutex-rwlock-preserve-state-like-a-sleeping-lock.patch index 23dbd30db..c5cd4973f 100644 --- a/debian/patches-rt/0146-rtmutex-rwlock-preserve-state-like-a-sleeping-lock.patch +++ b/debian/patches-rt/0146-rtmutex-rwlock-preserve-state-like-a-sleeping-lock.patch @@ -1,11 +1,11 @@ -From a1ca0463b6e4e2509ad7a28253890bec10fb5d60 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 37cef0066d9b77015698f8d65d9f3bbb439df92b Mon Sep 17 00:00:00 2001 +Message-Id: <37cef0066d9b77015698f8d65d9f3bbb439df92b.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 11 Jan 2019 21:16:31 +0100 -Subject: [PATCH 146/327] rtmutex/rwlock: preserve state like a sleeping lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 146/330] rtmutex/rwlock: preserve state like a sleeping lock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The rwlock is spinning while acquiring a lock. Therefore it must become a sleeping lock on RT and preserve its task state while sleeping and diff --git a/debian/patches-rt/0147-rtmutex-wire-up-RT-s-locking.patch b/debian/patches-rt/0147-rtmutex-wire-up-RT-s-locking.patch index 8781c6bc4..fe8a4a6f5 100644 --- a/debian/patches-rt/0147-rtmutex-wire-up-RT-s-locking.patch +++ b/debian/patches-rt/0147-rtmutex-wire-up-RT-s-locking.patch @@ -1,11 +1,11 @@ -From db560389f8b5219fc48a39c032464e95fa78c6b8 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 9511faf87bcb720a27f899f84222c838ac60ca8b Mon Sep 17 00:00:00 2001 +Message-Id: <9511faf87bcb720a27f899f84222c838ac60ca8b.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:31:14 +0200 -Subject: [PATCH 147/327] rtmutex: wire up RT's locking -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 147/330] rtmutex: wire up RT's locking +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Signed-off-by: Thomas Gleixner Signed-off-by: Sebastian Andrzej Siewior diff --git a/debian/patches-rt/0148-rtmutex-add-ww_mutex-addon-for-mutex-rt.patch b/debian/patches-rt/0148-rtmutex-add-ww_mutex-addon-for-mutex-rt.patch index 34393430b..be26b7cab 100644 --- a/debian/patches-rt/0148-rtmutex-add-ww_mutex-addon-for-mutex-rt.patch +++ b/debian/patches-rt/0148-rtmutex-add-ww_mutex-addon-for-mutex-rt.patch @@ -1,11 +1,11 @@ -From 50aee1b3bd469da0b78c22690ac59e1f26b86397 Mon Sep 17 00:00:00 2001 -Message-Id: <50aee1b3bd469da0b78c22690ac59e1f26b86397.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From ff0d5f239851ec525a993bf986caff0bdd883abd Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Oct 2017 17:34:38 +0200 -Subject: [PATCH 148/327] rtmutex: add ww_mutex addon for mutex-rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 148/330] rtmutex: add ww_mutex addon for mutex-rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Signed-off-by: Sebastian Andrzej Siewior --- diff --git a/debian/patches-rt/0149-kconfig-Add-PREEMPT_RT_FULL.patch b/debian/patches-rt/0149-kconfig-Add-PREEMPT_RT_FULL.patch index 626c74952..a3c7a2dc6 100644 --- a/debian/patches-rt/0149-kconfig-Add-PREEMPT_RT_FULL.patch +++ b/debian/patches-rt/0149-kconfig-Add-PREEMPT_RT_FULL.patch @@ -1,11 +1,11 @@ -From f0509efdd60e5c53cfb7c970a5fa509112c3d762 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From bd31bf253b93264d604435659bc5bee397ca60b3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 14:58:57 +0200 -Subject: [PATCH 149/327] kconfig: Add PREEMPT_RT_FULL -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 149/330] kconfig: Add PREEMPT_RT_FULL +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Introduce the final symbol for PREEMPT_RT_FULL. diff --git a/debian/patches-rt/0150-locking-rt-mutex-fix-deadlock-in-device-mapper-block.patch b/debian/patches-rt/0150-locking-rt-mutex-fix-deadlock-in-device-mapper-block.patch index 4c82f025b..022f5025f 100644 --- a/debian/patches-rt/0150-locking-rt-mutex-fix-deadlock-in-device-mapper-block.patch +++ b/debian/patches-rt/0150-locking-rt-mutex-fix-deadlock-in-device-mapper-block.patch @@ -1,12 +1,12 @@ -From 13eb3dcbef89e1f9036fd91e6b209917e26705b3 Mon Sep 17 00:00:00 2001 -Message-Id: <13eb3dcbef89e1f9036fd91e6b209917e26705b3.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 1dfad85220f7105489f2fee644d378628253b21b Mon Sep 17 00:00:00 2001 +Message-Id: <1dfad85220f7105489f2fee644d378628253b21b.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Mikulas Patocka Date: Mon, 13 Nov 2017 12:56:53 -0500 -Subject: [PATCH 150/327] locking/rt-mutex: fix deadlock in device mapper / +Subject: [PATCH 150/330] locking/rt-mutex: fix deadlock in device mapper / block-IO -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz When some block device driver creates a bio and submits it to another block device driver, the bio is added to current->bio_list (in order to diff --git a/debian/patches-rt/0151-locking-rt-mutex-Flush-block-plug-on-__down_read.patch b/debian/patches-rt/0151-locking-rt-mutex-Flush-block-plug-on-__down_read.patch index 1246a577d..9d1092fe9 100644 --- a/debian/patches-rt/0151-locking-rt-mutex-Flush-block-plug-on-__down_read.patch +++ b/debian/patches-rt/0151-locking-rt-mutex-Flush-block-plug-on-__down_read.patch @@ -1,11 +1,11 @@ -From f5697edd26b30c893122173a5c6889c5ab6e7cfb Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 504cbd97dfeff708043d3b59a0d3fae27cf74a87 Mon Sep 17 00:00:00 2001 +Message-Id: <504cbd97dfeff708043d3b59a0d3fae27cf74a87.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 4 Jan 2019 15:33:21 -0500 -Subject: [PATCH 151/327] locking/rt-mutex: Flush block plug on __down_read() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 151/330] locking/rt-mutex: Flush block plug on __down_read() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz __down_read() bypasses the rtmutex frontend to call rt_mutex_slowlock_locked() directly, and thus it needs to call diff --git a/debian/patches-rt/0152-locking-rtmutex-re-init-the-wait_lock-in-rt_mutex_in.patch b/debian/patches-rt/0152-locking-rtmutex-re-init-the-wait_lock-in-rt_mutex_in.patch index 9c15248ba..cb8e4e12f 100644 --- a/debian/patches-rt/0152-locking-rtmutex-re-init-the-wait_lock-in-rt_mutex_in.patch +++ b/debian/patches-rt/0152-locking-rtmutex-re-init-the-wait_lock-in-rt_mutex_in.patch @@ -1,12 +1,12 @@ -From f74200caed950b05a273bf9907ad662c00f4994b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8aa32b62194368d05be63b62d8cc31110add9adc Mon Sep 17 00:00:00 2001 +Message-Id: <8aa32b62194368d05be63b62d8cc31110add9adc.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 16 Nov 2017 16:48:48 +0100 -Subject: [PATCH 152/327] locking/rtmutex: re-init the wait_lock in +Subject: [PATCH 152/330] locking/rtmutex: re-init the wait_lock in rt_mutex_init_proxy_locked() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz We could provide a key-class for the lockdep (and fixup all callers) or move the init to all callers (like it was) in order to avoid lockdep diff --git a/debian/patches-rt/0153-ptrace-fix-ptrace-vs-tasklist_lock-race.patch b/debian/patches-rt/0153-ptrace-fix-ptrace-vs-tasklist_lock-race.patch index e49b92e58..b820d387b 100644 --- a/debian/patches-rt/0153-ptrace-fix-ptrace-vs-tasklist_lock-race.patch +++ b/debian/patches-rt/0153-ptrace-fix-ptrace-vs-tasklist_lock-race.patch @@ -1,11 +1,11 @@ -From 73dad537dfbcc32bb1ce45a03805452271eb6cab Mon Sep 17 00:00:00 2001 -Message-Id: <73dad537dfbcc32bb1ce45a03805452271eb6cab.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From a9b9bdffd6b42a14a9aca584e160bd0483d062d3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Aug 2013 18:21:04 +0200 -Subject: [PATCH 153/327] ptrace: fix ptrace vs tasklist_lock race -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 153/330] ptrace: fix ptrace vs tasklist_lock race +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz As explained by Alexander Fyodorov : diff --git a/debian/patches-rt/0154-rtmutex-annotate-sleeping-lock-context.patch b/debian/patches-rt/0154-rtmutex-annotate-sleeping-lock-context.patch index e7d999222..0c45a6b07 100644 --- a/debian/patches-rt/0154-rtmutex-annotate-sleeping-lock-context.patch +++ b/debian/patches-rt/0154-rtmutex-annotate-sleeping-lock-context.patch @@ -1,11 +1,11 @@ -From 616bc6b69f7dd02ad695ffd35a54d40606e17ba8 Mon Sep 17 00:00:00 2001 -Message-Id: <616bc6b69f7dd02ad695ffd35a54d40606e17ba8.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 313a073282879d0a45ec0abc6eeed3e244111017 Mon Sep 17 00:00:00 2001 +Message-Id: <313a073282879d0a45ec0abc6eeed3e244111017.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 21 Sep 2017 14:25:13 +0200 -Subject: [PATCH 154/327] rtmutex: annotate sleeping lock context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 154/330] rtmutex: annotate sleeping lock context +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The RCU code complains on schedule() within a rcu_readlock() section. The valid scenario on -RT is if a sleeping is held. In order to suppress diff --git a/debian/patches-rt/0155-sched-migrate_disable-fallback-to-preempt_disable-in.patch b/debian/patches-rt/0155-sched-migrate_disable-fallback-to-preempt_disable-in.patch index 526dddf47..ee7a8fb09 100644 --- a/debian/patches-rt/0155-sched-migrate_disable-fallback-to-preempt_disable-in.patch +++ b/debian/patches-rt/0155-sched-migrate_disable-fallback-to-preempt_disable-in.patch @@ -1,12 +1,12 @@ -From f8392d844a5bcc4502d70830dd030560520d2ad0 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 42dc89219c3c93c20b33563a85b42d8aa0d2c6c1 Mon Sep 17 00:00:00 2001 +Message-Id: <42dc89219c3c93c20b33563a85b42d8aa0d2c6c1.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 5 Jul 2018 14:44:51 +0200 -Subject: [PATCH 155/327] sched/migrate_disable: fallback to preempt_disable() +Subject: [PATCH 155/330] sched/migrate_disable: fallback to preempt_disable() instead barrier() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz On SMP + !RT migrate_disable() is still around. It is not part of spin_lock() anymore so it has almost no users. However the futex code has a workaround for diff --git a/debian/patches-rt/0156-locking-don-t-check-for-__LINUX_SPINLOCK_TYPES_H-on-.patch b/debian/patches-rt/0156-locking-don-t-check-for-__LINUX_SPINLOCK_TYPES_H-on-.patch index 90be6eeee..2ec6289e4 100644 --- a/debian/patches-rt/0156-locking-don-t-check-for-__LINUX_SPINLOCK_TYPES_H-on-.patch +++ b/debian/patches-rt/0156-locking-don-t-check-for-__LINUX_SPINLOCK_TYPES_H-on-.patch @@ -1,12 +1,12 @@ -From 11ff4e6fd9e05d88c850035fd606f3806702fbb6 Mon Sep 17 00:00:00 2001 -Message-Id: <11ff4e6fd9e05d88c850035fd606f3806702fbb6.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 84d22722929b6e0555582499d16bd3e41292cace Mon Sep 17 00:00:00 2001 +Message-Id: <84d22722929b6e0555582499d16bd3e41292cace.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 4 Aug 2017 17:40:42 +0200 -Subject: [PATCH 156/327] locking: don't check for __LINUX_SPINLOCK_TYPES_H on +Subject: [PATCH 156/330] locking: don't check for __LINUX_SPINLOCK_TYPES_H on -RT archs -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Upstream uses arch_spinlock_t within spinlock_t and requests that spinlock_types.h header file is included first. diff --git a/debian/patches-rt/0157-rcu-Frob-softirq-test.patch b/debian/patches-rt/0157-rcu-Frob-softirq-test.patch index 2fe41a12f..002276103 100644 --- a/debian/patches-rt/0157-rcu-Frob-softirq-test.patch +++ b/debian/patches-rt/0157-rcu-Frob-softirq-test.patch @@ -1,11 +1,11 @@ -From 47657c7386659398e7de16d4a3f29fb8a30fbf15 Mon Sep 17 00:00:00 2001 -Message-Id: <47657c7386659398e7de16d4a3f29fb8a30fbf15.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d5cafea4f3639cc21eb17e26655de27b533321c3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Peter Zijlstra Date: Sat, 13 Aug 2011 00:23:17 +0200 -Subject: [PATCH 157/327] rcu: Frob softirq test -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 157/330] rcu: Frob softirq test +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz With RT_FULL we get the below wreckage: diff --git a/debian/patches-rt/0158-rcu-Merge-RCU-bh-into-RCU-preempt.patch b/debian/patches-rt/0158-rcu-Merge-RCU-bh-into-RCU-preempt.patch index 90ccf2660..a14dc17ef 100644 --- a/debian/patches-rt/0158-rcu-Merge-RCU-bh-into-RCU-preempt.patch +++ b/debian/patches-rt/0158-rcu-Merge-RCU-bh-into-RCU-preempt.patch @@ -1,11 +1,11 @@ -From 0163362a420b6d3357ce30f3353f1e960435f4c2 Mon Sep 17 00:00:00 2001 -Message-Id: <0163362a420b6d3357ce30f3353f1e960435f4c2.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 78617fe6518ea6dcb76b03a3aeb2e06876dd8ac2 Mon Sep 17 00:00:00 2001 +Message-Id: <78617fe6518ea6dcb76b03a3aeb2e06876dd8ac2.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 5 Oct 2011 11:59:38 -0700 -Subject: [PATCH 158/327] rcu: Merge RCU-bh into RCU-preempt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 158/330] rcu: Merge RCU-bh into RCU-preempt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The Linux kernel has long RCU-bh read-side critical sections that intolerably increase scheduling latency under mainline's RCU-bh rules, diff --git a/debian/patches-rt/0159-rcu-Make-ksoftirqd-do-RCU-quiescent-states.patch b/debian/patches-rt/0159-rcu-Make-ksoftirqd-do-RCU-quiescent-states.patch index d2b1a7244..85ec98403 100644 --- a/debian/patches-rt/0159-rcu-Make-ksoftirqd-do-RCU-quiescent-states.patch +++ b/debian/patches-rt/0159-rcu-Make-ksoftirqd-do-RCU-quiescent-states.patch @@ -1,11 +1,11 @@ -From 2b9d2183329e9fc45f42c6a564db40492a818e9b Mon Sep 17 00:00:00 2001 -Message-Id: <2b9d2183329e9fc45f42c6a564db40492a818e9b.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From e9f7a22e68b4e4e6607a870e0b870d44de90db27 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Wed, 5 Oct 2011 11:45:18 -0700 -Subject: [PATCH 159/327] rcu: Make ksoftirqd do RCU quiescent states -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 159/330] rcu: Make ksoftirqd do RCU quiescent states +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Implementing RCU-bh in terms of RCU-preempt makes the system vulnerable to network-based denial-of-service attacks. This patch therefore diff --git a/debian/patches-rt/0160-rcu-Eliminate-softirq-processing-from-rcutree.patch b/debian/patches-rt/0160-rcu-Eliminate-softirq-processing-from-rcutree.patch index 6b1034b5f..867be2231 100644 --- a/debian/patches-rt/0160-rcu-Eliminate-softirq-processing-from-rcutree.patch +++ b/debian/patches-rt/0160-rcu-Eliminate-softirq-processing-from-rcutree.patch @@ -1,11 +1,11 @@ -From 9a3bc46cf334639b4284bacd0693d27025197600 Mon Sep 17 00:00:00 2001 -Message-Id: <9a3bc46cf334639b4284bacd0693d27025197600.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 08921753ffe2db93001cc400672c474c46622517 Mon Sep 17 00:00:00 2001 +Message-Id: <08921753ffe2db93001cc400672c474c46622517.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Mon, 4 Nov 2013 13:21:10 -0800 -Subject: [PATCH 160/327] rcu: Eliminate softirq processing from rcutree -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 160/330] rcu: Eliminate softirq processing from rcutree +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Running RCU out of softirq is a problem for some workloads that would like to manage RCU core processing independently of other softirq work, diff --git a/debian/patches-rt/0161-srcu-use-cpu_online-instead-custom-check.patch b/debian/patches-rt/0161-srcu-use-cpu_online-instead-custom-check.patch index bde11a9ed..221872f6e 100644 --- a/debian/patches-rt/0161-srcu-use-cpu_online-instead-custom-check.patch +++ b/debian/patches-rt/0161-srcu-use-cpu_online-instead-custom-check.patch @@ -1,11 +1,11 @@ -From eeb2f828977a3488ba77d3f2d97e5edfd4b3dd86 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 9f8e8547a854126a0f5839db93215dbc259d8ec2 Mon Sep 17 00:00:00 2001 +Message-Id: <9f8e8547a854126a0f5839db93215dbc259d8ec2.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Sep 2017 14:43:41 +0200 -Subject: [PATCH 161/327] srcu: use cpu_online() instead custom check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 161/330] srcu: use cpu_online() instead custom check +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The current check via srcu_online is slightly racy because after looking at srcu_online there could be an interrupt that interrupted us long diff --git a/debian/patches-rt/0162-srcu-replace-local_irqsave-with-a-locallock.patch b/debian/patches-rt/0162-srcu-replace-local_irqsave-with-a-locallock.patch index 0a8ba95f0..497b19ba2 100644 --- a/debian/patches-rt/0162-srcu-replace-local_irqsave-with-a-locallock.patch +++ b/debian/patches-rt/0162-srcu-replace-local_irqsave-with-a-locallock.patch @@ -1,11 +1,11 @@ -From a737bca6dd31f7c4e7136974e37eb442d7c418ab Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 9f82d2ac59a1a0c72b05c389d926e0952efdae29 Mon Sep 17 00:00:00 2001 +Message-Id: <9f82d2ac59a1a0c72b05c389d926e0952efdae29.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Oct 2017 18:37:12 +0200 -Subject: [PATCH 162/327] srcu: replace local_irqsave() with a locallock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 162/330] srcu: replace local_irqsave() with a locallock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz There are two instances which disable interrupts in order to become a stable this_cpu_ptr() pointer. The restore part is coupled with diff --git a/debian/patches-rt/0163-rcu-enable-rcu_normal_after_boot-by-default-for-RT.patch b/debian/patches-rt/0163-rcu-enable-rcu_normal_after_boot-by-default-for-RT.patch index ae6967b7a..265196519 100644 --- a/debian/patches-rt/0163-rcu-enable-rcu_normal_after_boot-by-default-for-RT.patch +++ b/debian/patches-rt/0163-rcu-enable-rcu_normal_after_boot-by-default-for-RT.patch @@ -1,11 +1,11 @@ -From 21b4adc5537213a5e9328ea5899f66330d1a623d Mon Sep 17 00:00:00 2001 -Message-Id: <21b4adc5537213a5e9328ea5899f66330d1a623d.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From e6e0994ce5c645183058e28ff889447c644f8d97 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Julia Cartwright Date: Wed, 12 Oct 2016 11:21:14 -0500 -Subject: [PATCH 163/327] rcu: enable rcu_normal_after_boot by default for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 163/330] rcu: enable rcu_normal_after_boot by default for RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The forcing of an expedited grace period is an expensive and very RT-application unfriendly operation, as it forcibly preempts all running diff --git a/debian/patches-rt/0164-tty-serial-omap-Make-the-locking-RT-aware.patch b/debian/patches-rt/0164-tty-serial-omap-Make-the-locking-RT-aware.patch index 44b9f88e4..b2ecd4c9e 100644 --- a/debian/patches-rt/0164-tty-serial-omap-Make-the-locking-RT-aware.patch +++ b/debian/patches-rt/0164-tty-serial-omap-Make-the-locking-RT-aware.patch @@ -1,11 +1,11 @@ -From 509c5133980292a424e3a9c8a62dbc759759d81a Mon Sep 17 00:00:00 2001 -Message-Id: <509c5133980292a424e3a9c8a62dbc759759d81a.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 4351744a1323868f6ff9585067eb87d3542c7ff2 Mon Sep 17 00:00:00 2001 +Message-Id: <4351744a1323868f6ff9585067eb87d3542c7ff2.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 28 Jul 2011 13:32:57 +0200 -Subject: [PATCH 164/327] tty/serial/omap: Make the locking RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 164/330] tty/serial/omap: Make the locking RT aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The lock is a sleeping lock and local_irq_save() is not the optimsation we are looking for. Redo it to make it work on -RT and diff --git a/debian/patches-rt/0165-tty-serial-pl011-Make-the-locking-work-on-RT.patch b/debian/patches-rt/0165-tty-serial-pl011-Make-the-locking-work-on-RT.patch index ec2832cb9..0173ab06e 100644 --- a/debian/patches-rt/0165-tty-serial-pl011-Make-the-locking-work-on-RT.patch +++ b/debian/patches-rt/0165-tty-serial-pl011-Make-the-locking-work-on-RT.patch @@ -1,11 +1,11 @@ -From 9ffa3bd42a4623ce800e0fa2a2645cb536b3208f Mon Sep 17 00:00:00 2001 -Message-Id: <9ffa3bd42a4623ce800e0fa2a2645cb536b3208f.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 9d8a7252bbd0fb318b264ad048365d289cc1cd84 Mon Sep 17 00:00:00 2001 +Message-Id: <9d8a7252bbd0fb318b264ad048365d289cc1cd84.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 8 Jan 2013 21:36:51 +0100 -Subject: [PATCH 165/327] tty/serial/pl011: Make the locking work on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 165/330] tty/serial/pl011: Make the locking work on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The lock is a sleeping lock and local_irq_save() is not the optimsation we are looking for. Redo it to make it work on -RT and non-RT. diff --git a/debian/patches-rt/0166-tty-serial-pl011-explicitly-initialize-the-flags-var.patch b/debian/patches-rt/0166-tty-serial-pl011-explicitly-initialize-the-flags-var.patch index f029fa808..7a057f778 100644 --- a/debian/patches-rt/0166-tty-serial-pl011-explicitly-initialize-the-flags-var.patch +++ b/debian/patches-rt/0166-tty-serial-pl011-explicitly-initialize-the-flags-var.patch @@ -1,15 +1,15 @@ -From 8a3cabfb2cc1799ee3092a447296e8b2263ff1f7 Mon Sep 17 00:00:00 2001 -Message-Id: <8a3cabfb2cc1799ee3092a447296e8b2263ff1f7.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From a9f3facc5fb8f9a6d275f3fce058cc40eea8fd0b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Kurt Kanzenbach Date: Mon, 24 Sep 2018 10:29:01 +0200 -Subject: [PATCH 166/327] tty: serial: pl011: explicitly initialize the flags +Subject: [PATCH 166/330] tty: serial: pl011: explicitly initialize the flags variable MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Silence the following gcc warning: diff --git a/debian/patches-rt/0167-rt-Improve-the-serial-console-PASS_LIMIT.patch b/debian/patches-rt/0167-rt-Improve-the-serial-console-PASS_LIMIT.patch index 78c5b4906..7b52c9b50 100644 --- a/debian/patches-rt/0167-rt-Improve-the-serial-console-PASS_LIMIT.patch +++ b/debian/patches-rt/0167-rt-Improve-the-serial-console-PASS_LIMIT.patch @@ -1,14 +1,14 @@ -From 71427154ff53a3decb71f389624d249cb3767fcd Mon Sep 17 00:00:00 2001 -Message-Id: <71427154ff53a3decb71f389624d249cb3767fcd.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 00680e4f6f2865781feb57c3f2a342e66c8ec466 Mon Sep 17 00:00:00 2001 +Message-Id: <00680e4f6f2865781feb57c3f2a342e66c8ec466.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Ingo Molnar Date: Wed, 14 Dec 2011 13:05:54 +0100 -Subject: [PATCH 167/327] rt: Improve the serial console PASS_LIMIT +Subject: [PATCH 167/330] rt: Improve the serial console PASS_LIMIT MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Beyond the warning: diff --git a/debian/patches-rt/0168-tty-serial-8250-don-t-take-the-trylock-during-oops.patch b/debian/patches-rt/0168-tty-serial-8250-don-t-take-the-trylock-during-oops.patch index 0578dffc7..f302ca847 100644 --- a/debian/patches-rt/0168-tty-serial-8250-don-t-take-the-trylock-during-oops.patch +++ b/debian/patches-rt/0168-tty-serial-8250-don-t-take-the-trylock-during-oops.patch @@ -1,11 +1,11 @@ -From 57362ee4061a1cdbde13a6c901d6e013b6819c2e Mon Sep 17 00:00:00 2001 -Message-Id: <57362ee4061a1cdbde13a6c901d6e013b6819c2e.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From caf97a9a126b4a188408f2d8d87185c333ad119d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Apr 2016 16:55:02 +0200 -Subject: [PATCH 168/327] tty: serial: 8250: don't take the trylock during oops -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 168/330] tty: serial: 8250: don't take the trylock during oops +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz An oops with irqs off (panic() from irqsafe hrtimer like the watchdog timer) will lead to a lockdep warning on each invocation and as such diff --git a/debian/patches-rt/0169-locking-percpu-rwsem-Remove-preempt_disable-variants.patch b/debian/patches-rt/0169-locking-percpu-rwsem-Remove-preempt_disable-variants.patch index 4633f2823..f297f9fdf 100644 --- a/debian/patches-rt/0169-locking-percpu-rwsem-Remove-preempt_disable-variants.patch +++ b/debian/patches-rt/0169-locking-percpu-rwsem-Remove-preempt_disable-variants.patch @@ -1,11 +1,11 @@ -From 8a5e899963704e7b96dd12b0b3fab4b5f3a603eb Mon Sep 17 00:00:00 2001 -Message-Id: <8a5e899963704e7b96dd12b0b3fab4b5f3a603eb.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 4c42325112ee3925ee92b4cc4b44b23ea073c057 Mon Sep 17 00:00:00 2001 +Message-Id: <4c42325112ee3925ee92b4cc4b44b23ea073c057.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Peter Zijlstra Date: Wed, 23 Nov 2016 16:29:32 +0100 -Subject: [PATCH 169/327] locking/percpu-rwsem: Remove preempt_disable variants -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 169/330] locking/percpu-rwsem: Remove preempt_disable variants +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Effective revert commit: diff --git a/debian/patches-rt/0170-mm-Protect-activate_mm-by-preempt_-disable-enable-_r.patch b/debian/patches-rt/0170-mm-Protect-activate_mm-by-preempt_-disable-enable-_r.patch index 073817075..ae6790a95 100644 --- a/debian/patches-rt/0170-mm-Protect-activate_mm-by-preempt_-disable-enable-_r.patch +++ b/debian/patches-rt/0170-mm-Protect-activate_mm-by-preempt_-disable-enable-_r.patch @@ -1,12 +1,12 @@ -From 63f9ffa4bf5f26fbe8cc5ae95f2e63ec02732082 Mon Sep 17 00:00:00 2001 -Message-Id: <63f9ffa4bf5f26fbe8cc5ae95f2e63ec02732082.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 3ae273bfdd1cde7f18154bcdd0cfe2026abca6cb Mon Sep 17 00:00:00 2001 +Message-Id: <3ae273bfdd1cde7f18154bcdd0cfe2026abca6cb.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Yong Zhang Date: Tue, 15 May 2012 13:53:56 +0800 -Subject: [PATCH 170/327] mm: Protect activate_mm() by +Subject: [PATCH 170/330] mm: Protect activate_mm() by preempt_[disable&enable]_rt() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz User preempt_*_rt instead of local_irq_*_rt or otherwise there will be warning on ARM like below: diff --git a/debian/patches-rt/0171-fs-dcache-bring-back-explicit-INIT_HLIST_BL_HEAD-ini.patch b/debian/patches-rt/0171-fs-dcache-bring-back-explicit-INIT_HLIST_BL_HEAD-ini.patch index 9a087c267..cdd3b9554 100644 --- a/debian/patches-rt/0171-fs-dcache-bring-back-explicit-INIT_HLIST_BL_HEAD-ini.patch +++ b/debian/patches-rt/0171-fs-dcache-bring-back-explicit-INIT_HLIST_BL_HEAD-ini.patch @@ -1,12 +1,12 @@ -From 096ea7062ca9f93a0b5f8fce308cfc6085b2e6b5 Mon Sep 17 00:00:00 2001 -Message-Id: <096ea7062ca9f93a0b5f8fce308cfc6085b2e6b5.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 33390317926d4a254812f09ee8944cf82d27b8f6 Mon Sep 17 00:00:00 2001 +Message-Id: <33390317926d4a254812f09ee8944cf82d27b8f6.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Sep 2017 12:32:34 +0200 -Subject: [PATCH 171/327] fs/dcache: bring back explicit INIT_HLIST_BL_HEAD +Subject: [PATCH 171/330] fs/dcache: bring back explicit INIT_HLIST_BL_HEAD init -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Commit 3d375d78593c ("mm: update callers to use HASH_ZERO flag") removed INIT_HLIST_BL_HEAD and uses the ZERO flag instead for the init. However diff --git a/debian/patches-rt/0172-fs-dcache-disable-preemption-on-i_dir_seq-s-write-si.patch b/debian/patches-rt/0172-fs-dcache-disable-preemption-on-i_dir_seq-s-write-si.patch index e402b9de3..83f72890e 100644 --- a/debian/patches-rt/0172-fs-dcache-disable-preemption-on-i_dir_seq-s-write-si.patch +++ b/debian/patches-rt/0172-fs-dcache-disable-preemption-on-i_dir_seq-s-write-si.patch @@ -1,12 +1,12 @@ -From 95fd8bf43c3097d8cf39e93139f324b278e2f940 Mon Sep 17 00:00:00 2001 -Message-Id: <95fd8bf43c3097d8cf39e93139f324b278e2f940.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From b08fcb88bc88e1ced888e28467b6fd3ec907554f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 20 Oct 2017 11:29:53 +0200 -Subject: [PATCH 172/327] fs/dcache: disable preemption on i_dir_seq's write +Subject: [PATCH 172/330] fs/dcache: disable preemption on i_dir_seq's write side -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz i_dir_seq is an opencoded seqcounter. Based on the code it looks like we could have two writers in parallel despite the fact that the d_lock is diff --git a/debian/patches-rt/0173-squashfs-make-use-of-local-lock-in-multi_cpu-decompr.patch b/debian/patches-rt/0173-squashfs-make-use-of-local-lock-in-multi_cpu-decompr.patch index 580c6d9f3..b07bdf136 100644 --- a/debian/patches-rt/0173-squashfs-make-use-of-local-lock-in-multi_cpu-decompr.patch +++ b/debian/patches-rt/0173-squashfs-make-use-of-local-lock-in-multi_cpu-decompr.patch @@ -1,12 +1,12 @@ -From d80c0bb950c290d5c8d1830ff95bc8e7ced931fe Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8f4f69c13e49174eae6e6dcc9a65b2549e33af1f Mon Sep 17 00:00:00 2001 +Message-Id: <8f4f69c13e49174eae6e6dcc9a65b2549e33af1f.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Julia Cartwright Date: Mon, 7 May 2018 08:58:57 -0500 -Subject: [PATCH 173/327] squashfs: make use of local lock in multi_cpu +Subject: [PATCH 173/330] squashfs: make use of local lock in multi_cpu decompressor -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Currently, the squashfs multi_cpu decompressor makes use of get_cpu_ptr()/put_cpu_ptr(), which unconditionally disable preemption diff --git a/debian/patches-rt/0174-thermal-Defer-thermal-wakups-to-threads.patch b/debian/patches-rt/0174-thermal-Defer-thermal-wakups-to-threads.patch index a0db9b405..331cf210b 100644 --- a/debian/patches-rt/0174-thermal-Defer-thermal-wakups-to-threads.patch +++ b/debian/patches-rt/0174-thermal-Defer-thermal-wakups-to-threads.patch @@ -1,11 +1,11 @@ -From a638f716f6ff3ceee47f7d82cea3d0530a91530b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From e19c759fc264301377f279733778b24d8f1be72a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Daniel Wagner Date: Tue, 17 Feb 2015 09:37:44 +0100 -Subject: [PATCH 174/327] thermal: Defer thermal wakups to threads -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 174/330] thermal: Defer thermal wakups to threads +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz On RT the spin lock in pkg_temp_thermal_platfrom_thermal_notify will call schedule while we run in irq context. diff --git a/debian/patches-rt/0175-x86-fpu-Disable-preemption-around-local_bh_disable.patch b/debian/patches-rt/0175-x86-fpu-Disable-preemption-around-local_bh_disable.patch index 2a1795121..13127bc96 100644 --- a/debian/patches-rt/0175-x86-fpu-Disable-preemption-around-local_bh_disable.patch +++ b/debian/patches-rt/0175-x86-fpu-Disable-preemption-around-local_bh_disable.patch @@ -1,11 +1,11 @@ -From e4715d0c2eedd8dc96f3294fc2adc6ffa53cf00b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From da1aa8fcd15559b15b97a52cd9c40578c25e19f3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 11 Dec 2018 15:10:33 +0100 -Subject: [PATCH 175/327] x86/fpu: Disable preemption around local_bh_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 175/330] x86/fpu: Disable preemption around local_bh_disable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz __fpu__restore_sig() restores the content of the FPU state in the CPUs and in order to avoid concurency it disbles BH. On !RT it also disables diff --git a/debian/patches-rt/0176-fs-epoll-Do-not-disable-preemption-on-RT.patch b/debian/patches-rt/0176-fs-epoll-Do-not-disable-preemption-on-RT.patch index 70478ef22..35f7ecab8 100644 --- a/debian/patches-rt/0176-fs-epoll-Do-not-disable-preemption-on-RT.patch +++ b/debian/patches-rt/0176-fs-epoll-Do-not-disable-preemption-on-RT.patch @@ -1,11 +1,11 @@ -From dfcb68abe2ccf680631a2cd2f40c3557bbd9ae0d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 9e2f0e23efa57a9884caec27a91b1707d651026e Mon Sep 17 00:00:00 2001 +Message-Id: <9e2f0e23efa57a9884caec27a91b1707d651026e.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 8 Jul 2011 16:35:35 +0200 -Subject: [PATCH 176/327] fs/epoll: Do not disable preemption on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 176/330] fs/epoll: Do not disable preemption on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz ep_call_nested() takes a sleeping lock so we can't disable preemption. The light version is enough since ep_call_nested() doesn't mind beeing diff --git a/debian/patches-rt/0177-mm-vmalloc-Another-preempt-disable-region-which-suck.patch b/debian/patches-rt/0177-mm-vmalloc-Another-preempt-disable-region-which-suck.patch index ad5746f08..7a6d604b7 100644 --- a/debian/patches-rt/0177-mm-vmalloc-Another-preempt-disable-region-which-suck.patch +++ b/debian/patches-rt/0177-mm-vmalloc-Another-preempt-disable-region-which-suck.patch @@ -1,12 +1,12 @@ -From 6df082a0cf468f8d94cca18b80d3b87430ec6eed Mon Sep 17 00:00:00 2001 -Message-Id: <6df082a0cf468f8d94cca18b80d3b87430ec6eed.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From fa6ff7159c068d7a931643de17835309501964ab Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 12 Jul 2011 11:39:36 +0200 -Subject: [PATCH 177/327] mm/vmalloc: Another preempt disable region which +Subject: [PATCH 177/330] mm/vmalloc: Another preempt disable region which sucks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Avoid the preempt disable version of get_cpu_var(). The inner-lock should provide enough serialisation. @@ -17,7 +17,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c -index 11d0f0b6ec79..c6dc3a96e8f3 100644 +index 1817871b0239..aa06badc76f4 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c @@ -853,7 +853,7 @@ static void *new_vmap_block(unsigned int order, gfp_t gfp_mask) diff --git a/debian/patches-rt/0178-block-mq-use-cpu_light.patch b/debian/patches-rt/0178-block-mq-use-cpu_light.patch index 984af9918..1a1b38c56 100644 --- a/debian/patches-rt/0178-block-mq-use-cpu_light.patch +++ b/debian/patches-rt/0178-block-mq-use-cpu_light.patch @@ -1,11 +1,11 @@ -From 403a6883115b82e579879c85241de57d1573098a Mon Sep 17 00:00:00 2001 -Message-Id: <403a6883115b82e579879c85241de57d1573098a.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From b3355755085aa26c9a58966925e50a1a33f2a1f0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 9 Apr 2014 10:37:23 +0200 -Subject: [PATCH 178/327] block: mq: use cpu_light() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 178/330] block: mq: use cpu_light() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz there is a might sleep splat because get_cpu() disables preemption and later we grab a lock. As a workaround for this we use get_cpu_light(). diff --git a/debian/patches-rt/0179-block-mq-do-not-invoke-preempt_disable.patch b/debian/patches-rt/0179-block-mq-do-not-invoke-preempt_disable.patch index 7795339a6..7b44cac83 100644 --- a/debian/patches-rt/0179-block-mq-do-not-invoke-preempt_disable.patch +++ b/debian/patches-rt/0179-block-mq-do-not-invoke-preempt_disable.patch @@ -1,11 +1,11 @@ -From 41a9ed45ed82787982379b95deed12ccad412547 Mon Sep 17 00:00:00 2001 -Message-Id: <41a9ed45ed82787982379b95deed12ccad412547.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d18ac5415ffb74a1761e7cd365e645687a0f561c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 179/327] block/mq: do not invoke preempt_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 179/330] block/mq: do not invoke preempt_disable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz preempt_disable() and get_cpu() don't play well together with the sleeping locks it tries to allocate later. diff --git a/debian/patches-rt/0180-block-mq-don-t-complete-requests-via-IPI.patch b/debian/patches-rt/0180-block-mq-don-t-complete-requests-via-IPI.patch index 7027b6fcd..c9281ced6 100644 --- a/debian/patches-rt/0180-block-mq-don-t-complete-requests-via-IPI.patch +++ b/debian/patches-rt/0180-block-mq-don-t-complete-requests-via-IPI.patch @@ -1,11 +1,11 @@ -From 3678f23d7ce40a775f2c0fa48a9f7bdaf867b09e Mon Sep 17 00:00:00 2001 -Message-Id: <3678f23d7ce40a775f2c0fa48a9f7bdaf867b09e.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From a423bf6c04e69c3c21e03a47d5d69e0e683d994a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Jan 2015 15:10:08 +0100 -Subject: [PATCH 180/327] block/mq: don't complete requests via IPI -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 180/330] block/mq: don't complete requests via IPI +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The IPI runs in hardirq context and there are sleeping locks. This patch moves the completion into a workqueue. diff --git a/debian/patches-rt/0181-md-raid5-Make-raid5_percpu-handling-RT-aware.patch b/debian/patches-rt/0181-md-raid5-Make-raid5_percpu-handling-RT-aware.patch index 312cb8a9c..9d5617b79 100644 --- a/debian/patches-rt/0181-md-raid5-Make-raid5_percpu-handling-RT-aware.patch +++ b/debian/patches-rt/0181-md-raid5-Make-raid5_percpu-handling-RT-aware.patch @@ -1,11 +1,11 @@ -From 3b2cca77ac7e2c5124a99566435d91c01bb8fa21 Mon Sep 17 00:00:00 2001 -Message-Id: <3b2cca77ac7e2c5124a99566435d91c01bb8fa21.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 837ad355b3236dcfed126c8d22d4dff7fa1530d1 Mon Sep 17 00:00:00 2001 +Message-Id: <837ad355b3236dcfed126c8d22d4dff7fa1530d1.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 6 Apr 2010 16:51:31 +0200 -Subject: [PATCH 181/327] md: raid5: Make raid5_percpu handling RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 181/330] md: raid5: Make raid5_percpu handling RT aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz __raid_run_ops() disables preemption with get_cpu() around the access to the raid5_percpu variables. That causes scheduling while atomic diff --git a/debian/patches-rt/0182-rt-Introduce-cpu_chill.patch b/debian/patches-rt/0182-rt-Introduce-cpu_chill.patch index 72c8f1a9a..fe3b49b21 100644 --- a/debian/patches-rt/0182-rt-Introduce-cpu_chill.patch +++ b/debian/patches-rt/0182-rt-Introduce-cpu_chill.patch @@ -1,11 +1,11 @@ -From 38bf7000532cae8693765ad31d9f035d26c17694 Mon Sep 17 00:00:00 2001 -Message-Id: <38bf7000532cae8693765ad31d9f035d26c17694.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 2918288a67e706d60b08bc409f37fa8f3239ff02 Mon Sep 17 00:00:00 2001 +Message-Id: <2918288a67e706d60b08bc409f37fa8f3239ff02.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 20:51:03 +0100 -Subject: [PATCH 182/327] rt: Introduce cpu_chill() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 182/330] rt: Introduce cpu_chill() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Retry loops on RT might loop forever when the modifying side was preempted. Add cpu_chill() to replace cpu_relax(). cpu_chill() diff --git a/debian/patches-rt/0183-hrtimer-Don-t-lose-state-in-cpu_chill.patch b/debian/patches-rt/0183-hrtimer-Don-t-lose-state-in-cpu_chill.patch index 60e95c848..569658c2c 100644 --- a/debian/patches-rt/0183-hrtimer-Don-t-lose-state-in-cpu_chill.patch +++ b/debian/patches-rt/0183-hrtimer-Don-t-lose-state-in-cpu_chill.patch @@ -1,11 +1,11 @@ -From cdc1fb3e08001f6e2accd4f6e605d26ad7a273e6 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 4c9cd1f060a8e1a2b87d38095ca2702867bbd08e Mon Sep 17 00:00:00 2001 +Message-Id: <4c9cd1f060a8e1a2b87d38095ca2702867bbd08e.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Feb 2019 16:59:15 +0100 -Subject: [PATCH 183/327] hrtimer: Don't lose state in cpu_chill() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 183/330] hrtimer: Don't lose state in cpu_chill() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz In cpu_chill() the state is set to TASK_UNINTERRUPTIBLE and a timer is programmed. On return the state is always TASK_RUNNING which means we diff --git a/debian/patches-rt/0184-hrtimer-cpu_chill-save-task-state-in-saved_state.patch b/debian/patches-rt/0184-hrtimer-cpu_chill-save-task-state-in-saved_state.patch index 1bf890623..53dfa4f64 100644 --- a/debian/patches-rt/0184-hrtimer-cpu_chill-save-task-state-in-saved_state.patch +++ b/debian/patches-rt/0184-hrtimer-cpu_chill-save-task-state-in-saved_state.patch @@ -1,12 +1,12 @@ -From b935d86994037078010817bab9263fa7fc100016 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 569087a0a762d646b454e09e9642345d5624babb Mon Sep 17 00:00:00 2001 +Message-Id: <569087a0a762d646b454e09e9642345d5624babb.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 12:31:10 +0100 -Subject: [PATCH 184/327] hrtimer: cpu_chill(): save task state in +Subject: [PATCH 184/330] hrtimer: cpu_chill(): save task state in ->saved_state() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz In the previous change I saved the current task state on stack. This was bad because while the task is scheduled-out it might receive a wake-up. diff --git a/debian/patches-rt/0185-block-blk-mq-move-blk_queue_usage_counter_release-in.patch b/debian/patches-rt/0185-block-blk-mq-move-blk_queue_usage_counter_release-in.patch index c172da46f..e64f2b3e0 100644 --- a/debian/patches-rt/0185-block-blk-mq-move-blk_queue_usage_counter_release-in.patch +++ b/debian/patches-rt/0185-block-blk-mq-move-blk_queue_usage_counter_release-in.patch @@ -1,12 +1,12 @@ -From e6ac0e3dea0bbc247167195fc3f793eec8f7c115 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 7dcfc21684266ea7a48b604a48ebf368d87e1e45 Mon Sep 17 00:00:00 2001 +Message-Id: <7dcfc21684266ea7a48b604a48ebf368d87e1e45.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Mar 2018 13:49:16 +0100 -Subject: [PATCH 185/327] block: blk-mq: move blk_queue_usage_counter_release() +Subject: [PATCH 185/330] block: blk-mq: move blk_queue_usage_counter_release() into process context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz | BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:914 | in_atomic(): 1, irqs_disabled(): 0, pid: 255, name: kworker/u257:6 diff --git a/debian/patches-rt/0186-block-Use-cpu_chill-for-retry-loops.patch b/debian/patches-rt/0186-block-Use-cpu_chill-for-retry-loops.patch index 55ae68881..2632221cc 100644 --- a/debian/patches-rt/0186-block-Use-cpu_chill-for-retry-loops.patch +++ b/debian/patches-rt/0186-block-Use-cpu_chill-for-retry-loops.patch @@ -1,11 +1,11 @@ -From d8497da53864b6f3323922bec554d5ec420398fc Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From ec866f740d2ecbb5a86266c2aee383f462c9bbb5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 20 Dec 2012 18:28:26 +0100 -Subject: [PATCH 186/327] block: Use cpu_chill() for retry loops -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 186/330] block: Use cpu_chill() for retry loops +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Retry loops on RT might loop forever when the modifying side was preempted. Steven also observed a live lock when there was a diff --git a/debian/patches-rt/0187-fs-dcache-Use-cpu_chill-in-trylock-loops.patch b/debian/patches-rt/0187-fs-dcache-Use-cpu_chill-in-trylock-loops.patch index ea12eb93d..92d3e0477 100644 --- a/debian/patches-rt/0187-fs-dcache-Use-cpu_chill-in-trylock-loops.patch +++ b/debian/patches-rt/0187-fs-dcache-Use-cpu_chill-in-trylock-loops.patch @@ -1,11 +1,11 @@ -From 50bff81512bb1a9dbd1b2f6977004c908576f42f Mon Sep 17 00:00:00 2001 -Message-Id: <50bff81512bb1a9dbd1b2f6977004c908576f42f.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 68cde82b625232531dfec53fbef3f21141549240 Mon Sep 17 00:00:00 2001 +Message-Id: <68cde82b625232531dfec53fbef3f21141549240.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 21:00:34 +0100 -Subject: [PATCH 187/327] fs: dcache: Use cpu_chill() in trylock loops -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 187/330] fs: dcache: Use cpu_chill() in trylock loops +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Retry loops on RT might loop forever when the modifying side was preempted. Use cpu_chill() instead of cpu_relax() to let the system diff --git a/debian/patches-rt/0188-net-Use-cpu_chill-instead-of-cpu_relax.patch b/debian/patches-rt/0188-net-Use-cpu_chill-instead-of-cpu_relax.patch index ba60bd5a2..9a2374b11 100644 --- a/debian/patches-rt/0188-net-Use-cpu_chill-instead-of-cpu_relax.patch +++ b/debian/patches-rt/0188-net-Use-cpu_chill-instead-of-cpu_relax.patch @@ -1,11 +1,11 @@ -From cf98c9b45e5eb2d1dde77f5ce91a0801b63eebb0 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 3e45e38580d79bf1f2456a9ea8b501bb7363a973 Mon Sep 17 00:00:00 2001 +Message-Id: <3e45e38580d79bf1f2456a9ea8b501bb7363a973.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 21:10:04 +0100 -Subject: [PATCH 188/327] net: Use cpu_chill() instead of cpu_relax() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 188/330] net: Use cpu_chill() instead of cpu_relax() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Retry loops on RT might loop forever when the modifying side was preempted. Use cpu_chill() instead of cpu_relax() to let the system diff --git a/debian/patches-rt/0189-fs-dcache-use-swait_queue-instead-of-waitqueue.patch b/debian/patches-rt/0189-fs-dcache-use-swait_queue-instead-of-waitqueue.patch index 279503112..dd7df64ca 100644 --- a/debian/patches-rt/0189-fs-dcache-use-swait_queue-instead-of-waitqueue.patch +++ b/debian/patches-rt/0189-fs-dcache-use-swait_queue-instead-of-waitqueue.patch @@ -1,11 +1,11 @@ -From 958af3604e64410fa305536a81cc951ef1583852 Mon Sep 17 00:00:00 2001 -Message-Id: <958af3604e64410fa305536a81cc951ef1583852.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5fb17df2b4e8fc49e587980d55f4548025999414 Mon Sep 17 00:00:00 2001 +Message-Id: <5fb17df2b4e8fc49e587980d55f4548025999414.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Sep 2016 14:35:49 +0200 -Subject: [PATCH 189/327] fs/dcache: use swait_queue instead of waitqueue -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 189/330] fs/dcache: use swait_queue instead of waitqueue +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz __d_lookup_done() invokes wake_up_all() while holding a hlist_bl_lock() which disables preemption. As a workaround convert it to swait. diff --git a/debian/patches-rt/0190-workqueue-Use-normal-rcu.patch b/debian/patches-rt/0190-workqueue-Use-normal-rcu.patch index ab6d78f96..8a9a33166 100644 --- a/debian/patches-rt/0190-workqueue-Use-normal-rcu.patch +++ b/debian/patches-rt/0190-workqueue-Use-normal-rcu.patch @@ -1,11 +1,11 @@ -From 94364b3bf58965763885d3b5bae9d2b262f9fbca Mon Sep 17 00:00:00 2001 -Message-Id: <94364b3bf58965763885d3b5bae9d2b262f9fbca.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 61eb806af3c3ca2b3418e5f22021537e66a436da Mon Sep 17 00:00:00 2001 +Message-Id: <61eb806af3c3ca2b3418e5f22021537e66a436da.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 24 Jul 2013 15:26:54 +0200 -Subject: [PATCH 190/327] workqueue: Use normal rcu -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 190/330] workqueue: Use normal rcu +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz There is no need for sched_rcu. The undocumented reason why sched_rcu is used is to avoid a few explicit rcu_read_lock()/unlock() pairs by diff --git a/debian/patches-rt/0191-workqueue-Use-local-irq-lock-instead-of-irq-disable-.patch b/debian/patches-rt/0191-workqueue-Use-local-irq-lock-instead-of-irq-disable-.patch index 3b4e92995..8782cd74d 100644 --- a/debian/patches-rt/0191-workqueue-Use-local-irq-lock-instead-of-irq-disable-.patch +++ b/debian/patches-rt/0191-workqueue-Use-local-irq-lock-instead-of-irq-disable-.patch @@ -1,12 +1,12 @@ -From afe816bc795dec2204fdf89e259f755b2ca6529e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 43595c8d9ce5178f8e13a2eee73c6ca2653da92f Mon Sep 17 00:00:00 2001 +Message-Id: <43595c8d9ce5178f8e13a2eee73c6ca2653da92f.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:42:26 +0200 -Subject: [PATCH 191/327] workqueue: Use local irq lock instead of irq disable +Subject: [PATCH 191/330] workqueue: Use local irq lock instead of irq disable regions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Use a local_irq_lock as a replacement for irq off regions. We keep the semantic of irq-off in regard to the pool->lock and remain preemptible. diff --git a/debian/patches-rt/0192-workqueue-Prevent-workqueue-versus-ata-piix-livelock.patch b/debian/patches-rt/0192-workqueue-Prevent-workqueue-versus-ata-piix-livelock.patch index 976f2eb16..08a3cbcb8 100644 --- a/debian/patches-rt/0192-workqueue-Prevent-workqueue-versus-ata-piix-livelock.patch +++ b/debian/patches-rt/0192-workqueue-Prevent-workqueue-versus-ata-piix-livelock.patch @@ -1,11 +1,11 @@ -From d0a0a19f5a36564bc7aa94c9343fde55c1354a9e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From cc3228fe3a528109bacb191683d1294f480de410 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 1 Jul 2013 11:02:42 +0200 -Subject: [PATCH 192/327] workqueue: Prevent workqueue versus ata-piix livelock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 192/330] workqueue: Prevent workqueue versus ata-piix livelock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz An Intel i7 system regularly detected rcu_preempt stalls after the kernel was upgraded from 3.6-rt to 3.8-rt. When the stall happened, disk I/O was no diff --git a/debian/patches-rt/0193-sched-Distangle-worker-accounting-from-rqlock.patch b/debian/patches-rt/0193-sched-Distangle-worker-accounting-from-rqlock.patch index 985f7c4e3..db177f3b8 100644 --- a/debian/patches-rt/0193-sched-Distangle-worker-accounting-from-rqlock.patch +++ b/debian/patches-rt/0193-sched-Distangle-worker-accounting-from-rqlock.patch @@ -1,11 +1,11 @@ -From ea40f7c043c4b012acde3852755c1e7c9245c8d0 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 477f99144bd2e1ef2e5e76ac94312873f80e7e52 Mon Sep 17 00:00:00 2001 +Message-Id: <477f99144bd2e1ef2e5e76ac94312873f80e7e52.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 22 Jun 2011 19:47:03 +0200 -Subject: [PATCH 193/327] sched: Distangle worker accounting from rqlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 193/330] sched: Distangle worker accounting from rqlock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The worker accounting for cpu bound workers is plugged into the core scheduler code and the wakeup code. This is not a hard requirement and diff --git a/debian/patches-rt/0194-debugobjects-Make-RT-aware.patch b/debian/patches-rt/0194-debugobjects-Make-RT-aware.patch index 600b7350d..46d16fd51 100644 --- a/debian/patches-rt/0194-debugobjects-Make-RT-aware.patch +++ b/debian/patches-rt/0194-debugobjects-Make-RT-aware.patch @@ -1,11 +1,11 @@ -From 3df8c68aa495b5da280875670a48ef574f3e714c Mon Sep 17 00:00:00 2001 -Message-Id: <3df8c68aa495b5da280875670a48ef574f3e714c.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From f01cea126f695969c00950fb10a6aa67baa1e83c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:41:35 +0200 -Subject: [PATCH 194/327] debugobjects: Make RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 194/330] debugobjects: Make RT aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Avoid filling the pool / allocating memory with irqs off(). diff --git a/debian/patches-rt/0195-seqlock-Prevent-rt-starvation.patch b/debian/patches-rt/0195-seqlock-Prevent-rt-starvation.patch index e99d8cd1a..d84e9b814 100644 --- a/debian/patches-rt/0195-seqlock-Prevent-rt-starvation.patch +++ b/debian/patches-rt/0195-seqlock-Prevent-rt-starvation.patch @@ -1,11 +1,11 @@ -From 293698596bd97ea09e1bd044be9123b123ca4cb0 Mon Sep 17 00:00:00 2001 -Message-Id: <293698596bd97ea09e1bd044be9123b123ca4cb0.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 88a88ad1f0e0805b6da5dcca83b828d540e0d4ef Mon Sep 17 00:00:00 2001 +Message-Id: <88a88ad1f0e0805b6da5dcca83b828d540e0d4ef.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 22 Feb 2012 12:03:30 +0100 -Subject: [PATCH 195/327] seqlock: Prevent rt starvation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 195/330] seqlock: Prevent rt starvation +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz If a low prio writer gets preempted while holding the seqlock write locked, a high prio reader spins forever on RT. diff --git a/debian/patches-rt/0196-sunrpc-Make-svc_xprt_do_enqueue-use-get_cpu_light.patch b/debian/patches-rt/0196-sunrpc-Make-svc_xprt_do_enqueue-use-get_cpu_light.patch index a6d5a0c44..e2da3c420 100644 --- a/debian/patches-rt/0196-sunrpc-Make-svc_xprt_do_enqueue-use-get_cpu_light.patch +++ b/debian/patches-rt/0196-sunrpc-Make-svc_xprt_do_enqueue-use-get_cpu_light.patch @@ -1,12 +1,12 @@ -From 34240f60df058342e5a9cfa41bc7730a5d71b42b Mon Sep 17 00:00:00 2001 -Message-Id: <34240f60df058342e5a9cfa41bc7730a5d71b42b.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 20cc8c5033c87d50273d865d426c5e03123ed76a Mon Sep 17 00:00:00 2001 +Message-Id: <20cc8c5033c87d50273d865d426c5e03123ed76a.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 18 Feb 2015 16:05:28 +0100 -Subject: [PATCH 196/327] sunrpc: Make svc_xprt_do_enqueue() use +Subject: [PATCH 196/330] sunrpc: Make svc_xprt_do_enqueue() use get_cpu_light() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:915 |in_atomic(): 1, irqs_disabled(): 0, pid: 3194, name: rpc.nfsd diff --git a/debian/patches-rt/0197-net-Use-skbufhead-with-raw-lock.patch b/debian/patches-rt/0197-net-Use-skbufhead-with-raw-lock.patch index e993ddf2b..1a714cdd7 100644 --- a/debian/patches-rt/0197-net-Use-skbufhead-with-raw-lock.patch +++ b/debian/patches-rt/0197-net-Use-skbufhead-with-raw-lock.patch @@ -1,11 +1,11 @@ -From 743f5eb2cd6b7d563feb7ec5059f0b7972c0b075 Mon Sep 17 00:00:00 2001 -Message-Id: <743f5eb2cd6b7d563feb7ec5059f0b7972c0b075.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 75d43c972c266add8520e55baa9d3670edfeaf31 Mon Sep 17 00:00:00 2001 +Message-Id: <75d43c972c266add8520e55baa9d3670edfeaf31.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 12 Jul 2011 15:38:34 +0200 -Subject: [PATCH 197/327] net: Use skbufhead with raw lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 197/330] net: Use skbufhead with raw lock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Use the rps lock as rawlock so we can keep irq-off regions. It looks low latency. However we can't kfree() from this context therefore we defer this @@ -56,7 +56,7 @@ index 25407c206e73..d4d7aea13cc6 100644 struct lock_class_key *class) { diff --git a/net/core/dev.c b/net/core/dev.c -index c5901d343d0a..fcc109d279e2 100644 +index d4b73961f54b..c0e089fde4b5 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -218,14 +218,14 @@ static inline struct hlist_head *dev_index_hash(struct net *net, int ifindex) @@ -76,7 +76,7 @@ index c5901d343d0a..fcc109d279e2 100644 #endif } -@@ -5249,7 +5249,7 @@ static void flush_backlog(struct work_struct *work) +@@ -5259,7 +5259,7 @@ static void flush_backlog(struct work_struct *work) skb_queue_walk_safe(&sd->input_pkt_queue, skb, tmp) { if (skb->dev->reg_state == NETREG_UNREGISTERING) { __skb_unlink(skb, &sd->input_pkt_queue); @@ -85,7 +85,7 @@ index c5901d343d0a..fcc109d279e2 100644 input_queue_head_incr(sd); } } -@@ -5259,11 +5259,14 @@ static void flush_backlog(struct work_struct *work) +@@ -5269,11 +5269,14 @@ static void flush_backlog(struct work_struct *work) skb_queue_walk_safe(&sd->process_queue, skb, tmp) { if (skb->dev->reg_state == NETREG_UNREGISTERING) { __skb_unlink(skb, &sd->process_queue); @@ -101,7 +101,7 @@ index c5901d343d0a..fcc109d279e2 100644 } static void flush_all_backlogs(void) -@@ -5842,7 +5845,9 @@ static int process_backlog(struct napi_struct *napi, int quota) +@@ -5852,7 +5855,9 @@ static int process_backlog(struct napi_struct *napi, int quota) while (again) { struct sk_buff *skb; @@ -111,7 +111,7 @@ index c5901d343d0a..fcc109d279e2 100644 rcu_read_lock(); __netif_receive_skb(skb); rcu_read_unlock(); -@@ -5850,9 +5855,9 @@ static int process_backlog(struct napi_struct *napi, int quota) +@@ -5860,9 +5865,9 @@ static int process_backlog(struct napi_struct *napi, int quota) if (++work >= quota) return work; @@ -122,7 +122,7 @@ index c5901d343d0a..fcc109d279e2 100644 rps_lock(sd); if (skb_queue_empty(&sd->input_pkt_queue)) { /* -@@ -6317,13 +6322,21 @@ static __latent_entropy void net_rx_action(struct softirq_action *h) +@@ -6327,13 +6332,21 @@ static __latent_entropy void net_rx_action(struct softirq_action *h) unsigned long time_limit = jiffies + usecs_to_jiffies(netdev_budget_usecs); int budget = netdev_budget; @@ -144,7 +144,7 @@ index c5901d343d0a..fcc109d279e2 100644 for (;;) { struct napi_struct *n; -@@ -9509,10 +9522,13 @@ static int dev_cpu_dead(unsigned int oldcpu) +@@ -9519,10 +9532,13 @@ static int dev_cpu_dead(unsigned int oldcpu) netif_rx_ni(skb); input_queue_head_incr(oldsd); } @@ -159,7 +159,7 @@ index c5901d343d0a..fcc109d279e2 100644 return 0; } -@@ -9823,8 +9839,9 @@ static int __init net_dev_init(void) +@@ -9833,8 +9849,9 @@ static int __init net_dev_init(void) INIT_WORK(flush, flush_backlog); diff --git a/debian/patches-rt/0198-net-move-xmit_recursion-to-per-task-variable-on-RT.patch b/debian/patches-rt/0198-net-move-xmit_recursion-to-per-task-variable-on-RT.patch index 99f94ac63..2fde4a9ce 100644 --- a/debian/patches-rt/0198-net-move-xmit_recursion-to-per-task-variable-on-RT.patch +++ b/debian/patches-rt/0198-net-move-xmit_recursion-to-per-task-variable-on-RT.patch @@ -1,11 +1,11 @@ -From 6162c120de61116d7286a7e90bc3edc6f8fe9d4d Mon Sep 17 00:00:00 2001 -Message-Id: <6162c120de61116d7286a7e90bc3edc6f8fe9d4d.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From c8dd410ff81f11189662f9bbfcdea62cd979bd7a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Jan 2016 15:55:02 +0100 -Subject: [PATCH 198/327] net: move xmit_recursion to per-task variable on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 198/330] net: move xmit_recursion to per-task variable on -RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz A softirq on -RT can be preempted. That means one task is in __dev_queue_xmit(), gets preempted and another task may enter @@ -201,7 +201,7 @@ index 4a4f03a8d8d4..37334ec1ab3e 100644 int pagefault_disabled; #ifdef CONFIG_MMU diff --git a/net/core/dev.c b/net/core/dev.c -index fcc109d279e2..a138f17321b0 100644 +index c0e089fde4b5..b223a825affc 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -3540,8 +3540,10 @@ static void skb_update_prio(struct sk_buff *skb) @@ -242,7 +242,7 @@ index fcc109d279e2..a138f17321b0 100644 if (dev_xmit_complete(rc)) { HARD_TX_UNLOCK(dev, txq); goto out; -@@ -8568,7 +8573,7 @@ static void netdev_init_one_queue(struct net_device *dev, +@@ -8578,7 +8583,7 @@ static void netdev_init_one_queue(struct net_device *dev, /* Initialize queue lock */ spin_lock_init(&queue->_xmit_lock); netdev_set_xmit_lockdep_class(&queue->_xmit_lock, dev->type); diff --git a/debian/patches-rt/0199-net-provide-a-way-to-delegate-processing-a-softirq-t.patch b/debian/patches-rt/0199-net-provide-a-way-to-delegate-processing-a-softirq-t.patch index d585171be..eba623415 100644 --- a/debian/patches-rt/0199-net-provide-a-way-to-delegate-processing-a-softirq-t.patch +++ b/debian/patches-rt/0199-net-provide-a-way-to-delegate-processing-a-softirq-t.patch @@ -1,12 +1,12 @@ -From a961c365ec0b963b34e1875de910531691058e96 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 44a1419ce83f9bae131640cc8ce0cedc3c1241d5 Mon Sep 17 00:00:00 2001 +Message-Id: <44a1419ce83f9bae131640cc8ce0cedc3c1241d5.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 20 Jan 2016 15:39:05 +0100 -Subject: [PATCH 199/327] net: provide a way to delegate processing a softirq +Subject: [PATCH 199/330] net: provide a way to delegate processing a softirq to ksoftirqd -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz If the NET_RX uses up all of his budget it moves the following NAPI invocations into the `ksoftirqd`. On -RT it does not do so. Instead it @@ -75,10 +75,10 @@ index 27a4bb2303d0..25bcf2f2714b 100644 * This function must run with irqs disabled! */ diff --git a/net/core/dev.c b/net/core/dev.c -index a138f17321b0..5e167ef1e2dd 100644 +index b223a825affc..55891a994094 100644 --- a/net/core/dev.c +++ b/net/core/dev.c -@@ -6371,7 +6371,7 @@ static __latent_entropy void net_rx_action(struct softirq_action *h) +@@ -6381,7 +6381,7 @@ static __latent_entropy void net_rx_action(struct softirq_action *h) list_splice_tail(&repoll, &list); list_splice(&list, &sd->poll_list); if (!list_empty(&sd->poll_list)) diff --git a/debian/patches-rt/0200-net-dev-always-take-qdisc-s-busylock-in-__dev_xmit_s.patch b/debian/patches-rt/0200-net-dev-always-take-qdisc-s-busylock-in-__dev_xmit_s.patch index 0d229ee28..1fe3f4da9 100644 --- a/debian/patches-rt/0200-net-dev-always-take-qdisc-s-busylock-in-__dev_xmit_s.patch +++ b/debian/patches-rt/0200-net-dev-always-take-qdisc-s-busylock-in-__dev_xmit_s.patch @@ -1,12 +1,12 @@ -From 9db440aa61c320399044b788233e29ce076a4c1c Mon Sep 17 00:00:00 2001 -Message-Id: <9db440aa61c320399044b788233e29ce076a4c1c.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 2b9c6db8f0c393b038cd357bc7ab7ae367380c1e Mon Sep 17 00:00:00 2001 +Message-Id: <2b9c6db8f0c393b038cd357bc7ab7ae367380c1e.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 30 Mar 2016 13:36:29 +0200 -Subject: [PATCH 200/327] net: dev: always take qdisc's busylock in +Subject: [PATCH 200/330] net: dev: always take qdisc's busylock in __dev_xmit_skb() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The root-lock is dropped before dev_hard_start_xmit() is invoked and after setting the __QDISC___STATE_RUNNING bit. If this task is now pushed away @@ -25,7 +25,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 4 insertions(+) diff --git a/net/core/dev.c b/net/core/dev.c -index 5e167ef1e2dd..8c7a4e988917 100644 +index 55891a994094..52d44a4db2ff 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -3468,7 +3468,11 @@ static inline int __dev_xmit_skb(struct sk_buff *skb, struct Qdisc *q, diff --git a/debian/patches-rt/0201-net-Qdisc-use-a-seqlock-instead-seqcount.patch b/debian/patches-rt/0201-net-Qdisc-use-a-seqlock-instead-seqcount.patch index 08f9d4246..035f86099 100644 --- a/debian/patches-rt/0201-net-Qdisc-use-a-seqlock-instead-seqcount.patch +++ b/debian/patches-rt/0201-net-Qdisc-use-a-seqlock-instead-seqcount.patch @@ -1,11 +1,11 @@ -From 6e815a4aa54b851a421419996b49c0a39beaabff Mon Sep 17 00:00:00 2001 -Message-Id: <6e815a4aa54b851a421419996b49c0a39beaabff.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 13205fdad1d92b748e79bdab4019ab763d35cc71 Mon Sep 17 00:00:00 2001 +Message-Id: <13205fdad1d92b748e79bdab4019ab763d35cc71.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Sep 2016 17:36:35 +0200 -Subject: [PATCH 201/327] net/Qdisc: use a seqlock instead seqcount -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 201/330] net/Qdisc: use a seqlock instead seqcount +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The seqcount disables preemption on -RT while it is held which can't remove. Also we don't want the reader to spin for ages if the writer is diff --git a/debian/patches-rt/0202-net-add-back-the-missing-serialization-in-ip_send_un.patch b/debian/patches-rt/0202-net-add-back-the-missing-serialization-in-ip_send_un.patch index e6af73983..17c74f115 100644 --- a/debian/patches-rt/0202-net-add-back-the-missing-serialization-in-ip_send_un.patch +++ b/debian/patches-rt/0202-net-add-back-the-missing-serialization-in-ip_send_un.patch @@ -1,15 +1,15 @@ -From 2f1d8f18ea3f9a1ccf757f48fbf1eeb7504756a6 Mon Sep 17 00:00:00 2001 -Message-Id: <2f1d8f18ea3f9a1ccf757f48fbf1eeb7504756a6.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 1f5eb8ce42664888b35845d7cab8149fcb69f783 Mon Sep 17 00:00:00 2001 +Message-Id: <1f5eb8ce42664888b35845d7cab8149fcb69f783.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 31 Aug 2016 17:21:56 +0200 -Subject: [PATCH 202/327] net: add back the missing serialization in +Subject: [PATCH 202/330] net: add back the missing serialization in ip_send_unicast_reply() MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Some time ago Sami Pietikäinen reported a crash on -RT in ip_send_unicast_reply() which was later fixed by Nicholas Mc Guire diff --git a/debian/patches-rt/0203-net-add-a-lock-around-icmp_sk.patch b/debian/patches-rt/0203-net-add-a-lock-around-icmp_sk.patch index af2e1a93f..344b27465 100644 --- a/debian/patches-rt/0203-net-add-a-lock-around-icmp_sk.patch +++ b/debian/patches-rt/0203-net-add-a-lock-around-icmp_sk.patch @@ -1,11 +1,11 @@ -From 76f6c7b6060f6a048c81005f9f77dafbe03e0cf0 Mon Sep 17 00:00:00 2001 -Message-Id: <76f6c7b6060f6a048c81005f9f77dafbe03e0cf0.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8eb504de6869a02cda203cce3db3d4518bf4cdd1 Mon Sep 17 00:00:00 2001 +Message-Id: <8eb504de6869a02cda203cce3db3d4518bf4cdd1.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 31 Aug 2016 17:54:09 +0200 -Subject: [PATCH 203/327] net: add a lock around icmp_sk() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 203/330] net: add a lock around icmp_sk() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz It looks like the this_cpu_ptr() access in icmp_sk() is protected with local_bh_disable(). To avoid missing serialization in -RT I am adding diff --git a/debian/patches-rt/0204-net-Have-__napi_schedule_irqoff-disable-interrupts-o.patch b/debian/patches-rt/0204-net-Have-__napi_schedule_irqoff-disable-interrupts-o.patch index e5f68b13b..a94204481 100644 --- a/debian/patches-rt/0204-net-Have-__napi_schedule_irqoff-disable-interrupts-o.patch +++ b/debian/patches-rt/0204-net-Have-__napi_schedule_irqoff-disable-interrupts-o.patch @@ -1,12 +1,12 @@ -From 18f0d88854206ae68cfb0c5b0bfdb21ad9a47906 Mon Sep 17 00:00:00 2001 -Message-Id: <18f0d88854206ae68cfb0c5b0bfdb21ad9a47906.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 590d25e7d72d525d63309d586bdb442818268a48 Mon Sep 17 00:00:00 2001 +Message-Id: <590d25e7d72d525d63309d586bdb442818268a48.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Steven Rostedt Date: Tue, 6 Dec 2016 17:50:30 -0500 -Subject: [PATCH 204/327] net: Have __napi_schedule_irqoff() disable interrupts +Subject: [PATCH 204/330] net: Have __napi_schedule_irqoff() disable interrupts on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz A customer hit a crash where the napi sd->poll_list became corrupted. The customer had the bnx2x driver, which does a @@ -56,10 +56,10 @@ index 5de4b66e11fe..1d6bb0ab437f 100644 static inline bool napi_disable_pending(struct napi_struct *n) { diff --git a/net/core/dev.c b/net/core/dev.c -index 8c7a4e988917..2f63f20bbcc9 100644 +index 52d44a4db2ff..c67056ad032b 100644 --- a/net/core/dev.c +++ b/net/core/dev.c -@@ -5941,6 +5941,7 @@ bool napi_schedule_prep(struct napi_struct *n) +@@ -5951,6 +5951,7 @@ bool napi_schedule_prep(struct napi_struct *n) } EXPORT_SYMBOL(napi_schedule_prep); @@ -67,7 +67,7 @@ index 8c7a4e988917..2f63f20bbcc9 100644 /** * __napi_schedule_irqoff - schedule for receive * @n: entry to schedule -@@ -5952,6 +5953,7 @@ void __napi_schedule_irqoff(struct napi_struct *n) +@@ -5962,6 +5963,7 @@ void __napi_schedule_irqoff(struct napi_struct *n) ____napi_schedule(this_cpu_ptr(&softnet_data), n); } EXPORT_SYMBOL(__napi_schedule_irqoff); diff --git a/debian/patches-rt/0205-irqwork-push-most-work-into-softirq-context.patch b/debian/patches-rt/0205-irqwork-push-most-work-into-softirq-context.patch index 1146bc7db..bf2c399a1 100644 --- a/debian/patches-rt/0205-irqwork-push-most-work-into-softirq-context.patch +++ b/debian/patches-rt/0205-irqwork-push-most-work-into-softirq-context.patch @@ -1,11 +1,11 @@ -From 9292c0aa99544f6f10d69671c3805deffe205d9e Mon Sep 17 00:00:00 2001 -Message-Id: <9292c0aa99544f6f10d69671c3805deffe205d9e.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From e6034ead729651f152a7472d103e8bafd18855fa Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 23 Jun 2015 15:32:51 +0200 -Subject: [PATCH 205/327] irqwork: push most work into softirq context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 205/330] irqwork: push most work into softirq context +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Initially we defered all irqwork into softirq because we didn't want the latency spikes if perf or another user was busy and delayed the RT task. diff --git a/debian/patches-rt/0206-printk-Make-rt-aware.patch b/debian/patches-rt/0206-printk-Make-rt-aware.patch index 167267936..fe4b9c6d7 100644 --- a/debian/patches-rt/0206-printk-Make-rt-aware.patch +++ b/debian/patches-rt/0206-printk-Make-rt-aware.patch @@ -1,11 +1,11 @@ -From fe42d12073d51a53182a0ceec601ad865801b3f7 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 9bacf7114ebee7464ea5b3637dc4f1d890e8ca77 Mon Sep 17 00:00:00 2001 +Message-Id: <9bacf7114ebee7464ea5b3637dc4f1d890e8ca77.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 19 Sep 2012 14:50:37 +0200 -Subject: [PATCH 206/327] printk: Make rt aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 206/330] printk: Make rt aware +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Drop the lock before calling the console driver and do not disable interrupts while printing to a serial console. diff --git a/debian/patches-rt/0207-kernel-printk-Don-t-try-to-print-from-IRQ-NMI-region.patch b/debian/patches-rt/0207-kernel-printk-Don-t-try-to-print-from-IRQ-NMI-region.patch index 462e069df..d3a7e7a0e 100644 --- a/debian/patches-rt/0207-kernel-printk-Don-t-try-to-print-from-IRQ-NMI-region.patch +++ b/debian/patches-rt/0207-kernel-printk-Don-t-try-to-print-from-IRQ-NMI-region.patch @@ -1,11 +1,11 @@ -From 3d497862a28753a21f5bd89cc6490856d4ab7a33 Mon Sep 17 00:00:00 2001 -Message-Id: <3d497862a28753a21f5bd89cc6490856d4ab7a33.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 88063244f722c331d4b2c91d6ca23fc0e597f78d Mon Sep 17 00:00:00 2001 +Message-Id: <88063244f722c331d4b2c91d6ca23fc0e597f78d.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 19 May 2016 17:45:27 +0200 -Subject: [PATCH 207/327] kernel/printk: Don't try to print from IRQ/NMI region -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 207/330] kernel/printk: Don't try to print from IRQ/NMI region +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz On -RT we try to acquire sleeping locks which might lead to warnings from lockdep or a warn_on() from spin_try_lock() (which is a rtmutex on diff --git a/debian/patches-rt/0208-printk-Drop-the-logbuf_lock-more-often.patch b/debian/patches-rt/0208-printk-Drop-the-logbuf_lock-more-often.patch index 186236394..fcf0f3435 100644 --- a/debian/patches-rt/0208-printk-Drop-the-logbuf_lock-more-often.patch +++ b/debian/patches-rt/0208-printk-Drop-the-logbuf_lock-more-often.patch @@ -1,11 +1,11 @@ -From ca9338b3ed00638ee8a13e918b1cb64d02757f75 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 930df01c3c062b4e6f57b53b8c8432e3b7915c62 Mon Sep 17 00:00:00 2001 +Message-Id: <930df01c3c062b4e6f57b53b8c8432e3b7915c62.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 21 Mar 2013 19:01:05 +0100 -Subject: [PATCH 208/327] printk: Drop the logbuf_lock more often -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 208/330] printk: Drop the logbuf_lock more often +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The lock is hold with irgs off. The latency drops 500us+ on my arm bugs with a "full" buffer after executing "dmesg" on the shell. diff --git a/debian/patches-rt/0209-ARM-enable-irq-in-translation-section-permission-fau.patch b/debian/patches-rt/0209-ARM-enable-irq-in-translation-section-permission-fau.patch index e3229e556..25d8702b6 100644 --- a/debian/patches-rt/0209-ARM-enable-irq-in-translation-section-permission-fau.patch +++ b/debian/patches-rt/0209-ARM-enable-irq-in-translation-section-permission-fau.patch @@ -1,15 +1,15 @@ -From c3bfbaf2bbf2dff66a04527741febd93637e3f65 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 3e10feb90d8a4aa938767db521dc63afbde7d0a3 Mon Sep 17 00:00:00 2001 +Message-Id: <3e10feb90d8a4aa938767db521dc63afbde7d0a3.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: "Yadi.hu" Date: Wed, 10 Dec 2014 10:32:09 +0800 -Subject: [PATCH 209/327] ARM: enable irq in translation/section permission +Subject: [PATCH 209/330] ARM: enable irq in translation/section permission fault handlers MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Probably happens on all ARM, with CONFIG_PREEMPT_RT_FULL diff --git a/debian/patches-rt/0210-genirq-update-irq_set_irqchip_state-documentation.patch b/debian/patches-rt/0210-genirq-update-irq_set_irqchip_state-documentation.patch index 501279a9e..f1e1234fc 100644 --- a/debian/patches-rt/0210-genirq-update-irq_set_irqchip_state-documentation.patch +++ b/debian/patches-rt/0210-genirq-update-irq_set_irqchip_state-documentation.patch @@ -1,11 +1,11 @@ -From 962246c92fc7a6c69779f0874724f35269a6f736 Mon Sep 17 00:00:00 2001 -Message-Id: <962246c92fc7a6c69779f0874724f35269a6f736.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 53455a5a7d8e3d1294adf87d1e0a7ef6fbcb88b9 Mon Sep 17 00:00:00 2001 +Message-Id: <53455a5a7d8e3d1294adf87d1e0a7ef6fbcb88b9.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 11 Feb 2016 11:54:00 -0600 -Subject: [PATCH 210/327] genirq: update irq_set_irqchip_state documentation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 210/330] genirq: update irq_set_irqchip_state documentation +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz On -rt kernels, the use of migrate_disable()/migrate_enable() is sufficient to guarantee a task isn't moved to another CPU. Update the diff --git a/debian/patches-rt/0211-KVM-arm-arm64-downgrade-preempt_disable-d-region-to-.patch b/debian/patches-rt/0211-KVM-arm-arm64-downgrade-preempt_disable-d-region-to-.patch index 8988f9d63..254bd981b 100644 --- a/debian/patches-rt/0211-KVM-arm-arm64-downgrade-preempt_disable-d-region-to-.patch +++ b/debian/patches-rt/0211-KVM-arm-arm64-downgrade-preempt_disable-d-region-to-.patch @@ -1,12 +1,12 @@ -From c58729f4332c87425f4a4cd46277c8f1ce5a4f60 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 384c127b185ee6b0489944dc079453403e60a94f Mon Sep 17 00:00:00 2001 +Message-Id: <384c127b185ee6b0489944dc079453403e60a94f.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 11 Feb 2016 11:54:01 -0600 -Subject: [PATCH 211/327] KVM: arm/arm64: downgrade preempt_disable()d region +Subject: [PATCH 211/330] KVM: arm/arm64: downgrade preempt_disable()d region to migrate_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz kvm_arch_vcpu_ioctl_run() disables the use of preemption when updating the vgic and timer states to prevent the calling task from migrating to diff --git a/debian/patches-rt/0212-arm64-fpsimd-use-preemp_disable-in-addition-to-local.patch b/debian/patches-rt/0212-arm64-fpsimd-use-preemp_disable-in-addition-to-local.patch index 956da36a0..8b7fd09a2 100644 --- a/debian/patches-rt/0212-arm64-fpsimd-use-preemp_disable-in-addition-to-local.patch +++ b/debian/patches-rt/0212-arm64-fpsimd-use-preemp_disable-in-addition-to-local.patch @@ -1,12 +1,12 @@ -From a6ae79539115b90ea4f5c6c91d093117b5fa2d46 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 0b46951e9e58abc007b26a408b6d2b84c11f8f2f Mon Sep 17 00:00:00 2001 +Message-Id: <0b46951e9e58abc007b26a408b6d2b84c11f8f2f.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 25 Jul 2018 14:02:38 +0200 -Subject: [PATCH 212/327] arm64: fpsimd: use preemp_disable in addition to +Subject: [PATCH 212/330] arm64: fpsimd: use preemp_disable in addition to local_bh_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz In v4.16-RT I noticed a number of warnings from task_fpsimd_load(). The code disables BH and expects that it is not preemptible. On -RT the diff --git a/debian/patches-rt/0213-kgdb-serial-Short-term-workaround.patch b/debian/patches-rt/0213-kgdb-serial-Short-term-workaround.patch index 1bf98b906..5ca9dfb57 100644 --- a/debian/patches-rt/0213-kgdb-serial-Short-term-workaround.patch +++ b/debian/patches-rt/0213-kgdb-serial-Short-term-workaround.patch @@ -1,11 +1,11 @@ -From e204f8efa3253fa6e8b918ed10254c0fd7d5b65a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 0f58b6c9bc1f8209a6035aa227982cad08a68408 Mon Sep 17 00:00:00 2001 +Message-Id: <0f58b6c9bc1f8209a6035aa227982cad08a68408.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Jason Wessel Date: Thu, 28 Jul 2011 12:42:23 -0500 -Subject: [PATCH 213/327] kgdb/serial: Short term workaround -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 213/330] kgdb/serial: Short term workaround +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz On 07/27/2011 04:37 PM, Thomas Gleixner wrote: > - KGDB (not yet disabled) is reportedly unusable on -rt right now due diff --git a/debian/patches-rt/0214-sysfs-Add-sys-kernel-realtime-entry.patch b/debian/patches-rt/0214-sysfs-Add-sys-kernel-realtime-entry.patch index 3b8bbc5a1..a9dbb5139 100644 --- a/debian/patches-rt/0214-sysfs-Add-sys-kernel-realtime-entry.patch +++ b/debian/patches-rt/0214-sysfs-Add-sys-kernel-realtime-entry.patch @@ -1,11 +1,11 @@ -From 73f71f6da1414229362b5bbb3cdc24ddebd4084f Mon Sep 17 00:00:00 2001 -Message-Id: <73f71f6da1414229362b5bbb3cdc24ddebd4084f.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 22dbbbb88222d2d0e24a88c2d706c04c8a6a3965 Mon Sep 17 00:00:00 2001 +Message-Id: <22dbbbb88222d2d0e24a88c2d706c04c8a6a3965.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Clark Williams Date: Sat, 30 Jul 2011 21:55:53 -0500 -Subject: [PATCH 214/327] sysfs: Add /sys/kernel/realtime entry -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 214/330] sysfs: Add /sys/kernel/realtime entry +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Add a /sys/kernel entry to indicate that the kernel is a realtime kernel. diff --git a/debian/patches-rt/0215-mm-rt-kmap_atomic-scheduling.patch b/debian/patches-rt/0215-mm-rt-kmap_atomic-scheduling.patch index 150e8a46c..627f790ef 100644 --- a/debian/patches-rt/0215-mm-rt-kmap_atomic-scheduling.patch +++ b/debian/patches-rt/0215-mm-rt-kmap_atomic-scheduling.patch @@ -1,11 +1,11 @@ -From e400ee6744b1e34aa54d9792702a540506e3063f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 413cb8e15d807d70d253234711e67abf4ca2890e Mon Sep 17 00:00:00 2001 +Message-Id: <413cb8e15d807d70d253234711e67abf4ca2890e.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Peter Zijlstra Date: Thu, 28 Jul 2011 10:43:51 +0200 -Subject: [PATCH 215/327] mm, rt: kmap_atomic scheduling -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 215/330] mm, rt: kmap_atomic scheduling +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz In fact, with migrate_disable() existing one could play games with kmap_atomic. You could save/restore the kmap_atomic slots on context diff --git a/debian/patches-rt/0216-x86-highmem-Add-a-already-used-pte-check.patch b/debian/patches-rt/0216-x86-highmem-Add-a-already-used-pte-check.patch index b2c7096a9..9c59c1dc9 100644 --- a/debian/patches-rt/0216-x86-highmem-Add-a-already-used-pte-check.patch +++ b/debian/patches-rt/0216-x86-highmem-Add-a-already-used-pte-check.patch @@ -1,11 +1,11 @@ -From ecffea451725608ac588f34c92d79e2aaaf1fcdd Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 010446144c1360626283de04c244b2f61602606f Mon Sep 17 00:00:00 2001 +Message-Id: <010446144c1360626283de04c244b2f61602606f.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Mar 2013 17:09:55 +0100 -Subject: [PATCH 216/327] x86/highmem: Add a "already used pte" check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 216/330] x86/highmem: Add a "already used pte" check +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz This is a copy from kmap_atomic_prot(). diff --git a/debian/patches-rt/0217-arm-highmem-Flush-tlb-on-unmap.patch b/debian/patches-rt/0217-arm-highmem-Flush-tlb-on-unmap.patch index e7f874612..b62308c45 100644 --- a/debian/patches-rt/0217-arm-highmem-Flush-tlb-on-unmap.patch +++ b/debian/patches-rt/0217-arm-highmem-Flush-tlb-on-unmap.patch @@ -1,11 +1,11 @@ -From 64cea0ac96a28b4ffa1cee88186ccb5f9adb1ecb Mon Sep 17 00:00:00 2001 -Message-Id: <64cea0ac96a28b4ffa1cee88186ccb5f9adb1ecb.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From aea2c0e41b1f7e7aa50b32c94b7238f9f64eb9d2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Mar 2013 21:37:27 +0100 -Subject: [PATCH 217/327] arm/highmem: Flush tlb on unmap -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 217/330] arm/highmem: Flush tlb on unmap +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The tlb should be flushed on unmap and thus make the mapping entry invalid. This is only done in the non-debug case which does not look diff --git a/debian/patches-rt/0218-arm-Enable-highmem-for-rt.patch b/debian/patches-rt/0218-arm-Enable-highmem-for-rt.patch index d7dd19d8b..4938efc6f 100644 --- a/debian/patches-rt/0218-arm-Enable-highmem-for-rt.patch +++ b/debian/patches-rt/0218-arm-Enable-highmem-for-rt.patch @@ -1,11 +1,11 @@ -From 0823f66a86be3b25897e856b4bf6873396262da2 Mon Sep 17 00:00:00 2001 -Message-Id: <0823f66a86be3b25897e856b4bf6873396262da2.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From cc8f6da32c3bea8090ef60509d92c131c20e9294 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 13 Feb 2013 11:03:11 +0100 -Subject: [PATCH 218/327] arm: Enable highmem for rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 218/330] arm: Enable highmem for rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz fixup highmem for ARM. diff --git a/debian/patches-rt/0219-scsi-fcoe-Make-RT-aware.patch b/debian/patches-rt/0219-scsi-fcoe-Make-RT-aware.patch index c135591a7..34dfc8d95 100644 --- a/debian/patches-rt/0219-scsi-fcoe-Make-RT-aware.patch +++ b/debian/patches-rt/0219-scsi-fcoe-Make-RT-aware.patch @@ -1,11 +1,11 @@ -From 20feb39c0ae3f5de4bb9e70daf94beb9e893b1ac Mon Sep 17 00:00:00 2001 -Message-Id: <20feb39c0ae3f5de4bb9e70daf94beb9e893b1ac.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From ab5c125724ea8ae6fa127a2ff57150be9a751267 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 12 Nov 2011 14:00:48 +0100 -Subject: [PATCH 219/327] scsi/fcoe: Make RT aware. -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 219/330] scsi/fcoe: Make RT aware. +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Do not disable preemption while taking sleeping locks. All user look safe for migrate_diable() only. diff --git a/debian/patches-rt/0220-x86-crypto-Reduce-preempt-disabled-regions.patch b/debian/patches-rt/0220-x86-crypto-Reduce-preempt-disabled-regions.patch index 8e069a44f..2a0abaa46 100644 --- a/debian/patches-rt/0220-x86-crypto-Reduce-preempt-disabled-regions.patch +++ b/debian/patches-rt/0220-x86-crypto-Reduce-preempt-disabled-regions.patch @@ -1,11 +1,11 @@ -From a06a6c5905928cf7251c4760b7bde81c6f221b14 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 95783ee93e8742bc9ac075e086e37f36d387302b Mon Sep 17 00:00:00 2001 +Message-Id: <95783ee93e8742bc9ac075e086e37f36d387302b.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 14 Nov 2011 18:19:27 +0100 -Subject: [PATCH 220/327] x86: crypto: Reduce preempt disabled regions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 220/330] x86: crypto: Reduce preempt disabled regions +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Restrict the preempt disabled regions to the actual floating point operations and enable preemption for the administrative actions. diff --git a/debian/patches-rt/0221-crypto-Reduce-preempt-disabled-regions-more-algos.patch b/debian/patches-rt/0221-crypto-Reduce-preempt-disabled-regions-more-algos.patch index 8c6c09736..feda119da 100644 --- a/debian/patches-rt/0221-crypto-Reduce-preempt-disabled-regions-more-algos.patch +++ b/debian/patches-rt/0221-crypto-Reduce-preempt-disabled-regions-more-algos.patch @@ -1,11 +1,11 @@ -From 5d5e459a291be419759b0e15bb3ad244b042d37e Mon Sep 17 00:00:00 2001 -Message-Id: <5d5e459a291be419759b0e15bb3ad244b042d37e.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From b7e42023414475d244443b73c555603de0315678 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2014 17:24:04 +0100 -Subject: [PATCH 221/327] crypto: Reduce preempt disabled regions, more algos -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 221/330] crypto: Reduce preempt disabled regions, more algos +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Don Estabrook reported | kernel: WARNING: CPU: 2 PID: 858 at kernel/sched/core.c:2428 migrate_disable+0xed/0x100() diff --git a/debian/patches-rt/0222-crypto-limit-more-FPU-enabled-sections.patch b/debian/patches-rt/0222-crypto-limit-more-FPU-enabled-sections.patch index 1e68f7d34..86c88e5f6 100644 --- a/debian/patches-rt/0222-crypto-limit-more-FPU-enabled-sections.patch +++ b/debian/patches-rt/0222-crypto-limit-more-FPU-enabled-sections.patch @@ -1,14 +1,14 @@ -From a1853e9b07af239de86a4884d2e7f542985ebe63 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d046a77a159054fc36804a547d2191e49b9cb607 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 30 Nov 2017 13:40:10 +0100 -Subject: [PATCH 222/327] crypto: limit more FPU-enabled sections +Subject: [PATCH 222/330] crypto: limit more FPU-enabled sections MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Those crypto drivers use SSE/AVX/… for their crypto work and in order to do so in kernel they need to enable the "FPU" in kernel mode which diff --git a/debian/patches-rt/0223-crypto-scompress-serialize-RT-percpu-scratch-buffer-.patch b/debian/patches-rt/0223-crypto-scompress-serialize-RT-percpu-scratch-buffer-.patch index 63e46662d..ee393ee09 100644 --- a/debian/patches-rt/0223-crypto-scompress-serialize-RT-percpu-scratch-buffer-.patch +++ b/debian/patches-rt/0223-crypto-scompress-serialize-RT-percpu-scratch-buffer-.patch @@ -1,12 +1,12 @@ -From 07749057c848fdb279ee98e31b004e7b2bbc6226 Mon Sep 17 00:00:00 2001 -Message-Id: <07749057c848fdb279ee98e31b004e7b2bbc6226.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From cb16d1f5f60fe332bfe3b9087ce41127a4a2b6f6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 11 Jul 2018 17:14:47 +0200 -Subject: [PATCH 223/327] crypto: scompress - serialize RT percpu scratch +Subject: [PATCH 223/330] crypto: scompress - serialize RT percpu scratch buffer access with a local lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz | BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:974 | in_atomic(): 1, irqs_disabled(): 0, pid: 1401, name: cryptomgr_test diff --git a/debian/patches-rt/0224-crypto-cryptd-add-a-lock-instead-preempt_disable-loc.patch b/debian/patches-rt/0224-crypto-cryptd-add-a-lock-instead-preempt_disable-loc.patch index 3786a895b..2f6775703 100644 --- a/debian/patches-rt/0224-crypto-cryptd-add-a-lock-instead-preempt_disable-loc.patch +++ b/debian/patches-rt/0224-crypto-cryptd-add-a-lock-instead-preempt_disable-loc.patch @@ -1,12 +1,12 @@ -From 5c3d1f5c1f420357bbc79382d5362526343b22bf Mon Sep 17 00:00:00 2001 -Message-Id: <5c3d1f5c1f420357bbc79382d5362526343b22bf.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From b0bbd309321efb8ada7dd55f8cb33da285c993a8 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 18:52:00 +0200 -Subject: [PATCH 224/327] crypto: cryptd - add a lock instead +Subject: [PATCH 224/330] crypto: cryptd - add a lock instead preempt_disable/local_bh_disable -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz cryptd has a per-CPU lock which protected with local_bh_disable() and preempt_disable(). diff --git a/debian/patches-rt/0225-panic-skip-get_random_bytes-for-RT_FULL-in-init_oops.patch b/debian/patches-rt/0225-panic-skip-get_random_bytes-for-RT_FULL-in-init_oops.patch index b0b1df787..c03af6a66 100644 --- a/debian/patches-rt/0225-panic-skip-get_random_bytes-for-RT_FULL-in-init_oops.patch +++ b/debian/patches-rt/0225-panic-skip-get_random_bytes-for-RT_FULL-in-init_oops.patch @@ -1,12 +1,12 @@ -From 210d31cc7e09d416580edb2b7a3a796eff930b92 Mon Sep 17 00:00:00 2001 -Message-Id: <210d31cc7e09d416580edb2b7a3a796eff930b92.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From cedcd2ac6b88c1741f257bc54a574db15f0950cc Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 14 Jul 2015 14:26:34 +0200 -Subject: [PATCH 225/327] panic: skip get_random_bytes for RT_FULL in +Subject: [PATCH 225/330] panic: skip get_random_bytes for RT_FULL in init_oops_id -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Disable on -RT. If this is invoked from irq-context we will have problems to acquire the sleeping lock. diff --git a/debian/patches-rt/0226-x86-stackprotector-Avoid-random-pool-on-rt.patch b/debian/patches-rt/0226-x86-stackprotector-Avoid-random-pool-on-rt.patch index af3cb884e..59a914166 100644 --- a/debian/patches-rt/0226-x86-stackprotector-Avoid-random-pool-on-rt.patch +++ b/debian/patches-rt/0226-x86-stackprotector-Avoid-random-pool-on-rt.patch @@ -1,11 +1,11 @@ -From 0fc87a2a7bfdb73b974a3db105408d6581816cd5 Mon Sep 17 00:00:00 2001 -Message-Id: <0fc87a2a7bfdb73b974a3db105408d6581816cd5.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 72a4312a231a4bd5e0209a71865e9c7ca93e61f9 Mon Sep 17 00:00:00 2001 +Message-Id: <72a4312a231a4bd5e0209a71865e9c7ca93e61f9.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 16 Dec 2010 14:25:18 +0100 -Subject: [PATCH 226/327] x86: stackprotector: Avoid random pool on rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 226/330] x86: stackprotector: Avoid random pool on rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz CPU bringup calls into the random pool to initialize the stack canary. During boot that works nicely even on RT as the might sleep diff --git a/debian/patches-rt/0227-random-Make-it-work-on-rt.patch b/debian/patches-rt/0227-random-Make-it-work-on-rt.patch index c9b079ec6..74172095a 100644 --- a/debian/patches-rt/0227-random-Make-it-work-on-rt.patch +++ b/debian/patches-rt/0227-random-Make-it-work-on-rt.patch @@ -1,11 +1,11 @@ -From 1feea850faf98b92650773d3e167980af9150fa3 Mon Sep 17 00:00:00 2001 -Message-Id: <1feea850faf98b92650773d3e167980af9150fa3.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 111d77c4af4668c0748dd3a79edea1511cc6fed6 Mon Sep 17 00:00:00 2001 +Message-Id: <111d77c4af4668c0748dd3a79edea1511cc6fed6.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 21 Aug 2012 20:38:50 +0200 -Subject: [PATCH 227/327] random: Make it work on rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 227/330] random: Make it work on rt +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Delegate the random insertion to the forced threaded interrupt handler. Store the return IP of the hard interrupt handler in the irq diff --git a/debian/patches-rt/0228-cpu-hotplug-Implement-CPU-pinning.patch b/debian/patches-rt/0228-cpu-hotplug-Implement-CPU-pinning.patch index f5a2b0600..ecc098fee 100644 --- a/debian/patches-rt/0228-cpu-hotplug-Implement-CPU-pinning.patch +++ b/debian/patches-rt/0228-cpu-hotplug-Implement-CPU-pinning.patch @@ -1,11 +1,11 @@ -From ddbf51a5bd0bab1af8760213f51e2df8be502511 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8e152de56629f2252111613eb660749537f6e1ae Mon Sep 17 00:00:00 2001 +Message-Id: <8e152de56629f2252111613eb660749537f6e1ae.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 19 Jul 2017 17:31:20 +0200 -Subject: [PATCH 228/327] cpu/hotplug: Implement CPU pinning -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 228/330] cpu/hotplug: Implement CPU pinning +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Signed-off-by: Thomas Gleixner --- diff --git a/debian/patches-rt/0229-sched-Allow-pinned-user-tasks-to-be-awakened-to-the-.patch b/debian/patches-rt/0229-sched-Allow-pinned-user-tasks-to-be-awakened-to-the-.patch index dfc7f4514..07a05aa6b 100644 --- a/debian/patches-rt/0229-sched-Allow-pinned-user-tasks-to-be-awakened-to-the-.patch +++ b/debian/patches-rt/0229-sched-Allow-pinned-user-tasks-to-be-awakened-to-the-.patch @@ -1,12 +1,12 @@ -From 7f0ef57e0d554e60767e89bd5868d4a83479b2db Mon Sep 17 00:00:00 2001 -Message-Id: <7f0ef57e0d554e60767e89bd5868d4a83479b2db.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From a3e885fd9cafc709dcb6d14e2e04f66e43c7db6e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 19 Aug 2018 08:28:35 +0200 -Subject: [PATCH 229/327] sched: Allow pinned user tasks to be awakened to the +Subject: [PATCH 229/330] sched: Allow pinned user tasks to be awakened to the CPU they pinned -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Since commit 7af443ee16976 ("sched/core: Require cpu_active() in select_task_rq(), for user tasks") select_fallback_rq() will BUG() if diff --git a/debian/patches-rt/0230-hotplug-duct-tape-RT-rwlock-usage-for-non-RT.patch b/debian/patches-rt/0230-hotplug-duct-tape-RT-rwlock-usage-for-non-RT.patch index c3ca6d9f4..ded73e216 100644 --- a/debian/patches-rt/0230-hotplug-duct-tape-RT-rwlock-usage-for-non-RT.patch +++ b/debian/patches-rt/0230-hotplug-duct-tape-RT-rwlock-usage-for-non-RT.patch @@ -1,11 +1,11 @@ -From 96fc455b1f994fcb865fb3b27030462eb212a969 Mon Sep 17 00:00:00 2001 -Message-Id: <96fc455b1f994fcb865fb3b27030462eb212a969.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 868d0c19593c39020b71eb6c63794996e42471c2 Mon Sep 17 00:00:00 2001 +Message-Id: <868d0c19593c39020b71eb6c63794996e42471c2.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 4 Aug 2017 18:31:00 +0200 -Subject: [PATCH 230/327] hotplug: duct-tape RT-rwlock usage for non-RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 230/330] hotplug: duct-tape RT-rwlock usage for non-RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz This type is only available on -RT. We need to craft something for non-RT. Since the only migrate_disable() user is -RT only, there is no diff --git a/debian/patches-rt/0231-net-Remove-preemption-disabling-in-netif_rx.patch b/debian/patches-rt/0231-net-Remove-preemption-disabling-in-netif_rx.patch index 8c4e896e9..7e0323ad4 100644 --- a/debian/patches-rt/0231-net-Remove-preemption-disabling-in-netif_rx.patch +++ b/debian/patches-rt/0231-net-Remove-preemption-disabling-in-netif_rx.patch @@ -1,11 +1,11 @@ -From 87baa8529294c17ee5e8bc293673398e15a36c66 Mon Sep 17 00:00:00 2001 -Message-Id: <87baa8529294c17ee5e8bc293673398e15a36c66.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5eb268be9849842589d4af1bf2c7aa712de60914 Mon Sep 17 00:00:00 2001 +Message-Id: <5eb268be9849842589d4af1bf2c7aa712de60914.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Priyanka Jain Date: Thu, 17 May 2012 09:35:11 +0530 -Subject: [PATCH 231/327] net: Remove preemption disabling in netif_rx() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 231/330] net: Remove preemption disabling in netif_rx() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz 1)enqueue_to_backlog() (called from netif_rx) should be bind to a particluar CPU. This can be achieved by @@ -39,7 +39,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/net/core/dev.c b/net/core/dev.c -index 2f63f20bbcc9..b91c2f0fa199 100644 +index c67056ad032b..528b89d2ff2e 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -4490,7 +4490,7 @@ static int netif_rx_internal(struct sk_buff *skb) diff --git a/debian/patches-rt/0232-net-Another-local_irq_disable-kmalloc-headache.patch b/debian/patches-rt/0232-net-Another-local_irq_disable-kmalloc-headache.patch index 9d59fe889..beb37640d 100644 --- a/debian/patches-rt/0232-net-Another-local_irq_disable-kmalloc-headache.patch +++ b/debian/patches-rt/0232-net-Another-local_irq_disable-kmalloc-headache.patch @@ -1,11 +1,11 @@ -From 9e95d16c6eca2cae1b0be05d59d1728d20f15f99 Mon Sep 17 00:00:00 2001 -Message-Id: <9e95d16c6eca2cae1b0be05d59d1728d20f15f99.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 7f6015ab5636b089f53f5f5a08c32988dc5fd639 Mon Sep 17 00:00:00 2001 +Message-Id: <7f6015ab5636b089f53f5f5a08c32988dc5fd639.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 26 Sep 2012 16:21:08 +0200 -Subject: [PATCH 232/327] net: Another local_irq_disable/kmalloc headache -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 232/330] net: Another local_irq_disable/kmalloc headache +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Replace it by a local lock. Though that's pretty inefficient :( diff --git a/debian/patches-rt/0233-net-core-protect-users-of-napi_alloc_cache-against-r.patch b/debian/patches-rt/0233-net-core-protect-users-of-napi_alloc_cache-against-r.patch index 700ef0b12..584329246 100644 --- a/debian/patches-rt/0233-net-core-protect-users-of-napi_alloc_cache-against-r.patch +++ b/debian/patches-rt/0233-net-core-protect-users-of-napi_alloc_cache-against-r.patch @@ -1,12 +1,12 @@ -From 0714e84287fbc26ba5cb809fd6a868a720ccd11a Mon Sep 17 00:00:00 2001 -Message-Id: <0714e84287fbc26ba5cb809fd6a868a720ccd11a.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 098879aa8b0108a02ec64bd7119542712b2fa703 Mon Sep 17 00:00:00 2001 +Message-Id: <098879aa8b0108a02ec64bd7119542712b2fa703.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 15 Jan 2016 16:33:34 +0100 -Subject: [PATCH 233/327] net/core: protect users of napi_alloc_cache against +Subject: [PATCH 233/330] net/core: protect users of napi_alloc_cache against reentrance -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz On -RT the code running in BH can not be moved to another CPU so CPU local variable remain local. However the code can be preempted diff --git a/debian/patches-rt/0234-net-netfilter-Serialize-xt_write_recseq-sections-on-.patch b/debian/patches-rt/0234-net-netfilter-Serialize-xt_write_recseq-sections-on-.patch index dd0594076..ddd7c0f0d 100644 --- a/debian/patches-rt/0234-net-netfilter-Serialize-xt_write_recseq-sections-on-.patch +++ b/debian/patches-rt/0234-net-netfilter-Serialize-xt_write_recseq-sections-on-.patch @@ -1,12 +1,12 @@ -From 905cd469f3bcc2395bb5732809f755de224115cf Mon Sep 17 00:00:00 2001 -Message-Id: <905cd469f3bcc2395bb5732809f755de224115cf.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8ba436ecb8ea603036e8da052e938ed2961430c9 Mon Sep 17 00:00:00 2001 +Message-Id: <8ba436ecb8ea603036e8da052e938ed2961430c9.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 28 Oct 2012 11:18:08 +0100 -Subject: [PATCH 234/327] net: netfilter: Serialize xt_write_recseq sections on +Subject: [PATCH 234/330] net: netfilter: Serialize xt_write_recseq sections on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The netfilter code relies only on the implicit semantics of local_bh_disable() for serializing wt_write_recseq sections. RT breaks diff --git a/debian/patches-rt/0235-net-Add-a-mutex-around-devnet_rename_seq.patch b/debian/patches-rt/0235-net-Add-a-mutex-around-devnet_rename_seq.patch index 4f1758829..589527466 100644 --- a/debian/patches-rt/0235-net-Add-a-mutex-around-devnet_rename_seq.patch +++ b/debian/patches-rt/0235-net-Add-a-mutex-around-devnet_rename_seq.patch @@ -1,11 +1,11 @@ -From 02c687a4d1b7748b9b8cdfd95abf2872b2cb084e Mon Sep 17 00:00:00 2001 -Message-Id: <02c687a4d1b7748b9b8cdfd95abf2872b2cb084e.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From ada1c576f528b64d47816a874a0bf71f0b70dff0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 20 Mar 2013 18:06:20 +0100 -Subject: [PATCH 235/327] net: Add a mutex around devnet_rename_seq -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 235/330] net: Add a mutex around devnet_rename_seq +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz On RT write_seqcount_begin() disables preemption and device_rename() allocates memory with GFP_KERNEL and grabs later the sysfs_mutex @@ -25,7 +25,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 20 insertions(+), 14 deletions(-) diff --git a/net/core/dev.c b/net/core/dev.c -index b91c2f0fa199..22ab7a06843f 100644 +index 528b89d2ff2e..a2a3625338d4 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -196,6 +196,7 @@ static unsigned int napi_gen_id = NR_CPUS; diff --git a/debian/patches-rt/0236-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch b/debian/patches-rt/0236-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch index 77e619823..c0406b2e8 100644 --- a/debian/patches-rt/0236-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch +++ b/debian/patches-rt/0236-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch @@ -1,12 +1,12 @@ -From 7086ff5392c51036e09d54ac38fd9f13a8bf0506 Mon Sep 17 00:00:00 2001 -Message-Id: <7086ff5392c51036e09d54ac38fd9f13a8bf0506.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 0e5b48162b7e08556fac58f2f57266b80225a350 Mon Sep 17 00:00:00 2001 +Message-Id: <0e5b48162b7e08556fac58f2f57266b80225a350.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Yong Zhang Date: Mon, 16 Apr 2012 15:01:56 +0800 -Subject: [PATCH 236/327] lockdep: selftest: Only do hardirq context test for +Subject: [PATCH 236/330] lockdep: selftest: Only do hardirq context test for raw spinlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz On -rt there is no softirq context any more and rwlock is sleepable, disable softirq context test and rwlock+irq test. diff --git a/debian/patches-rt/0237-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch b/debian/patches-rt/0237-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch index 910f2bfaf..64d27bce0 100644 --- a/debian/patches-rt/0237-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch +++ b/debian/patches-rt/0237-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch @@ -1,12 +1,12 @@ -From c167840f7faa2d918939f2619e681501021d114f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From b49bc8ef54b13139b11a9f706d2f86bef94dc46f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Josh Cartwright Date: Wed, 28 Jan 2015 13:08:45 -0600 -Subject: [PATCH 237/327] lockdep: selftest: fix warnings due to missing +Subject: [PATCH 237/330] lockdep: selftest: fix warnings due to missing PREEMPT_RT conditionals -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz "lockdep: Selftest: Only do hardirq context test for raw spinlock" disabled the execution of certain tests with PREEMPT_RT_FULL, but did diff --git a/debian/patches-rt/0238-sched-Add-support-for-lazy-preemption.patch b/debian/patches-rt/0238-sched-Add-support-for-lazy-preemption.patch index 065fdee9c..0395f7c71 100644 --- a/debian/patches-rt/0238-sched-Add-support-for-lazy-preemption.patch +++ b/debian/patches-rt/0238-sched-Add-support-for-lazy-preemption.patch @@ -1,11 +1,11 @@ -From 14b7a2aeae41497fb8ec2b74a80b28e37e9b0331 Mon Sep 17 00:00:00 2001 -Message-Id: <14b7a2aeae41497fb8ec2b74a80b28e37e9b0331.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 1d3aebe709090a4051617281d0f33634b8c0ca2e Mon Sep 17 00:00:00 2001 +Message-Id: <1d3aebe709090a4051617281d0f33634b8c0ca2e.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 26 Oct 2012 18:50:54 +0100 -Subject: [PATCH 238/327] sched: Add support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 238/330] sched: Add support for lazy preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz It has become an obsession to mitigate the determinism vs. throughput loss of RT. Looking at the mainline semantics of preemption points diff --git a/debian/patches-rt/0239-ftrace-Fix-trace-header-alignment.patch b/debian/patches-rt/0239-ftrace-Fix-trace-header-alignment.patch index 7df3699fe..6d5e4a369 100644 --- a/debian/patches-rt/0239-ftrace-Fix-trace-header-alignment.patch +++ b/debian/patches-rt/0239-ftrace-Fix-trace-header-alignment.patch @@ -1,11 +1,11 @@ -From 6f7b0145324b2ff2e8befc0699789fa47661bc64 Mon Sep 17 00:00:00 2001 -Message-Id: <6f7b0145324b2ff2e8befc0699789fa47661bc64.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From bc559bf8fbf52aeeaff6faa8a4b4d6ac0cc2da52 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 16 Oct 2016 05:08:30 +0200 -Subject: [PATCH 239/327] ftrace: Fix trace header alignment -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 239/330] ftrace: Fix trace header alignment +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Line up helper arrows to the right column. diff --git a/debian/patches-rt/0240-x86-Support-for-lazy-preemption.patch b/debian/patches-rt/0240-x86-Support-for-lazy-preemption.patch index 24224fb16..8407f0249 100644 --- a/debian/patches-rt/0240-x86-Support-for-lazy-preemption.patch +++ b/debian/patches-rt/0240-x86-Support-for-lazy-preemption.patch @@ -1,11 +1,11 @@ -From 8ffd8ce2e4fdce3b034fd1110d20d79a111d5147 Mon Sep 17 00:00:00 2001 -Message-Id: <8ffd8ce2e4fdce3b034fd1110d20d79a111d5147.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 4b671af47115b2d520a1ca6665cbf42f48621269 Mon Sep 17 00:00:00 2001 +Message-Id: <4b671af47115b2d520a1ca6665cbf42f48621269.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 1 Nov 2012 11:03:47 +0100 -Subject: [PATCH 240/327] x86: Support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 240/330] x86: Support for lazy preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Implement the x86 pieces for lazy preempt. diff --git a/debian/patches-rt/0241-x86-lazy-preempt-properly-check-against-preempt-mask.patch b/debian/patches-rt/0241-x86-lazy-preempt-properly-check-against-preempt-mask.patch index 5c2aa57c1..064396eef 100644 --- a/debian/patches-rt/0241-x86-lazy-preempt-properly-check-against-preempt-mask.patch +++ b/debian/patches-rt/0241-x86-lazy-preempt-properly-check-against-preempt-mask.patch @@ -1,12 +1,12 @@ -From 28db966bbcbd6f471714725cc71bf95ec46681f2 Mon Sep 17 00:00:00 2001 -Message-Id: <28db966bbcbd6f471714725cc71bf95ec46681f2.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From fdcecdbbef33371371b9cdb15ae6918af2b96978 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 18 Feb 2019 16:57:09 +0100 -Subject: [PATCH 241/327] x86: lazy-preempt: properly check against +Subject: [PATCH 241/330] x86: lazy-preempt: properly check against preempt-mask -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz should_resched() should check against preempt_offset after unmasking the need-resched-bit. Otherwise should_resched() won't work for diff --git a/debian/patches-rt/0242-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch b/debian/patches-rt/0242-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch index 70d69533c..3cacc2f7c 100644 --- a/debian/patches-rt/0242-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch +++ b/debian/patches-rt/0242-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch @@ -1,12 +1,12 @@ -From 5b93dc2de19b5d91cb4cdcd273f47ae61e48958b Mon Sep 17 00:00:00 2001 -Message-Id: <5b93dc2de19b5d91cb4cdcd273f47ae61e48958b.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5fd4eedd6c9f19c50a5d7ea66edc4a07bf3ddb32 Mon Sep 17 00:00:00 2001 +Message-Id: <5fd4eedd6c9f19c50a5d7ea66edc4a07bf3ddb32.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 14:53:49 +0100 -Subject: [PATCH 242/327] x86: lazy-preempt: use proper return label on +Subject: [PATCH 242/330] x86: lazy-preempt: use proper return label on 32bit-x86 -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The lazy-preempt uses the wrong return label in case preemption isn't possible. This results crash while returning to the kernel. diff --git a/debian/patches-rt/0243-arm-Add-support-for-lazy-preemption.patch b/debian/patches-rt/0243-arm-Add-support-for-lazy-preemption.patch index 5c7948599..b93ba2cfb 100644 --- a/debian/patches-rt/0243-arm-Add-support-for-lazy-preemption.patch +++ b/debian/patches-rt/0243-arm-Add-support-for-lazy-preemption.patch @@ -1,11 +1,11 @@ -From ef65750247e5e5b35efbaef6b363f3ded2d8cd06 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 6bfa6ae306b184b9a686976852d8503fdb364142 Mon Sep 17 00:00:00 2001 +Message-Id: <6bfa6ae306b184b9a686976852d8503fdb364142.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 31 Oct 2012 12:04:11 +0100 -Subject: [PATCH 243/327] arm: Add support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 243/330] arm: Add support for lazy preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Implement the arm pieces for lazy preempt. @@ -84,10 +84,10 @@ index 3968d6c22455..b35d373fc982 100644 DEFINE(TI_TASK, offsetof(struct thread_info, task)); DEFINE(TI_CPU, offsetof(struct thread_info, cpu)); diff --git a/arch/arm/kernel/entry-armv.S b/arch/arm/kernel/entry-armv.S -index e85a3af9ddeb..cc67c0a3ae7b 100644 +index 89e551eebff1..4fba92bcebfe 100644 --- a/arch/arm/kernel/entry-armv.S +++ b/arch/arm/kernel/entry-armv.S -@@ -216,11 +216,18 @@ __irq_svc: +@@ -209,11 +209,18 @@ __irq_svc: #ifdef CONFIG_PREEMPT ldr r8, [tsk, #TI_PREEMPT] @ get preempt count @@ -108,7 +108,7 @@ index e85a3af9ddeb..cc67c0a3ae7b 100644 #endif svc_exit r5, irq = 1 @ return from exception -@@ -235,8 +242,14 @@ svc_preempt: +@@ -228,8 +235,14 @@ svc_preempt: 1: bl preempt_schedule_irq @ irq en/disable is done inside ldr r0, [tsk, #TI_FLAGS] @ get new tasks TI_FLAGS tst r0, #_TIF_NEED_RESCHED diff --git a/debian/patches-rt/0244-powerpc-Add-support-for-lazy-preemption.patch b/debian/patches-rt/0244-powerpc-Add-support-for-lazy-preemption.patch index c3fafe698..4c2ff3d39 100644 --- a/debian/patches-rt/0244-powerpc-Add-support-for-lazy-preemption.patch +++ b/debian/patches-rt/0244-powerpc-Add-support-for-lazy-preemption.patch @@ -1,11 +1,11 @@ -From 2d3d51cd68f10a3f7fa8b23078ba24e2ee882c7f Mon Sep 17 00:00:00 2001 -Message-Id: <2d3d51cd68f10a3f7fa8b23078ba24e2ee882c7f.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5d9b43bc809a72f178b8cd1dc9d63c7ebd97bc77 Mon Sep 17 00:00:00 2001 +Message-Id: <5d9b43bc809a72f178b8cd1dc9d63c7ebd97bc77.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 1 Nov 2012 10:14:11 +0100 -Subject: [PATCH 244/327] powerpc: Add support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 244/330] powerpc: Add support for lazy preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Implement the powerpc pieces for lazy preempt. @@ -19,7 +19,7 @@ Signed-off-by: Thomas Gleixner 5 files changed, 33 insertions(+), 11 deletions(-) diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig -index 1b332f69dd36..c8c2230c8aff 100644 +index 8455293d1435..dbf8cb62e77b 100644 --- a/arch/powerpc/Kconfig +++ b/arch/powerpc/Kconfig @@ -216,6 +216,7 @@ config PPC diff --git a/debian/patches-rt/0245-arch-arm64-Add-lazy-preempt-support.patch b/debian/patches-rt/0245-arch-arm64-Add-lazy-preempt-support.patch index 8c2762663..a2b4be6a1 100644 --- a/debian/patches-rt/0245-arch-arm64-Add-lazy-preempt-support.patch +++ b/debian/patches-rt/0245-arch-arm64-Add-lazy-preempt-support.patch @@ -1,11 +1,11 @@ -From 63caeb2e285bf04f0c7222ca6f15fee4084a1782 Mon Sep 17 00:00:00 2001 -Message-Id: <63caeb2e285bf04f0c7222ca6f15fee4084a1782.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 96e3ced3dbd7022ebe4b722d30e6c57394820cc3 Mon Sep 17 00:00:00 2001 +Message-Id: <96e3ced3dbd7022ebe4b722d30e6c57394820cc3.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Anders Roxell Date: Thu, 14 May 2015 17:52:17 +0200 -Subject: [PATCH 245/327] arch/arm64: Add lazy preempt support -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 245/330] arch/arm64: Add lazy preempt support +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz arm64 is missing support for PREEMPT_RT. The main feature which is lacking is support for lazy preemption. The arch-specific entry code, diff --git a/debian/patches-rt/0246-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch b/debian/patches-rt/0246-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch index d575659ff..f3c605750 100644 --- a/debian/patches-rt/0246-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch +++ b/debian/patches-rt/0246-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch @@ -1,12 +1,12 @@ -From 10c182904200fddea7eb60d9a9bf40cbe7cd0809 Mon Sep 17 00:00:00 2001 -Message-Id: <10c182904200fddea7eb60d9a9bf40cbe7cd0809.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 3ee2327f0664af523a61428effbd062295f25e20 Mon Sep 17 00:00:00 2001 +Message-Id: <3ee2327f0664af523a61428effbd062295f25e20.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 16 Oct 2016 05:11:54 +0200 -Subject: [PATCH 246/327] connector/cn_proc: Protect send_msg() with a local +Subject: [PATCH 246/330] connector/cn_proc: Protect send_msg() with a local lock on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:931 |in_atomic(): 1, irqs_disabled(): 0, pid: 31807, name: sleep diff --git a/debian/patches-rt/0247-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch b/debian/patches-rt/0247-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch index b0baac1bf..6f0f4cdfc 100644 --- a/debian/patches-rt/0247-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch +++ b/debian/patches-rt/0247-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch @@ -1,12 +1,12 @@ -From 266f976dcab9b08f3ab88c92aaee9aca5a8eeb83 Mon Sep 17 00:00:00 2001 -Message-Id: <266f976dcab9b08f3ab88c92aaee9aca5a8eeb83.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From bde23f0fd8dced4d464e85e5509b5d5858bddf51 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Mike Galbraith Date: Thu, 31 Mar 2016 04:08:28 +0200 -Subject: [PATCH 247/327] drivers/block/zram: Replace bit spinlocks with +Subject: [PATCH 247/330] drivers/block/zram: Replace bit spinlocks with rtmutex for -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz They're nondeterministic, and lead to ___might_sleep() splats in -rt. OTOH, they're a lot less wasteful than an rtmutex per page. diff --git a/debian/patches-rt/0248-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch b/debian/patches-rt/0248-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch index bb437c12b..2cd37f7f1 100644 --- a/debian/patches-rt/0248-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch +++ b/debian/patches-rt/0248-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch @@ -1,12 +1,12 @@ -From 4a3ea230992860aec5d15c038bc96698b1a6bbfd Mon Sep 17 00:00:00 2001 -Message-Id: <4a3ea230992860aec5d15c038bc96698b1a6bbfd.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 2bc0a885483d450bb6a887953c0be7c9eee779d2 Mon Sep 17 00:00:00 2001 +Message-Id: <2bc0a885483d450bb6a887953c0be7c9eee779d2.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Mike Galbraith Date: Thu, 20 Oct 2016 11:15:22 +0200 -Subject: [PATCH 248/327] drivers/zram: Don't disable preemption in +Subject: [PATCH 248/330] drivers/zram: Don't disable preemption in zcomp_stream_get/put() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz In v4.7, the driver switched to percpu compression streams, disabling preemption via get/put_cpu_ptr(). Use a per-zcomp_strm lock here. We diff --git a/debian/patches-rt/0249-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch b/debian/patches-rt/0249-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch index 68cefbd86..b8657df19 100644 --- a/debian/patches-rt/0249-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch +++ b/debian/patches-rt/0249-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch @@ -1,12 +1,12 @@ -From 5ca50cf96a16b54bfb3e9813499a959c46932906 Mon Sep 17 00:00:00 2001 -Message-Id: <5ca50cf96a16b54bfb3e9813499a959c46932906.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 4cdcaa5f91b01d5ed1e71b1ac82067edaa42f1da Mon Sep 17 00:00:00 2001 +Message-Id: <4cdcaa5f91b01d5ed1e71b1ac82067edaa42f1da.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 23 Aug 2017 11:57:29 +0200 -Subject: [PATCH 249/327] drivers/zram: fix zcomp_stream_get() +Subject: [PATCH 249/330] drivers/zram: fix zcomp_stream_get() smp_processor_id() use in preemptible code -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Use get_local_ptr() instead this_cpu_ptr() to avoid a warning regarding smp_processor_id() in preemptible code. diff --git a/debian/patches-rt/0250-tpm_tis-fix-stall-after-iowrite-s.patch b/debian/patches-rt/0250-tpm_tis-fix-stall-after-iowrite-s.patch index de5a5b300..1190e40b0 100644 --- a/debian/patches-rt/0250-tpm_tis-fix-stall-after-iowrite-s.patch +++ b/debian/patches-rt/0250-tpm_tis-fix-stall-after-iowrite-s.patch @@ -1,11 +1,11 @@ -From 120c84d752e389cd4f4d7985e4164749e4dee6a7 Mon Sep 17 00:00:00 2001 -Message-Id: <120c84d752e389cd4f4d7985e4164749e4dee6a7.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d334dbe65f86ee654d0653c61bd2c5e5e3426d6a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Haris Okanovic Date: Tue, 15 Aug 2017 15:13:08 -0500 -Subject: [PATCH 250/327] tpm_tis: fix stall after iowrite*()s -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 250/330] tpm_tis: fix stall after iowrite*()s +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz ioread8() operations to TPM MMIO addresses can stall the cpu when immediately following a sequence of iowrite*()'s to the same region. diff --git a/debian/patches-rt/0251-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch b/debian/patches-rt/0251-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch index fe0071224..93f426898 100644 --- a/debian/patches-rt/0251-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch +++ b/debian/patches-rt/0251-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch @@ -1,11 +1,11 @@ -From fd381309b3c6198a5c343b637c1ef318923832e6 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From da11a4140d575b4486113ea80a344c2f10526634 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Julia Cartwright Date: Fri, 28 Sep 2018 21:03:51 +0000 -Subject: [PATCH 251/327] watchdog: prevent deferral of watchdogd wakeup on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 251/330] watchdog: prevent deferral of watchdogd wakeup on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz When PREEMPT_RT_FULL is enabled, all hrtimer expiry functions are deferred for execution into the context of ktimersoftd unless otherwise diff --git a/debian/patches-rt/0252-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch b/debian/patches-rt/0252-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch index ed8400f94..023e91eb3 100644 --- a/debian/patches-rt/0252-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch +++ b/debian/patches-rt/0252-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch @@ -1,12 +1,12 @@ -From 709075783ebbaf04e76aeacb295595fbd9b2dba1 Mon Sep 17 00:00:00 2001 -Message-Id: <709075783ebbaf04e76aeacb295595fbd9b2dba1.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 137193a9e29aab337a25b34884ee028e00b4ffff Mon Sep 17 00:00:00 2001 +Message-Id: <137193a9e29aab337a25b34884ee028e00b4ffff.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Mike Galbraith Date: Sat, 27 Feb 2016 08:09:11 +0100 -Subject: [PATCH 252/327] drm,radeon,i915: Use preempt_disable/enable_rt() +Subject: [PATCH 252/330] drm,radeon,i915: Use preempt_disable/enable_rt() where recommended -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz DRM folks identified the spots, so use them. diff --git a/debian/patches-rt/0253-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch b/debian/patches-rt/0253-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch index 08cf0eb58..fa278966d 100644 --- a/debian/patches-rt/0253-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch +++ b/debian/patches-rt/0253-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch @@ -1,12 +1,12 @@ -From ebe8850346724e0fd4c7c055490d6304d7777394 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From ad9a22a28b78660154ae7153813ea337679a4f13 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Mike Galbraith Date: Sat, 27 Feb 2016 09:01:42 +0100 -Subject: [PATCH 253/327] drm,i915: Use local_lock/unlock_irq() in +Subject: [PATCH 253/330] drm,i915: Use local_lock/unlock_irq() in intel_pipe_update_start/end() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ 8.014039] BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:918 [ 8.014041] in_atomic(): 0, irqs_disabled(): 1, pid: 78, name: kworker/u4:4 diff --git a/debian/patches-rt/0254-drm-i915-disable-tracing-on-RT.patch b/debian/patches-rt/0254-drm-i915-disable-tracing-on-RT.patch index 71c664346..99f48c5b6 100644 --- a/debian/patches-rt/0254-drm-i915-disable-tracing-on-RT.patch +++ b/debian/patches-rt/0254-drm-i915-disable-tracing-on-RT.patch @@ -1,11 +1,11 @@ -From f5ca5efcce88651570b363c9a5b119ef30fea777 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 87a5e8b4b0f251c4d0a8a67b82198016c1b6ca54 Mon Sep 17 00:00:00 2001 +Message-Id: <87a5e8b4b0f251c4d0a8a67b82198016c1b6ca54.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 6 Dec 2018 09:52:20 +0100 -Subject: [PATCH 254/327] drm/i915: disable tracing on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 254/330] drm/i915: disable tracing on -RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Luca Abeni reported this: | BUG: scheduling while atomic: kworker/u8:2/15203/0x00000003 diff --git a/debian/patches-rt/0255-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch b/debian/patches-rt/0255-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch index 75ccf7370..0acf90dea 100644 --- a/debian/patches-rt/0255-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch +++ b/debian/patches-rt/0255-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch @@ -1,12 +1,12 @@ -From 22fff76c44cac090d4d082f12c75add9c126133b Mon Sep 17 00:00:00 2001 -Message-Id: <22fff76c44cac090d4d082f12c75add9c126133b.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From ed2b80308dad5ff63222215fb548a977e5dacc69 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 19 Dec 2018 10:47:02 +0100 -Subject: [PATCH 255/327] drm/i915: skip DRM_I915_LOW_LEVEL_TRACEPOINTS with +Subject: [PATCH 255/330] drm/i915: skip DRM_I915_LOW_LEVEL_TRACEPOINTS with NOTRACE -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The order of the header files is important. If this header file is included after tracepoint.h was included then the NOTRACE here becomes a diff --git a/debian/patches-rt/0256-cgroups-use-simple-wait-in-css_release.patch b/debian/patches-rt/0256-cgroups-use-simple-wait-in-css_release.patch index 7ab28d794..ecb244fe6 100644 --- a/debian/patches-rt/0256-cgroups-use-simple-wait-in-css_release.patch +++ b/debian/patches-rt/0256-cgroups-use-simple-wait-in-css_release.patch @@ -1,11 +1,11 @@ -From 0eb7830f7576277448609d9fd4118b3a87d4b064 Mon Sep 17 00:00:00 2001 -Message-Id: <0eb7830f7576277448609d9fd4118b3a87d4b064.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5036ae1296cc6936c2cb686f902b272dcd74c3e0 Mon Sep 17 00:00:00 2001 +Message-Id: <5036ae1296cc6936c2cb686f902b272dcd74c3e0.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 13 Feb 2015 15:52:24 +0100 -Subject: [PATCH 256/327] cgroups: use simple wait in css_release() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 256/330] cgroups: use simple wait in css_release() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz To avoid: |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:914 diff --git a/debian/patches-rt/0257-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch b/debian/patches-rt/0257-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch index e0b48d595..e104ac52e 100644 --- a/debian/patches-rt/0257-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch +++ b/debian/patches-rt/0257-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch @@ -1,11 +1,11 @@ -From 891ff86c8b8d37f55d4a76f3318c7cc09e85480a Mon Sep 17 00:00:00 2001 -Message-Id: <891ff86c8b8d37f55d4a76f3318c7cc09e85480a.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8564b96e7c4c3afd51a3d4f4f84f54b55c238245 Mon Sep 17 00:00:00 2001 +Message-Id: <8564b96e7c4c3afd51a3d4f4f84f54b55c238245.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 8 Jan 2017 09:32:25 +0100 -Subject: [PATCH 257/327] cpuset: Convert callback_lock to raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 257/330] cpuset: Convert callback_lock to raw_spinlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The two commits below add up to a cpuset might_sleep() splat for RT: diff --git a/debian/patches-rt/0258-apparmor-use-a-locallock-instead-preempt_disable.patch b/debian/patches-rt/0258-apparmor-use-a-locallock-instead-preempt_disable.patch index 90fe8be9b..4c18e20ed 100644 --- a/debian/patches-rt/0258-apparmor-use-a-locallock-instead-preempt_disable.patch +++ b/debian/patches-rt/0258-apparmor-use-a-locallock-instead-preempt_disable.patch @@ -1,11 +1,11 @@ -From a945ff9968dc70c8763665b205b4f3dce6958d57 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 0d8d113a16a89c356895a373f5ff9a4ada819248 Mon Sep 17 00:00:00 2001 +Message-Id: <0d8d113a16a89c356895a373f5ff9a4ada819248.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 11 Oct 2017 17:43:49 +0200 -Subject: [PATCH 258/327] apparmor: use a locallock instead preempt_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 258/330] apparmor: use a locallock instead preempt_disable() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz get_buffers() disables preemption which acts as a lock for the per-CPU variable. Since we can't disable preemption here on RT, a local_lock is diff --git a/debian/patches-rt/0259-workqueue-Prevent-deadlock-stall-on-RT.patch b/debian/patches-rt/0259-workqueue-Prevent-deadlock-stall-on-RT.patch index 7cf20200a..080f172f6 100644 --- a/debian/patches-rt/0259-workqueue-Prevent-deadlock-stall-on-RT.patch +++ b/debian/patches-rt/0259-workqueue-Prevent-deadlock-stall-on-RT.patch @@ -1,11 +1,11 @@ -From eb5315fca9e129bdc6a02bcc7ce92fe09a688e69 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 3f8e7374498092be66a247e893cda1001a29ee1a Mon Sep 17 00:00:00 2001 +Message-Id: <3f8e7374498092be66a247e893cda1001a29ee1a.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 27 Jun 2014 16:24:52 +0200 -Subject: [PATCH 259/327] workqueue: Prevent deadlock/stall on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 259/330] workqueue: Prevent deadlock/stall on RT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Austin reported a XFS deadlock/stall on RT where scheduled work gets never exececuted and tasks are waiting for each other for ever. diff --git a/debian/patches-rt/0260-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch b/debian/patches-rt/0260-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch index 982e8a97a..11a307018 100644 --- a/debian/patches-rt/0260-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch +++ b/debian/patches-rt/0260-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch @@ -1,11 +1,11 @@ -From c60c943eb50e14a7094ed2662541730655c6429e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8a6f6e3539a8ae5e6455004a233dbbd7e6cbf6d2 Mon Sep 17 00:00:00 2001 +Message-Id: <8a6f6e3539a8ae5e6455004a233dbbd7e6cbf6d2.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 3 Jul 2009 08:44:56 -0500 -Subject: [PATCH 260/327] signals: Allow rt tasks to cache one sigqueue struct -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 260/330] signals: Allow rt tasks to cache one sigqueue struct +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz To avoid allocation allow rt tasks to cache one sigqueue struct in task struct. diff --git a/debian/patches-rt/0261-Add-localversion-for-RT-release.patch b/debian/patches-rt/0261-Add-localversion-for-RT-release.patch index 980f4d7cd..1777f54ba 100644 --- a/debian/patches-rt/0261-Add-localversion-for-RT-release.patch +++ b/debian/patches-rt/0261-Add-localversion-for-RT-release.patch @@ -1,11 +1,11 @@ -From e0cc9c6c3ecac665018d274071b37112bbd61ce2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From b9e5fdc337addc5c3b49658c7804fc67081ee4a9 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 8 Jul 2011 20:25:16 +0200 -Subject: [PATCH 261/327] Add localversion for -RT release -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 261/330] Add localversion for -RT release +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Signed-off-by: Thomas Gleixner --- diff --git a/debian/patches-rt/0262-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch b/debian/patches-rt/0262-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch index caea6978a..88ad44414 100644 --- a/debian/patches-rt/0262-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch +++ b/debian/patches-rt/0262-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch @@ -1,12 +1,12 @@ -From 1373005cb6e8ba51cf3a46846e18a9e980288996 Mon Sep 17 00:00:00 2001 -Message-Id: <1373005cb6e8ba51cf3a46846e18a9e980288996.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 8a21a4074affa0eb2be5aa587d7766a00e7605b5 Mon Sep 17 00:00:00 2001 +Message-Id: <8a21a4074affa0eb2be5aa587d7766a00e7605b5.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Mar 2019 18:31:54 +0100 -Subject: [PATCH 262/327] powerpc/pseries/iommu: Use a locallock instead +Subject: [PATCH 262/330] powerpc/pseries/iommu: Use a locallock instead local_irq_save() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The locallock protects the per-CPU variable tce_page. The function attempts to allocate memory while tce_page is protected (by disabling diff --git a/debian/patches-rt/0263-powerpc-reshuffle-TIF-bits.patch b/debian/patches-rt/0263-powerpc-reshuffle-TIF-bits.patch index f29dfa019..82dfa5f97 100644 --- a/debian/patches-rt/0263-powerpc-reshuffle-TIF-bits.patch +++ b/debian/patches-rt/0263-powerpc-reshuffle-TIF-bits.patch @@ -1,11 +1,11 @@ -From 5c6e98bc5261d48723ae47dd72081af204d42917 Mon Sep 17 00:00:00 2001 -Message-Id: <5c6e98bc5261d48723ae47dd72081af204d42917.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 7ab06e1f695ee73b1bfe354ed23c5082df34daf6 Mon Sep 17 00:00:00 2001 +Message-Id: <7ab06e1f695ee73b1bfe354ed23c5082df34daf6.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 22 Mar 2019 17:15:58 +0100 -Subject: [PATCH 263/327] powerpc: reshuffle TIF bits -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 263/330] powerpc: reshuffle TIF bits +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Powerpc32/64 does not compile because TIF_SYSCALL_TRACE's bit is higher than 15 and the assembly instructions don't expect that. diff --git a/debian/patches-rt/0264-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch b/debian/patches-rt/0264-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch index b854ccb6c..28df5649a 100644 --- a/debian/patches-rt/0264-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch +++ b/debian/patches-rt/0264-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch @@ -1,11 +1,11 @@ -From 0ab19e6d4443d706278cc9271789e9a182fa6be3 Mon Sep 17 00:00:00 2001 -Message-Id: <0ab19e6d4443d706278cc9271789e9a182fa6be3.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From daa9e1b6dcd7026c46a10816dc421bf7fab18bb5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 13 Mar 2019 11:40:34 +0000 -Subject: [PATCH 264/327] tty/sysrq: Convert show_lock to raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 264/330] tty/sysrq: Convert show_lock to raw_spinlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Systems which don't provide arch_trigger_cpumask_backtrace() will invoke showacpu() from a smp_call_function() function which is invoked diff --git a/debian/patches-rt/0265-drm-i915-Don-t-disable-interrupts-independently-of-t.patch b/debian/patches-rt/0265-drm-i915-Don-t-disable-interrupts-independently-of-t.patch index 4ee1a0f60..ff0ea6c0a 100644 --- a/debian/patches-rt/0265-drm-i915-Don-t-disable-interrupts-independently-of-t.patch +++ b/debian/patches-rt/0265-drm-i915-Don-t-disable-interrupts-independently-of-t.patch @@ -1,12 +1,12 @@ -From 6800816b2516e527e89468b7a90475f09152314c Mon Sep 17 00:00:00 2001 -Message-Id: <6800816b2516e527e89468b7a90475f09152314c.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From aab06248c5ebc69cebfb4034783e82cd3bcb583c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 10 Apr 2019 11:01:37 +0200 -Subject: [PATCH 265/327] drm/i915: Don't disable interrupts independently of +Subject: [PATCH 265/330] drm/i915: Don't disable interrupts independently of the lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The locks (timeline->lock and rq->lock) need to be taken with disabled interrupts. This is done in __retire_engine_request() by disabling the diff --git a/debian/patches-rt/0266-sched-completion-Fix-a-lockup-in-wait_for_completion.patch b/debian/patches-rt/0266-sched-completion-Fix-a-lockup-in-wait_for_completion.patch index e1be868cb..287e44068 100644 --- a/debian/patches-rt/0266-sched-completion-Fix-a-lockup-in-wait_for_completion.patch +++ b/debian/patches-rt/0266-sched-completion-Fix-a-lockup-in-wait_for_completion.patch @@ -1,12 +1,12 @@ -From 1f9cd057c9185fd9e5528565d89282447cec84a2 Mon Sep 17 00:00:00 2001 -Message-Id: <1f9cd057c9185fd9e5528565d89282447cec84a2.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5b5332b66ab73ff8f749772e6932cd1597bc1919 Mon Sep 17 00:00:00 2001 +Message-Id: <5b5332b66ab73ff8f749772e6932cd1597bc1919.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Corey Minyard Date: Thu, 9 May 2019 14:33:20 -0500 -Subject: [PATCH 266/327] sched/completion: Fix a lockup in +Subject: [PATCH 266/330] sched/completion: Fix a lockup in wait_for_completion() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Consider following race: diff --git a/debian/patches-rt/0267-kthread-add-a-global-worker-thread.patch b/debian/patches-rt/0267-kthread-add-a-global-worker-thread.patch index 8c4c1a847..9fdcdd2d8 100644 --- a/debian/patches-rt/0267-kthread-add-a-global-worker-thread.patch +++ b/debian/patches-rt/0267-kthread-add-a-global-worker-thread.patch @@ -1,11 +1,11 @@ -From 2d0cb06fc789ff1b383d8f97b43fac629dd39e47 Mon Sep 17 00:00:00 2001 -Message-Id: <2d0cb06fc789ff1b383d8f97b43fac629dd39e47.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From cb3a32333406ad52b02055815dfe396f2676bfe8 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 12 Feb 2019 15:09:38 +0100 -Subject: [PATCH 267/327] kthread: add a global worker thread. -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 267/330] kthread: add a global worker thread. +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 0532e87d9d44795221aa921ba7024bde689cc894 ] diff --git a/debian/patches-rt/0268-arm-imx6-cpuidle-Use-raw_spinlock_t.patch b/debian/patches-rt/0268-arm-imx6-cpuidle-Use-raw_spinlock_t.patch index 031824db5..af47c3c8e 100644 --- a/debian/patches-rt/0268-arm-imx6-cpuidle-Use-raw_spinlock_t.patch +++ b/debian/patches-rt/0268-arm-imx6-cpuidle-Use-raw_spinlock_t.patch @@ -1,11 +1,11 @@ -From 43074e5990b3dcd7e776f083ed0323c29a6890d8 Mon Sep 17 00:00:00 2001 -Message-Id: <43074e5990b3dcd7e776f083ed0323c29a6890d8.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 58fe9b05e086a9b62bc81814a545291426c64262 Mon Sep 17 00:00:00 2001 +Message-Id: <58fe9b05e086a9b62bc81814a545291426c64262.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 14 May 2019 17:07:44 +0200 -Subject: [PATCH 268/327] arm: imx6: cpuidle: Use raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 268/330] arm: imx6: cpuidle: Use raw_spinlock_t +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 40d0332ec8312e9c090f0a5414d9c90e12b13611 ] diff --git a/debian/patches-rt/0269-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch b/debian/patches-rt/0269-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch index 14f381a87..6f9af42ca 100644 --- a/debian/patches-rt/0269-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch +++ b/debian/patches-rt/0269-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch @@ -1,12 +1,12 @@ -From 9bcc6dc6d660c95fccb68afd7d8f10e99cfb2b7c Mon Sep 17 00:00:00 2001 -Message-Id: <9bcc6dc6d660c95fccb68afd7d8f10e99cfb2b7c.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 1e9114e34389619347eecc362b72d28efdf53b1a Mon Sep 17 00:00:00 2001 +Message-Id: <1e9114e34389619347eecc362b72d28efdf53b1a.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 18:29:13 +0200 -Subject: [PATCH 269/327] rcu: Don't allow to change rcu_normal_after_boot on +Subject: [PATCH 269/330] rcu: Don't allow to change rcu_normal_after_boot on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit c6c058c10577815a2491ce661876cff00a4c3b15 ] diff --git a/debian/patches-rt/0270-pci-switchtec-fix-stream_open.cocci-warnings.patch b/debian/patches-rt/0270-pci-switchtec-fix-stream_open.cocci-warnings.patch index 249c58ec0..8ab0ee6f6 100644 --- a/debian/patches-rt/0270-pci-switchtec-fix-stream_open.cocci-warnings.patch +++ b/debian/patches-rt/0270-pci-switchtec-fix-stream_open.cocci-warnings.patch @@ -1,11 +1,11 @@ -From 00646185d868e54b469ceac1ecca54fce34f8342 Mon Sep 17 00:00:00 2001 -Message-Id: <00646185d868e54b469ceac1ecca54fce34f8342.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From c68ac93ed423e121095839f7e136c768b4699d43 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: kbuild test robot Date: Sat, 13 Apr 2019 11:22:51 +0800 -Subject: [PATCH 270/327] pci/switchtec: fix stream_open.cocci warnings -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 270/330] pci/switchtec: fix stream_open.cocci warnings +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 9462c69e29307adc95c289f50839d5d683973891 ] diff --git a/debian/patches-rt/0271-sched-core-Drop-a-preempt_disable_rt-statement.patch b/debian/patches-rt/0271-sched-core-Drop-a-preempt_disable_rt-statement.patch index 1cdd323c4..f06c1b5b1 100644 --- a/debian/patches-rt/0271-sched-core-Drop-a-preempt_disable_rt-statement.patch +++ b/debian/patches-rt/0271-sched-core-Drop-a-preempt_disable_rt-statement.patch @@ -1,11 +1,11 @@ -From 860a02cef702995886aa9d05feeba75860128d16 Mon Sep 17 00:00:00 2001 -Message-Id: <860a02cef702995886aa9d05feeba75860128d16.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5b4d2d85f418c86a8cc12f7a59dbf13f9d0085da Mon Sep 17 00:00:00 2001 +Message-Id: <5b4d2d85f418c86a8cc12f7a59dbf13f9d0085da.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 19:33:16 +0200 -Subject: [PATCH 271/327] sched/core: Drop a preempt_disable_rt() statement -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 271/330] sched/core: Drop a preempt_disable_rt() statement +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 761126efdcbe3fa3e99c9079fa0ad6eca2f251f2 ] diff --git a/debian/patches-rt/0272-timers-Redo-the-notification-of-canceling-timers-on-.patch b/debian/patches-rt/0272-timers-Redo-the-notification-of-canceling-timers-on-.patch index a5ded6aa8..1fa081131 100644 --- a/debian/patches-rt/0272-timers-Redo-the-notification-of-canceling-timers-on-.patch +++ b/debian/patches-rt/0272-timers-Redo-the-notification-of-canceling-timers-on-.patch @@ -1,12 +1,12 @@ -From e87f4f8c1800acd083f29d276187f39bda1a6b3c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From fd3fade471b409c16306174c905526d89bbcda7c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 19:39:06 +0200 -Subject: [PATCH 272/327] timers: Redo the notification of canceling timers on +Subject: [PATCH 272/330] timers: Redo the notification of canceling timers on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit c71273154c2ad12e13333aada340ff30e826a11b ] diff --git a/debian/patches-rt/0273-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch b/debian/patches-rt/0273-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch index c6aa01398..b908e264e 100644 --- a/debian/patches-rt/0273-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch +++ b/debian/patches-rt/0273-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch @@ -1,12 +1,12 @@ -From 2873b4166d424a4d44753b9a34a20ab2924c1e0a Mon Sep 17 00:00:00 2001 -Message-Id: <2873b4166d424a4d44753b9a34a20ab2924c1e0a.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 3036d52feed97ae1dc6496ffc6e96d3bdf68c2dd Mon Sep 17 00:00:00 2001 +Message-Id: <3036d52feed97ae1dc6496ffc6e96d3bdf68c2dd.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:13 +0200 -Subject: [PATCH 273/327] Revert "futex: Ensure lock/unlock symetry versus +Subject: [PATCH 273/330] Revert "futex: Ensure lock/unlock symetry versus pi_lock and hash bucket lock" -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 6a773b70cf105b46298ed3b44e77c102ce31d9ec ] diff --git a/debian/patches-rt/0274-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch b/debian/patches-rt/0274-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch index 5f5c32ea5..cbccd0181 100644 --- a/debian/patches-rt/0274-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch +++ b/debian/patches-rt/0274-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch @@ -1,12 +1,12 @@ -From 50f14b1792b5a5700cd53746d9ea6615fbea610c Mon Sep 17 00:00:00 2001 -Message-Id: <50f14b1792b5a5700cd53746d9ea6615fbea610c.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 1dba455f84fb97d18a94e6115a8569a81a63d396 Mon Sep 17 00:00:00 2001 +Message-Id: <1dba455f84fb97d18a94e6115a8569a81a63d396.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:18 +0200 -Subject: [PATCH 274/327] Revert "futex: Fix bug on when a requeued RT task +Subject: [PATCH 274/330] Revert "futex: Fix bug on when a requeued RT task times out" -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit f1a170cb3289a48df26cae3c60d77608f7a988bb ] diff --git a/debian/patches-rt/0275-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch b/debian/patches-rt/0275-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch index 0bffdf848..1ce803ec8 100644 --- a/debian/patches-rt/0275-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch +++ b/debian/patches-rt/0275-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch @@ -1,12 +1,12 @@ -From a91167a3a3b8adccadd699c454fe81bcc1e860df Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 0fc7b125aa031c61c4ef8f772ab3b0c8ad568240 Mon Sep 17 00:00:00 2001 +Message-Id: <0fc7b125aa031c61c4ef8f772ab3b0c8ad568240.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:21 +0200 -Subject: [PATCH 275/327] Revert "rtmutex: Handle the various new futex race +Subject: [PATCH 275/330] Revert "rtmutex: Handle the various new futex race conditions" -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 9e0265c21af4d6388d47dcd5ce20f76ec3a2e468 ] diff --git a/debian/patches-rt/0276-Revert-futex-workaround-migrate_disable-enable-in-di.patch b/debian/patches-rt/0276-Revert-futex-workaround-migrate_disable-enable-in-di.patch index 40ad7c074..3b397149c 100644 --- a/debian/patches-rt/0276-Revert-futex-workaround-migrate_disable-enable-in-di.patch +++ b/debian/patches-rt/0276-Revert-futex-workaround-migrate_disable-enable-in-di.patch @@ -1,12 +1,12 @@ -From bb567bea0cb72e8ecf05950cffa6ac867e03a97a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From c144f30bad7b8830004837edaaefc0a343ce2e6a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:27 +0200 -Subject: [PATCH 276/327] Revert "futex: workaround migrate_disable/enable in +Subject: [PATCH 276/330] Revert "futex: workaround migrate_disable/enable in different context" -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit a71221d81cc4873891ae44f3aa02df596079b786 ] diff --git a/debian/patches-rt/0277-futex-Make-the-futex_hash_bucket-lock-raw.patch b/debian/patches-rt/0277-futex-Make-the-futex_hash_bucket-lock-raw.patch index 65f468f7b..ee4ffdeec 100644 --- a/debian/patches-rt/0277-futex-Make-the-futex_hash_bucket-lock-raw.patch +++ b/debian/patches-rt/0277-futex-Make-the-futex_hash_bucket-lock-raw.patch @@ -1,11 +1,11 @@ -From 235aa6d27cc3c405332320102faa240f176eb0ac Mon Sep 17 00:00:00 2001 -Message-Id: <235aa6d27cc3c405332320102faa240f176eb0ac.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 483572bcc0a470f60955deb2a9536df74a4cd177 Mon Sep 17 00:00:00 2001 +Message-Id: <483572bcc0a470f60955deb2a9536df74a4cd177.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 11:59:44 +0200 -Subject: [PATCH 277/327] futex: Make the futex_hash_bucket lock raw -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 277/330] futex: Make the futex_hash_bucket lock raw +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit f646521aadedab78801c9befe193e2e8a0c99298 ] diff --git a/debian/patches-rt/0278-futex-Delay-deallocation-of-pi_state.patch b/debian/patches-rt/0278-futex-Delay-deallocation-of-pi_state.patch index 7aad7ea16..32f55706a 100644 --- a/debian/patches-rt/0278-futex-Delay-deallocation-of-pi_state.patch +++ b/debian/patches-rt/0278-futex-Delay-deallocation-of-pi_state.patch @@ -1,11 +1,11 @@ -From deb0a4358fdd2bfb715f111615cd289690478677 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d3c2b2ffe7e4deb822dcba767a1a380bc34010c5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 26 Jun 2019 13:35:36 +0200 -Subject: [PATCH 278/327] futex: Delay deallocation of pi_state -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 278/330] futex: Delay deallocation of pi_state +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit d7c7cf8cb68b7df17e6e50be1f25f35d83e686c7 ] diff --git a/debian/patches-rt/0279-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch b/debian/patches-rt/0279-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch index 63ab842d0..33a30bbaa 100644 --- a/debian/patches-rt/0279-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch +++ b/debian/patches-rt/0279-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch @@ -1,12 +1,12 @@ -From 82b889d961c4553d3101bf171d14754810644129 Mon Sep 17 00:00:00 2001 -Message-Id: <82b889d961c4553d3101bf171d14754810644129.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 78df42872fccc85b692b2af42413e7c1a1bdf656 Mon Sep 17 00:00:00 2001 +Message-Id: <78df42872fccc85b692b2af42413e7c1a1bdf656.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: "Luis Claudio R. Goncalves" Date: Tue, 25 Jun 2019 11:28:04 -0300 -Subject: [PATCH 279/327] mm/zswap: Do not disable preemption in +Subject: [PATCH 279/330] mm/zswap: Do not disable preemption in zswap_frontswap_store() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 4e4cf4be79635e67144632d9135286381acbc95a ] diff --git a/debian/patches-rt/0280-revert-aio.patch b/debian/patches-rt/0280-revert-aio.patch index 19933940d..f08edd270 100644 --- a/debian/patches-rt/0280-revert-aio.patch +++ b/debian/patches-rt/0280-revert-aio.patch @@ -1,11 +1,11 @@ -From 9cda606bb6d6569b9d372db2af5fcbff01ac47cc Mon Sep 17 00:00:00 2001 -Message-Id: <9cda606bb6d6569b9d372db2af5fcbff01ac47cc.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 48b84b3913f814323d617ce874fe87bec4f0e5dc Mon Sep 17 00:00:00 2001 +Message-Id: <48b84b3913f814323d617ce874fe87bec4f0e5dc.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:53 -0400 -Subject: [PATCH 280/327] revert-aio -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 280/330] revert-aio +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz revert: fs/aio: simple simple work diff --git a/debian/patches-rt/0281-fs-aio-simple-simple-work.patch b/debian/patches-rt/0281-fs-aio-simple-simple-work.patch index 1c4a00395..04a7b88e0 100644 --- a/debian/patches-rt/0281-fs-aio-simple-simple-work.patch +++ b/debian/patches-rt/0281-fs-aio-simple-simple-work.patch @@ -1,11 +1,11 @@ -From cb2ea732c95a075a9b90e06a7dc09cf21766c0d1 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 7a7d6085c81d6e0cf4ea15cf7b404919cd9e4328 Mon Sep 17 00:00:00 2001 +Message-Id: <7a7d6085c81d6e0cf4ea15cf7b404919cd9e4328.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Feb 2015 18:49:10 +0100 -Subject: [PATCH 281/327] fs/aio: simple simple work -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 281/330] fs/aio: simple simple work +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 1a142116f6435ef070ecebb66d2d599507c10601 ] diff --git a/debian/patches-rt/0282-revert-thermal.patch b/debian/patches-rt/0282-revert-thermal.patch index 7d10b8bb7..00cd564f2 100644 --- a/debian/patches-rt/0282-revert-thermal.patch +++ b/debian/patches-rt/0282-revert-thermal.patch @@ -1,11 +1,11 @@ -From 504e23a112a7e667a99b4133e4153c5d56cbce42 Mon Sep 17 00:00:00 2001 -Message-Id: <504e23a112a7e667a99b4133e4153c5d56cbce42.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d3c2d84818c626aa75486d2d4860d96157a3778c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:53 -0400 -Subject: [PATCH 282/327] revert-thermal -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 282/330] revert-thermal +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Revert: thermal: Defer thermal wakups to threads diff --git a/debian/patches-rt/0283-thermal-Defer-thermal-wakups-to-threads.patch b/debian/patches-rt/0283-thermal-Defer-thermal-wakups-to-threads.patch index 0ea1bae12..d621b7476 100644 --- a/debian/patches-rt/0283-thermal-Defer-thermal-wakups-to-threads.patch +++ b/debian/patches-rt/0283-thermal-Defer-thermal-wakups-to-threads.patch @@ -1,11 +1,11 @@ -From 70466cfea12404a528aa72525509d2f439d9e732 Mon Sep 17 00:00:00 2001 -Message-Id: <70466cfea12404a528aa72525509d2f439d9e732.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From adeb85fb9c262ab2c7dc699ca6e164d7f2f784df Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Daniel Wagner Date: Tue, 17 Feb 2015 09:37:44 +0100 -Subject: [PATCH 283/327] thermal: Defer thermal wakups to threads -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 283/330] thermal: Defer thermal wakups to threads +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit ad2408dc248fe58536eef5b2b5734d8f9d3a280b ] diff --git a/debian/patches-rt/0284-revert-block.patch b/debian/patches-rt/0284-revert-block.patch index 154abd0ae..7954efcc4 100644 --- a/debian/patches-rt/0284-revert-block.patch +++ b/debian/patches-rt/0284-revert-block.patch @@ -1,11 +1,11 @@ -From 4ca2929421d5babd9ff082686b4ce85a2d442283 Mon Sep 17 00:00:00 2001 -Message-Id: <4ca2929421d5babd9ff082686b4ce85a2d442283.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 048ffdc22f7d41c94db5dbd39e592fc4fb99802a Mon Sep 17 00:00:00 2001 +Message-Id: <048ffdc22f7d41c94db5dbd39e592fc4fb99802a.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:54 -0400 -Subject: [PATCH 284/327] revert-block -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 284/330] revert-block +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Revert swork version of: block: blk-mq: move blk_queue_usage_counter_release() into process context diff --git a/debian/patches-rt/0285-block-blk-mq-move-blk_queue_usage_counter_release-in.patch b/debian/patches-rt/0285-block-blk-mq-move-blk_queue_usage_counter_release-in.patch index bbc39613a..432aa6970 100644 --- a/debian/patches-rt/0285-block-blk-mq-move-blk_queue_usage_counter_release-in.patch +++ b/debian/patches-rt/0285-block-blk-mq-move-blk_queue_usage_counter_release-in.patch @@ -1,12 +1,12 @@ -From e7db51657db876ea78a203bba133db44ba538c8e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 58a163041c755da3c9cda688a917ef6a30497c91 Mon Sep 17 00:00:00 2001 +Message-Id: <58a163041c755da3c9cda688a917ef6a30497c91.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Mar 2018 13:49:16 +0100 -Subject: [PATCH 285/327] block: blk-mq: move blk_queue_usage_counter_release() +Subject: [PATCH 285/330] block: blk-mq: move blk_queue_usage_counter_release() into process context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 61c928ecf4fe200bda9b49a0813b5ba0f43995b5 ] diff --git a/debian/patches-rt/0286-workqueue-rework.patch b/debian/patches-rt/0286-workqueue-rework.patch index b45eaf7ad..e9c0ecfdd 100644 --- a/debian/patches-rt/0286-workqueue-rework.patch +++ b/debian/patches-rt/0286-workqueue-rework.patch @@ -1,11 +1,11 @@ -From 37fb54fe2cbc4ea724cfba49861964d3c62b8d67 Mon Sep 17 00:00:00 2001 -Message-Id: <37fb54fe2cbc4ea724cfba49861964d3c62b8d67.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 22f861cf6e0f3a56d943758f086f0a1b7d67900b Mon Sep 17 00:00:00 2001 +Message-Id: <22f861cf6e0f3a56d943758f086f0a1b7d67900b.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 29 May 2019 18:52:27 +0200 -Subject: [PATCH 286/327] workqueue: rework -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 286/330] workqueue: rework +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit d15a862f24df983458533aebd6fa207ecdd1095a ] diff --git a/debian/patches-rt/0287-i2c-exynos5-Remove-IRQF_ONESHOT.patch b/debian/patches-rt/0287-i2c-exynos5-Remove-IRQF_ONESHOT.patch index 3880978bb..8b189f33b 100644 --- a/debian/patches-rt/0287-i2c-exynos5-Remove-IRQF_ONESHOT.patch +++ b/debian/patches-rt/0287-i2c-exynos5-Remove-IRQF_ONESHOT.patch @@ -1,11 +1,11 @@ -From c3cff520759b8386f62c5fa432a35e9041c52761 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 4c04d0c8bb09e9ab75d962e9c4d1d93489c76bba Mon Sep 17 00:00:00 2001 +Message-Id: <4c04d0c8bb09e9ab75d962e9c4d1d93489c76bba.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Aug 2019 12:30:12 +0200 -Subject: [PATCH 287/327] i2c: exynos5: Remove IRQF_ONESHOT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 287/330] i2c: exynos5: Remove IRQF_ONESHOT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 4b217df0ab3f7910c96e42091cc7d9f221d05f01 ] diff --git a/debian/patches-rt/0288-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch b/debian/patches-rt/0288-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch index 5050ebec2..57b37308c 100644 --- a/debian/patches-rt/0288-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch +++ b/debian/patches-rt/0288-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch @@ -1,11 +1,11 @@ -From f32352c34162bb5b9adb9a3e84fee89b619c58b8 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 6ff9b214d36eac6d50c62c1c5ac762c965ea337f Mon Sep 17 00:00:00 2001 +Message-Id: <6ff9b214d36eac6d50c62c1c5ac762c965ea337f.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Aug 2019 12:30:37 +0200 -Subject: [PATCH 288/327] i2c: hix5hd2: Remove IRQF_ONESHOT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 288/330] i2c: hix5hd2: Remove IRQF_ONESHOT +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit e88b481f3f86f11e3243e0808a830e5ca5782a9d ] diff --git a/debian/patches-rt/0289-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch b/debian/patches-rt/0289-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch index fa34cffc2..451226f0a 100644 --- a/debian/patches-rt/0289-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch +++ b/debian/patches-rt/0289-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch @@ -1,12 +1,12 @@ -From e2c9896ec5494329a34f3349adf1638a96dd2452 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5de7d5f1057536b8240b95d51c4dadda432cb394 Mon Sep 17 00:00:00 2001 +Message-Id: <5de7d5f1057536b8240b95d51c4dadda432cb394.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Juri Lelli Date: Wed, 31 Jul 2019 12:37:15 +0200 -Subject: [PATCH 289/327] sched/deadline: Ensure inactive_timer runs in hardirq +Subject: [PATCH 289/330] sched/deadline: Ensure inactive_timer runs in hardirq context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit ba94e7aed7405c58251b1380e6e7d73aa8284b41 ] diff --git a/debian/patches-rt/0290-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch b/debian/patches-rt/0290-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch index 70bb7f82e..201c1dd3d 100644 --- a/debian/patches-rt/0290-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch +++ b/debian/patches-rt/0290-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch @@ -1,12 +1,12 @@ -From 7cb4eef0939f66835be6b8735b2d6783e809a670 Mon Sep 17 00:00:00 2001 -Message-Id: <7cb4eef0939f66835be6b8735b2d6783e809a670.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From ed4192f1c240668a285fb54f0892aa7b04a223ce Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Clark Williams Date: Mon, 15 Jul 2019 15:25:00 -0500 -Subject: [PATCH 290/327] thermal/x86_pkg_temp: make pkg_temp_lock a raw +Subject: [PATCH 290/330] thermal/x86_pkg_temp: make pkg_temp_lock a raw spinlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 8b03bb3ea7861b70b506199a69b1c8f81fe2d4d0 ] diff --git a/debian/patches-rt/0291-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch b/debian/patches-rt/0291-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch index 2eb47f098..a242a0a10 100644 --- a/debian/patches-rt/0291-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch +++ b/debian/patches-rt/0291-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch @@ -1,11 +1,11 @@ -From bdd8709c3d3d60efc5e070a6f6df888070d13739 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 7dca0aaa2c80f7d5f4a76374693823010a2ee1c8 Mon Sep 17 00:00:00 2001 +Message-Id: <7dca0aaa2c80f7d5f4a76374693823010a2ee1c8.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Aug 2019 16:38:43 +0200 -Subject: [PATCH 291/327] dma-buf: Use seqlock_t instread disabling preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 291/330] dma-buf: Use seqlock_t instread disabling preemption +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 240610aa31094f51f299f06eb8dae8d4cd8d4500 ] diff --git a/debian/patches-rt/0292-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch b/debian/patches-rt/0292-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch index 009598031..3d133fb37 100644 --- a/debian/patches-rt/0292-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch +++ b/debian/patches-rt/0292-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch @@ -1,12 +1,12 @@ -From 642a7852fb6a13d4e2821a59dea138b1209c0e66 Mon Sep 17 00:00:00 2001 -Message-Id: <642a7852fb6a13d4e2821a59dea138b1209c0e66.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 73929727d444255e92ca4821e3f3005b209182b6 Mon Sep 17 00:00:00 2001 +Message-Id: <73929727d444255e92ca4821e3f3005b209182b6.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 13 Aug 2019 14:29:41 +0200 -Subject: [PATCH 292/327] KVM: arm/arm64: Let the timer expire in hardirq +Subject: [PATCH 292/330] KVM: arm/arm64: Let the timer expire in hardirq context on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 719cc080c914045a6e35787bf4dc3ba91cfd3efb ] diff --git a/debian/patches-rt/0293-x86-preempt-Check-preemption-level-before-looking-at.patch b/debian/patches-rt/0293-x86-preempt-Check-preemption-level-before-looking-at.patch index be4d2c8f8..a962db901 100644 --- a/debian/patches-rt/0293-x86-preempt-Check-preemption-level-before-looking-at.patch +++ b/debian/patches-rt/0293-x86-preempt-Check-preemption-level-before-looking-at.patch @@ -1,12 +1,12 @@ -From 7e0137fd8eb67661551628eae1deee359663623c Mon Sep 17 00:00:00 2001 -Message-Id: <7e0137fd8eb67661551628eae1deee359663623c.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5cb9797fd9e06ce374ac54ba38fee47f4fb81a38 Mon Sep 17 00:00:00 2001 +Message-Id: <5cb9797fd9e06ce374ac54ba38fee47f4fb81a38.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Aug 2019 17:08:58 +0200 -Subject: [PATCH 293/327] x86: preempt: Check preemption level before looking +Subject: [PATCH 293/330] x86: preempt: Check preemption level before looking at lazy-preempt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 19fc8557f2323c52b26561651ed4d51fc688a740 ] diff --git a/debian/patches-rt/0294-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch b/debian/patches-rt/0294-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch index a6e249dc5..546322d39 100644 --- a/debian/patches-rt/0294-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch +++ b/debian/patches-rt/0294-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch @@ -1,12 +1,12 @@ -From 64f009b8e74a6e1425e1f658f512c89ee944afe9 Mon Sep 17 00:00:00 2001 -Message-Id: <64f009b8e74a6e1425e1f658f512c89ee944afe9.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From e5996b01815226166260502e786e0e9d7ad91aac Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:07 +0100 -Subject: [PATCH 294/327] hrtimer: Use READ_ONCE to access timer->base in +Subject: [PATCH 294/330] hrtimer: Use READ_ONCE to access timer->base in hrimer_grab_expiry_lock() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 2c8fdbe7ef0ad06c1a326886c5954e117b5657d6 ] diff --git a/debian/patches-rt/0295-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch b/debian/patches-rt/0295-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch index dc22a5728..501008bc8 100644 --- a/debian/patches-rt/0295-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch +++ b/debian/patches-rt/0295-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch @@ -1,12 +1,12 @@ -From 1bec862a2b2110f44d8d8bb37f06a73a516494ec Mon Sep 17 00:00:00 2001 -Message-Id: <1bec862a2b2110f44d8d8bb37f06a73a516494ec.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 53da28755db7fc25ef7b25282e4309f85984e886 Mon Sep 17 00:00:00 2001 +Message-Id: <53da28755db7fc25ef7b25282e4309f85984e886.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:08 +0100 -Subject: [PATCH 295/327] hrtimer: Don't grab the expiry lock for non-soft +Subject: [PATCH 295/330] hrtimer: Don't grab the expiry lock for non-soft hrtimer -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit fd420354bea2f57c11f3de191dffdeea76531e76 ] diff --git a/debian/patches-rt/0296-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch b/debian/patches-rt/0296-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch index 4b94c8964..646d717a7 100644 --- a/debian/patches-rt/0296-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch +++ b/debian/patches-rt/0296-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch @@ -1,12 +1,12 @@ -From 0438a85803e3091e0febf2ca371607d5d42355ff Mon Sep 17 00:00:00 2001 -Message-Id: <0438a85803e3091e0febf2ca371607d5d42355ff.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 6ef6d9da759c26bedbafb948953e5e3e9f89447a Mon Sep 17 00:00:00 2001 +Message-Id: <6ef6d9da759c26bedbafb948953e5e3e9f89447a.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:09 +0100 -Subject: [PATCH 296/327] hrtimer: Prevent using hrtimer_grab_expiry_lock() on +Subject: [PATCH 296/330] hrtimer: Prevent using hrtimer_grab_expiry_lock() on migration_base -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit cef1b87f98823af923a386f3f69149acb212d4a1 ] diff --git a/debian/patches-rt/0297-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch b/debian/patches-rt/0297-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch index 7f5f6dd7a..678413078 100644 --- a/debian/patches-rt/0297-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch +++ b/debian/patches-rt/0297-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch @@ -1,12 +1,12 @@ -From d4770c984f3beb4e31d99950cb1a82ba912d498f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 1e3b340de0a2c04fa1d94e940359ce7eb2fda330 Mon Sep 17 00:00:00 2001 +Message-Id: <1e3b340de0a2c04fa1d94e940359ce7eb2fda330.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 4 Sep 2019 16:55:27 +0200 -Subject: [PATCH 297/327] hrtimer: Add a missing bracket and hide +Subject: [PATCH 297/330] hrtimer: Add a missing bracket and hide `migration_base' on !SMP -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 47b6de0b7f22c28b40275aeede3993d807668c3b ] diff --git a/debian/patches-rt/0298-posix-timers-Unlock-expiry-lock-in-the-early-return.patch b/debian/patches-rt/0298-posix-timers-Unlock-expiry-lock-in-the-early-return.patch index c8a98e20e..5235b6ed6 100644 --- a/debian/patches-rt/0298-posix-timers-Unlock-expiry-lock-in-the-early-return.patch +++ b/debian/patches-rt/0298-posix-timers-Unlock-expiry-lock-in-the-early-return.patch @@ -1,11 +1,11 @@ -From cc67c9bff2c5cd35fa45d82d637ad5f078219e5b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 85a7f8fe8d263b8fd22f3328e32d4f852df8cdf4 Mon Sep 17 00:00:00 2001 +Message-Id: <85a7f8fe8d263b8fd22f3328e32d4f852df8cdf4.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Sep 2019 12:33:59 +0200 -Subject: [PATCH 298/327] posix-timers: Unlock expiry lock in the early return -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 298/330] posix-timers: Unlock expiry lock in the early return +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 356a2781375ec58521a9bc3f500488745990c242 ] diff --git a/debian/patches-rt/0299-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch b/debian/patches-rt/0299-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch index d9c08d05e..5f65f7306 100644 --- a/debian/patches-rt/0299-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch +++ b/debian/patches-rt/0299-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch @@ -1,15 +1,15 @@ -From b6093cc6f7c1e582662a33e7cae0ec05babd74c2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 7200d432f6acca88cd524ac2ba4d530956270297 Mon Sep 17 00:00:00 2001 +Message-Id: <7200d432f6acca88cd524ac2ba4d530956270297.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Scott Wood Date: Tue, 24 Sep 2019 14:36:41 +0200 -Subject: [PATCH 299/327] =?UTF-8?q?sched:=20migrate=5Fdis/enable:=20Use=20?= +Subject: [PATCH 299/330] =?UTF-8?q?sched:=20migrate=5Fdis/enable:=20Use=20?= =?UTF-8?q?sleeping=5Flock=E2=80=A6()=20to=20annotate=20sleeping=20points?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 4230dd3824c3e1785504e6f757ce79a4b55651fa ] diff --git a/debian/patches-rt/0300-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch b/debian/patches-rt/0300-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch index f410c9354..0dbb5ce61 100644 --- a/debian/patches-rt/0300-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch +++ b/debian/patches-rt/0300-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch @@ -1,12 +1,12 @@ -From 91c2cb2920f6b5c6d7c3a1ceb72846db14331ae5 Mon Sep 17 00:00:00 2001 -Message-Id: <91c2cb2920f6b5c6d7c3a1ceb72846db14331ae5.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 735958fb6ab655fb68850f0ef23b7c37a8b258f9 Mon Sep 17 00:00:00 2001 +Message-Id: <735958fb6ab655fb68850f0ef23b7c37a8b258f9.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:32 -0500 -Subject: [PATCH 300/327] sched: __set_cpus_allowed_ptr: Check cpus_mask, not +Subject: [PATCH 300/330] sched: __set_cpus_allowed_ptr: Check cpus_mask, not cpus_ptr -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit e5606fb7b042db634ed62b4dd733d62e050e468f ] diff --git a/debian/patches-rt/0301-sched-Remove-dead-__migrate_disabled-check.patch b/debian/patches-rt/0301-sched-Remove-dead-__migrate_disabled-check.patch index 4266b9579..f4f9f61aa 100644 --- a/debian/patches-rt/0301-sched-Remove-dead-__migrate_disabled-check.patch +++ b/debian/patches-rt/0301-sched-Remove-dead-__migrate_disabled-check.patch @@ -1,11 +1,11 @@ -From 1b6d410b715108de2198c5182eeb69baa2fc31b4 Mon Sep 17 00:00:00 2001 -Message-Id: <1b6d410b715108de2198c5182eeb69baa2fc31b4.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5aff0cf55a25bc3263b630530b9709bcb061e49b Mon Sep 17 00:00:00 2001 +Message-Id: <5aff0cf55a25bc3263b630530b9709bcb061e49b.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:33 -0500 -Subject: [PATCH 301/327] sched: Remove dead __migrate_disabled() check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 301/330] sched: Remove dead __migrate_disabled() check +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 14d9272d534ea91262e15db99443fc5995c7c016 ] diff --git a/debian/patches-rt/0302-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch b/debian/patches-rt/0302-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch index 837e87715..c422ade62 100644 --- a/debian/patches-rt/0302-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch +++ b/debian/patches-rt/0302-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch @@ -1,11 +1,11 @@ -From 64a88392dda208f2c6bbb81dd2eeaff338ba5d6e Mon Sep 17 00:00:00 2001 -Message-Id: <64a88392dda208f2c6bbb81dd2eeaff338ba5d6e.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 30bf6f60094018e4f878ea339be2f6e921107b1b Mon Sep 17 00:00:00 2001 +Message-Id: <30bf6f60094018e4f878ea339be2f6e921107b1b.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:34 -0500 -Subject: [PATCH 302/327] sched: migrate disable: Protect cpus_ptr with lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 302/330] sched: migrate disable: Protect cpus_ptr with lock +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 27ee52a891ed2c7e2e2c8332ccae0de7c2674b09 ] diff --git a/debian/patches-rt/0303-lib-smp_processor_id-Don-t-use-cpumask_equal.patch b/debian/patches-rt/0303-lib-smp_processor_id-Don-t-use-cpumask_equal.patch index 4e568f64c..0823de13d 100644 --- a/debian/patches-rt/0303-lib-smp_processor_id-Don-t-use-cpumask_equal.patch +++ b/debian/patches-rt/0303-lib-smp_processor_id-Don-t-use-cpumask_equal.patch @@ -1,11 +1,11 @@ -From 5a1baef2364e13de74ca2bd2eed8523ba5e9156a Mon Sep 17 00:00:00 2001 -Message-Id: <5a1baef2364e13de74ca2bd2eed8523ba5e9156a.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 605c6a52c867dfd1974385c3769e39c6affd3ff4 Mon Sep 17 00:00:00 2001 +Message-Id: <605c6a52c867dfd1974385c3769e39c6affd3ff4.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Waiman Long Date: Thu, 3 Oct 2019 16:36:08 -0400 -Subject: [PATCH 303/327] lib/smp_processor_id: Don't use cpumask_equal() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 303/330] lib/smp_processor_id: Don't use cpumask_equal() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 659252061477862f45b79e1de169e6030f5c8918 ] diff --git a/debian/patches-rt/0304-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch b/debian/patches-rt/0304-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch index 0d16d219b..4f5da9df6 100644 --- a/debian/patches-rt/0304-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch +++ b/debian/patches-rt/0304-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch @@ -1,12 +1,12 @@ -From 5e0218a52e4fad016fbc0e46256a14493a88c4c1 Mon Sep 17 00:00:00 2001 -Message-Id: <5e0218a52e4fad016fbc0e46256a14493a88c4c1.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 7a4faab21a6ad6420fbc93acc87ad339a1f6a22c Mon Sep 17 00:00:00 2001 +Message-Id: <7a4faab21a6ad6420fbc93acc87ad339a1f6a22c.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 7 Oct 2019 16:45:18 +0200 -Subject: [PATCH 304/327] futex: Make the futex_hash_bucket spinlock_t again +Subject: [PATCH 304/330] futex: Make the futex_hash_bucket spinlock_t again and bring back its old state -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 954ad80c23edfe71f4e8ce70b961eac884320c3a ] diff --git a/debian/patches-rt/0305-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch b/debian/patches-rt/0305-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch index 541387705..69f769003 100644 --- a/debian/patches-rt/0305-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch +++ b/debian/patches-rt/0305-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch @@ -1,12 +1,12 @@ -From ff1318eac796a64edb06fc4ea05efab4fad348a8 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 7879a78135546124887f0dce41e189da8212a53d Mon Sep 17 00:00:00 2001 +Message-Id: <7879a78135546124887f0dce41e189da8212a53d.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 30 Sep 2019 18:15:44 +0200 -Subject: [PATCH 305/327] locking/rtmutex: Clean ->pi_blocked_on in the error +Subject: [PATCH 305/330] locking/rtmutex: Clean ->pi_blocked_on in the error case -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 0be4ea6e3ce693101be0fbd55a0cc7ce238ab2eb ] diff --git a/debian/patches-rt/0306-lib-ubsan-Don-t-seralize-UBSAN-report.patch b/debian/patches-rt/0306-lib-ubsan-Don-t-seralize-UBSAN-report.patch index 0110a80fa..5911c6272 100644 --- a/debian/patches-rt/0306-lib-ubsan-Don-t-seralize-UBSAN-report.patch +++ b/debian/patches-rt/0306-lib-ubsan-Don-t-seralize-UBSAN-report.patch @@ -1,11 +1,11 @@ -From 67968665a403e3960a25236deff8c980d9914ce1 Mon Sep 17 00:00:00 2001 -Message-Id: <67968665a403e3960a25236deff8c980d9914ce1.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 641bdbffcda79c8d95fbd813967007d966319d5e Mon Sep 17 00:00:00 2001 +Message-Id: <641bdbffcda79c8d95fbd813967007d966319d5e.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Julien Grall Date: Fri, 20 Sep 2019 11:08:35 +0100 -Subject: [PATCH 306/327] lib/ubsan: Don't seralize UBSAN report -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 306/330] lib/ubsan: Don't seralize UBSAN report +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 4702c28ac777b27acb499cbd5e8e787ce1a7d82d ] diff --git a/debian/patches-rt/0307-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch b/debian/patches-rt/0307-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch index ef00f3658..599b5aeb0 100644 --- a/debian/patches-rt/0307-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch +++ b/debian/patches-rt/0307-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch @@ -1,12 +1,12 @@ -From 57c00f0bce67acc8af7f2429e96ed7dcedf2cd6d Mon Sep 17 00:00:00 2001 -Message-Id: <57c00f0bce67acc8af7f2429e96ed7dcedf2cd6d.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5c2b16ab5e41f4b2f4d045a564c87df4af3a7b80 Mon Sep 17 00:00:00 2001 +Message-Id: <5c2b16ab5e41f4b2f4d045a564c87df4af3a7b80.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Liu Haitao Date: Fri, 27 Sep 2019 16:22:30 +0800 -Subject: [PATCH 307/327] kmemleak: Change the lock of kmemleak_object to +Subject: [PATCH 307/330] kmemleak: Change the lock of kmemleak_object to raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 217847f57119b5fdd377bfa3d344613ddb98d9fc ] diff --git a/debian/patches-rt/0308-sched-migrate_enable-Use-select_fallback_rq.patch b/debian/patches-rt/0308-sched-migrate_enable-Use-select_fallback_rq.patch index 72dbd5dd1..81c2453ea 100644 --- a/debian/patches-rt/0308-sched-migrate_enable-Use-select_fallback_rq.patch +++ b/debian/patches-rt/0308-sched-migrate_enable-Use-select_fallback_rq.patch @@ -1,11 +1,11 @@ -From 9851f278916a2a8b9454e4538f85d8f7482d1bff Mon Sep 17 00:00:00 2001 -Message-Id: <9851f278916a2a8b9454e4538f85d8f7482d1bff.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From e8f09d73623c4aa3148170d6f1176477dc69c9a9 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:12 -0500 -Subject: [PATCH 308/327] sched: migrate_enable: Use select_fallback_rq() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 308/330] sched: migrate_enable: Use select_fallback_rq() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit adfa969d4cfcc995a9d866020124e50f1827d2d1 ] diff --git a/debian/patches-rt/0309-sched-Lazy-migrate_disable-processing.patch b/debian/patches-rt/0309-sched-Lazy-migrate_disable-processing.patch index 12782c80c..bcad65872 100644 --- a/debian/patches-rt/0309-sched-Lazy-migrate_disable-processing.patch +++ b/debian/patches-rt/0309-sched-Lazy-migrate_disable-processing.patch @@ -1,11 +1,11 @@ -From f89750ad117039071c2297e1e35e190e24f43c8a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From f52d8b9fda534cb6f083517fe283fa5e65410c7e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:13 -0500 -Subject: [PATCH 309/327] sched: Lazy migrate_disable processing -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 309/330] sched: Lazy migrate_disable processing +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 425c5b38779a860062aa62219dc920d374b13c17 ] diff --git a/debian/patches-rt/0310-sched-migrate_enable-Use-stop_one_cpu_nowait.patch b/debian/patches-rt/0310-sched-migrate_enable-Use-stop_one_cpu_nowait.patch index ab19873ee..b20f77b28 100644 --- a/debian/patches-rt/0310-sched-migrate_enable-Use-stop_one_cpu_nowait.patch +++ b/debian/patches-rt/0310-sched-migrate_enable-Use-stop_one_cpu_nowait.patch @@ -1,11 +1,11 @@ -From ef1b96bd98e1385ef3ff6d01d7040090f57ca3e6 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 0a537f78a9c7a2d565ffb556fc5fe4afbb246909 Mon Sep 17 00:00:00 2001 +Message-Id: <0a537f78a9c7a2d565ffb556fc5fe4afbb246909.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:14 -0500 -Subject: [PATCH 310/327] sched: migrate_enable: Use stop_one_cpu_nowait() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 310/330] sched: migrate_enable: Use stop_one_cpu_nowait() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 6b39a1fa8c53cae08dc03afdae193b7d3a78a173 ] diff --git a/debian/patches-rt/0311-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch b/debian/patches-rt/0311-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch index 9fc369cfa..97359d5f8 100644 --- a/debian/patches-rt/0311-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch +++ b/debian/patches-rt/0311-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch @@ -1,12 +1,12 @@ -From b0a75fa3239f3ef5f765d7e2ea1913b4fd07fe24 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 82f96941ce72468ca5a0f98ea49b074f6cb0dd16 Mon Sep 17 00:00:00 2001 +Message-Id: <82f96941ce72468ca5a0f98ea49b074f6cb0dd16.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 18 Oct 2019 13:04:15 +0200 -Subject: [PATCH 311/327] Revert "ARM: Initialize split page table locks for +Subject: [PATCH 311/330] Revert "ARM: Initialize split page table locks for vector page" -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 247074c44d8c3e619dfde6404a52295d8d671d38 ] diff --git a/debian/patches-rt/0312-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch b/debian/patches-rt/0312-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch index d0156b5b6..8e9e90352 100644 --- a/debian/patches-rt/0312-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch +++ b/debian/patches-rt/0312-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch @@ -1,12 +1,12 @@ -From 9cb74740f782083dd0118051f2dd17619da8f0c6 Mon Sep 17 00:00:00 2001 -Message-Id: <9cb74740f782083dd0118051f2dd17619da8f0c6.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From c6b4aa78233bb5eed54d03b491b1cd1ee2281614 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Nov 2019 09:25:04 +0100 -Subject: [PATCH 312/327] locking: Make spinlock_t and rwlock_t a RCU section +Subject: [PATCH 312/330] locking: Make spinlock_t and rwlock_t a RCU section on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 84440022a0e1c8c936d61f8f97593674a295d409 ] diff --git a/debian/patches-rt/0313-sched-core-migrate_enable-must-access-takedown_cpu_t.patch b/debian/patches-rt/0313-sched-core-migrate_enable-must-access-takedown_cpu_t.patch index 2fa929a9b..5f8841831 100644 --- a/debian/patches-rt/0313-sched-core-migrate_enable-must-access-takedown_cpu_t.patch +++ b/debian/patches-rt/0313-sched-core-migrate_enable-must-access-takedown_cpu_t.patch @@ -1,12 +1,12 @@ -From 65702ae3d69beea5df3526fe9f2d1dfda6cd68e2 Mon Sep 17 00:00:00 2001 -Message-Id: <65702ae3d69beea5df3526fe9f2d1dfda6cd68e2.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 29c32d3972bb9d63cde1df12571bb803d2ba0579 Mon Sep 17 00:00:00 2001 +Message-Id: <29c32d3972bb9d63cde1df12571bb803d2ba0579.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 29 Nov 2019 17:24:55 +0100 -Subject: [PATCH 313/327] sched/core: migrate_enable() must access +Subject: [PATCH 313/330] sched/core: migrate_enable() must access takedown_cpu_task on !HOTPLUG_CPU -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit a61d1977f692e46bad99a100f264981ba08cb4bd ] diff --git a/debian/patches-rt/0314-lib-smp_processor_id-Adjust-check_preemption_disable.patch b/debian/patches-rt/0314-lib-smp_processor_id-Adjust-check_preemption_disable.patch index 51ddaa275..f854d1ac8 100644 --- a/debian/patches-rt/0314-lib-smp_processor_id-Adjust-check_preemption_disable.patch +++ b/debian/patches-rt/0314-lib-smp_processor_id-Adjust-check_preemption_disable.patch @@ -1,12 +1,12 @@ -From 341fd2d6c916e75c5be5475f0e833e0407632d54 Mon Sep 17 00:00:00 2001 -Message-Id: <341fd2d6c916e75c5be5475f0e833e0407632d54.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 02bb5f7235090f7478b2ce234db678feefbd5235 Mon Sep 17 00:00:00 2001 +Message-Id: <02bb5f7235090f7478b2ce234db678feefbd5235.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Daniel Wagner Date: Mon, 16 Dec 2019 16:15:57 +0100 -Subject: [PATCH 314/327] lib/smp_processor_id: Adjust +Subject: [PATCH 314/330] lib/smp_processor_id: Adjust check_preemption_disabled() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit af3c1c5fdf177870fb5e6e16b24e374696ab28f5 ] diff --git a/debian/patches-rt/0315-sched-migrate_enable-Busy-loop-until-the-migration-r.patch b/debian/patches-rt/0315-sched-migrate_enable-Busy-loop-until-the-migration-r.patch index 5df030d8e..25d70c148 100644 --- a/debian/patches-rt/0315-sched-migrate_enable-Busy-loop-until-the-migration-r.patch +++ b/debian/patches-rt/0315-sched-migrate_enable-Busy-loop-until-the-migration-r.patch @@ -1,12 +1,12 @@ -From c382636f5b0add5bb44053f81987bef20246f241 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 1cb8e2e65fad8f3e5de07e090b2b391b591a19ec Mon Sep 17 00:00:00 2001 +Message-Id: <1cb8e2e65fad8f3e5de07e090b2b391b591a19ec.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Dec 2019 10:53:59 +0100 -Subject: [PATCH 315/327] sched: migrate_enable: Busy loop until the migration +Subject: [PATCH 315/330] sched: migrate_enable: Busy loop until the migration request is completed -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 140d7f54a5fff02898d2ca9802b39548bf7455f1 ] diff --git a/debian/patches-rt/0316-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch b/debian/patches-rt/0316-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch index 1e46841b7..53e108019 100644 --- a/debian/patches-rt/0316-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch +++ b/debian/patches-rt/0316-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch @@ -1,11 +1,11 @@ -From 6acff8407f5c3a3baa08212536ba5d1d5ef78233 Mon Sep 17 00:00:00 2001 -Message-Id: <6acff8407f5c3a3baa08212536ba5d1d5ef78233.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 0b842c8f3f7cfa306ba7dc58d11e3ad524582290 Mon Sep 17 00:00:00 2001 +Message-Id: <0b842c8f3f7cfa306ba7dc58d11e3ad524582290.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 18 Dec 2019 12:25:09 +0100 -Subject: [PATCH 316/327] userfaultfd: Use a seqlock instead of seqcount -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 316/330] userfaultfd: Use a seqlock instead of seqcount +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit dc952a564d02997330654be9628bbe97ba2a05d3 ] diff --git a/debian/patches-rt/0317-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch b/debian/patches-rt/0317-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch index a543be1b6..da102f13a 100644 --- a/debian/patches-rt/0317-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch +++ b/debian/patches-rt/0317-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch @@ -1,11 +1,11 @@ -From eb4363f5cebba313962d64240609b40b18873ff2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 57b22807d21698b7f1ee8f42c59ab3a62aeaf0af Mon Sep 17 00:00:00 2001 +Message-Id: <57b22807d21698b7f1ee8f42c59ab3a62aeaf0af.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 24 Jan 2020 06:11:46 -0500 -Subject: [PATCH 317/327] sched: migrate_enable: Use per-cpu cpu_stop_work -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 317/330] sched: migrate_enable: Use per-cpu cpu_stop_work +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 2dcd94b443c5dcbc20281666321b7f025f9cc85c ] diff --git a/debian/patches-rt/0318-sched-migrate_enable-Remove-__schedule-call.patch b/debian/patches-rt/0318-sched-migrate_enable-Remove-__schedule-call.patch index 40b226f36..1b8cc766a 100644 --- a/debian/patches-rt/0318-sched-migrate_enable-Remove-__schedule-call.patch +++ b/debian/patches-rt/0318-sched-migrate_enable-Remove-__schedule-call.patch @@ -1,11 +1,11 @@ -From 02cd9bc2ad02a45f3454a8f85b7615f74af33e28 Mon Sep 17 00:00:00 2001 -Message-Id: <02cd9bc2ad02a45f3454a8f85b7615f74af33e28.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 9bb913d2bb12dc4b240a73d30676a378929d19ac Mon Sep 17 00:00:00 2001 +Message-Id: <9bb913d2bb12dc4b240a73d30676a378929d19ac.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 24 Jan 2020 06:11:47 -0500 -Subject: [PATCH 318/327] sched: migrate_enable: Remove __schedule() call -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 318/330] sched: migrate_enable: Remove __schedule() call +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit b8162e61e9a33bd1de6452eb838fbf50a93ddd9a ] diff --git a/debian/patches-rt/0319-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch b/debian/patches-rt/0319-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch index 7ddcdad43..010b36573 100644 --- a/debian/patches-rt/0319-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch +++ b/debian/patches-rt/0319-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch @@ -1,12 +1,12 @@ -From d3ca6725643c02176fc3d31b1441c1c1b4a62740 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From de1993758391183fb2f6c2b22c78a655962ca786 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Matt Fleming Date: Sun, 26 Jan 2020 21:19:45 +0000 -Subject: [PATCH 319/327] mm/memcontrol: Move misplaced +Subject: [PATCH 319/330] mm/memcontrol: Move misplaced local_unlock_irqrestore() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit 071a1d6a6e14d0dec240a8c67b425140d7f92f6a ] diff --git a/debian/patches-rt/0320-locallock-Include-header-for-the-current-macro.patch b/debian/patches-rt/0320-locallock-Include-header-for-the-current-macro.patch index 67c148145..38557d0f9 100644 --- a/debian/patches-rt/0320-locallock-Include-header-for-the-current-macro.patch +++ b/debian/patches-rt/0320-locallock-Include-header-for-the-current-macro.patch @@ -1,11 +1,11 @@ -From 5796f4a587dda1180ce0733b00b8645176c14574 Mon Sep 17 00:00:00 2001 -Message-Id: <5796f4a587dda1180ce0733b00b8645176c14574.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 6003658de7b7328becd8c9d1de5fb85a48843b7f Mon Sep 17 00:00:00 2001 +Message-Id: <6003658de7b7328becd8c9d1de5fb85a48843b7f.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 4 Feb 2020 13:29:50 +0100 -Subject: [PATCH 320/327] locallock: Include header for the `current' macro -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 320/330] locallock: Include header for the `current' macro +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit e693075a5fd852043fa8d2b0467e078d9e5cb782 ] diff --git a/debian/patches-rt/0321-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch b/debian/patches-rt/0321-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch index 73859a787..0d69ec74d 100644 --- a/debian/patches-rt/0321-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch +++ b/debian/patches-rt/0321-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch @@ -1,12 +1,12 @@ -From cd092a6ab4fbe1138a03fabc6cc9d69d6444e55c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 398200d74770e1ecce0e14ed1dcb977c6c301c2b Mon Sep 17 00:00:00 2001 +Message-Id: <398200d74770e1ecce0e14ed1dcb977c6c301c2b.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2020 18:57:11 +0100 -Subject: [PATCH 321/327] drm/vmwgfx: Drop preempt_disable() in +Subject: [PATCH 321/330] drm/vmwgfx: Drop preempt_disable() in vmw_fifo_ping_host() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit b901491e7b9b7a676818d84e482b69be72fc142f ] diff --git a/debian/patches-rt/0322-tracing-make-preempt_lazy-and-migrate_disable-counte.patch b/debian/patches-rt/0322-tracing-make-preempt_lazy-and-migrate_disable-counte.patch index 5ae7a928f..b93a0befe 100644 --- a/debian/patches-rt/0322-tracing-make-preempt_lazy-and-migrate_disable-counte.patch +++ b/debian/patches-rt/0322-tracing-make-preempt_lazy-and-migrate_disable-counte.patch @@ -1,12 +1,12 @@ -From 5dd7ee383de435669971be29e95a5ac76c02e63b Mon Sep 17 00:00:00 2001 -Message-Id: <5dd7ee383de435669971be29e95a5ac76c02e63b.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From d4baa0fe18784afb68110aa1e54bf9f9fb746ab8 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2020 18:15:15 +0100 -Subject: [PATCH 322/327] tracing: make preempt_lazy and migrate_disable +Subject: [PATCH 322/330] tracing: make preempt_lazy and migrate_disable counter smaller -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz [ Upstream commit dd430bf5ecb40f9a89679c85868826475d71de54 ] diff --git a/debian/patches-rt/0323-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch b/debian/patches-rt/0323-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch index 452caf88b..c2e8d1ae2 100644 --- a/debian/patches-rt/0323-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch +++ b/debian/patches-rt/0323-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch @@ -1,12 +1,12 @@ -From a3d9f4e7283272231c8773f326ab25e456e45c76 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 5230c041cb74d157caf6562fd8c91a83034d50c3 Mon Sep 17 00:00:00 2001 +Message-Id: <5230c041cb74d157caf6562fd8c91a83034d50c3.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Tiejun Chen Date: Mon, 30 Mar 2020 18:45:23 -0400 -Subject: [PATCH 323/327] lib/ubsan: Remove flags parameter from calls to +Subject: [PATCH 323/330] lib/ubsan: Remove flags parameter from calls to ubsan_prologue() and ubsan_epilogue() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Fails to build with CONFIG_UBSAN=y diff --git a/debian/patches-rt/0324-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch b/debian/patches-rt/0324-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch index 626397f64..6f57a7e99 100644 --- a/debian/patches-rt/0324-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch +++ b/debian/patches-rt/0324-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch @@ -1,12 +1,12 @@ -From 0b9af28c02afae1e2e1c080fc7501cc360ab0e93 Mon Sep 17 00:00:00 2001 -Message-Id: <0b9af28c02afae1e2e1c080fc7501cc360ab0e93.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From c46f0f670266408c152eaf4ed06578d55d27b819 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Sun, 22 Mar 2020 00:00:28 +0100 -Subject: [PATCH 324/327] irq_work: Fix checking of IRQ_WORK_LAZY flag set on +Subject: [PATCH 324/330] irq_work: Fix checking of IRQ_WORK_LAZY flag set on non PREEMPT_RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz When CONFIG_PREEMPT_RT_FULL is not set, some of the checks for using lazy_list are not properly made as the IRQ_WORK_LAZY is not checked. There's diff --git a/debian/patches-rt/0325-tasklet-Address-a-race-resulting-in-double-enqueue.patch b/debian/patches-rt/0325-tasklet-Address-a-race-resulting-in-double-enqueue.patch index 44b9435f5..31c804989 100644 --- a/debian/patches-rt/0325-tasklet-Address-a-race-resulting-in-double-enqueue.patch +++ b/debian/patches-rt/0325-tasklet-Address-a-race-resulting-in-double-enqueue.patch @@ -1,11 +1,11 @@ -From 0d19965029f2573866f9c372c9578a642ca732c7 Mon Sep 17 00:00:00 2001 -Message-Id: <0d19965029f2573866f9c372c9578a642ca732c7.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 055fcdf83308de4850a75e7b5da0cacbaefb632c Mon Sep 17 00:00:00 2001 +Message-Id: <055fcdf83308de4850a75e7b5da0cacbaefb632c.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Zhang Xiao Date: Tue, 17 Mar 2020 12:47:43 +0100 -Subject: [PATCH 325/327] tasklet: Address a race resulting in double-enqueue -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Subject: [PATCH 325/330] tasklet: Address a race resulting in double-enqueue +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz The kernel bugzilla has the following race condition reported: diff --git a/debian/patches-rt/0326-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch b/debian/patches-rt/0326-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch index 2e5e73e43..7160c8353 100644 --- a/debian/patches-rt/0326-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch +++ b/debian/patches-rt/0326-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch @@ -1,12 +1,12 @@ -From 2005a14ca24c8fed7fee4e211911cf27a6e292cb Mon Sep 17 00:00:00 2001 -Message-Id: <2005a14ca24c8fed7fee4e211911cf27a6e292cb.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> +From 0d328c09a6239925e54530d121e8ea8d23f1aa37 Mon Sep 17 00:00:00 2001 +Message-Id: <0d328c09a6239925e54530d121e8ea8d23f1aa37.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> From: Rasmus Villemoes Date: Tue, 28 Apr 2020 16:40:26 +0200 -Subject: [PATCH 326/327] hrtimer: fix logic for when grabbing +Subject: [PATCH 326/330] hrtimer: fix logic for when grabbing softirq_expiry_lock can be elided -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz Commit diff --git a/debian/patches-rt/0327-Linux-4.19.124-rt53-REBASE.patch b/debian/patches-rt/0327-Linux-4.19.124-rt53-REBASE.patch deleted file mode 100644 index 095a0856c..000000000 --- a/debian/patches-rt/0327-Linux-4.19.124-rt53-REBASE.patch +++ /dev/null @@ -1,24 +0,0 @@ -From 943c393e9a144210707ac0689f5ed06cbab1ca03 Mon Sep 17 00:00:00 2001 -Message-Id: <943c393e9a144210707ac0689f5ed06cbab1ca03.1590093525.git.zanussi@kernel.org> -In-Reply-To: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -References: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.git.zanussi@kernel.org> -From: Tom Zanussi -Date: Thu, 21 May 2020 15:35:48 -0500 -Subject: [PATCH 327/327] Linux 4.19.124-rt53 REBASE -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz - -Signed-off-by: Tom Zanussi ---- - localversion-rt | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/localversion-rt b/localversion-rt -index 1199ebade17b..e6c0dc6a54cd 100644 ---- a/localversion-rt -+++ b/localversion-rt -@@ -1 +1 @@ ---rt16 -+-rt53 --- -2.17.1 - diff --git a/debian/patches-rt/0327-fs-dcache-Include-swait.h-header.patch b/debian/patches-rt/0327-fs-dcache-Include-swait.h-header.patch new file mode 100644 index 000000000..438ed2862 --- /dev/null +++ b/debian/patches-rt/0327-fs-dcache-Include-swait.h-header.patch @@ -0,0 +1,39 @@ +From c4fafd10ae410a9b577a4016b0071034e3113ffd Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +From: Sebastian Andrzej Siewior +Date: Thu, 16 Apr 2020 12:42:15 +0200 +Subject: [PATCH 327/330] fs/dcache: Include swait.h header +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz + +[ Upstream commit 279f90ddf53cd6bd3c203fbbf488d642ea2603de ] + +Include the swait.h header so it compiles even if not all patches are +applied. + +Reported-by: kbuild test robot +Signed-off-by: Sebastian Andrzej Siewior +Signed-off-by: Tom Zanussi + + Conflicts: + fs/proc/base.c +--- + fs/proc/base.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/fs/proc/base.c b/fs/proc/base.c +index a45d4d640f01..56b1c4f1e8c0 100644 +--- a/fs/proc/base.c ++++ b/fs/proc/base.c +@@ -95,6 +95,7 @@ + #include + #include + #include ++#include + #include "internal.h" + #include "fd.h" + +-- +2.17.1 + diff --git a/debian/patches-rt/0328-mm-slub-Always-flush-the-delayed-empty-slubs-in-flus.patch b/debian/patches-rt/0328-mm-slub-Always-flush-the-delayed-empty-slubs-in-flus.patch new file mode 100644 index 000000000..22e446462 --- /dev/null +++ b/debian/patches-rt/0328-mm-slub-Always-flush-the-delayed-empty-slubs-in-flus.patch @@ -0,0 +1,67 @@ +From 35163550074015f85b43664a5b4ae464a44a6529 Mon Sep 17 00:00:00 2001 +Message-Id: <35163550074015f85b43664a5b4ae464a44a6529.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +From: Kevin Hao +Date: Mon, 4 May 2020 11:34:07 +0800 +Subject: [PATCH 328/330] mm: slub: Always flush the delayed empty slubs in + flush_all() +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz + +[ Upstream commit 23a2c31b19e99beaf5107071b0f32a596202cdae ] + +After commit f0b231101c94 ("mm/SLUB: delay giving back empty slubs to +IRQ enabled regions"), when the free_slab() is invoked with the IRQ +disabled, the empty slubs are moved to a per-CPU list and will be +freed after IRQ enabled later. But in the current codes, there is +a check to see if there really has the cpu slub on a specific cpu +before flushing the delayed empty slubs, this may cause a reference +of already released kmem_cache in a scenario like below: + cpu 0 cpu 1 + kmem_cache_destroy() + flush_all() + --->IPI flush_cpu_slab() + flush_slab() + deactivate_slab() + discard_slab() + free_slab() + c->page = NULL; + for_each_online_cpu(cpu) + if (!has_cpu_slab(1, s)) + continue + this skip to flush the delayed + empty slub released by cpu1 + kmem_cache_free(kmem_cache, s) + + kmalloc() + __slab_alloc() + free_delayed() + __free_slab() + reference to released kmem_cache + +Fixes: f0b231101c94 ("mm/SLUB: delay giving back empty slubs to IRQ enabled regions") +Signed-off-by: Kevin Hao +Signed-off-by: Sebastian Andrzej Siewior +Cc: stable-rt@vger.kernel.org +Signed-off-by: Tom Zanussi +--- + mm/slub.c | 3 --- + 1 file changed, 3 deletions(-) + +diff --git a/mm/slub.c b/mm/slub.c +index d243c6ef7fc9..a9473bbb1338 100644 +--- a/mm/slub.c ++++ b/mm/slub.c +@@ -2341,9 +2341,6 @@ static void flush_all(struct kmem_cache *s) + for_each_online_cpu(cpu) { + struct slub_free_list *f; + +- if (!has_cpu_slab(cpu, s)) +- continue; +- + f = &per_cpu(slub_free_list, cpu); + raw_spin_lock_irq(&f->lock); + list_splice_init(&f->list, &tofree); +-- +2.17.1 + diff --git a/debian/patches-rt/0329-tasklet-Fix-UP-case-for-tasklet-CHAINED-state.patch b/debian/patches-rt/0329-tasklet-Fix-UP-case-for-tasklet-CHAINED-state.patch new file mode 100644 index 000000000..3b0033023 --- /dev/null +++ b/debian/patches-rt/0329-tasklet-Fix-UP-case-for-tasklet-CHAINED-state.patch @@ -0,0 +1,59 @@ +From 6fdc9a6ad87faf040f7455e1371cfb7fa2535889 Mon Sep 17 00:00:00 2001 +Message-Id: <6fdc9a6ad87faf040f7455e1371cfb7fa2535889.1592846147.git.zanussi@kernel.org> +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +From: Tom Zanussi +Date: Tue, 9 Jun 2020 11:04:08 -0500 +Subject: [PATCH 329/330] tasklet: Fix UP case for tasklet CHAINED state +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz + +commit 62d0a2a30cd0 (tasklet: Address a race resulting in +double-enqueue) addresses a problem that can result in a tasklet being +enqueued on two cpus at the same time by combining the RUN flag with a +new CHAINED flag, and relies on the combination to be present in order +to zero it out, which can never happen on (!SMP and !PREEMPT_RT_FULL) +because the RUN flag is SMP/PREEMPT_RT_FULL-only. + +So make sure the above commit is only applied for the SMP || +PREEMPT_RT_FULL case. + +Fixes: 62d0a2a30cd0 ("tasklet: Address a race resulting in double-enqueue") +Signed-off-by: Tom Zanussi +Reported-by: Ramon Fried +Tested-By: Ramon Fried +--- + kernel/softirq.c | 6 ++++++ + 1 file changed, 6 insertions(+) + +diff --git a/kernel/softirq.c b/kernel/softirq.c +index 73dae64bfc9c..9bad7a16dc61 100644 +--- a/kernel/softirq.c ++++ b/kernel/softirq.c +@@ -947,10 +947,12 @@ static void __tasklet_schedule_common(struct tasklet_struct *t, + * is locked before adding it to the list. + */ + if (test_bit(TASKLET_STATE_SCHED, &t->state)) { ++#if defined(CONFIG_SMP) || defined(CONFIG_PREEMPT_RT_FULL) + if (test_and_set_bit(TASKLET_STATE_CHAINED, &t->state)) { + tasklet_unlock(t); + return; + } ++#endif + t->next = NULL; + *head->tail = t; + head->tail = &(t->next); +@@ -1044,7 +1046,11 @@ static void tasklet_action_common(struct softirq_action *a, + again: + t->func(t->data); + ++#if defined(CONFIG_SMP) || defined(CONFIG_PREEMPT_RT_FULL) + while (cmpxchg(&t->state, TASKLET_STATEF_RC, 0) != TASKLET_STATEF_RC) { ++#else ++ while (!tasklet_tryunlock(t)) { ++#endif + /* + * If it got disabled meanwhile, bail out: + */ +-- +2.17.1 + diff --git a/debian/patches-rt/0330-Linux-4.19.127-rt55-REBASE.patch b/debian/patches-rt/0330-Linux-4.19.127-rt55-REBASE.patch new file mode 100644 index 000000000..22a2f3807 --- /dev/null +++ b/debian/patches-rt/0330-Linux-4.19.127-rt55-REBASE.patch @@ -0,0 +1,24 @@ +From ba502b6eab1519d57f6ea13cb61984415fa7c361 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +References: <07cd0dbc80b976663c80755496a03f288decfe5a.1592846146.git.zanussi@kernel.org> +From: Tom Zanussi +Date: Wed, 10 Jun 2020 12:21:34 -0500 +Subject: [PATCH 330/330] Linux 4.19.127-rt55 REBASE +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.127-rt55.tar.xz + +Signed-off-by: Tom Zanussi +--- + localversion-rt | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/localversion-rt b/localversion-rt +index 1199ebade17b..51b05e9abe6f 100644 +--- a/localversion-rt ++++ b/localversion-rt +@@ -1 +1 @@ +--rt16 ++-rt55 +-- +2.17.1 + diff --git a/debian/patches-rt/series b/debian/patches-rt/series index 06a7b7e7f..32fa4a085 100644 --- a/debian/patches-rt/series +++ b/debian/patches-rt/series @@ -324,4 +324,7 @@ 0324-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch 0325-tasklet-Address-a-race-resulting-in-double-enqueue.patch 0326-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch -0327-Linux-4.19.124-rt53-REBASE.patch +0327-fs-dcache-Include-swait.h-header.patch +0328-mm-slub-Always-flush-the-delayed-empty-slubs-in-flus.patch +0329-tasklet-Fix-UP-case-for-tasklet-CHAINED-state.patch +0330-Linux-4.19.127-rt55-REBASE.patch