diff --git a/debian/changelog b/debian/changelog index 2ca9e55b3..ef6ae25d4 100644 --- a/debian/changelog +++ b/debian/changelog @@ -315,6 +315,7 @@ linux (4.19.124-1) UNRELEASED; urgency=medium (Closes: #963493) * nfsd: apply umask on fs without ACL support (Closes: #962254) * [rt] Update to 4.19.120-rt52 + * [rt] Update to 4.19.124-rt53 -- 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 e16896840..d1b91d90e 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 94c546b56877133a33b6e344bfe3ee7f698d069a Mon Sep 17 00:00:00 2001 -Message-Id: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +From 4f310e18bbb62e33196484e72d1a7d0416189d63 Mon Sep 17 00:00:00 2001 +Message-Id: <4f310e18bbb62e33196484e72d1a7d0416189d63.1590093525.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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 3f1a9e5b2..9a566add3 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 f4ba1e096c17024b919eed42e42b95906f78e9d4 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:19 +0200 Subject: [PATCH 002/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 d9c69a8a2..74a4efdf5 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 606f1ed4ca9ae32b18b73646e197f5bccddd24e8 Mon Sep 17 00:00:00 2001 -Message-Id: <606f1ed4ca9ae32b18b73646e197f5bccddd24e8.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:20 +0200 Subject: [PATCH 003/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 420329e9d..4192305d1 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 5a68ab1574e969066b19959eea4f840184d8c234 Mon Sep 17 00:00:00 2001 -Message-Id: <5a68ab1574e969066b19959eea4f840184d8c234.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 2a57fe58c..2ff94818a 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 8c3d27d3b3cd3aecb7c92684466a2edab6702d74 Mon Sep 17 00:00:00 2001 -Message-Id: <8c3d27d3b3cd3aecb7c92684466a2edab6702d74.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 24eb6591b..8fdd796bf 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 b03704eee6d051563cf2a10bad6eb191d1199e7e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 3d6772ca4..c5f23537b 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 f1aaef6e633365e7d9ab49f80ccac5bd16ae4fa1 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 dd04b5f69..342196ece 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 9e80d0692dd5fa2ead7ea71292c9bcc52d4f41bc Mon Sep 17 00:00:00 2001 -Message-Id: <9e80d0692dd5fa2ead7ea71292c9bcc52d4f41bc.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Marc Zyngier Date: Fri, 27 Jul 2018 13:38:54 +0100 Subject: [PATCH 008/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 705f68ddb..0def24b88 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 7d31f7cf7f58f99e34da1a431615e876dbca1918 Mon Sep 17 00:00:00 2001 -Message-Id: <7d31f7cf7f58f99e34da1a431615e876dbca1918.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 07a85f348..c4dd44278 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 e3dad4d17535d9521beda4efbe2fc44795f67d7a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: =?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 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 4a0c331fe..b93c4227b 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 448b243a1fb84f0081f5652354423456e2fc0373 Mon Sep 17 00:00:00 2001 -Message-Id: <448b243a1fb84f0081f5652354423456e2fc0373.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 869dbf530..447a14326 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 3564312da18561b00498caa06842ff388bbef279 Mon Sep 17 00:00:00 2001 -Message-Id: <3564312da18561b00498caa06842ff388bbef279.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 912e0b723..cb61d3620 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 79aa953ef9dcd175074ab38896df71155ca4fc42 Mon Sep 17 00:00:00 2001 -Message-Id: <79aa953ef9dcd175074ab38896df71155ca4fc42.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Thomas Gleixner Date: Tue, 17 Jul 2018 18:25:31 +0200 Subject: [PATCH 013/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 0e687beee..62ce999a6 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 7de545a7d799671cc1910dae9275ce7c21e58da7 Mon Sep 17 00:00:00 2001 -Message-Id: <7de545a7d799671cc1910dae9275ce7c21e58da7.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz All callers of cgroup_rstat_flush_locked() acquire cgroup_rstat_lock either with spin_lock_irq() or spin_lock_irqsave(). 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 945fad8bc..f7988dcc2 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 fff6de28ff6dd3522a77ca5c667d20bc9b2086d2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 3a83eeea9..63a3f4b39 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 7b406e85875d67693cecc7cfe09a5e7180af01a5 Mon Sep 17 00:00:00 2001 -Message-Id: <7b406e85875d67693cecc7cfe09a5e7180af01a5.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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() 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 e4e59f9fd..01b7ac6d7 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 70614aac8907a90efde502dd5bf9e7916c26afb6 Mon Sep 17 00:00:00 2001 -Message-Id: <70614aac8907a90efde502dd5bf9e7916c26afb6.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 3cb01a658..b4e44b643 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 fbe5b00e47354c46adcab1cf9e19a9df96d60e8b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 46e1af7ba..c5ef9d3b5 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 065037d4d75ed96573ea0c6343fe85f0dc2f83ff Mon Sep 17 00:00:00 2001 -Message-Id: <065037d4d75ed96573ea0c6343fe85f0dc2f83ff.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 54ed3d707..65d653ad0 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 2e4aceaf2bdbd76b1fc8ed5629d29734eb3ca502 Mon Sep 17 00:00:00 2001 -Message-Id: <2e4aceaf2bdbd76b1fc8ed5629d29734eb3ca502.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 09:13:42 +0200 Subject: [PATCH 020/327] arm64: KVM: compute_layout before altenates are applied -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 8f4b112e8..91ad50fd3 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 09e6d3bbfa22914d304001c21b15f919b330c8d7 Mon Sep 17 00:00:00 2001 -Message-Id: <09e6d3bbfa22914d304001c21b15f919b330c8d7.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Fri, 31 Aug 2018 14:16:30 +0200 Subject: [PATCH 021/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 1f6c08ee4..a66010ac2 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 fbfa89ba167f66519adf09c37d8ba7972cd38e8b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 306faf3d7..70f359a08 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 f923443ca5a98d8b3208d3f04dca281fea90524d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: "Paul E. McKenney" Date: Mon, 29 Oct 2018 11:53:01 +0100 Subject: [PATCH 023/327] EXP rcu: Revert expedited GP parallelization cleverness -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 935c9c511..7f9af1f4a 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 5ffb480060a6dfc773ccd3696324297c8754242d Mon Sep 17 00:00:00 2001 -Message-Id: <5ffb480060a6dfc773ccd3696324297c8754242d.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: He Zhe Date: Wed, 19 Dec 2018 16:30:57 +0100 Subject: [PATCH 024/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 1145539da..e1360d8d6 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 e8b73ba5194e2f3d7d57b665986c8a09406d4483 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 0c0b0fb28..54652ce8a 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,7 +1,7 @@ -From c09d1e32b858b93d1a3412ca593e4b2f59218148 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 @@ -9,7 +9,7 @@ Subject: [PATCH 026/327] kernel: sched: Provide a pointer to the valid CPU 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 f29a4ff3f..02f7c2bb1 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 139cf7b485c546a3ebe3564e6c1cc1836a992210 Mon Sep 17 00:00:00 2001 -Message-Id: <139cf7b485c546a3ebe3564e6c1cc1836a992210.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 2866d96dc..345678259 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 925eb3a76af6bf2409e1a698a16fd635649510fb Mon Sep 17 00:00:00 2001 -Message-Id: <925eb3a76af6bf2409e1a698a16fd635649510fb.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Tue, 9 Oct 2018 17:34:50 +0200 Subject: [PATCH 028/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 bfbfcfc07..9f7de4777 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 a9060ecc13b1730d842179e1e994baef67a67ad9 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 45536e46d..18ebfda31 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,7 +1,7 @@ -From 157c4da19a2359aa5f6ad7be90cf289ec0b0563d Mon Sep 17 00:00:00 2001 -Message-Id: <157c4da19a2359aa5f6ad7be90cf289ec0b0563d.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Benedikt Spranger Date: Mon, 8 Mar 2010 18:57:04 +0100 Subject: [PATCH 030/327] clocksource: TCLIB: Allow higher clock rates for @@ -9,7 +9,7 @@ Subject: [PATCH 030/327] clocksource: TCLIB: Allow higher clock rates for 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 a2f65e162..87c7aadf7 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 30643112afa23900442cbdd3189874c02bc5a091 Mon Sep 17 00:00:00 2001 -Message-Id: <30643112afa23900442cbdd3189874c02bc5a091.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 f3c573d1d..a505fa3ce 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 cbd9fb5407709f0ec74da747ae0c536695fd99d2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 63d87b2c8..044da086c 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 5f7256f96320961ff13d7850dced5905b034b306 Mon Sep 17 00:00:00 2001 -Message-Id: <5f7256f96320961ff13d7850dced5905b034b306.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 207be2611..483a4347b 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 68e48cddc25a2a910412069ffba3ad451852aff9 Mon Sep 17 00:00:00 2001 -Message-Id: <68e48cddc25a2a910412069ffba3ad451852aff9.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 0e172da77..8e6f9c39e 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 05fc669340e52618fc81f50128bff56b69e76cee Mon Sep 17 00:00:00 2001 -Message-Id: <05fc669340e52618fc81f50128bff56b69e76cee.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 6ac1da5f7..7500c7704 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 6871a9d9f0f9fb7c1d05fb7a784fa22ea1d4ad79 Mon Sep 17 00:00:00 2001 -Message-Id: <6871a9d9f0f9fb7c1d05fb7a784fa22ea1d4ad79.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 7bd7102a0..5957aebc6 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 5c4696b4c4304ab06f88521a00124ea89c54c232 Mon Sep 17 00:00:00 2001 -Message-Id: <5c4696b4c4304ab06f88521a00124ea89c54c232.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 c91461279..6f2faabc7 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 4f16dc1b3805c09027ea0a66cb4ce5b1c8728857 Mon Sep 17 00:00:00 2001 -Message-Id: <4f16dc1b3805c09027ea0a66cb4ce5b1c8728857.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 11996526c..0134c1b00 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 ebaffcc127b4f2a3a4e8292068d75a6d4d86a4be Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Thomas Gleixner Date: Sun, 24 Jul 2011 12:11:43 +0200 Subject: [PATCH 039/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 7dbfd4e92..7ba48725e 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 c259ffabcd899b0caa72863f57ac9b48523af9e7 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Tue, 17 Oct 2017 16:36:18 +0200 Subject: [PATCH 040/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 e3fbef51d..315894dbf 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 a344e0d75f6f733c2febd47922a980dd114b6e8c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 100b47afd..8cf15c67c 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 73b8f03591c067230e953f05175d3218bf8286d4 Mon Sep 17 00:00:00 2001 -Message-Id: <73b8f03591c067230e953f05175d3218bf8286d4.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Thomas Gleixner Date: Sun, 17 Jul 2011 21:51:45 +0200 Subject: [PATCH 042/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 c4a12b8cd..6ab9114cd 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 80720135f27a7e65bcdf6e6d8ba6b7aaf92d6f79 Mon Sep 17 00:00:00 2001 -Message-Id: <80720135f27a7e65bcdf6e6d8ba6b7aaf92d6f79.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 1bf5945c6..7d6ce6c00 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 fda6ef2c4bdaedc6cbe018bcfc61ad84d7e94e1e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 d464b64f6..39533b728 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 c628b5bf1ee888f471438a80954d50813a981cb1 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 aee720dd2..33a9b4782 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 c01244956b4f87fb0eb7384e9f803b2792f456fe Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Sat, 27 May 2017 19:02:06 +0200 Subject: [PATCH 046/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 0e232a4fd..4f5ad4ea4 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 2380b2865c54f45e1a90d477ca35585171673264 Mon Sep 17 00:00:00 2001 -Message-Id: <2380b2865c54f45e1a90d477ca35585171673264.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 ec7abfc96..0b47514cc 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 54d3f6184f43d8339af4d52ce2945810f8378a00 Mon Sep 17 00:00:00 2001 -Message-Id: <54d3f6184f43d8339af4d52ce2945810f8378a00.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz Use generic code which uses rtmutex 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 da7be1551..072eba8b6 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 380f81e47f4aa5c13aba9365a4653ada7a863f93 Mon Sep 17 00:00:00 2001 -Message-Id: <380f81e47f4aa5c13aba9365a4653ada7a863f93.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Bogdan Purcareata Date: Fri, 24 Apr 2015 15:53:13 +0000 Subject: [PATCH 049/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 4ef2963c6..6bc9568ef 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 a87a0a78e22ce91976f859d6674bb3e78e304c92 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz The current highmem handling on -RT is not compatible and needs fixups. 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 f6853f7bd..f0691ad06 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 8bb6a4ae52df124954ab3ae4a3f48237a5bc1d69 Mon Sep 17 00:00:00 2001 -Message-Id: <8bb6a4ae52df124954ab3ae4a3f48237a5bc1d69.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 68f421819..d422cf24c 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 5911e094e0d179e9838030f203dafcb32426c5e9 Mon Sep 17 00:00:00 2001 -Message-Id: <5911e094e0d179e9838030f203dafcb32426c5e9.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 3a6a614ad..5ad2238a7 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 460db135f97d9a70b2816dd9f144f3f2c35ff377 Mon Sep 17 00:00:00 2001 -Message-Id: <460db135f97d9a70b2816dd9f144f3f2c35ff377.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 aad920201..a02415897 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 a93d761262d0879d910b5f5ce26647629208377c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 acfa852be..71cba47eb 100644 --- a/debian/patches-rt/0055-md-disable-bcache.patch +++ b/debian/patches-rt/0055-md-disable-bcache.patch @@ -1,14 +1,14 @@ -From 4577b0695f66714783f37d0405ab0c346b454932 Mon Sep 17 00:00:00 2001 -Message-Id: <4577b0695f66714783f37d0405ab0c346b454932.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Thu, 29 Aug 2013 11:48:57 +0200 Subject: [PATCH 055/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 7417d4e1c..fc0ebb121 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 c62d404a7168f5f8a35b729d4d9c2dd239749d77 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 899b3a425..e28ed008e 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 c52a01426d383f219e672d2467a5c665663be377 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 2bb599a0e..4f47a4c4f 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 4bff794a89e6457eb993efdf28add5adc54c7c67 Mon Sep 17 00:00:00 2001 -Message-Id: <4bff794a89e6457eb993efdf28add5adc54c7c67.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Peter Zijlstra Date: Fri, 2 Sep 2011 14:41:29 +0200 Subject: [PATCH 058/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 078b52f90..f46d1a4bf 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 dd900385018514a60bcc9360375c61a5410c61ba Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 177a2fc02..d03093c85 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 4167e3164bcb032ee75d8bf13ad7a738efda1089 Mon Sep 17 00:00:00 2001 -Message-Id: <4167e3164bcb032ee75d8bf13ad7a738efda1089.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Thomas Gleixner Date: Wed, 8 Mar 2017 14:23:35 +0100 Subject: [PATCH 060/327] futex: workaround migrate_disable/enable in different context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 f227b3ac3..6cfef7ef3 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 9f6ecffc6d635246096f7ec3969d41610a935758 Mon Sep 17 00:00:00 2001 -Message-Id: <9f6ecffc6d635246096f7ec3969d41610a935758.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 619d1ab97..8c12743cf 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 fb993bc3f80687fab2eeca35f423f962c0b4fab2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 3b443393e..57dcaf145 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 e7231e5dd20630c1cafcbd17ac28158f6b83df67 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 9194e9a7e..c4f9c4c0f 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 6142215abb31c009bcb3fade2ad2a2d08e8b83d3 Mon Sep 17 00:00:00 2001 -Message-Id: <6142215abb31c009bcb3fade2ad2a2d08e8b83d3.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 f68aa7c57..a3bbeb3d8 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 e314282c5471e279928516be35ffa9bb2cc119f6 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 dc5181d99..c83f38dd4 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 b08a29a9d276cd58847e046d0adc6e8b7870bc67 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 ac76dbd01..48ebdfe20 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 48ab2622802d5673b7a70938e105302459a1cf0c Mon Sep 17 00:00:00 2001 -Message-Id: <48ab2622802d5673b7a70938e105302459a1cf0c.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 rt safe -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 713fc5262..637e13575 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 57cc0b8d65688453d22cf66aba450d1eb5a8c98a Mon Sep 17 00:00:00 2001 -Message-Id: <57cc0b8d65688453d22cf66aba450d1eb5a8c98a.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 b94d61d8b..8e0d49a93 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 e3aad949c572926872e1fb2d6c943cc0d74f51ef Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 83af85af5..5844c88da 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 2a9efdf100596f35e61e0f712b68f5bda3dc7b99 Mon Sep 17 00:00:00 2001 -Message-Id: <2a9efdf100596f35e61e0f712b68f5bda3dc7b99.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 ddb4efe98..0eaa3b4eb 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 8de462e06c1de7e3cc9b0eaa6d5c6f7368c22b6f Mon Sep 17 00:00:00 2001 -Message-Id: <8de462e06c1de7e3cc9b0eaa6d5c6f7368c22b6f.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 1d84c43ea..3d195d63d 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 70454fd8a8f7c8caa65becb67bb179cfe4ebce8a Mon Sep 17 00:00:00 2001 -Message-Id: <70454fd8a8f7c8caa65becb67bb179cfe4ebce8a.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 PCP list #1 -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz Split the IRQ-off section while accessing the PCP list from zone->lock while freeing pages. @@ -21,7 +21,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 52 insertions(+), 30 deletions(-) diff --git a/mm/page_alloc.c b/mm/page_alloc.c -index 57888cedf244..b8138a5d6ef3 100644 +index d8c3051387d1..2a543a376a40 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -1095,7 +1095,7 @@ static inline void prefetch_buddy(struct page *page) @@ -115,7 +115,7 @@ index 57888cedf244..b8138a5d6ef3 100644 } static void free_one_page(struct zone *zone, -@@ -2544,13 +2551,18 @@ void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp) +@@ -2545,13 +2552,18 @@ void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp) { unsigned long flags; int to_drain, batch; @@ -135,7 +135,7 @@ index 57888cedf244..b8138a5d6ef3 100644 } #endif -@@ -2566,14 +2578,21 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) +@@ -2567,14 +2579,21 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) unsigned long flags; struct per_cpu_pageset *pset; struct per_cpu_pages *pcp; @@ -159,7 +159,7 @@ index 57888cedf244..b8138a5d6ef3 100644 } /* -@@ -2795,7 +2814,10 @@ static void free_unref_page_commit(struct page *page, unsigned long pfn) +@@ -2796,7 +2815,10 @@ static void free_unref_page_commit(struct page *page, unsigned long pfn) pcp->count++; if (pcp->count >= pcp->high) { unsigned long batch = READ_ONCE(pcp->batch); 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 4253afd62..fbbe3a416 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 1f4423aeb9a88fef1113af43d1694859d2361e3e Mon Sep 17 00:00:00 2001 -Message-Id: <1f4423aeb9a88fef1113af43d1694859d2361e3e.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 PCP list #2 -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz Split the IRQ-off section while accessing the PCP list from zone->lock while freeing pages. @@ -21,7 +21,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 50 insertions(+), 10 deletions(-) diff --git a/mm/page_alloc.c b/mm/page_alloc.c -index b8138a5d6ef3..19f274de32f0 100644 +index 2a543a376a40..62b39e3e5cea 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -1105,8 +1105,8 @@ static inline void prefetch_buddy(struct page *page) @@ -63,7 +63,7 @@ index b8138a5d6ef3..19f274de32f0 100644 __free_one_page(page, page_to_pfn(page), zone, 0, mt); trace_mm_page_pcpu_drain(page, 0, mt); } -@@ -2562,7 +2577,7 @@ void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp) +@@ -2563,7 +2578,7 @@ void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp) local_irq_restore(flags); if (to_drain > 0) @@ -72,7 +72,7 @@ index b8138a5d6ef3..19f274de32f0 100644 } #endif -@@ -2592,7 +2607,7 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) +@@ -2593,7 +2608,7 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) local_irq_restore(flags); if (count) @@ -81,7 +81,7 @@ index b8138a5d6ef3..19f274de32f0 100644 } /* -@@ -2785,7 +2800,8 @@ static bool free_unref_page_prepare(struct page *page, unsigned long pfn) +@@ -2786,7 +2801,8 @@ static bool free_unref_page_prepare(struct page *page, unsigned long pfn) return true; } @@ -91,7 +91,7 @@ index b8138a5d6ef3..19f274de32f0 100644 { struct zone *zone = page_zone(page); struct per_cpu_pages *pcp; -@@ -2814,10 +2830,8 @@ static void free_unref_page_commit(struct page *page, unsigned long pfn) +@@ -2815,10 +2831,8 @@ static void free_unref_page_commit(struct page *page, unsigned long pfn) pcp->count++; if (pcp->count >= pcp->high) { unsigned long batch = READ_ONCE(pcp->batch); @@ -103,7 +103,7 @@ index b8138a5d6ef3..19f274de32f0 100644 } } -@@ -2828,13 +2842,17 @@ void free_unref_page(struct page *page) +@@ -2829,13 +2843,17 @@ void free_unref_page(struct page *page) { unsigned long flags; unsigned long pfn = page_to_pfn(page); @@ -122,7 +122,7 @@ index b8138a5d6ef3..19f274de32f0 100644 } /* -@@ -2845,6 +2863,11 @@ void free_unref_page_list(struct list_head *list) +@@ -2846,6 +2864,11 @@ void free_unref_page_list(struct list_head *list) struct page *page, *next; unsigned long flags, pfn; int batch_count = 0; @@ -134,7 +134,7 @@ index b8138a5d6ef3..19f274de32f0 100644 /* Prepare pages for freeing */ list_for_each_entry_safe(page, next, list, lru) { -@@ -2857,10 +2880,12 @@ void free_unref_page_list(struct list_head *list) +@@ -2858,10 +2881,12 @@ void free_unref_page_list(struct list_head *list) local_irq_save(flags); list_for_each_entry_safe(page, next, list, lru) { unsigned long pfn = page_private(page); @@ -148,7 +148,7 @@ index b8138a5d6ef3..19f274de32f0 100644 /* * Guard against excessive IRQ disabled times when we get -@@ -2873,6 +2898,21 @@ void free_unref_page_list(struct list_head *list) +@@ -2874,6 +2899,21 @@ void free_unref_page_list(struct list_head *list) } } local_irq_restore(flags); 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 fb08e4acc..5ead99f78 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 70c54093e553bef72c4d5a174f1590eea0e8dfdb Mon Sep 17 00:00:00 2001 -Message-Id: <70c54093e553bef72c4d5a174f1590eea0e8dfdb.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 e75b4aa91..ea1ab87fb 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 6f6587f18a69bb2cc89c39e1eef158658ef63e62 Mon Sep 17 00:00:00 2001 -Message-Id: <6f6587f18a69bb2cc89c39e1eef158658ef63e62.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 regions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 1d8be3406..1ab2c4d68 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 5c03bb8685149b61919cf8bf3a273e9a3e4e7634 Mon Sep 17 00:00:00 2001 -Message-Id: <5c03bb8685149b61919cf8bf3a273e9a3e4e7634.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz rt-friendly per-cpu pages: convert the irqs-off per-cpu locking method into a preemptible, explicit-per-cpu-locks method. @@ -21,7 +21,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 43 insertions(+), 20 deletions(-) diff --git a/mm/page_alloc.c b/mm/page_alloc.c -index 19f274de32f0..4180a5312060 100644 +index 62b39e3e5cea..0aad0dbd8bf4 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -60,6 +60,7 @@ @@ -64,7 +64,7 @@ index 19f274de32f0..4180a5312060 100644 } static void __init __free_pages_boot_core(struct page *page, unsigned int order) -@@ -2568,13 +2581,13 @@ void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp) +@@ -2569,13 +2582,13 @@ void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp) int to_drain, batch; LIST_HEAD(dst); @@ -80,7 +80,7 @@ index 19f274de32f0..4180a5312060 100644 if (to_drain > 0) free_pcppages_bulk(zone, &dst, false); -@@ -2596,7 +2609,7 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) +@@ -2597,7 +2610,7 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) LIST_HEAD(dst); int count; @@ -89,7 +89,7 @@ index 19f274de32f0..4180a5312060 100644 pset = per_cpu_ptr(zone->pageset, cpu); pcp = &pset->pcp; -@@ -2604,7 +2617,7 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) +@@ -2605,7 +2618,7 @@ static void drain_pages_zone(unsigned int cpu, struct zone *zone) if (count) isolate_pcp_pages(count, pcp, &dst); @@ -98,7 +98,7 @@ index 19f274de32f0..4180a5312060 100644 if (count) free_pcppages_bulk(zone, &dst, false); -@@ -2642,6 +2655,7 @@ void drain_local_pages(struct zone *zone) +@@ -2643,6 +2656,7 @@ void drain_local_pages(struct zone *zone) drain_pages(cpu); } @@ -106,7 +106,7 @@ index 19f274de32f0..4180a5312060 100644 static void drain_local_pages_wq(struct work_struct *work) { /* -@@ -2655,6 +2669,7 @@ static void drain_local_pages_wq(struct work_struct *work) +@@ -2656,6 +2670,7 @@ static void drain_local_pages_wq(struct work_struct *work) drain_local_pages(NULL); preempt_enable(); } @@ -114,7 +114,7 @@ index 19f274de32f0..4180a5312060 100644 /* * Spill all the per-cpu pages from all CPUs back into the buddy allocator. -@@ -2721,7 +2736,14 @@ void drain_all_pages(struct zone *zone) +@@ -2722,7 +2737,14 @@ void drain_all_pages(struct zone *zone) else cpumask_clear_cpu(cpu, &cpus_with_pcps); } @@ -130,7 +130,7 @@ index 19f274de32f0..4180a5312060 100644 for_each_cpu(cpu, &cpus_with_pcps) { struct work_struct *work = per_cpu_ptr(&pcpu_drain, cpu); INIT_WORK(work, drain_local_pages_wq); -@@ -2729,6 +2751,7 @@ void drain_all_pages(struct zone *zone) +@@ -2730,6 +2752,7 @@ void drain_all_pages(struct zone *zone) } for_each_cpu(cpu, &cpus_with_pcps) flush_work(per_cpu_ptr(&pcpu_drain, cpu)); @@ -138,7 +138,7 @@ index 19f274de32f0..4180a5312060 100644 mutex_unlock(&pcpu_drain_mutex); } -@@ -2848,9 +2871,9 @@ void free_unref_page(struct page *page) +@@ -2849,9 +2872,9 @@ void free_unref_page(struct page *page) if (!free_unref_page_prepare(page, pfn)) return; @@ -150,7 +150,7 @@ index 19f274de32f0..4180a5312060 100644 if (!list_empty(&dst)) free_pcppages_bulk(zone, &dst, false); } -@@ -2877,7 +2900,7 @@ void free_unref_page_list(struct list_head *list) +@@ -2878,7 +2901,7 @@ void free_unref_page_list(struct list_head *list) set_page_private(page, pfn); } @@ -159,7 +159,7 @@ index 19f274de32f0..4180a5312060 100644 list_for_each_entry_safe(page, next, list, lru) { unsigned long pfn = page_private(page); enum zone_type type; -@@ -2892,12 +2915,12 @@ void free_unref_page_list(struct list_head *list) +@@ -2893,12 +2916,12 @@ void free_unref_page_list(struct list_head *list) * a large list of pages to free. */ if (++batch_count == SWAP_CLUSTER_MAX) { @@ -175,7 +175,7 @@ index 19f274de32f0..4180a5312060 100644 for (i = 0; i < __MAX_NR_ZONES; ) { struct page *page; -@@ -3046,7 +3069,7 @@ static struct page *rmqueue_pcplist(struct zone *preferred_zone, +@@ -3047,7 +3070,7 @@ static struct page *rmqueue_pcplist(struct zone *preferred_zone, struct page *page; unsigned long flags; @@ -184,7 +184,7 @@ index 19f274de32f0..4180a5312060 100644 pcp = &this_cpu_ptr(zone->pageset)->pcp; list = &pcp->lists[migratetype]; page = __rmqueue_pcplist(zone, migratetype, pcp, list); -@@ -3054,7 +3077,7 @@ static struct page *rmqueue_pcplist(struct zone *preferred_zone, +@@ -3055,7 +3078,7 @@ static struct page *rmqueue_pcplist(struct zone *preferred_zone, __count_zid_vm_events(PGALLOC, page_zonenum(page), 1 << order); zone_statistics(preferred_zone, zone); } @@ -193,7 +193,7 @@ index 19f274de32f0..4180a5312060 100644 return page; } -@@ -3081,7 +3104,7 @@ struct page *rmqueue(struct zone *preferred_zone, +@@ -3082,7 +3105,7 @@ struct page *rmqueue(struct zone *preferred_zone, * allocate greater than order-1 page units with __GFP_NOFAIL. */ WARN_ON_ONCE((gfp_flags & __GFP_NOFAIL) && (order > 1)); @@ -202,7 +202,7 @@ index 19f274de32f0..4180a5312060 100644 do { page = NULL; -@@ -3101,14 +3124,14 @@ struct page *rmqueue(struct zone *preferred_zone, +@@ -3102,14 +3125,14 @@ struct page *rmqueue(struct zone *preferred_zone, __count_zid_vm_events(PGALLOC, page_zonenum(page), 1 << order); zone_statistics(preferred_zone, zone); @@ -219,7 +219,7 @@ index 19f274de32f0..4180a5312060 100644 return NULL; } -@@ -8129,7 +8152,7 @@ void zone_pcp_reset(struct zone *zone) +@@ -8130,7 +8153,7 @@ void zone_pcp_reset(struct zone *zone) struct per_cpu_pageset *pset; /* avoid races with drain_pages() */ @@ -228,7 +228,7 @@ index 19f274de32f0..4180a5312060 100644 if (zone->pageset != &boot_pageset) { for_each_online_cpu(cpu) { pset = per_cpu_ptr(zone->pageset, cpu); -@@ -8138,7 +8161,7 @@ void zone_pcp_reset(struct zone *zone) +@@ -8139,7 +8162,7 @@ void zone_pcp_reset(struct zone *zone) free_percpu(zone->pageset); zone->pageset = &boot_pageset; } 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 0e8977e20..67a67f2c2 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 8db6812f18080154df9d8679ce16af51a8ba4fe3 Mon Sep 17 00:00:00 2001 -Message-Id: <8db6812f18080154df9d8679ce16af51a8ba4fe3.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz Replace global locks (get_cpu + local_irq_save) with "local_locks()". Currently there is one of for "rotate" and one for "swap". @@ -59,10 +59,10 @@ index 5079ddbec8f9..c40d3a13cbbd 100644 cc->last_migrated_pfn = 0; } diff --git a/mm/page_alloc.c b/mm/page_alloc.c -index 4180a5312060..889b4089b289 100644 +index 0aad0dbd8bf4..98abae7e843e 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c -@@ -7242,8 +7242,9 @@ void __init free_area_init(unsigned long *zones_size) +@@ -7243,8 +7243,9 @@ void __init free_area_init(unsigned long *zones_size) static int page_alloc_cpu_dead(unsigned int cpu) { 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 3c26c0418..3b1bfb1d9 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 919fb5c7ab71b28ea96b7f83055b52fcc5c9119c Mon Sep 17 00:00:00 2001 -Message-Id: <919fb5c7ab71b28ea96b7f83055b52fcc5c9119c.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 e0ac49eb1..687315cab 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 36be6e4e76ea93741b345abb97d40b48eab57cac Mon Sep 17 00:00:00 2001 -Message-Id: <36be6e4e76ea93741b345abb97d40b48eab57cac.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Ingo Molnar Date: Fri, 3 Jul 2009 08:30:13 -0500 Subject: [PATCH 079/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 38fa7c0a6..d63b73d97 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 d904f1ae3ddf7b7f19c043f65a1dc8f681cdc4aa Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Frank Rowand Date: Sat, 1 Oct 2011 18:58:13 -0700 Subject: [PATCH 080/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 a8fd25b41..ec16c21fd 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 43968d25f34cc0c7e453f17c63fa23dc50bccff6 Mon Sep 17 00:00:00 2001 -Message-Id: <43968d25f34cc0c7e453f17c63fa23dc50bccff6.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 c7eeb73a4..898939340 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 ac660441fdc328b4e835f6a2eb15ba2a9ae56a73 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 fb0f083e0..18efeb664 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 3f101e56bfa35092043bc11d64e199792ef0234b Mon Sep 17 00:00:00 2001 -Message-Id: <3f101e56bfa35092043bc11d64e199792ef0234b.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 ad9c9c6d7..6e9ef850f 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 4acb7f24767f76d8499f2818c8c823db0dcaedce Mon Sep 17 00:00:00 2001 -Message-Id: <4acb7f24767f76d8499f2818c8c823db0dcaedce.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Yang Shi Date: Wed, 30 Oct 2013 11:48:33 -0700 Subject: [PATCH 084/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 7f16191b7..cabbca4e2 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 a6498df708e70b00c5b0dc27ae24bec3bb4544f8 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Wed, 28 Jan 2015 17:14:16 +0100 Subject: [PATCH 085/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 d67b792af..65a6bb0ed 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 5435ab24adf4b67ad5116ebc31ebfaf2ad9dc386 Mon Sep 17 00:00:00 2001 -Message-Id: <5435ab24adf4b67ad5116ebc31ebfaf2ad9dc386.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 a3249ebe5..6b9620516 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 ebc47cf9b47497d1cd89845dce7a4a51a6da1f45 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Tue, 11 Dec 2018 21:53:43 +0100 Subject: [PATCH 087/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 dd2482b17..891d1243e 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 905387933bea4aee6079cb329a06a8a30481f092 Mon Sep 17 00:00:00 2001 -Message-Id: <905387933bea4aee6079cb329a06a8a30481f092.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 32abf2aa4..01f89e776 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 d4eec20885c0c2a25d3ee5d83464077e0b77ca13 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 172e7cca3..c320eb99c 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 17b7ebb5784c83799e57c61008f6f618f901ac3c Mon Sep 17 00:00:00 2001 -Message-Id: <17b7ebb5784c83799e57c61008f6f618f901ac3c.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz Non constant TSC is a nightmare on bare metal already, but with virtualization it becomes a complete disaster because the workarounds @@ -18,7 +18,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 7 insertions(+) diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c -index 6bfc9eaf8dee..166eaf163324 100644 +index b0fd24ee08d2..dc1d536a86ba 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -6877,6 +6877,13 @@ int kvm_arch_init(void *opaque) 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 0ba343ef1..d9677e4f2 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 a8dd4b63ac98dd63230cfee544da29c6c7c875e6 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 1fad8d348..2ef611a47 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 c0653cc1d3e43bd0e43f3fee9dafb456ed28190a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Mon, 28 Oct 2013 12:19:57 +0100 Subject: [PATCH 092/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 5ff92fb3b..ec5055248 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 9e18254d6c03db9399865a50b4742d362e613d74 Mon Sep 17 00:00:00 2001 -Message-Id: <9e18254d6c03db9399865a50b4742d362e613d74.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 48d0efe52..9a1fd0aef 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 8491c30bd13faf3015ca096ea7eb516275f42829 Mon Sep 17 00:00:00 2001 -Message-Id: <8491c30bd13faf3015ca096ea7eb516275f42829.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Mon, 10 Sep 2018 18:00:31 +0200 Subject: [PATCH 094/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 281eb0bce..d22359710 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 ff3fe1c0c7ede76e82b6bcae4929af93851e4bbc Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz Completions have no long lasting callbacks and therefor do not need the complex waitqueue variant. Use simple waitqueues which reduces the @@ -164,7 +164,7 @@ index 73e06e9986d4..f426a0661aa0 100644 extern long prepare_to_swait_event(struct swait_queue_head *q, struct swait_queue *wait, int state); diff --git a/kernel/power/hibernate.c b/kernel/power/hibernate.c -index f5ce9f7ec132..0f00ba01376f 100644 +index 537a2a3c1dea..5b1c16500d07 100644 --- a/kernel/power/hibernate.c +++ b/kernel/power/hibernate.c @@ -690,6 +690,10 @@ static int load_image_and_restore(void) 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 504ede051..68deb42bb 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 d559faa98e79d0b61a303cf6d6c537f4d689ab47 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 65e3476b2..0d4d065f6 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 b441e3f0879e664e8a57feb984aca62a3e9fc16a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Wed, 15 Nov 2017 17:29:51 +0100 Subject: [PATCH 097/327] time/hrtimer: avoid schedule_work() with interrupts disabled -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 c4d5835c8..028ea91b4 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 9edffccea750b6ec0ab51d8e3937a13fde2cd4da Mon Sep 17 00:00:00 2001 -Message-Id: <9edffccea750b6ec0ab51d8e3937a13fde2cd4da.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Tue, 3 Jul 2018 11:25:41 +0200 Subject: [PATCH 098/327] hrtimer: consolidate hrtimer_init() + hrtimer_init_sleeper() calls -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 cf84afa87..637b7fa0f 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 06cbb8d5488d87cdbe5aee4ae8a6da12174d6855 Mon Sep 17 00:00:00 2001 -Message-Id: <06cbb8d5488d87cdbe5aee4ae8a6da12174d6855.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 8556b22eb..71b259986 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 12f39aa1a76582c4859f698a9da3718435915530 Mon Sep 17 00:00:00 2001 -Message-Id: <12f39aa1a76582c4859f698a9da3718435915530.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Fri, 3 Jul 2009 08:44:31 -0500 Subject: [PATCH 100/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 37cd3a2e6..edea39b02 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 b6d871ce2f3bf0aa834270504ea41ce04ffa4568 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 6a742b0d6..84865f51e 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 9077421b81d7d8416255378c63f3af858ccc6a48 Mon Sep 17 00:00:00 2001 -Message-Id: <9077421b81d7d8416255378c63f3af858ccc6a48.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 3f9b7cbc6..50b471d33 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 2b97b3a792f4099621f1986b820650f0a775aff2 Mon Sep 17 00:00:00 2001 -Message-Id: <2b97b3a792f4099621f1986b820650f0a775aff2.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Thu, 6 Dec 2018 10:15:13 +0100 Subject: [PATCH 103/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 ca3d5d789..9ed99a1eb 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 0cb59b04e24b45a80cd395bcdb7816a79005c66a Mon Sep 17 00:00:00 2001 -Message-Id: <0cb59b04e24b45a80cd395bcdb7816a79005c66a.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 606b249be..fa29e99cb 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 ac273456b5dd89be9b9b094687bc91fbec5ab7e4 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 3293f0d35..0c33def36 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 4bd7e2a1c07e3ae8d49fc8b5f45a61dd630a9b45 Mon Sep 17 00:00:00 2001 -Message-Id: <4bd7e2a1c07e3ae8d49fc8b5f45a61dd630a9b45.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 a39390bc3..c66e63b03 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 e10e3f01658879df9a140ebc1fa6a833306d205b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 a0e12bf72..01dee5048 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 b130de87f13cecffd99e3bef73cf43e41bf3735f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Mon, 21 Nov 2016 19:31:08 +0100 Subject: [PATCH 108/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 2d87dfa9f..ee0c35911 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 06dbc7b47e3c61b393a1a5d4df735ef17dd71782 Mon Sep 17 00:00:00 2001 -Message-Id: <06dbc7b47e3c61b393a1a5d4df735ef17dd71782.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Thomas Gleixner Date: Sat, 25 Jun 2011 09:21:04 +0200 Subject: [PATCH 109/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 29e95dd2a..f5ed27cf7 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 43f68c55c3b13d255be2f0c794673f8e9a7adca0 Mon Sep 17 00:00:00 2001 -Message-Id: <43f68c55c3b13d255be2f0c794673f8e9a7adca0.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 might_sleep() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 b24d4efb7..b7fc56bdf 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 c3d5e26fee97bdf9e8f7c6667e4e1a58585b41f5 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 f78a4f54f..e8e91b3c5 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 736af57f8829849f1b10042f7ed84952e6d13618 Mon Sep 17 00:00:00 2001 -Message-Id: <736af57f8829849f1b10042f7ed84952e6d13618.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 5f721504c..0b89b1024 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 84ad34b48591ce857eeef88bf4f16997e18bf143 Mon Sep 17 00:00:00 2001 -Message-Id: <84ad34b48591ce857eeef88bf4f16997e18bf143.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Steven Rostedt Date: Mon, 18 Mar 2013 15:12:49 -0400 Subject: [PATCH 113/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 3ff8af063..f4b69c002 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 4565f5f72adec71306213058dafdf1cef42ac060 Mon Sep 17 00:00:00 2001 -Message-Id: <4565f5f72adec71306213058dafdf1cef42ac060.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 enabling/disabling migration -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 c7f812834..b1ccab832 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 09bf70d9e6db271e5f93dbfbc7f0d8479cccbce3 Mon Sep 17 00:00:00 2001 -Message-Id: <09bf70d9e6db271e5f93dbfbc7f0d8479cccbce3.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 46e36b9b4..34d0fd542 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 7b1ff832adbdc5ee8eb2f772a90975c9f56bbf14 Mon Sep 17 00:00:00 2001 -Message-Id: <7b1ff832adbdc5ee8eb2f772a90975c9f56bbf14.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz Signed-off-by: Thomas Gleixner --- @@ -29,7 +29,7 @@ index 0643c083ed86..1cc4d2da954c 100644 #define TRACE_EVENT_TYPE_MAX \ diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c -index c41f7d1ab5fa..1fac8a2de78f 100644 +index 4966410bb0f4..a7b187f74f34 100644 --- a/kernel/trace/trace.c +++ b/kernel/trace/trace.c @@ -2151,6 +2151,8 @@ tracing_generic_entry_update(struct trace_entry *entry, unsigned long flags, 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 10840d578..289cb13ef 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 8571380c6cad699003ce1b1322bb673e5ee32525 Mon Sep 17 00:00:00 2001 -Message-Id: <8571380c6cad699003ce1b1322bb673e5ee32525.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 613d89c0b..4eea5b4f4 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 0f8c73a41cc21e19f3cd6bf007535734425b6e3e Mon Sep 17 00:00:00 2001 -Message-Id: <0f8c73a41cc21e19f3cd6bf007535734425b6e3e.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Ingo Molnar Date: Tue, 29 Nov 2011 20:18:22 -0500 Subject: [PATCH 118/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 da89b32a2..7e35f7450 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 f0075d43b45fbc244844c63f364e7b2461e72a0a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 426635e188fc..e1b0618e231e 100644 +index 9ccc14200b80..a109f1acd3a0 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -2727,6 +2727,7 @@ static void __netif_reschedule(struct Qdisc *q) @@ -170,7 +170,7 @@ index 426635e188fc..e1b0618e231e 100644 } EXPORT_SYMBOL(__napi_schedule); -@@ -9489,6 +9495,7 @@ static int dev_cpu_dead(unsigned int oldcpu) +@@ -9491,6 +9497,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 faf765fda..90810a65a 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 9e86dd147e8ddd3b1ad01b287979c781e4583224 Mon Sep 17 00:00:00 2001 -Message-Id: <9e86dd147e8ddd3b1ad01b287979c781e4583224.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz Disable extra stacks for softirqs. We want to preempt softirqs and having them on special IRQ-stack does not make this easier. @@ -123,10 +123,10 @@ index 713670e6d13d..5dfc715343f9 100644 #ifdef CONFIG_HOTPLUG_CPU void fixup_irqs(void) diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S -index ccb5e3486aee..7ffd83c57ef2 100644 +index dfe26f3cfffc..f53d995b1370 100644 --- a/arch/x86/entry/entry_64.S +++ b/arch/x86/entry/entry_64.S -@@ -1083,6 +1083,7 @@ bad_gs: +@@ -1084,6 +1084,7 @@ bad_gs: jmp 2b .previous @@ -134,7 +134,7 @@ index ccb5e3486aee..7ffd83c57ef2 100644 /* Call softirq on interrupt stack. Interrupts are off. */ ENTRY(do_softirq_own_stack) pushq %rbp -@@ -1093,6 +1094,7 @@ ENTRY(do_softirq_own_stack) +@@ -1094,6 +1095,7 @@ ENTRY(do_softirq_own_stack) leaveq ret ENDPROC(do_softirq_own_stack) diff --git a/debian/patches-rt/0121-softirq-Split-softirq-locks.patch b/debian/patches-rt/0121-softirq-Split-softirq-locks.patch index bf4a96dce..c34c7c221 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 b235e2305fdffaf44c89c88e619e3454aa379a5f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 @@ -202,7 +202,7 @@ index 42846a65df9a..30895ae9e82d 100644 #define PF_EXITING 0x00000004 /* Getting shut down */ #define PF_EXITPIDONE 0x00000008 /* PI exit done on shut down */ diff --git a/init/main.c b/init/main.c -index 38a603f62b7b..6e02188386a7 100644 +index ec78f2312610..7c064c6aff55 100644 --- a/init/main.c +++ b/init/main.c @@ -560,6 +560,7 @@ asmlinkage __visible void __init start_kernel(void) 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 37d911ae5..1feb6fd60 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 dddf06fedee6ba0e9cc8d0190602fb8997b02d46 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 e1b0618e231e..0285ea11a788 100644 +index a109f1acd3a0..c5901d343d0a 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 c4eb2cdd9..cdd11f2a7 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 674a3349419deac69b7d910ea8b7bc0d1fe74345 Mon Sep 17 00:00:00 2001 -Message-Id: <674a3349419deac69b7d910ea8b7bc0d1fe74345.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Thomas Gleixner Date: Tue, 31 Jan 2012 13:01:27 +0100 Subject: [PATCH 123/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 1bb7fee7c..7d75494d8 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 b0e0ebc73a36ee8775266c92bcfbd7fe099ccac6 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 de24cd2d0..6a10dc009 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 0f2aac697da6c7a4e8c705f76fd9a745c7b8b5a9 Mon Sep 17 00:00:00 2001 -Message-Id: <0f2aac697da6c7a4e8c705f76fd9a745c7b8b5a9.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Mon, 18 Feb 2019 13:19:59 +0100 Subject: [PATCH 125/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 adacb6fa8..669ba0383 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 f07757f81d35f9cbaee287b5eabb7bbe9e0298d8 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Tue, 19 Feb 2019 16:49:29 +0100 Subject: [PATCH 126/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 5f78cd2e9..71a11c01a 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 005706af111e1fc4b9b316e4a6736d0fdb5ea0d9 Mon Sep 17 00:00:00 2001 -Message-Id: <005706af111e1fc4b9b316e4a6736d0fdb5ea0d9.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 d508fa8cc..39f66bb4d 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 e746beb20a46175c355c737e8181f89ecf105400 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 01393cf82..9bcf4cade 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 a3e55790c1c9490150de3e93b4e2810d7d5eb965 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 1a7339dfd..0035da9fe 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 f2ca4d9cb2113ba369f0716b2477b913dfcb3543 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 d824c8187..0d824ed16 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 1d84f8d3fb288f896e08d93a418892df9e3d910c Mon Sep 17 00:00:00 2001 -Message-Id: <1d84f8d3fb288f896e08d93a418892df9e3d910c.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Thomas Gleixner Date: Fri, 1 Mar 2013 11:17:42 +0100 Subject: [PATCH 131/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 22f6b9c8d..ea0ddbda2 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 48464789e57bdd127279a41db126d18101581c93 Mon Sep 17 00:00:00 2001 -Message-Id: <48464789e57bdd127279a41db126d18101581c93.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 cc2cea2be..cde24f20f 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 a47ed74947403d7e564ba5f2d6888701ff728b21 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 b8efe115f..1aefe36e7 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 d08a6afe831e619cca789594e8b77bf5f755bd6a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: "Wolfgang M. Reimer" Date: Tue, 21 Jul 2015 16:20:07 +0200 Subject: [PATCH 134/327] locking: locktorture: Do NOT include rwlock.h directly -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 916f297e6..e8b9567cf 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 b73a272cb3b9510c0f8ba239c1d111127edaf442 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 5395c21a4..634e0c87c 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 b2bcd460da9efcea6eb253a42e7b9b40d83f87fe Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 eaf7a3006..cbb4abbb6 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 052ae080585d0e500348d996348b86711e3747b4 Mon Sep 17 00:00:00 2001 -Message-Id: <052ae080585d0e500348d996348b86711e3747b4.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 84cbf4ef2..1ada7eccf 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 058f3288007e8ca9efd8455d8b1d9f9648b2179f Mon Sep 17 00:00:00 2001 -Message-Id: <058f3288007e8ca9efd8455d8b1d9f9648b2179f.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 ded122e55..7879977f4 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 32ba7416d5cd9967803dab55255f6f11dfddc344 Mon Sep 17 00:00:00 2001 -Message-Id: <32ba7416d5cd9967803dab55255f6f11dfddc344.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 16:56:02 +0100 Subject: [PATCH 139/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 8fc89f5fe..75ce7edae 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 7ccedbfac836ed42081e1d575cc44efb80e313a5 Mon Sep 17 00:00:00 2001 -Message-Id: <7ccedbfac836ed42081e1d575cc44efb80e313a5.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 91e1abbe8..f8b4d0db3 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 de9c57bfea054f4cc0788a50ab5c0ce7166b59b1 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Thomas Gleixner Date: Thu, 12 Oct 2017 16:36:39 +0200 Subject: [PATCH 141/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 04f0784d8..dbf0fdfa6 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 5aa02edaba5d2f35a437de770dac87e498b134c4 Mon Sep 17 00:00:00 2001 -Message-Id: <5aa02edaba5d2f35a437de770dac87e498b134c4.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 5935a499c..3b0595f5c 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 6355bbb9427dc916be52ca71e9e32d33e7fc5bc4 Mon Sep 17 00:00:00 2001 -Message-Id: <6355bbb9427dc916be52ca71e9e32d33e7fc5bc4.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 64ad24122..4fbf99098 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 72c52b3d53f9a8ffbfaa3820237dd04dd13ab2b7 Mon Sep 17 00:00:00 2001 -Message-Id: <72c52b3d53f9a8ffbfaa3820237dd04dd13ab2b7.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 d0d4d848c..be5c7728b 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 56305d86f046828c4a67051025437ea09a20804d Mon Sep 17 00:00:00 2001 -Message-Id: <56305d86f046828c4a67051025437ea09a20804d.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 a40cc47fe..23dbd30db 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 54e4d9eea44c2049d36141f662848cc069e0970e Mon Sep 17 00:00:00 2001 -Message-Id: <54e4d9eea44c2049d36141f662848cc069e0970e.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 9d1ea8b0e..8781c6bc4 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 bb46e4ae14099068f1c053ac7ec806290b32cf6d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 7ba0c6d23..34393430b 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 276f1bb9886b48d3e86f7cda80f4f5f4955a3c69 Mon Sep 17 00:00:00 2001 -Message-Id: <276f1bb9886b48d3e86f7cda80f4f5f4955a3c69.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 32a56896f..626c74952 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 92a9890eaac73f4208352afb16de0bea72bd4867 Mon Sep 17 00:00:00 2001 -Message-Id: <92a9890eaac73f4208352afb16de0bea72bd4867.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 c5a1a7160..4c82f025b 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 e50dc2d16eb0856f23296afc37c81d056d27be5c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Mikulas Patocka Date: Mon, 13 Nov 2017 12:56:53 -0500 Subject: [PATCH 150/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 35d57d4d0..1246a577d 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 5ed8bca72547bc6b4ea93b356bafb784c3c6fd1b Mon Sep 17 00:00:00 2001 -Message-Id: <5ed8bca72547bc6b4ea93b356bafb784c3c6fd1b.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 2e75daac7..9c15248ba 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 8e48bd288e4a0d386891d2a60eb2a2b5d360f2e0 Mon Sep 17 00:00:00 2001 -Message-Id: <8e48bd288e4a0d386891d2a60eb2a2b5d360f2e0.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Thu, 16 Nov 2017 16:48:48 +0100 Subject: [PATCH 152/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 bb744f928..e49b92e58 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 7c8a05b1504ccad35d1c11e58fbcd0ea12f3691c Mon Sep 17 00:00:00 2001 -Message-Id: <7c8a05b1504ccad35d1c11e58fbcd0ea12f3691c.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 ce5edc5d1..e7d999222 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 8d309d9cd1061b11cb90cdd581927310e4745c97 Mon Sep 17 00:00:00 2001 -Message-Id: <8d309d9cd1061b11cb90cdd581927310e4745c97.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 4dd76b678..526dddf47 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 185813801e9ef2197f69582c36fc21dd3b89dddb Mon Sep 17 00:00:00 2001 -Message-Id: <185813801e9ef2197f69582c36fc21dd3b89dddb.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Thu, 5 Jul 2018 14:44:51 +0200 Subject: [PATCH 155/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 6c500b288..90be6eeee 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 d9ade2d1711540821faa94700e934ba4e8514b7d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 -RT archs -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 02ebd54b3..2fe41a12f 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 f349091ea918e71dcabb8ec65ead69b92f7a8669 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 ee928bbd1..90ccf2660 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 db28805b69b200f1ca395cb2e93c8430091f5276 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 04f94e2d9..d2b1a7244 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 8d775d47d5fce590774180cf890951d3d760a04c Mon Sep 17 00:00:00 2001 -Message-Id: <8d775d47d5fce590774180cf890951d3d760a04c.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: "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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 6747a451a..6b1034b5f 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 2af125c8322614ce120f9796a621907f3639ce5c Mon Sep 17 00:00:00 2001 -Message-Id: <2af125c8322614ce120f9796a621907f3639ce5c.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: "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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 fef4a4bd9..bde11a9ed 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 fe13debb17e595e7bf219cb0f43d117b7e20494e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 9015905be..0a8ba95f0 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 e485ff43030b7b329d09f41ba72fcc7c19859767 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 3cc160f34..ae6967b7a 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 bdce9650c14de21dc6f883c78b63cdde85ac104b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 d6b97c230..44b9f88e4 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 49b86fe86a9000eca1eddd0faf271f5a928711a7 Mon Sep 17 00:00:00 2001 -Message-Id: <49b86fe86a9000eca1eddd0faf271f5a928711a7.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 744a303d1..ec2832cb9 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 136c9182fdb6f6db5ae52d147b50350f745177f6 Mon Sep 17 00:00:00 2001 -Message-Id: <136c9182fdb6f6db5ae52d147b50350f745177f6.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 d2da6c520..f029fa808 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,7 +1,7 @@ -From f42cd7c94b862b9618f1488d0bdb886a436a47c9 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Kurt Kanzenbach Date: Mon, 24 Sep 2018 10:29:01 +0200 Subject: [PATCH 166/327] tty: serial: pl011: explicitly initialize the flags @@ -9,7 +9,7 @@ Subject: [PATCH 166/327] tty: serial: pl011: explicitly initialize the flags 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 471d94ad4..78c5b4906 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 076acf7cd2411e5216c03b86d9065e91465502ae Mon Sep 17 00:00:00 2001 -Message-Id: <076acf7cd2411e5216c03b86d9065e91465502ae.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Ingo Molnar Date: Wed, 14 Dec 2011 13:05:54 +0100 Subject: [PATCH 167/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 92bf6d801..0578dffc7 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 04dcace8e4d31440646c49655ffdfc3458feb381 Mon Sep 17 00:00:00 2001 -Message-Id: <04dcace8e4d31440646c49655ffdfc3458feb381.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 1d349d7da..4633f2823 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 8528a2844b2d0c4d2f5211428d89a883c6aef9a9 Mon Sep 17 00:00:00 2001 -Message-Id: <8528a2844b2d0c4d2f5211428d89a883c6aef9a9.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 7c9899c23..073817075 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 2d140e77056f2485d97fc71e86eb4fe88ea9b638 Mon Sep 17 00:00:00 2001 -Message-Id: <2d140e77056f2485d97fc71e86eb4fe88ea9b638.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Yong Zhang Date: Tue, 15 May 2012 13:53:56 +0800 Subject: [PATCH 170/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz User preempt_*_rt instead of local_irq_*_rt or otherwise there will be warning on ARM like below: @@ -41,7 +41,7 @@ Signed-off-by: Thomas Gleixner 2 files changed, 4 insertions(+) diff --git a/fs/exec.c b/fs/exec.c -index 3818813d725d..4c7de4ac4302 100644 +index cece8c14f377..1941f39a3453 100644 --- a/fs/exec.c +++ b/fs/exec.c @@ -1028,12 +1028,14 @@ static int exec_mmap(struct mm_struct *mm) 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 651ece684..9a087c267 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 c06901b5bffca9fb653d9b2d9afacb19b0a528a4 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 init -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 c98ae716a..e402b9de3 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 e5a9997fa04ef53d80f7102e7c27e4797d790ce9 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 side -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 @@ -85,7 +85,7 @@ index c9eb5041ffae..e1fb0b743c96 100644 inode->dirtied_when = 0; diff --git a/include/linux/fs.h b/include/linux/fs.h -index 15b8e02880c3..d27634022105 100644 +index 8d568b51778b..f964aeac78bd 100644 --- a/include/linux/fs.h +++ b/include/linux/fs.h @@ -679,7 +679,7 @@ struct inode { 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 c337b182e..580c6d9f3 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 78ec6e98b057176aa4b029dba7e8a4a918b41927 Mon Sep 17 00:00:00 2001 -Message-Id: <78ec6e98b057176aa4b029dba7e8a4a918b41927.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Julia Cartwright Date: Mon, 7 May 2018 08:58:57 -0500 Subject: [PATCH 173/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 c185e117b..a0db9b405 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 49156a90f418d34f0f6b6911cd3f14b15523ed09 Mon Sep 17 00:00:00 2001 -Message-Id: <49156a90f418d34f0f6b6911cd3f14b15523ed09.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 d8cc2e703..2a1795121 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 70873feadccc7d8297eb626c3ab1ca823cf12bfc Mon Sep 17 00:00:00 2001 -Message-Id: <70873feadccc7d8297eb626c3ab1ca823cf12bfc.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 dd65cfcb5..70478ef22 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 8aafb3c9debaf8f93cb0162c38acdeb2b3385421 Mon Sep 17 00:00:00 2001 -Message-Id: <8aafb3c9debaf8f93cb0162c38acdeb2b3385421.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 7f62d8d2b..ad5746f08 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 b8d2101f5c4f2c19e14cf33526b3c56532ac5bdb Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Thomas Gleixner Date: Tue, 12 Jul 2011 11:39:36 +0200 Subject: [PATCH 177/327] mm/vmalloc: Another preempt disable region which sucks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz Avoid the preempt disable version of get_cpu_var(). The inner-lock should provide enough serialisation. 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 debad35a5..984af9918 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 0574a9bc12339798fa90b2da8a2a208db018a595 Mon Sep 17 00:00:00 2001 -Message-Id: <0574a9bc12339798fa90b2da8a2a208db018a595.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 ad8cb6337..7795339a6 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 32489808541b98fed062da430dbca78a182e9f0b Mon Sep 17 00:00:00 2001 -Message-Id: <32489808541b98fed062da430dbca78a182e9f0b.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 f0788013f..7027b6fcd 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 8bb6d1462d076710f231b5bf4e92e2bc9107be96 Mon Sep 17 00:00:00 2001 -Message-Id: <8bb6d1462d076710f231b5bf4e92e2bc9107be96.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 2f9c231c3..312cb8a9c 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 db24bcf7ef7994db85d563c384823cb25a9cdd2b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 ec44b0759..72c8f1a9a 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 b10c792e154c2c9a50625d02ceeb51d35645d3d4 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 3b0031590..60e95c848 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 861e51805cbfdb94f431cb77ce3b956f99072130 Mon Sep 17 00:00:00 2001 -Message-Id: <861e51805cbfdb94f431cb77ce3b956f99072130.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 82b9d5f53..1bf890623 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 51e89a0899c3defe006a25d9121f17dcdcee77a6 Mon Sep 17 00:00:00 2001 -Message-Id: <51e89a0899c3defe006a25d9121f17dcdcee77a6.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 12:31:10 +0100 Subject: [PATCH 184/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 c6de901b8..c172da46f 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 0cefcdeaa779d1328d15a1ca1ae4fe3eab120370 Mon Sep 17 00:00:00 2001 -Message-Id: <0cefcdeaa779d1328d15a1ca1ae4fe3eab120370.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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() into process context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 a20b9f283..55ae68881 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 388868aedb175c3245a18f5247504248e586ff97 Mon Sep 17 00:00:00 2001 -Message-Id: <388868aedb175c3245a18f5247504248e586ff97.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 b4f884fb8..ea12eb93d 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 13e35ce47c66c5b2e7feba9b08093e2eaafca8eb Mon Sep 17 00:00:00 2001 -Message-Id: <13e35ce47c66c5b2e7feba9b08093e2eaafca8eb.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 b93694ef1..ba60bd5a2 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 2ef5814e3af178fcc931b671bd31fdbb874f2c94 Mon Sep 17 00:00:00 2001 -Message-Id: <2ef5814e3af178fcc931b671bd31fdbb874f2c94.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 9e065caff..279503112 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 9871b743e0f6d93cfef299da532d6e33b0c7f2fa Mon Sep 17 00:00:00 2001 -Message-Id: <9871b743e0f6d93cfef299da532d6e33b0c7f2fa.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 cef5d1992..ab6d78f96 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 73f0f196c0fbc35d972c4ae6d4a8b713cb90156d Mon Sep 17 00:00:00 2001 -Message-Id: <73f0f196c0fbc35d972c4ae6d4a8b713cb90156d.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 66e1a34c0..3b4e92995 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 226f2f0b37980629bafb11fc647d58fb72a8e378 Mon Sep 17 00:00:00 2001 -Message-Id: <226f2f0b37980629bafb11fc647d58fb72a8e378.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Thomas Gleixner Date: Sun, 17 Jul 2011 21:42:26 +0200 Subject: [PATCH 191/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 9aec9c24b..976f2eb16 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 53a76c0acb2fe389e007df6a22af08c78fc36a49 Mon Sep 17 00:00:00 2001 -Message-Id: <53a76c0acb2fe389e007df6a22af08c78fc36a49.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 701262869..985f7c4e3 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 ebeaac812cbd7b7349f59a18d22cd64b704d10f5 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 7e4e753b1..600b7350d 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 2fb1b4abf0ad125279cf04ced9e94c086fe9f9cf Mon Sep 17 00:00:00 2001 -Message-Id: <2fb1b4abf0ad125279cf04ced9e94c086fe9f9cf.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 f4e884b17..e99d8cd1a 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 d56d49e0ec841441cf4611f3e4bbd987061bc6cb Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 b895e00e3..a6d5a0c44 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 cfc604a13c627c81a23145d22fac31d31b6f21b3 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Mike Galbraith Date: Wed, 18 Feb 2015 16:05:28 +0100 Subject: [PATCH 196/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 80a53a0ce..e993ddf2b 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 649410da34cec1ddfcb05a58b0ddfe99a2580f21 Mon Sep 17 00:00:00 2001 -Message-Id: <649410da34cec1ddfcb05a58b0ddfe99a2580f21.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 0285ea11a788..4c1ee6e8679d 100644 +index c5901d343d0a..fcc109d279e2 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) @@ -144,7 +144,7 @@ index 0285ea11a788..4c1ee6e8679d 100644 for (;;) { struct napi_struct *n; -@@ -9507,10 +9520,13 @@ static int dev_cpu_dead(unsigned int oldcpu) +@@ -9509,10 +9522,13 @@ static int dev_cpu_dead(unsigned int oldcpu) netif_rx_ni(skb); input_queue_head_incr(oldsd); } @@ -159,7 +159,7 @@ index 0285ea11a788..4c1ee6e8679d 100644 return 0; } -@@ -9821,8 +9837,9 @@ static int __init net_dev_init(void) +@@ -9823,8 +9839,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 2cb071618..99f94ac63 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 72e097fa8ef1fd8ecd84399ddbb74b19e63d164a Mon Sep 17 00:00:00 2001 -Message-Id: <72e097fa8ef1fd8ecd84399ddbb74b19e63d164a.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 4c1ee6e8679d..53a86d09f3ca 100644 +index fcc109d279e2..a138f17321b0 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 4c1ee6e8679d..53a86d09f3ca 100644 if (dev_xmit_complete(rc)) { HARD_TX_UNLOCK(dev, txq); goto out; -@@ -8566,7 +8571,7 @@ static void netdev_init_one_queue(struct net_device *dev, +@@ -8568,7 +8573,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 64929462e..d585171be 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 49e52dc25459141a12f80f24b152ed2db30e19ed Mon Sep 17 00:00:00 2001 -Message-Id: <49e52dc25459141a12f80f24b152ed2db30e19ed.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 to ksoftirqd -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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,7 +75,7 @@ index 27a4bb2303d0..25bcf2f2714b 100644 * This function must run with irqs disabled! */ diff --git a/net/core/dev.c b/net/core/dev.c -index 53a86d09f3ca..2752a525d57e 100644 +index a138f17321b0..5e167ef1e2dd 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) 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 5bcf3dd0e..0d229ee28 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 6c5f6a711e2d489bd04217f6103652a6a63bd28b Mon Sep 17 00:00:00 2001 -Message-Id: <6c5f6a711e2d489bd04217f6103652a6a63bd28b.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Wed, 30 Mar 2016 13:36:29 +0200 Subject: [PATCH 200/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 2752a525d57e..d8c7c53e1746 100644 +index 5e167ef1e2dd..8c7a4e988917 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 8057beb80..08f9d4246 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 0c3b73535c653cd8d9086a71a93293af81bb413f Mon Sep 17 00:00:00 2001 -Message-Id: <0c3b73535c653cd8d9086a71a93293af81bb413f.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 38adbc00b..e6af73983 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,7 +1,7 @@ -From 926d037cd86721a844c00b3fcf572cdff6ba37de Mon Sep 17 00:00:00 2001 -Message-Id: <926d037cd86721a844c00b3fcf572cdff6ba37de.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Wed, 31 Aug 2016 17:21:56 +0200 Subject: [PATCH 202/327] net: add back the missing serialization in @@ -9,7 +9,7 @@ Subject: [PATCH 202/327] net: add back the missing serialization in 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 312110ce9..af2e1a93f 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 0683fd68e530053a37eda2d5c73a7db4a230e6e1 Mon Sep 17 00:00:00 2001 -Message-Id: <0683fd68e530053a37eda2d5c73a7db4a230e6e1.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 0d79ec4a0..e5f68b13b 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 834e229e50e6c18d38b9c5e66232e2e60f7f9901 Mon Sep 17 00:00:00 2001 -Message-Id: <834e229e50e6c18d38b9c5e66232e2e60f7f9901.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Steven Rostedt Date: Tue, 6 Dec 2016 17:50:30 -0500 Subject: [PATCH 204/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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,7 +56,7 @@ 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 d8c7c53e1746..40f04f102f20 100644 +index 8c7a4e988917..2f63f20bbcc9 100644 --- a/net/core/dev.c +++ b/net/core/dev.c @@ -5941,6 +5941,7 @@ bool napi_schedule_prep(struct napi_struct *n) 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 60c85572a..1146bc7db 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 bd9134a027f082d0fde6c508f43f1e18895f30d0 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 154204227..167267936 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 720391fc581c0448db646eba74cce7481ad0db79 Mon Sep 17 00:00:00 2001 -Message-Id: <720391fc581c0448db646eba74cce7481ad0db79.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 db559c7f3..462e069df 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 a9a6aadcd03c4b2f49c9712b703214b23099ed5c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 15f5ad77a..186236394 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 25be3b45d50c42251a10913b9c1a14ec64925e56 Mon Sep 17 00:00:00 2001 -Message-Id: <25be3b45d50c42251a10913b9c1a14ec64925e56.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 f50de1787..e3229e556 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,7 +1,7 @@ -From efb659c8e2c2664479469b9ade75616201004964 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: "Yadi.hu" Date: Wed, 10 Dec 2014 10:32:09 +0800 Subject: [PATCH 209/327] ARM: enable irq in translation/section permission @@ -9,7 +9,7 @@ Subject: [PATCH 209/327] ARM: enable irq in translation/section permission 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 db6ad2162..501279a9e 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 7a277c502a25ccc72209d2403003df058644f774 Mon Sep 17 00:00:00 2001 -Message-Id: <7a277c502a25ccc72209d2403003df058644f774.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 a48a7ca4e..8988f9d63 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 07ae278abba38ca5193ad0dbeb0f7a44bfa0041a Mon Sep 17 00:00:00 2001 -Message-Id: <07ae278abba38ca5193ad0dbeb0f7a44bfa0041a.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Josh Cartwright Date: Thu, 11 Feb 2016 11:54:01 -0600 Subject: [PATCH 211/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 f00cf8d7a..956da36a0 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 e48ab745454fd06631eabb8407fd706741e96842 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Wed, 25 Jul 2018 14:02:38 +0200 Subject: [PATCH 212/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 fbef70ce4..1bf98b906 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 b03b52a1c0ada966349d978f63694711f4886c0f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 ac80e3d20..3b8bbc5a1 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 fdeaa601470c87da07098368fb1e024b95cadd3f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 0224f459a..150e8a46c 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 f816993d61b04e5660ec3fbfcf1ee44b76c3fff3 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 759ffa025..b2c7096a9 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 b2d1c972af3abf2f0994d969cf968033c569916c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 983083f9b..e7f874612 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 8edc794852167a4e17981e677be5cf82365d85b0 Mon Sep 17 00:00:00 2001 -Message-Id: <8edc794852167a4e17981e677be5cf82365d85b0.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 cec2b1f21..d7dd19d8b 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 c9eda580e525766a543472623318f020ab73d37f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 5475f1dcb..c135591a7 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 5abb9840afaaa4e3935ac609013c1f28148a7feb Mon Sep 17 00:00:00 2001 -Message-Id: <5abb9840afaaa4e3935ac609013c1f28148a7feb.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 f3a6e2110..8e069a44f 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 8af4085d71a12122609f5009818af7db77aacf67 Mon Sep 17 00:00:00 2001 -Message-Id: <8af4085d71a12122609f5009818af7db77aacf67.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 289d62914..8c6c09736 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 67cdc048042ccfcc95a4c64f47137fd3792abccc Mon Sep 17 00:00:00 2001 -Message-Id: <67cdc048042ccfcc95a4c64f47137fd3792abccc.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 0644f6c06..1e68f7d34 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 37c6deaa26be42b026c801fd852a5f590c613fc8 Mon Sep 17 00:00:00 2001 -Message-Id: <37c6deaa26be42b026c801fd852a5f590c613fc8.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Thu, 30 Nov 2017 13:40:10 +0100 Subject: [PATCH 222/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 b9c6e67a0..63e46662d 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 2b3aab178446471bf8bc15f995b7949360c4786b Mon Sep 17 00:00:00 2001 -Message-Id: <2b3aab178446471bf8bc15f995b7949360c4786b.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Mike Galbraith Date: Wed, 11 Jul 2018 17:14:47 +0200 Subject: [PATCH 223/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 79d5fb8a3..3786a895b 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 a530d6830e609debd667089469ee1ef5a077084d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 18:52:00 +0200 Subject: [PATCH 224/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 e92474e37..b0b1df787 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 e6e355f3d19f6889b295b28c534f113255882251 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Thomas Gleixner Date: Tue, 14 Jul 2015 14:26:34 +0200 Subject: [PATCH 225/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 1111a38cb..af3cb884e 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 52fcf66c1b4f281bec1dbfd8daa9669cd67ab610 Mon Sep 17 00:00:00 2001 -Message-Id: <52fcf66c1b4f281bec1dbfd8daa9669cd67ab610.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 @@ -22,10 +22,10 @@ Signed-off-by: Thomas Gleixner 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/arch/x86/include/asm/stackprotector.h b/arch/x86/include/asm/stackprotector.h -index 8ec97a62c245..7bc85841fc56 100644 +index 9c556ea2eaa7..b136992beb1b 100644 --- a/arch/x86/include/asm/stackprotector.h +++ b/arch/x86/include/asm/stackprotector.h -@@ -60,7 +60,7 @@ +@@ -65,7 +65,7 @@ */ static __always_inline void boot_init_stack_canary(void) { @@ -34,7 +34,7 @@ index 8ec97a62c245..7bc85841fc56 100644 u64 tsc; #ifdef CONFIG_X86_64 -@@ -71,8 +71,14 @@ static __always_inline void boot_init_stack_canary(void) +@@ -76,8 +76,14 @@ static __always_inline void boot_init_stack_canary(void) * of randomness. The TSC only matters for very early init, * there it already has some randomness on most systems. Later * on during the bootup the random pool has true entropy too. 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 ca004d61e..c9b079ec6 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 218a3a3be9f0a569aadc632ea2cb55badcc66c31 Mon Sep 17 00:00:00 2001 -Message-Id: <218a3a3be9f0a569aadc632ea2cb55badcc66c31.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 203e8e77a..f5a2b0600 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 c5190a8398ef2e9ce8dc267ec8a2f27807578989 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 03c263000..dfc7f4514 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 3368d2233e8cf9fe184446b68e13215e1c033889 Mon Sep 17 00:00:00 2001 -Message-Id: <3368d2233e8cf9fe184446b68e13215e1c033889.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 CPU they pinned -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 41ade42bb..c3ca6d9f4 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 8bd097564d158db7352d7339c5bfd3a774559d27 Mon Sep 17 00:00:00 2001 -Message-Id: <8bd097564d158db7352d7339c5bfd3a774559d27.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 c232353b8..8c4e896e9 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 71a332a0660d2f29b981dc7a62d62dbc1268e286 Mon Sep 17 00:00:00 2001 -Message-Id: <71a332a0660d2f29b981dc7a62d62dbc1268e286.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 40f04f102f20..0544619bf62b 100644 +index 2f63f20bbcc9..b91c2f0fa199 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 1bca2a78c..9d59fe889 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 2608599ac9cf769d8a52fcbac2439790f136c966 Mon Sep 17 00:00:00 2001 -Message-Id: <2608599ac9cf769d8a52fcbac2439790f136c966.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 2213e6526..700ef0b12 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 c023a3e44757d028d779a93a150909511e9a583c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 reentrance -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 37eb3722f..dd0594076 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 638925d9a73dbee1a98f11df9e3da0e071b3d58b Mon Sep 17 00:00:00 2001 -Message-Id: <638925d9a73dbee1a98f11df9e3da0e071b3d58b.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Thomas Gleixner Date: Sun, 28 Oct 2012 11:18:08 +0100 Subject: [PATCH 234/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 7f52aaeec..4f1758829 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 aff8fe96bd1f91327dcc5711c71b8ac9334763d9 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 0544619bf62b..7be74a0cee23 100644 +index b91c2f0fa199..22ab7a06843f 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 45dbfb334..77e619823 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 8a88f96f8d22784eafd3395e45d7918f7438dedb Mon Sep 17 00:00:00 2001 -Message-Id: <8a88f96f8d22784eafd3395e45d7918f7438dedb.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Yong Zhang Date: Mon, 16 Apr 2012 15:01:56 +0800 Subject: [PATCH 236/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 373ca0ff0..910f2bfaf 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 aa8945e200d231bcd73cc4879b95437fde2153de Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Josh Cartwright Date: Wed, 28 Jan 2015 13:08:45 -0600 Subject: [PATCH 237/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 052c6d0a3..065fdee9c 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 22321605269fd1510f3175f23208cfab0e75a30c Mon Sep 17 00:00:00 2001 -Message-Id: <22321605269fd1510f3175f23208cfab0e75a30c.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz It has become an obsession to mitigate the determinism vs. throughput loss of RT. Looking at the mainline semantics of preemption points @@ -533,7 +533,7 @@ index 96823c632599..005874299b04 100644 extern void init_rt_bandwidth(struct rt_bandwidth *rt_b, u64 period, u64 runtime); diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c -index 1fac8a2de78f..89d54ed4f9a7 100644 +index a7b187f74f34..e46347b3d061 100644 --- a/kernel/trace/trace.c +++ b/kernel/trace/trace.c @@ -2139,6 +2139,7 @@ tracing_generic_entry_update(struct trace_entry *entry, unsigned long flags, 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 6642d5167..7df3699fe 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 1f028c3fa41b6d0e061772451c518b4d0ccbd97d Mon Sep 17 00:00:00 2001 -Message-Id: <1f028c3fa41b6d0e061772451c518b4d0ccbd97d.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz Line up helper arrows to the right column. @@ -18,7 +18,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c -index 89d54ed4f9a7..1d7fc29ac791 100644 +index e46347b3d061..dc1e0b7c7984 100644 --- a/kernel/trace/trace.c +++ b/kernel/trace/trace.c @@ -3353,17 +3353,17 @@ get_total_entries(struct trace_buffer *buf, 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 7a524d66a..24224fb16 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 a68c49357d823798978eb8648ef51cdd4507aac0 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz Implement the x86 pieces for lazy preempt. @@ -85,10 +85,10 @@ index 37d9016d4768..324b7539eaab 100644 jz restore_all_kernel call preempt_schedule_irq diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S -index 7ffd83c57ef2..663a99f6320f 100644 +index f53d995b1370..94fccaa04bfa 100644 --- a/arch/x86/entry/entry_64.S +++ b/arch/x86/entry/entry_64.S -@@ -732,7 +732,23 @@ retint_kernel: +@@ -733,7 +733,23 @@ retint_kernel: btl $9, EFLAGS(%rsp) /* were interrupts off? */ jnc 1f 0: cmpl $0, PER_CPU_VAR(__preempt_count) 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 5ab7c5bc4..5c2aa57c1 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 eec11c55311df8e5260514905cb94be65d685f5d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Mon, 18 Feb 2019 16:57:09 +0100 Subject: [PATCH 241/327] x86: lazy-preempt: properly check against preempt-mask -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 eb28fb31d..70d69533c 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 babaa84c4b56177e15c6b292f1a180519eb1d5c0 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 14:53:49 +0100 Subject: [PATCH 242/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 0655b4d9d..5c7948599 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 5144a4b80748eee8b8b4501d5139aa9b57cb3a92 Mon Sep 17 00:00:00 2001 -Message-Id: <5144a4b80748eee8b8b4501d5139aa9b57cb3a92.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz Implement the arm pieces for lazy preempt. 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 b52c3f70f..c3fafe698 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 5face30891c5ee1313adfabbf77e0cb7c1d06de6 Mon Sep 17 00:00:00 2001 -Message-Id: <5face30891c5ee1313adfabbf77e0cb7c1d06de6.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz Implement the powerpc pieces for lazy preempt. 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 a941e765e..8c2762663 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 6da13f809db48d860b72eaca9fc870c05eeecd03 Mon Sep 17 00:00:00 2001 -Message-Id: <6da13f809db48d860b72eaca9fc870c05eeecd03.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 c07fca0c9..d575659ff 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 c11c7b9369ed010493e8ee6bcdf275566aab8e64 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Mike Galbraith Date: Sun, 16 Oct 2016 05:11:54 +0200 Subject: [PATCH 246/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 4a339180f..b0baac1bf 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 6a9f3b3224d6932cbd20176d28645bd9e71da50e Mon Sep 17 00:00:00 2001 -Message-Id: <6a9f3b3224d6932cbd20176d28645bd9e71da50e.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Mike Galbraith Date: Thu, 31 Mar 2016 04:08:28 +0200 Subject: [PATCH 247/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 6a4701f94..bb437c12b 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 af7f66c685825c4cf835696a0e833fa5dce30ca3 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Mike Galbraith Date: Thu, 20 Oct 2016 11:15:22 +0200 Subject: [PATCH 248/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 a6fda9a63..68cefbd86 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 fff3d02075c974741a1943f2ce9b4fa3e0f123bb Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Mike Galbraith Date: Wed, 23 Aug 2017 11:57:29 +0200 Subject: [PATCH 249/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 81e8896f1..de5a5b300 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 43974733073ca5b9de9280ec07789fdc89465464 Mon Sep 17 00:00:00 2001 -Message-Id: <43974733073ca5b9de9280ec07789fdc89465464.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 021779475..fe0071224 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 e36a324a0736f2cba48a43c5b326be8ec4de7062 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 80e21eefa..ed8400f94 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 2b8d0867028ebb2c534fc4736255a317a2f01c61 Mon Sep 17 00:00:00 2001 -Message-Id: <2b8d0867028ebb2c534fc4736255a317a2f01c61.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Mike Galbraith Date: Sat, 27 Feb 2016 08:09:11 +0100 Subject: [PATCH 252/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 3b17da8e0..08cf0eb58 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 710ddc2503ed051fa5343c1eb5b950444b05147b Mon Sep 17 00:00:00 2001 -Message-Id: <710ddc2503ed051fa5343c1eb5b950444b05147b.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Mike Galbraith Date: Sat, 27 Feb 2016 09:01:42 +0100 Subject: [PATCH 253/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 9df05c587..71c664346 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 7ed8d38963d1fa985cd15013ed057b4fee4df002 Mon Sep 17 00:00:00 2001 -Message-Id: <7ed8d38963d1fa985cd15013ed057b4fee4df002.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 e23e32130..75ccf7370 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 5ec5b253489612a052795fbf5439c2a00f146c67 Mon Sep 17 00:00:00 2001 -Message-Id: <5ec5b253489612a052795fbf5439c2a00f146c67.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 NOTRACE -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 9545485a6..7ab28d794 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 23f06bf7e786602ab35b4abed68bbe45bec93200 Mon Sep 17 00:00:00 2001 -Message-Id: <23f06bf7e786602ab35b4abed68bbe45bec93200.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 0e3e6640e..e0b48d595 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 c3933176cb4bcaa676a0743119c434f03f4690f8 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 aa5340c96..90fe8be9b 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 e7e3512033bbed59bdf83b068c3dd4673a706a5b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 f5624b7f4..7cf20200a 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 aca8bffd46f70f5caad69fc3ba1b7b4875ca4ac0 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 cbaade945..982e8a97a 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 8f3b2b722f4a5d076cd798d0adffa16bfd554e48 Mon Sep 17 00:00:00 2001 -Message-Id: <8f3b2b722f4a5d076cd798d0adffa16bfd554e48.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 310b4ef8a..980f4d7cd 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 c530fcb23cfbb541c2ab38fd262d1be8a787f43c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 5136768a6..caea6978a 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 476cebd9d429366f7296fa1dad5d963b3ac7b77a Mon Sep 17 00:00:00 2001 -Message-Id: <476cebd9d429366f7296fa1dad5d963b3ac7b77a.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Tue, 26 Mar 2019 18:31:54 +0100 Subject: [PATCH 262/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 36c32b836..f29dfa019 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 0db09cfa3e5a8117220a0353a02aa10fb4924373 Mon Sep 17 00:00:00 2001 -Message-Id: <0db09cfa3e5a8117220a0353a02aa10fb4924373.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 8848a03da..b854ccb6c 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 f5c9f0a7737b549b4e439ed591eb7ac113c8b575 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 cc0b3dd75..4ee1a0f60 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 4b720165d0e03ea4eaf4e00dbf1954384e2a09de Mon Sep 17 00:00:00 2001 -Message-Id: <4b720165d0e03ea4eaf4e00dbf1954384e2a09de.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Wed, 10 Apr 2019 11:01:37 +0200 Subject: [PATCH 265/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 02af5a75c..e1be868cb 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 bf17ec3875abb55507d2cb7595df233a25c80199 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Corey Minyard Date: Thu, 9 May 2019 14:33:20 -0500 Subject: [PATCH 266/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 99f096160..8c4c1a847 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 a0ea89698f63ecdd3c04325e9fa053e607bd1c3d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz [ Upstream commit 0532e87d9d44795221aa921ba7024bde689cc894 ] @@ -135,10 +135,10 @@ index ad292898f7f2..7cf56eb54103 100644 + #endif /* _LINUX_KTHREAD_H */ diff --git a/init/main.c b/init/main.c -index 6e02188386a7..e514dd93de76 100644 +index 7c064c6aff55..064bdf98544b 100644 --- a/init/main.c +++ b/init/main.c -@@ -1129,6 +1129,7 @@ static noinline void __init kernel_init_freeable(void) +@@ -1131,6 +1131,7 @@ static noinline void __init kernel_init_freeable(void) smp_prepare_cpus(setup_max_cpus); workqueue_init(); 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 80c19e0d2..031824db5 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 f784856a817d703029f506a9546b4b7c4980b240 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 57ed58fbe..14f381a87 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 80fc81c734ab88f202dc415ce5b301276f184f8e Mon Sep 17 00:00:00 2001 -Message-Id: <80fc81c734ab88f202dc415ce5b301276f184f8e.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 c938bffa3..249c58ec0 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 2899a2c8b2ad6c1ced301bed400ec6286aff59ec Mon Sep 17 00:00:00 2001 -Message-Id: <2899a2c8b2ad6c1ced301bed400ec6286aff59ec.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 669d0a5f2..1cdd323c4 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 5249a037647b59d7001625081ec239e472eeadc2 Mon Sep 17 00:00:00 2001 -Message-Id: <5249a037647b59d7001625081ec239e472eeadc2.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 a09b0b91b..a5ded6aa8 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 dd509894c7509d682f0aab3909d55ee6c32084e5 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 19:39:06 +0200 Subject: [PATCH 272/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 ceb59cabf..c6aa01398 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 fd5dcc82e6e272600097d6ae911aaf6890beb58b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:13 +0200 Subject: [PATCH 273/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 4dd12d8f6..5f5c32ea5 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 f5552be3656c38e090fe9e94f8d60d42a542a6f7 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 times out" -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 76eb3b45f..0bffdf848 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 1896d1cae8fe2408ea75067287741090d16b85db Mon Sep 17 00:00:00 2001 -Message-Id: <1896d1cae8fe2408ea75067287741090d16b85db.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:21 +0200 Subject: [PATCH 275/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 9f0853541..40ad7c074 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 9677a2e0da781ad1cfa98e0cd02f4f81fc15086c Mon Sep 17 00:00:00 2001 -Message-Id: <9677a2e0da781ad1cfa98e0cd02f4f81fc15086c.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:27 +0200 Subject: [PATCH 276/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 2628eff8d..65f468f7b 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 4dc70d7b78801ad210c7e585d1895ee5651f3b0e Mon Sep 17 00:00:00 2001 -Message-Id: <4dc70d7b78801ad210c7e585d1895ee5651f3b0e.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 9da2b1dcf..7aad7ea16 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 0538c9acfdb919e72b2fd2660cee77b589bcc18b Mon Sep 17 00:00:00 2001 -Message-Id: <0538c9acfdb919e72b2fd2660cee77b589bcc18b.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 a7df49f62..63ab842d0 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 3d2c756141f1e830f68fe6b8aa27ba395f72c02f Mon Sep 17 00:00:00 2001 -Message-Id: <3d2c756141f1e830f68fe6b8aa27ba395f72c02f.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: "Luis Claudio R. Goncalves" Date: Tue, 25 Jun 2019 11:28:04 -0300 Subject: [PATCH 279/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz [ Upstream commit 4e4cf4be79635e67144632d9135286381acbc95a ] diff --git a/debian/patches-rt/0280-revert-aio.patch b/debian/patches-rt/0280-revert-aio.patch index 3cb973809..19933940d 100644 --- a/debian/patches-rt/0280-revert-aio.patch +++ b/debian/patches-rt/0280-revert-aio.patch @@ -1,11 +1,11 @@ -From 4bad7a9c1c1747bf47f5ef2a0d9e73ec114345bc Mon Sep 17 00:00:00 2001 -Message-Id: <4bad7a9c1c1747bf47f5ef2a0d9e73ec114345bc.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: "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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 f8d83d16f..1c4a00395 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 1cc75eebd2107911c948e07f921dc73befb80609 Mon Sep 17 00:00:00 2001 -Message-Id: <1cc75eebd2107911c948e07f921dc73befb80609.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz [ Upstream commit 1a142116f6435ef070ecebb66d2d599507c10601 ] diff --git a/debian/patches-rt/0282-revert-thermal.patch b/debian/patches-rt/0282-revert-thermal.patch index 917e755b9..7d10b8bb7 100644 --- a/debian/patches-rt/0282-revert-thermal.patch +++ b/debian/patches-rt/0282-revert-thermal.patch @@ -1,11 +1,11 @@ -From c3c4fea752b256b173678612d1c848bd76710d25 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: "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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 b53b9afc0..0ea1bae12 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 b572ed9793f7a54696726f5b9d38a977900ac0c9 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz [ Upstream commit ad2408dc248fe58536eef5b2b5734d8f9d3a280b ] diff --git a/debian/patches-rt/0284-revert-block.patch b/debian/patches-rt/0284-revert-block.patch index 261741b0e..154abd0ae 100644 --- a/debian/patches-rt/0284-revert-block.patch +++ b/debian/patches-rt/0284-revert-block.patch @@ -1,11 +1,11 @@ -From ef5a3ea0768019ea8fe629118a47088f3d650be2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: "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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 e804c3ad1..bbc39613a 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 95afd918acf568a8a130cf4eb9c32fa3aaafaf0b Mon Sep 17 00:00:00 2001 -Message-Id: <95afd918acf568a8a130cf4eb9c32fa3aaafaf0b.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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() into process context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz [ Upstream commit 61c928ecf4fe200bda9b49a0813b5ba0f43995b5 ] diff --git a/debian/patches-rt/0286-workqueue-rework.patch b/debian/patches-rt/0286-workqueue-rework.patch index c72ba2097..b45eaf7ad 100644 --- a/debian/patches-rt/0286-workqueue-rework.patch +++ b/debian/patches-rt/0286-workqueue-rework.patch @@ -1,11 +1,11 @@ -From 4d2d7e60f7fcf4dbf22b7e125f8633c8d5901fae Mon Sep 17 00:00:00 2001 -Message-Id: <4d2d7e60f7fcf4dbf22b7e125f8633c8d5901fae.1588797587.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz [ Upstream commit d15a862f24df983458533aebd6fa207ecdd1095a ] @@ -312,10 +312,10 @@ index 60d673e15632..546aa73fba6a 100644 extern bool queue_work_on(int cpu, struct workqueue_struct *wq, diff --git a/init/main.c b/init/main.c -index e514dd93de76..6e02188386a7 100644 +index 064bdf98544b..7c064c6aff55 100644 --- a/init/main.c +++ b/init/main.c -@@ -1129,7 +1129,6 @@ static noinline void __init kernel_init_freeable(void) +@@ -1131,7 +1131,6 @@ static noinline void __init kernel_init_freeable(void) smp_prepare_cpus(setup_max_cpus); workqueue_init(); 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 28e1ec9f3..3880978bb 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 1d1b6053f05dd32a49f9c85fda37e0a60a156c79 Mon Sep 17 00:00:00 2001 -Message-Id: <1d1b6053f05dd32a49f9c85fda37e0a60a156c79.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 18e9466d5..5050ebec2 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 ec731db4eae02d57a8d9b2caaecaf5f37fa7768c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 ee1ff5f43..fa34cffc2 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 cc107e8351dec73ed4f52a3e5df1267ce51a04a2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Juri Lelli Date: Wed, 31 Jul 2019 12:37:15 +0200 Subject: [PATCH 289/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 87bdad615..70bb7f82e 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 1025cefe767bf870e57c02f9907413d04c1b0c5f Mon Sep 17 00:00:00 2001 -Message-Id: <1025cefe767bf870e57c02f9907413d04c1b0c5f.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 spinlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 7a7de1f40..2eb47f098 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 ace9a654bb67fb7d66327244d09b9668113aa449 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 6ea375e35..009598031 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 19529328ab32e8fb204571c9db204936c151f214 Mon Sep 17 00:00:00 2001 -Message-Id: <19529328ab32e8fb204571c9db204936c151f214.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Thomas Gleixner Date: Tue, 13 Aug 2019 14:29:41 +0200 Subject: [PATCH 292/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 577397ec1..be4d2c8f8 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 777c5bbf8cd5ffb6fff8fcc2ce5c919f1c40f765 Mon Sep 17 00:00:00 2001 -Message-Id: <777c5bbf8cd5ffb6fff8fcc2ce5c919f1c40f765.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Wed, 14 Aug 2019 17:08:58 +0200 Subject: [PATCH 293/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 dffb52c6f..a6e249dc5 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 fcbf301bbdad4ed46684e9805ad9d6ac5f1ac669 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Julien Grall Date: Wed, 21 Aug 2019 10:24:07 +0100 Subject: [PATCH 294/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 75ee23daf..dc22a5728 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 fee308ee0c3ef4d90276bb692a31b3c639f4817f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 hrtimer -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 4339f12bc..4b94c8964 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 71608ca953e7884a5b61055b0c97a4dd63313586 Mon Sep 17 00:00:00 2001 -Message-Id: <71608ca953e7884a5b61055b0c97a4dd63313586.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Julien Grall Date: Wed, 21 Aug 2019 10:24:09 +0100 Subject: [PATCH 296/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 0a18d04dc..7f5f6dd7a 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 d5f7eeb5eef02de850fdf4723e90f694c76308eb Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Wed, 4 Sep 2019 16:55:27 +0200 Subject: [PATCH 297/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 35ab7a9f4..c8a98e20e 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 c6a286eb70e14effea5ef6dce7b90ea60b52bab7 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 e415089cd..d9c08d05e 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,7 +1,7 @@ -From c5709957ae653dd7d880138b09c7af210f4a1529 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Scott Wood Date: Tue, 24 Sep 2019 14:36:41 +0200 Subject: [PATCH 299/327] =?UTF-8?q?sched:=20migrate=5Fdis/enable:=20Use=20?= @@ -9,7 +9,7 @@ Subject: [PATCH 299/327] =?UTF-8?q?sched:=20migrate=5Fdis/enable:=20Use=20?= 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 9fbd74f85..f410c9354 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 e4cfc5e5a879ac24d491760291475ab58d7a0c6d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Scott Wood Date: Sat, 27 Jul 2019 00:56:32 -0500 Subject: [PATCH 300/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 dd9e4d931..4266b9579 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 04ea3d30f7001d150698a624217e5b0ecbbb4145 Mon Sep 17 00:00:00 2001 -Message-Id: <04ea3d30f7001d150698a624217e5b0ecbbb4145.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 8547a0e02..837e87715 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 7f5e600685c5df3c778beae852093327bc83978b Mon Sep 17 00:00:00 2001 -Message-Id: <7f5e600685c5df3c778beae852093327bc83978b.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 cc7e6008c..4e568f64c 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 d481be6a8ec2e68abc2a2a9aa5ffeead29b8f1e6 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 73d62c4f9..0d16d219b 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 ceaa27c1dae4bdd9eea6c3bb5bec59694645a1f9 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 and bring back its old state -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 aab984095..541387705 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 8e1caa450f6713822afba2aafcc5b1cc3162b0fa Mon Sep 17 00:00:00 2001 -Message-Id: <8e1caa450f6713822afba2aafcc5b1cc3162b0fa.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Peter Zijlstra Date: Mon, 30 Sep 2019 18:15:44 +0200 Subject: [PATCH 305/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 4c8634c75..0110a80fa 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 0b8b8cee2a83a8974149a59ebd44def7899b0637 Mon Sep 17 00:00:00 2001 -Message-Id: <0b8b8cee2a83a8974149a59ebd44def7899b0637.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 86949fd6f..ef00f3658 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 e912714873cfc2f9b790d5353c2a3a036b9a9009 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Liu Haitao Date: Fri, 27 Sep 2019 16:22:30 +0800 Subject: [PATCH 307/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 8d6c15edf..72dbd5dd1 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 f94c66add46088b6083b57d104c6c7c8577cc981 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 b026fee19..12782c80c 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 5384dc959a29567748c81a3c3f33190ea34fc20e Mon Sep 17 00:00:00 2001 -Message-Id: <5384dc959a29567748c81a3c3f33190ea34fc20e.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 c081599bd..ab19873ee 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 878918a0eb2f8d15c795728687a5137671a7c4e2 Mon Sep 17 00:00:00 2001 -Message-Id: <878918a0eb2f8d15c795728687a5137671a7c4e2.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 dba0499a5..9fc369cfa 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 71ed8c2ce0e4186e19236547d35702003a92fad5 Mon Sep 17 00:00:00 2001 -Message-Id: <71ed8c2ce0e4186e19236547d35702003a92fad5.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Fri, 18 Oct 2019 13:04:15 +0200 Subject: [PATCH 311/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 bde23505b..d0156b5b6 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 6763f583ac0514fcceec18f3b6d24501229829c8 Mon Sep 17 00:00:00 2001 -Message-Id: <6763f583ac0514fcceec18f3b6d24501229829c8.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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 on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 3c7303f0a..2fa929a9b 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 d75f580250a6bee8aeb4153e051153e167a6a17a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Fri, 29 Nov 2019 17:24:55 +0100 Subject: [PATCH 313/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 09646d740..51ddaa275 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 3e022d320cb74a5770778b069a80ad7a1899cfb8 Mon Sep 17 00:00:00 2001 -Message-Id: <3e022d320cb74a5770778b069a80ad7a1899cfb8.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Daniel Wagner Date: Mon, 16 Dec 2019 16:15:57 +0100 Subject: [PATCH 314/327] lib/smp_processor_id: Adjust check_preemption_disabled() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 d8f53c088..5df030d8e 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 15f182fdbb462481876d5cbaf57f8b85e6b06c2c Mon Sep 17 00:00:00 2001 -Message-Id: <15f182fdbb462481876d5cbaf57f8b85e6b06c2c.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Thu, 12 Dec 2019 10:53:59 +0100 Subject: [PATCH 315/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 188384ef8..1e46841b7 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 3a17364c0fc5f24a827c869cf451a86f0c300b43 Mon Sep 17 00:00:00 2001 -Message-Id: <3a17364c0fc5f24a827c869cf451a86f0c300b43.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 66cb31003..a543be1b6 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 47459b060c4eb4be038a5623bc07cb91e75afacd Mon Sep 17 00:00:00 2001 -Message-Id: <47459b060c4eb4be038a5623bc07cb91e75afacd.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 7c77ffd93..40b226f36 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 20c2500d81b2da25336c3c4a629a09d3b3043c1e Mon Sep 17 00:00:00 2001 -Message-Id: <20c2500d81b2da25336c3c4a629a09d3b3043c1e.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 431900a95..7ddcdad43 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 3a9891960143566efeccaf7363b2f0602abba5b3 Mon Sep 17 00:00:00 2001 -Message-Id: <3a9891960143566efeccaf7363b2f0602abba5b3.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Matt Fleming Date: Sun, 26 Jan 2020 21:19:45 +0000 Subject: [PATCH 319/327] mm/memcontrol: Move misplaced local_unlock_irqrestore() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 76ec4d690..67c148145 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 76281d7c00b4156764f2a77b03b1ddea772132b9 Mon Sep 17 00:00:00 2001 -Message-Id: <76281d7c00b4156764f2a77b03b1ddea772132b9.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 a4ad9e05c..73859a787 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 ef924f91f05eae6fcb1c1c9969d363b255289854 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2020 18:57:11 +0100 Subject: [PATCH 321/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 675fe378d..5ae7a928f 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 fb0b75771dbf1c10f0923035b67390100054a136 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2020 18:15:15 +0100 Subject: [PATCH 322/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 c71f3f104..452caf88b 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 71da8e9b9157813ec898f01fff08a38fdebaf510 Mon Sep 17 00:00:00 2001 -Message-Id: <71da8e9b9157813ec898f01fff08a38fdebaf510.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Tiejun Chen Date: Mon, 30 Mar 2020 18:45:23 -0400 Subject: [PATCH 323/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 e4e0a6c88..626397f64 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 9632a622d8f957d390d1ea53a0d5eaaeb0f27370 Mon Sep 17 00:00:00 2001 -Message-Id: <9632a622d8f957d390d1ea53a0d5eaaeb0f27370.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: "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 non PREEMPT_RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 553d98f92..44b9435f5 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 bb278370b5b74a9f82eddc685ece70e9858ef58f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.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 dc0920416..2e5e73e43 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 87f9b21f14403942c6d2ccc92ab978f3d364e53d Mon Sep 17 00:00:00 2001 -Message-Id: <87f9b21f14403942c6d2ccc92ab978f3d364e53d.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> +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: Rasmus Villemoes Date: Tue, 28 Apr 2020 16:40:26 +0200 Subject: [PATCH 326/327] 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.120-rt52.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.124-rt53.tar.xz Commit diff --git a/debian/patches-rt/0327-Linux-4.19.120-rt52-REBASE.patch b/debian/patches-rt/0327-Linux-4.19.120-rt52-REBASE.patch deleted file mode 100644 index ac5d60285..000000000 --- a/debian/patches-rt/0327-Linux-4.19.120-rt52-REBASE.patch +++ /dev/null @@ -1,24 +0,0 @@ -From 7c005718e34690dcb3eec30a9e4b9e3920a14064 Mon Sep 17 00:00:00 2001 -Message-Id: <7c005718e34690dcb3eec30a9e4b9e3920a14064.1588797588.git.zanussi@kernel.org> -In-Reply-To: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -References: <94c546b56877133a33b6e344bfe3ee7f698d069a.1588797587.git.zanussi@kernel.org> -From: Tom Zanussi -Date: Wed, 6 May 2020 15:31:36 -0500 -Subject: [PATCH 327/327] Linux 4.19.120-rt52 REBASE -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.120-rt52.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..66a5ed8bf3d7 100644 ---- a/localversion-rt -+++ b/localversion-rt -@@ -1 +1 @@ ---rt16 -+-rt52 --- -2.17.1 - 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 new file mode 100644 index 000000000..095a0856c --- /dev/null +++ b/debian/patches-rt/0327-Linux-4.19.124-rt53-REBASE.patch @@ -0,0 +1,24 @@ +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/series b/debian/patches-rt/series index 068d47e34..06a7b7e7f 100644 --- a/debian/patches-rt/series +++ b/debian/patches-rt/series @@ -324,4 +324,4 @@ 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.120-rt52-REBASE.patch +0327-Linux-4.19.124-rt53-REBASE.patch