diff --git a/debian/changelog b/debian/changelog index 2f1c72bef..0eac25798 100644 --- a/debian/changelog +++ b/debian/changelog @@ -237,6 +237,7 @@ linux (4.19.135-1) UNRELEASED; urgency=medium [ Salvatore Bonaccorso ] * Bump ABI to 11 * Drop 'Revert "mips: Add udelay lpj numbers adjustment"' + * [rt] Update to 4.19.135-rt60 -- Salvatore Bonaccorso Tue, 04 Aug 2020 16:33:40 +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 5cb88cae9..54d806862 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 832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81 Mon Sep 17 00:00:00 2001 -Message-Id: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 378ee68279f6a7631221f2670a9298620148690d Mon Sep 17 00:00:00 2001 +Message-Id: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:18 +0200 Subject: [PATCH 001/329] ARM: at91: add TCB registers definitions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 155b79301..c54f62fab 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 e2dc33e3c6862f67375763e71e0faa769276a14d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 965acd390f989c4828cc2c363c5d2b5ba13788b7 Mon Sep 17 00:00:00 2001 +Message-Id: <965acd390f989c4828cc2c363c5d2b5ba13788b7.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:19 +0200 Subject: [PATCH 002/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 4fb2c0e9f..ab757fe1e 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 973df36d2ea81e30640a9618db832a77d03287f6 Mon Sep 17 00:00:00 2001 -Message-Id: <973df36d2ea81e30640a9618db832a77d03287f6.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From a4837437e5d30cac40a7601e491f2f2d39204d6a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:20 +0200 Subject: [PATCH 003/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 aee2037b2..0aba26caa 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 6585d2242c353963685bd6af832ed97e9a27255a Mon Sep 17 00:00:00 2001 -Message-Id: <6585d2242c353963685bd6af832ed97e9a27255a.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 93345e1b63b69cd0c590ce777e203b06cf7bcb69 Mon Sep 17 00:00:00 2001 +Message-Id: <93345e1b63b69cd0c590ce777e203b06cf7bcb69.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:21 +0200 Subject: [PATCH 004/329] clocksource/drivers: atmel-pit: make option silent -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 d05b04631..3d899b2c7 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 d7c4971ed35222efb7237485812eab5b3e72938e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From f7c582cf48ef62e26df4240e10321a1e47ade705 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:22 +0200 Subject: [PATCH 005/329] ARM: at91: Implement clocksource selection -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 6d77b3e39..55c2cddb3 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 96f44f96d14cb5465687b6c7d6ec2cf4d26d449d Mon Sep 17 00:00:00 2001 -Message-Id: <96f44f96d14cb5465687b6c7d6ec2cf4d26d449d.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c90cec3fe051b5fdafcc85ebd1c51348ce7a37a0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:23 +0200 Subject: [PATCH 006/329] ARM: configs: at91: use new TCB timer driver -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 330d8a9de..e011dafa7 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 1d94c2c8967e08c944fc90a6787c242793e7b3cc Mon Sep 17 00:00:00 2001 -Message-Id: <1d94c2c8967e08c944fc90a6787c242793e7b3cc.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From f07baa3335ef764494f3f554e26878349a8ff49d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Alexandre Belloni Date: Thu, 13 Sep 2018 13:30:24 +0200 Subject: [PATCH 007/329] ARM: configs: at91: unselect PIT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 96e563040..edd33d825 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 0b822e3b084ef66097cc19d9fcd35ee4ab6eccbc Mon Sep 17 00:00:00 2001 -Message-Id: <0b822e3b084ef66097cc19d9fcd35ee4ab6eccbc.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 5bd91a93666e2e1332ef72277afcf35207ba24f6 Mon Sep 17 00:00:00 2001 +Message-Id: <5bd91a93666e2e1332ef72277afcf35207ba24f6.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Marc Zyngier Date: Fri, 27 Jul 2018 13:38:54 +0100 Subject: [PATCH 008/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 2d661bbf2..e170dff6c 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 c9d7a2fed0bcf2c9a82c59ebcbc2a9a11a198f3b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 436c3539b5d3b39dccf769a3627cb94ecb075698 Mon Sep 17 00:00:00 2001 +Message-Id: <436c3539b5d3b39dccf769a3627cb94ecb075698.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Julia Cartwright Date: Fri, 28 Sep 2018 21:03:51 +0000 Subject: [PATCH 009/329] kthread: convert worker lock to raw spinlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 f2bfbb24b..cf7f9b08b 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 32f8d559da2d1a8bcc3d3354e6e2cbe244a5da2f Mon Sep 17 00:00:00 2001 -Message-Id: <32f8d559da2d1a8bcc3d3354e6e2cbe244a5da2f.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From d95c42605a6295992e066a29cb8e7ec96d58978f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: =?UTF-8?q?Horia=20Geant=C4=83?= Date: Mon, 8 Oct 2018 14:09:37 +0300 Subject: [PATCH 010/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 1f44670d2..e9d151ae1 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 4e9e5190267f92f4430dbcde4e7fe5d29acb26d3 Mon Sep 17 00:00:00 2001 -Message-Id: <4e9e5190267f92f4430dbcde4e7fe5d29acb26d3.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 4e2c3189e75ee0f047d79efd36f66b7fdcc65504 Mon Sep 17 00:00:00 2001 +Message-Id: <4e2c3189e75ee0f047d79efd36f66b7fdcc65504.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 7 Jan 2019 13:52:31 +0100 Subject: [PATCH 011/329] sched/fair: Robustify CFS-bandwidth timer locking -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Traditionally hrtimer callbacks were run with IRQs disabled, but with the introduction of HRTIMER_MODE_SOFT it is possible they run from @@ -33,7 +33,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 16 insertions(+), 14 deletions(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c -index 92b1e71f13c8..a05bcb5f5c26 100644 +index d8c249e6dcb7..4665c6c03292 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -4597,7 +4597,7 @@ static u64 distribute_cfs_runtime(struct cfs_bandwidth *cfs_b, u64 remaining) 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 dbf1f9e9e..dd4854d5a 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 8f09b49880e9787d12d0d4374d3389e9fa98b998 Mon Sep 17 00:00:00 2001 -Message-Id: <8f09b49880e9787d12d0d4374d3389e9fa98b998.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 865f8ddda5b9fc471bbf7c080c06e72062b9dc36 Mon Sep 17 00:00:00 2001 +Message-Id: <865f8ddda5b9fc471bbf7c080c06e72062b9dc36.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Frank Rowand Date: Mon, 19 Sep 2011 14:51:14 -0700 Subject: [PATCH 012/329] arm: Convert arm boot_lock to raw -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 be809b713..e649ba69e 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 309eeb867ddba794bd01ff1616eac9bc3c3791c6 Mon Sep 17 00:00:00 2001 -Message-Id: <309eeb867ddba794bd01ff1616eac9bc3c3791c6.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 9862698c10d9149c9a71c22c0f34ffd4781143c6 Mon Sep 17 00:00:00 2001 +Message-Id: <9862698c10d9149c9a71c22c0f34ffd4781143c6.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 17 Jul 2018 18:25:31 +0200 Subject: [PATCH 013/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz There is an issue with threaded interrupts which are marked ONESHOT and using the fasteoi handler. @@ -38,7 +38,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c -index fa3b85b222e3..1bdad61a3ef7 100644 +index 08e2f3a5f124..c3978452c49b 100644 --- a/arch/x86/kernel/apic/io_apic.c +++ b/arch/x86/kernel/apic/io_apic.c @@ -1722,7 +1722,7 @@ static bool io_apic_level_ack_pending(struct mp_chip_data *data) 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 c978a37b6..c404b5669 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 aabbb543ca4b9a9bc2922b2c0b5538fd8c1460b8 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 0f967f53b47a147c58857b9e76845cc842377c4f Mon Sep 17 00:00:00 2001 +Message-Id: <0f967f53b47a147c58857b9e76845cc842377c4f.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 3 Jul 2018 18:19:48 +0200 Subject: [PATCH 014/329] cgroup: use irqsave in cgroup_rstat_flush_locked() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 597527cf6..665cc76fc 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 7c9df5c1b58a7859ef142b8aa653626bced61cdb Mon Sep 17 00:00:00 2001 -Message-Id: <7c9df5c1b58a7859ef142b8aa653626bced61cdb.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 0051d62d6d49a02db52d948335e9f5024cf73fa6 Mon Sep 17 00:00:00 2001 +Message-Id: <0051d62d6d49a02db52d948335e9f5024cf73fa6.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Clark Williams Date: Tue, 3 Jul 2018 13:34:30 -0500 Subject: [PATCH 015/329] fscache: initialize cookie hash table raw spinlocks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 9f43b373c..6d0321433 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 9de54a8f8bd75789fe994fdbd84724ffc4331bde Mon Sep 17 00:00:00 2001 -Message-Id: <9de54a8f8bd75789fe994fdbd84724ffc4331bde.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c19335c8a6df13f2b73b8abf58d9f14ca725715f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 29 Aug 2018 21:59:04 +0200 Subject: [PATCH 016/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 a74010251..30631b457 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 0c8f6d96e3ffefd149facbc13f4c9cfe5f11e9e5 Mon Sep 17 00:00:00 2001 -Message-Id: <0c8f6d96e3ffefd149facbc13f4c9cfe5f11e9e5.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From f2b2f9460d69551ea290a63a7e45e017b04add58 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 11 Oct 2018 16:39:59 +0200 Subject: [PATCH 017/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 bcc8e3223..7a319f62d 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 807b85149744e2d210e0808fe6a354611c9e63e8 Mon Sep 17 00:00:00 2001 -Message-Id: <807b85149744e2d210e0808fe6a354611c9e63e8.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 75f0aa39a3a6ffc854e325be51913e161dc7b10a Mon Sep 17 00:00:00 2001 +Message-Id: <75f0aa39a3a6ffc854e325be51913e161dc7b10a.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 15:06:10 +0200 Subject: [PATCH 018/329] efi: Allow efi=runtime -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 851e776a3..de3f00741 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 87dc5fa070c8d28ca266fedb2a41308233133907 Mon Sep 17 00:00:00 2001 -Message-Id: <87dc5fa070c8d28ca266fedb2a41308233133907.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 28a1e1b3e8ec3632df3d230bcfd2bc885a4c8512 Mon Sep 17 00:00:00 2001 +Message-Id: <28a1e1b3e8ec3632df3d230bcfd2bc885a4c8512.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 24 Jul 2018 14:48:55 +0200 Subject: [PATCH 019/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 ff8eff09a..14e134305 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 44752bc069e62368005b7e0d78b5f55972476ab5 Mon Sep 17 00:00:00 2001 -Message-Id: <44752bc069e62368005b7e0d78b5f55972476ab5.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 7130507c8f5a29402c5361c526def1ea1c492e5f Mon Sep 17 00:00:00 2001 +Message-Id: <7130507c8f5a29402c5361c526def1ea1c492e5f.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 09:13:42 +0200 Subject: [PATCH 020/329] arm64: KVM: compute_layout before altenates are applied -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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(). @@ -21,7 +21,7 @@ Signed-off-by: Sebastian Andrzej Siewior 3 files changed, 8 insertions(+), 6 deletions(-) diff --git a/arch/arm64/include/asm/alternative.h b/arch/arm64/include/asm/alternative.h -index 1a7ba3de7079..d011309e7ad0 100644 +index 849d891c60a8..02064155e1b3 100644 --- a/arch/arm64/include/asm/alternative.h +++ b/arch/arm64/include/asm/alternative.h @@ -35,6 +35,12 @@ void apply_alternatives_module(void *start, size_t length); @@ -38,10 +38,10 @@ index 1a7ba3de7079..d011309e7ad0 100644 " .word 661b - .\n" /* label */ \ " .word 663f - .\n" /* new instruction */ \ diff --git a/arch/arm64/kernel/alternative.c b/arch/arm64/kernel/alternative.c -index b5d603992d40..f92815d56d17 100644 +index 0d345622bbba..ab96c1c3ab77 100644 --- a/arch/arm64/kernel/alternative.c +++ b/arch/arm64/kernel/alternative.c -@@ -224,6 +224,7 @@ static int __apply_alternatives_multi_stop(void *unused) +@@ -212,6 +212,7 @@ static int __apply_alternatives_multi_stop(void *unused) void __init apply_alternatives_all(void) { /* better not try code patching on a live SMP system */ 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 7e3219d08..3f516e175 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 a93b7610c9ca29439bc6db08b0a000a7d0e66a4d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 09fb2688bce798d653e25c1d01566b4490b544eb Mon Sep 17 00:00:00 2001 +Message-Id: <09fb2688bce798d653e25c1d01566b4490b544eb.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 31 Aug 2018 14:16:30 +0200 Subject: [PATCH 021/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 e0506d1f8..8bab04800 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 7f30e9221eefb7abeeae12bf1a6f366c3b6bd5b3 Mon Sep 17 00:00:00 2001 -Message-Id: <7f30e9221eefb7abeeae12bf1a6f366c3b6bd5b3.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 8ef99f3b1883c99b24bb07d010ff17bf045c8bf5 Mon Sep 17 00:00:00 2001 +Message-Id: <8ef99f3b1883c99b24bb07d010ff17bf045c8bf5.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Clark Williams Date: Tue, 18 Sep 2018 10:29:31 -0500 Subject: [PATCH 022/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 3c25e356b..4a8acaa06 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 ae23d611aae11ce024a695eebdf3e9001e51898a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From dd173d3ecc5f2d30bb8563ff03ad65cc424b7a59 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Mon, 29 Oct 2018 11:53:01 +0100 Subject: [PATCH 023/329] EXP rcu: Revert expedited GP parallelization cleverness -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 c34406f6e..dca3fb848 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 4874f8128a86f1f82b2d0cc160114d6ba2eb3aea Mon Sep 17 00:00:00 2001 -Message-Id: <4874f8128a86f1f82b2d0cc160114d6ba2eb3aea.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 0c800bec45fabc7662e22ff337d1771b183e893e Mon Sep 17 00:00:00 2001 +Message-Id: <0c800bec45fabc7662e22ff337d1771b183e893e.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: He Zhe Date: Wed, 19 Dec 2018 16:30:57 +0100 Subject: [PATCH 024/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 a684c05a1..fc17c5541 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 b677c35c663fffab6ced63c01c62095fb5e4d93d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c873c16b68def8fbba678def5b7bd2712e826f83 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 28 Oct 2016 23:05:11 +0200 Subject: [PATCH 025/329] NFSv4: replace seqcount_t with a seqlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 5624300c8..db7251578 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 0393a98b00493daec3caf00a7e579c3f2fb07404 Mon Sep 17 00:00:00 2001 -Message-Id: <0393a98b00493daec3caf00a7e579c3f2fb07404.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 88f6158fd18709b5d03549be2807845859394129 Mon Sep 17 00:00:00 2001 +Message-Id: <88f6158fd18709b5d03549be2807845859394129.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 4 Apr 2017 12:50:16 +0200 Subject: [PATCH 026/329] kernel: sched: Provide a pointer to the valid CPU @@ -9,7 +9,7 @@ Subject: [PATCH 026/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 @@ -337,7 +337,7 @@ index 1a2d18e98bf9..bc182d6fa2a9 100644 /* * One for us, one for whoever does the "release_task()" (usually diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 843394d0ea42..85d663321fb9 100644 +index faef74f63262..42343f58cea4 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -878,7 +878,7 @@ static inline bool is_per_cpu_kthread(struct task_struct *p) @@ -451,7 +451,7 @@ index 843394d0ea42..85d663321fb9 100644 * CPU. * * Since this is common to all placement strategies, this lives here. -@@ -2402,7 +2402,7 @@ void wake_up_new_task(struct task_struct *p) +@@ -2403,7 +2403,7 @@ void wake_up_new_task(struct task_struct *p) #ifdef CONFIG_SMP /* * Fork balancing, do it here and not earlier because: @@ -460,7 +460,7 @@ index 843394d0ea42..85d663321fb9 100644 * - any previously selected CPU might disappear through hotplug * * Use __set_task_cpu() to avoid calling sched_class::migrate_task_rq, -@@ -4317,7 +4317,7 @@ static int __sched_setscheduler(struct task_struct *p, +@@ -4319,7 +4319,7 @@ static int __sched_setscheduler(struct task_struct *p, * the entire root_domain to become SCHED_DEADLINE. We * will also fail if there's no bandwidth available. */ @@ -469,7 +469,7 @@ index 843394d0ea42..85d663321fb9 100644 rq->rd->dl_bw.bw == 0) { task_rq_unlock(rq, p, &rf); return -EPERM; -@@ -4916,7 +4916,7 @@ long sched_getaffinity(pid_t pid, struct cpumask *mask) +@@ -4918,7 +4918,7 @@ long sched_getaffinity(pid_t pid, struct cpumask *mask) goto out_unlock; raw_spin_lock_irqsave(&p->pi_lock, flags); @@ -478,7 +478,7 @@ index 843394d0ea42..85d663321fb9 100644 raw_spin_unlock_irqrestore(&p->pi_lock, flags); out_unlock: -@@ -5497,7 +5497,7 @@ int task_can_attach(struct task_struct *p, +@@ -5499,7 +5499,7 @@ int task_can_attach(struct task_struct *p, * allowed nodes is unnecessary. Thus, cpusets are not * applicable for such threads. This prevents checking for * success of set_cpus_allowed_ptr() on all attached tasks @@ -487,7 +487,7 @@ index 843394d0ea42..85d663321fb9 100644 */ if (p->flags & PF_NO_SETAFFINITY) { ret = -EINVAL; -@@ -5524,7 +5524,7 @@ int migrate_task_to(struct task_struct *p, int target_cpu) +@@ -5526,7 +5526,7 @@ int migrate_task_to(struct task_struct *p, int target_cpu) if (curr_cpu == target_cpu) return 0; @@ -496,7 +496,7 @@ index 843394d0ea42..85d663321fb9 100644 return -EINVAL; /* TODO: This is not properly updating schedstats */ -@@ -5663,7 +5663,7 @@ static void migrate_tasks(struct rq *dead_rq, struct rq_flags *rf) +@@ -5665,7 +5665,7 @@ static void migrate_tasks(struct rq *dead_rq, struct rq_flags *rf) put_prev_task(rq, next); /* @@ -576,7 +576,7 @@ index 8aecfb143859..311b3cf1270e 100644 !dl_task(task) || !task_on_rq_queued(task))) { diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c -index a05bcb5f5c26..97de4ea7dbea 100644 +index 4665c6c03292..80289617ce3d 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -1691,7 +1691,7 @@ static void task_numa_compare(struct task_numa_env *env, @@ -695,7 +695,7 @@ index a05bcb5f5c26..97de4ea7dbea 100644 env->flags |= LBF_DST_PINNED; env->new_dst_cpu = cpu; break; -@@ -7827,7 +7827,7 @@ check_cpu_capacity(struct rq *rq, struct sched_domain *sd) +@@ -7835,7 +7835,7 @@ check_cpu_capacity(struct rq *rq, struct sched_domain *sd) /* * Group imbalance indicates (and tries to solve) the problem where balancing @@ -704,7 +704,7 @@ index a05bcb5f5c26..97de4ea7dbea 100644 * * Imagine a situation of two groups of 4 CPUs each and 4 tasks each with a * cpumask covering 1 CPU of the first group and 3 CPUs of the second group. -@@ -8442,7 +8442,7 @@ static struct sched_group *find_busiest_group(struct lb_env *env) +@@ -8450,7 +8450,7 @@ static struct sched_group *find_busiest_group(struct lb_env *env) /* * If the busiest group is imbalanced the below checks don't * work because they assume all things are equal, which typically @@ -713,7 +713,7 @@ index a05bcb5f5c26..97de4ea7dbea 100644 */ if (busiest->group_type == group_imbalanced) goto force_balance; -@@ -8838,7 +8838,7 @@ static int load_balance(int this_cpu, struct rq *this_rq, +@@ -8846,7 +8846,7 @@ static int load_balance(int this_cpu, struct rq *this_rq, * if the curr task on busiest CPU can't be * moved to this_cpu: */ 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 838042a23..a713622f4 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 6de086b99c4e4b3fbf978f04612591cc50c6ac79 Mon Sep 17 00:00:00 2001 -Message-Id: <6de086b99c4e4b3fbf978f04612591cc50c6ac79.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c6aabaf2f8225455297c0309233fa485c8bc7fd3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Sat, 27 May 2017 19:02:06 +0200 Subject: [PATCH 027/329] kernel/sched/core: add migrate_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz --- include/linux/preempt.h | 23 +++++++ @@ -89,7 +89,7 @@ index 9fb239e12b82..5801e516ba63 100644 * Callback to arch code if there's nosmp or maxcpus=0 on the * boot command line: diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 85d663321fb9..fbdf142013b9 100644 +index 42343f58cea4..77afdcb4d3ba 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -1008,7 +1008,15 @@ void set_cpus_allowed_common(struct task_struct *p, const struct cpumask *new_ma @@ -148,7 +148,7 @@ index 85d663321fb9..fbdf142013b9 100644 if (task_running(rq, p) || p->state == TASK_WAKING) { struct migration_arg arg = { p, dest_cpu }; /* Need help from migration thread: drop lock and wait. */ -@@ -7107,3 +7136,100 @@ const u32 sched_prio_to_wmult[40] = { +@@ -7109,3 +7138,100 @@ const u32 sched_prio_to_wmult[40] = { }; #undef CREATE_TRACE_POINTS 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 3e7ed69cc..7764ecd9a 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 89a73d8e7ad3ce8e0626924dcf9dd3979ef3be3b Mon Sep 17 00:00:00 2001 -Message-Id: <89a73d8e7ad3ce8e0626924dcf9dd3979ef3be3b.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 327d4be878fe3153861c000211b5b7dad3c91111 Mon Sep 17 00:00:00 2001 +Message-Id: <327d4be878fe3153861c000211b5b7dad3c91111.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 9 Oct 2018 17:34:50 +0200 Subject: [PATCH 028/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Jonathan reported that lttng/modules can't use __migrate_disabled(). This function is only used by sched/core itself and the tracing @@ -25,7 +25,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 1 insertion(+) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index fbdf142013b9..183881fe4aab 100644 +index 77afdcb4d3ba..541c7222ffc2 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -1013,6 +1013,7 @@ int __migrate_disabled(struct task_struct *p) 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 239d18a15..a04d08395 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 19083799e26fad55fbebf807fd419af8d1aa1f8a Mon Sep 17 00:00:00 2001 -Message-Id: <19083799e26fad55fbebf807fd419af8d1aa1f8a.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 21a8607e3ac87d41524400aa9e076db312e261ff Mon Sep 17 00:00:00 2001 +Message-Id: <21a8607e3ac87d41524400aa9e076db312e261ff.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 9 Mar 2016 10:51:06 +0100 Subject: [PATCH 029/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 e5f2bbffe..b8b5b6036 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 12118ddc139a78b39c1f463eb3856aefaf4465a8 Mon Sep 17 00:00:00 2001 -Message-Id: <12118ddc139a78b39c1f463eb3856aefaf4465a8.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 6cbc59ebdedbb6bd37674dbb550981dcc81ba140 Mon Sep 17 00:00:00 2001 +Message-Id: <6cbc59ebdedbb6bd37674dbb550981dcc81ba140.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Benedikt Spranger Date: Mon, 8 Mar 2010 18:57:04 +0100 Subject: [PATCH 030/329] clocksource: TCLIB: Allow higher clock rates for @@ -9,7 +9,7 @@ Subject: [PATCH 030/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 22171f269..867927d93 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 c475b279431f075c7a47aa0eaea252ef670eb27b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c7b1c3d119e7b79eff59e2e1d7ad37e563dfd44d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 14 Feb 2013 22:36:59 +0100 Subject: [PATCH 031/329] timekeeping: Split jiffies seqlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 4a4a6ec67..b2acee166 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 0c9739e057ac5da9d2a2ee50e19be93ab49685a0 Mon Sep 17 00:00:00 2001 -Message-Id: <0c9739e057ac5da9d2a2ee50e19be93ab49685a0.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 84a22c05e9c7875ad6465dd1e4960fb7f263fd0c Mon Sep 17 00:00:00 2001 +Message-Id: <84a22c05e9c7875ad6465dd1e4960fb7f263fd0c.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 21 Sep 2011 19:57:12 +0200 Subject: [PATCH 032/329] signal: Revert ptrace preempt magic -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 f3b0b9ec4..b960cfbee 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 f5cdeb20f9bf3932bd736a4b056aa499a57fd2f5 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c110ab27bbd2b2c2eac4ded87343ee5d42346b54 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Marc Kleine-Budde Date: Wed, 5 Mar 2014 00:49:47 +0100 Subject: [PATCH 033/329] net: sched: Use msleep() instead of yield() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 80bfd770b..0e0b4816f 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 033640b308c05afca115999c55e7733ee6946b6a Mon Sep 17 00:00:00 2001 -Message-Id: <033640b308c05afca115999c55e7733ee6946b6a.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From cc7b16e6616fa85c9349dd2eb9799b3748863aac Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 27 Mar 2018 16:24:15 +0200 Subject: [PATCH 034/329] dm rq: remove BUG_ON(!irqs_disabled) check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 190a4628b..9341cca3f 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 41387348a210d60b68464edf4fa4488c918d7d70 Mon Sep 17 00:00:00 2001 -Message-Id: <41387348a210d60b68464edf4fa4488c918d7d70.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 552d07429e80cd7b1d6d87fe0d61bdd35a9d5a5f Mon Sep 17 00:00:00 2001 +Message-Id: <552d07429e80cd7b1d6d87fe0d61bdd35a9d5a5f.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 8 Nov 2013 17:34:54 +0100 Subject: [PATCH 035/329] usb: do no disable interrupts in giveback -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 535258ad1..5f403ea27 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 e598cf96c0e78d1880934e0887b40b90364f4e5c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 82f11a5600cdb8585441eeced935fd48121a2ea7 Mon Sep 17 00:00:00 2001 +Message-Id: <82f11a5600cdb8585441eeced935fd48121a2ea7.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 17 Jun 2011 12:39:57 +0200 Subject: [PATCH 036/329] rt: Provide PREEMPT_RT_BASE config switch -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 2c5a43de2..1001cd83c 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 f0f0a18808e74adade966893b7ad7d367042701b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 69dd1016823043f0c84a17ec7ecf0d684cdd6f95 Mon Sep 17 00:00:00 2001 +Message-Id: <69dd1016823043f0c84a17ec7ecf0d684cdd6f95.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 14 Dec 2011 01:03:49 +0100 Subject: [PATCH 037/329] cpumask: Disable CONFIG_CPUMASK_OFFSTACK for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 5ce5950ba..e133b2e6d 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 70ce69d8a88a7bed92c04ac1f2e8221c9b971f97 Mon Sep 17 00:00:00 2001 -Message-Id: <70ce69d8a88a7bed92c04ac1f2e8221c9b971f97.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 14aff7b583613ece34543f3458216a94c1a0df0c Mon Sep 17 00:00:00 2001 +Message-Id: <14aff7b583613ece34543f3458216a94c1a0df0c.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 8 Jul 2015 17:14:48 +0200 Subject: [PATCH 038/329] jump-label: disable if stop_machine() is used -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 a344ed197..714daa2b4 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 f35ee432990b9cab2a5de108c7f38c769dfccb4e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From e015cf61deaff432c4c48275a462077c72df3c3e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 24 Jul 2011 12:11:43 +0200 Subject: [PATCH 039/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 fb3d95bbf..97885185f 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 a3d74f3ed28e8f5f0427b8a9a418fca257c4cf45 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 5eb5969abd57284025ae4254d3903db0dd6358b0 Mon Sep 17 00:00:00 2001 +Message-Id: <5eb5969abd57284025ae4254d3903db0dd6358b0.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 17 Oct 2017 16:36:18 +0200 Subject: [PATCH 040/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 507cc6543..5965be45e 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 7c1315ffc5e93492cbf98ca4a9794d6f1daab01e Mon Sep 17 00:00:00 2001 -Message-Id: <7c1315ffc5e93492cbf98ca4a9794d6f1daab01e.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 75e8e99566245484bb4121f470e15b5de738afde Mon Sep 17 00:00:00 2001 +Message-Id: <75e8e99566245484bb4121f470e15b5de738afde.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:44:03 -0500 Subject: [PATCH 041/329] mm: Allow only slub on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 48dd257b2..e729676f9 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 0fd7d310ba9d51979d738e34c436a22a60e8219c Mon Sep 17 00:00:00 2001 -Message-Id: <0fd7d310ba9d51979d738e34c436a22a60e8219c.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 456301f31a3d91d8a89c8b2b3c8f9c7ffeb332b8 Mon Sep 17 00:00:00 2001 +Message-Id: <456301f31a3d91d8a89c8b2b3c8f9c7ffeb332b8.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:51:45 +0200 Subject: [PATCH 042/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 5ac479e3c..cea8007fb 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 55b88b1d29e9c569c69871e2da7999ea189907ba Mon Sep 17 00:00:00 2001 -Message-Id: <55b88b1d29e9c569c69871e2da7999ea189907ba.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 1fd9b737374cbbc250831d4a21e8def84743299c Mon Sep 17 00:00:00 2001 +Message-Id: <1fd9b737374cbbc250831d4a21e8def84743299c.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 28 Oct 2012 13:26:09 +0000 Subject: [PATCH 043/329] rcu: Disable RCU_FAST_NO_HZ on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 a96f4bdd6..e7a2b60ce 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 e526523e9b37dd8f44d62f77fde92263bf9c02bb Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 9c14b48cadd85fa31494520009df855bf2b4d6a9 Mon Sep 17 00:00:00 2001 +Message-Id: <9c14b48cadd85fa31494520009df855bf2b4d6a9.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Mar 2014 20:19:05 +0100 Subject: [PATCH 044/329] rcu: make RCU_BOOST default on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 ab9e34185..258060923 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 d3dc8f3b1baa6968fcd4780bf2d31bdf3050d7f1 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 09cf710fc64a9e6c7d99ccdb3e3e10f3b86e5eb7 Mon Sep 17 00:00:00 2001 +Message-Id: <09cf710fc64a9e6c7d99ccdb3e3e10f3b86e5eb7.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:03:52 +0200 Subject: [PATCH 045/329] sched: Disable CONFIG_RT_GROUP_SCHED on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 6869b6643..8d4bdb6c6 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 42e8a7d40e071b6783aa5ac83d6188be0ae3d61c Mon Sep 17 00:00:00 2001 -Message-Id: <42e8a7d40e071b6783aa5ac83d6188be0ae3d61c.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 77683e414fc9fa4cb544f1ceb6ea8907d4622d20 Mon Sep 17 00:00:00 2001 +Message-Id: <77683e414fc9fa4cb544f1ceb6ea8907d4622d20.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Sat, 27 May 2017 19:02:06 +0200 Subject: [PATCH 046/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 bafdb6a95..c004d90e9 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 5918302b4766f0f5e17df8105c65cd5c2597b72a Mon Sep 17 00:00:00 2001 -Message-Id: <5918302b4766f0f5e17df8105c65cd5c2597b72a.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c2bf4d4aecad7e710c7f723a4a0a00144e8a9bab Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 1 Dec 2017 10:42:03 +0100 Subject: [PATCH 047/329] arm*: disable NEON in kernel mode -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 f4e9ee059..7e74ac96b 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 7b06e6d47b0282d98d760f57b6e09fcb2527a943 Mon Sep 17 00:00:00 2001 -Message-Id: <7b06e6d47b0282d98d760f57b6e09fcb2527a943.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 90fcc4e0f87316ecc6d872f902dbd6f67e250c97 Mon Sep 17 00:00:00 2001 +Message-Id: <90fcc4e0f87316ecc6d872f902dbd6f67e250c97.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 14 Jul 2015 14:26:34 +0200 Subject: [PATCH 048/329] powerpc: Use generic rwsem on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 575e7382c..930ea6fa2 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 24faf9104542179355d175b583038573de4ccacf Mon Sep 17 00:00:00 2001 -Message-Id: <24faf9104542179355d175b583038573de4ccacf.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 78ee7dff849f0262f8f0f33501bfaac8c6b26b3b Mon Sep 17 00:00:00 2001 +Message-Id: <78ee7dff849f0262f8f0f33501bfaac8c6b26b3b.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Bogdan Purcareata Date: Fri, 24 Apr 2015 15:53:13 +0000 Subject: [PATCH 049/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 8616f9bc5..9b6eca9f8 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 ff136e3ac7b3eecaf41868d7aa9a1df09386181d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From be153791bdf7b8518d51beb1a5984ccba801fac6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:08:34 +0200 Subject: [PATCH 050/329] powerpc: Disable highmem on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 095e28091..c3ab83944 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 bf22715f3c9c2ceb2fbe4338248a6fc80369c708 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From dfc9c5288d3cb0f41eaebde9e37efa4ecb646fbe Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 17:10:12 +0200 Subject: [PATCH 051/329] mips: Disable highmem on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 1b64be320..1b6ce10d1 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 fe2b32241ea0797ff22b67eac8d314bc374c854a Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ad23b6483e30d8483a7afd6a6ee001fe2f4b54dc Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 26 Jul 2009 02:21:32 +0200 Subject: [PATCH 052/329] x86: Use generic rwsem_spinlocks on -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 3a908749f..b18de95d2 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 5b72bb93781b699ad039895e327ccc0ca866970b Mon Sep 17 00:00:00 2001 -Message-Id: <5b72bb93781b699ad039895e327ccc0ca866970b.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From faa3dca80a4355c6531b06794a1857d389ef7287 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 23 Jan 2014 14:45:59 +0100 Subject: [PATCH 053/329] leds: trigger: disable CPU trigger on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 a8e5029e5..473814bca 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 cbe5992c8901a9a1a94d018817cf08bf3b4b67b5 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b29a1a6addff932e6d55f0515790f56603381fc6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 9 Apr 2015 15:23:01 +0200 Subject: [PATCH 054/329] cpufreq: drop K8's driver from beeing selected -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 77bd12c1e..62a4f4309 100644 --- a/debian/patches-rt/0055-md-disable-bcache.patch +++ b/debian/patches-rt/0055-md-disable-bcache.patch @@ -1,14 +1,14 @@ -From aff098564c44ccec507faea44195f42fe5641478 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 041479007eb05b08b7275d0deba18bdeb6870905 Mon Sep 17 00:00:00 2001 +Message-Id: <041479007eb05b08b7275d0deba18bdeb6870905.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Aug 2013 11:48:57 +0200 Subject: [PATCH 055/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 11db346f6..1bab24bd9 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 000a39fe9c2683f5c4e4d51e0556638f942661b4 Mon Sep 17 00:00:00 2001 -Message-Id: <000a39fe9c2683f5c4e4d51e0556638f942661b4.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 92130515a97aabba57c55ae1632b5f2e248a7055 Mon Sep 17 00:00:00 2001 +Message-Id: <92130515a97aabba57c55ae1632b5f2e248a7055.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 15:03:16 +0200 Subject: [PATCH 056/329] efi: Disable runtime services on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 984bbc912..6df17abf7 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 4ffb1d59149f330e94cf7d65a55d7129cc29a07c Mon Sep 17 00:00:00 2001 -Message-Id: <4ffb1d59149f330e94cf7d65a55d7129cc29a07c.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From db6223c7072c86363a0817ffb9328cc9ed85996d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 22 Jul 2011 17:58:40 +0200 Subject: [PATCH 057/329] printk: Add a printk kill switch -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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. @@ -18,7 +18,7 @@ Signed-off-by: Thomas Gleixner 3 files changed, 71 insertions(+), 20 deletions(-) diff --git a/include/linux/printk.h b/include/linux/printk.h -index cf3eccfe1543..30ebf5f82a7c 100644 +index 6dd867e39365..b9d050428456 100644 --- a/include/linux/printk.h +++ b/include/linux/printk.h @@ -140,9 +140,11 @@ struct va_format { @@ -34,7 +34,7 @@ index cf3eccfe1543..30ebf5f82a7c 100644 #ifdef CONFIG_PRINTK_NMI diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c -index 7a2fdc097c8c..29838e532f46 100644 +index 3cb0e5b479ff..e14732bd316f 100644 --- a/kernel/printk/printk.c +++ b/kernel/printk/printk.c @@ -405,6 +405,58 @@ DEFINE_RAW_SPINLOCK(logbuf_lock); @@ -96,7 +96,7 @@ index 7a2fdc097c8c..29838e532f46 100644 #ifdef CONFIG_PRINTK DECLARE_WAIT_QUEUE_HEAD(log_wait); /* the next printk record to read by syslog(READ) or /proc/kmsg */ -@@ -1905,6 +1957,13 @@ asmlinkage int vprintk_emit(int facility, int level, +@@ -1933,6 +1985,13 @@ asmlinkage int vprintk_emit(int facility, int level, unsigned long flags; u64 curr_log_seq; @@ -110,7 +110,7 @@ index 7a2fdc097c8c..29838e532f46 100644 if (level == LOGLEVEL_SCHED) { level = LOGLEVEL_DEFAULT; in_sched = true; -@@ -2049,26 +2108,6 @@ static bool suppress_message_printing(int level) { return false; } +@@ -2077,26 +2136,6 @@ static bool suppress_message_printing(int level) { return false; } #endif /* CONFIG_PRINTK */ 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 cca2aa56d..5dac0ac23 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 71d2e16cc060770b11a4c867f3a5989141ee159b Mon Sep 17 00:00:00 2001 -Message-Id: <71d2e16cc060770b11a4c867f3a5989141ee159b.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 630e29fe03ffcbb3ccd8e7d0fd82f106d786571e Mon Sep 17 00:00:00 2001 +Message-Id: <630e29fe03ffcbb3ccd8e7d0fd82f106d786571e.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Peter Zijlstra Date: Fri, 2 Sep 2011 14:41:29 +0200 Subject: [PATCH 058/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Gives me an option to screw printk and actually see what the machine says. @@ -20,7 +20,7 @@ Link: http://lkml.kernel.org/n/tip-ykb97nsfmobq44xketrxs977@git.kernel.org 1 file changed, 7 insertions(+) diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c -index 29838e532f46..f934baed564d 100644 +index e14732bd316f..e582817249ce 100644 --- a/kernel/printk/printk.c +++ b/kernel/printk/printk.c @@ -435,6 +435,13 @@ asmlinkage void early_printk(const char *fmt, ...) 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 ed2084440..150fe875f 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 34090a54f73194b31812d6a3f9970d1aafa34edc Mon Sep 17 00:00:00 2001 -Message-Id: <34090a54f73194b31812d6a3f9970d1aafa34edc.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 254e10dd953adfcab9a52a9ca628feb74be83087 Mon Sep 17 00:00:00 2001 +Message-Id: <254e10dd953adfcab9a52a9ca628feb74be83087.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 24 Jul 2009 12:38:56 +0200 Subject: [PATCH 059/329] preempt: Provide preempt_*_(no)rt variants -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 84472e388..ab84ec695 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 603f4c2d045a534af9b69a5996ee1f748e479353 Mon Sep 17 00:00:00 2001 -Message-Id: <603f4c2d045a534af9b69a5996ee1f748e479353.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 6ba1c5e4cd013bee8cee0cc93451dd6cdf18ffdc Mon Sep 17 00:00:00 2001 +Message-Id: <6ba1c5e4cd013bee8cee0cc93451dd6cdf18ffdc.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 8 Mar 2017 14:23:35 +0100 Subject: [PATCH 060/329] futex: workaround migrate_disable/enable in different context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 57a674983..0152c1c44 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 7fa2cc7cf2727d220551ce312905ea470ec0bc09 Mon Sep 17 00:00:00 2001 -Message-Id: <7fa2cc7cf2727d220551ce312905ea470ec0bc09.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 4bbaefcae2f5afe88738712a4d007e178bc67b3c Mon Sep 17 00:00:00 2001 +Message-Id: <4bbaefcae2f5afe88738712a4d007e178bc67b3c.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 20 Jun 2011 09:03:47 +0200 Subject: [PATCH 061/329] rt: Add local irq locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 03d4a6a74..cfbf49e3b 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 d5e4aaae89b930a326c559c93a31a4161ee676f2 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From dc6d393bb513f3c2466b2ea4b55d4f26e71ef900 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Julia Cartwright Date: Mon, 7 May 2018 08:58:56 -0500 Subject: [PATCH 062/329] locallock: provide {get,put}_locked_ptr() variants -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 fda59022c..b21963a81 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 16071d673e3c362fce46ecd14dade1f535c3871e Mon Sep 17 00:00:00 2001 -Message-Id: <16071d673e3c362fce46ecd14dade1f535c3871e.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From d4b8c181b8f5f2ba6edbf89abfcb5320cf73fa78 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 3 Jul 2009 08:44:34 -0500 Subject: [PATCH 063/329] mm/scatterlist: Do not disable irqs on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 355619489..fe146c434 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 139479d76d767ceae115de7929cf34220233ab1f Mon Sep 17 00:00:00 2001 -Message-Id: <139479d76d767ceae115de7929cf34220233ab1f.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From baec3246ff6f71b863cabd866d8471b3dd772236 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Oleg Nesterov Date: Tue, 14 Jul 2015 14:26:34 +0200 Subject: [PATCH 064/329] signal/x86: Delay calling signals in atomic -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 8e4af62cd..62f3dca69 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 438ef86de6bb44a4e122dc430e6fdd9d17612656 Mon Sep 17 00:00:00 2001 -Message-Id: <438ef86de6bb44a4e122dc430e6fdd9d17612656.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 7a87b78c64bc3cf8343852b447d78cf6ae106b87 Mon Sep 17 00:00:00 2001 +Message-Id: <7a87b78c64bc3cf8343852b447d78cf6ae106b87.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Yang Shi Date: Thu, 10 Dec 2015 10:58:51 -0800 Subject: [PATCH 065/329] x86/signal: delay calling signals on 32bit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 d971669f9..3b7f18b88 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 007865c6e1bdc90fdff24aa16899d34d3ac41db4 Mon Sep 17 00:00:00 2001 -Message-Id: <007865c6e1bdc90fdff24aa16899d34d3ac41db4.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 8ccfb80f356bcdc7939cfd20b82977096f52019c Mon Sep 17 00:00:00 2001 +Message-Id: <8ccfb80f356bcdc7939cfd20b82977096f52019c.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 18 Mar 2011 09:18:52 +0100 Subject: [PATCH 066/329] buffer_head: Replace bh_uptodate_lock for -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 e26f4a75c..d4557c83d 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 20e223c31710fe0d220cf31f56ea32ef0c61c991 Mon Sep 17 00:00:00 2001 -Message-Id: <20e223c31710fe0d220cf31f56ea32ef0c61c991.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 5c0e35ebae1e5e08ab49e72aefb76de3969de85f Mon Sep 17 00:00:00 2001 +Message-Id: <5c0e35ebae1e5e08ab49e72aefb76de3969de85f.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 18 Mar 2011 10:11:25 +0100 Subject: [PATCH 067/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 88594b418..1a43ccad8 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 9f2cbdda6b8144d29072afe1527c5dbe54f1bc8f Mon Sep 17 00:00:00 2001 -Message-Id: <9f2cbdda6b8144d29072afe1527c5dbe54f1bc8f.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 59b96aa2d57b0cbfcb7d10b46ecd17f4e364b6c0 Mon Sep 17 00:00:00 2001 +Message-Id: <59b96aa2d57b0cbfcb7d10b46ecd17f4e364b6c0.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Paul Gortmaker Date: Fri, 21 Jun 2013 15:07:25 -0400 Subject: [PATCH 068/329] list_bl: Make list head locking RT safe -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 55af8980e..f1c541e92 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 cf5d4a1b169ff7de5df4b8660e3481af31a2b31c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 5658c126fee12d5c478ad9d45be3ad0fb718c332 Mon Sep 17 00:00:00 2001 +Message-Id: <5658c126fee12d5c478ad9d45be3ad0fb718c332.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 31 Mar 2016 00:04:25 -0500 Subject: [PATCH 069/329] list_bl: fixup bogus lockdep warning -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 e647548a9..bd68fc088 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 7c927f69c47dec2b3a90373d1c0749a88b8e27e2 Mon Sep 17 00:00:00 2001 -Message-Id: <7c927f69c47dec2b3a90373d1c0749a88b8e27e2.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 1a66c09be3bc7fdf90e0267de627a4b888bd765d Mon Sep 17 00:00:00 2001 +Message-Id: <1a66c09be3bc7fdf90e0267de627a4b888bd765d.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:57 -0500 Subject: [PATCH 070/329] genirq: Disable irqpoll on -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 5be2cb9a4..cb4fff88e 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 5ba03b8944101e0f576b7b359eaf19543a7fee9b Mon Sep 17 00:00:00 2001 -Message-Id: <5ba03b8944101e0f576b7b359eaf19543a7fee9b.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 956db5b60cab8cdc9eb1876da6836cf2e3e9cb38 Mon Sep 17 00:00:00 2001 +Message-Id: <956db5b60cab8cdc9eb1876da6836cf2e3e9cb38.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 3 Apr 2011 11:57:29 +0200 Subject: [PATCH 071/329] genirq: Force interrupt thread on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Force threaded_irqs and optimize the code (force_irqthreads) in regard to this. @@ -33,7 +33,7 @@ index eeceac3376fc..315f852b4981 100644 #define force_irqthreads (0) #endif diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c -index efcb54ee0922..0809bf7743af 100644 +index 025fcd029f83..b57d1a2d4d79 100644 --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c @@ -24,6 +24,7 @@ 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 1d4f2491d..14a17288c 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 82fff72073846080cecc7ffa0f3ed27724de4a9b Mon Sep 17 00:00:00 2001 -Message-Id: <82fff72073846080cecc7ffa0f3ed27724de4a9b.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 532c38e1e5fb5c27b6574adbd5ec0abafa87e590 Mon Sep 17 00:00:00 2001 +Message-Id: <532c38e1e5fb5c27b6574adbd5ec0abafa87e590.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 28 May 2018 15:24:20 +0200 Subject: [PATCH 072/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Split the IRQ-off section while accessing the PCP list from zone->lock while freeing pages. diff --git a/debian/patches-rt/0073-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch b/debian/patches-rt/0073-Split-IRQ-off-and-zone-lock-while-freeing-pages-from.patch index 3b961d754..f56d95d58 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 1212c4e9c6d7769a6b923e0bea6b8791b7395b90 Mon Sep 17 00:00:00 2001 -Message-Id: <1212c4e9c6d7769a6b923e0bea6b8791b7395b90.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From d72a0b854a4bc197365cac871e1051f1c21f170a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 28 May 2018 15:24:21 +0200 Subject: [PATCH 073/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Split the IRQ-off section while accessing the PCP list from zone->lock while freeing pages. diff --git a/debian/patches-rt/0074-mm-SLxB-change-list_lock-to-raw_spinlock_t.patch b/debian/patches-rt/0074-mm-SLxB-change-list_lock-to-raw_spinlock_t.patch index d1facdea5..784133a17 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 6b1bf65d021e071dccf657fbae57841973070648 Mon Sep 17 00:00:00 2001 -Message-Id: <6b1bf65d021e071dccf657fbae57841973070648.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From dd386f034c72580313da947e4d61291caec56ddf Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 28 May 2018 15:24:22 +0200 Subject: [PATCH 074/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 334d000c1..2d96d628f 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 1b9d60f29367a7b27d8a716a5d70daa700e744d8 Mon Sep 17 00:00:00 2001 -Message-Id: <1b9d60f29367a7b27d8a716a5d70daa700e744d8.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 814fd358ca735f82d5c61ef025e930407b323939 Mon Sep 17 00:00:00 2001 +Message-Id: <814fd358ca735f82d5c61ef025e930407b323939.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 21 Jun 2018 17:29:19 +0200 Subject: [PATCH 075/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 1a56f0946..969cfd8b4 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 2fed6ba2f350959239f45b5e4d5dc888b23cb153 Mon Sep 17 00:00:00 2001 -Message-Id: <2fed6ba2f350959239f45b5e4d5dc888b23cb153.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From d22cba7e76710f715c9096a58b3bb0ce8b58640a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:37 -0500 Subject: [PATCH 076/329] mm: page_alloc: rt-friendly per-cpu pages -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz rt-friendly per-cpu pages: convert the irqs-off per-cpu locking method into a preemptible, explicit-per-cpu-locks method. diff --git a/debian/patches-rt/0077-mm-swap-Convert-to-percpu-locked.patch b/debian/patches-rt/0077-mm-swap-Convert-to-percpu-locked.patch index 9a0b12561..b03b8ebb7 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 2f5c7c8e52ba0322a60691186db870ca4d57c5cb Mon Sep 17 00:00:00 2001 -Message-Id: <2f5c7c8e52ba0322a60691186db870ca4d57c5cb.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From bb9ad4172a3a877e89400822d859b6bfd8bb9f48 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:51 -0500 Subject: [PATCH 077/329] mm/swap: Convert to percpu locked -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Replace global locks (get_cpu + local_irq_save) with "local_locks()". Currently there is one of for "rotate" and one for "swap". diff --git a/debian/patches-rt/0078-mm-perform-lru_add_drain_all-remotely.patch b/debian/patches-rt/0078-mm-perform-lru_add_drain_all-remotely.patch index 99e6b5886..b75d22683 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 6fe4f5a1dfdf070124bb35ca904901baf7d92445 Mon Sep 17 00:00:00 2001 -Message-Id: <6fe4f5a1dfdf070124bb35ca904901baf7d92445.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 16d32cb8fdd33bacf654c4a7bb0774ec6d48fbc4 Mon Sep 17 00:00:00 2001 +Message-Id: <16d32cb8fdd33bacf654c4a7bb0774ec6d48fbc4.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Luiz Capitulino Date: Fri, 27 May 2016 15:03:28 +0200 Subject: [PATCH 078/329] mm: perform lru_add_drain_all() remotely -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 66b851bdd..887572ff1 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 411a7404a2e510ec921a6ad71986569dd9a74d44 Mon Sep 17 00:00:00 2001 -Message-Id: <411a7404a2e510ec921a6ad71986569dd9a74d44.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From d9de2b64e27437cb8cd89fedebd0d0048f5340b7 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:30:13 -0500 Subject: [PATCH 079/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 6a2c780d0..9fd7d0799 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 b16baaea8beaa395bcf9150ca30f9f60fed4a3d3 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 1f9ecc22bc3d924555ae11dbe0ddeab01952a512 Mon Sep 17 00:00:00 2001 +Message-Id: <1f9ecc22bc3d924555ae11dbe0ddeab01952a512.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Frank Rowand Date: Sat, 1 Oct 2011 18:58:13 -0700 Subject: [PATCH 080/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 ddae864f2..5a67dff03 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 4873fd9bc55e5233bb796f72f661818ff5750e73 Mon Sep 17 00:00:00 2001 -Message-Id: <4873fd9bc55e5233bb796f72f661818ff5750e73.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ed3c40729340989bec3949fc03ecefb279f16084 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 25 Oct 2012 10:32:35 +0100 Subject: [PATCH 081/329] mm: Enable SLUB for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 de567d436..2b3b15944 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 69e10b79d2137f1009db28e55a8f04e23e84de60 Mon Sep 17 00:00:00 2001 -Message-Id: <69e10b79d2137f1009db28e55a8f04e23e84de60.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 3e9e31775846ca871bff4cfe9e435b325b36cfee Mon Sep 17 00:00:00 2001 +Message-Id: <3e9e31775846ca871bff4cfe9e435b325b36cfee.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 9 Jan 2013 12:08:15 +0100 Subject: [PATCH 082/329] slub: Enable irqs for __GFP_WAIT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 faf1bbb60..ddf742f65 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 136df21f36f63830989f9293b62640e7a7d22859 Mon Sep 17 00:00:00 2001 -Message-Id: <136df21f36f63830989f9293b62640e7a7d22859.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From d241c137df7f939bfb97b53197bd348d328dc6b0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 15 Apr 2015 19:00:47 +0200 Subject: [PATCH 083/329] slub: Disable SLUB_CPU_PARTIAL -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 494c8ef8c..e001189df 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 4110484e4a50e5389415841f106f6292665c8d68 Mon Sep 17 00:00:00 2001 -Message-Id: <4110484e4a50e5389415841f106f6292665c8d68.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b48a83eb78e110ba650dc000f03d8e010b3bfb93 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Yang Shi Date: Wed, 30 Oct 2013 11:48:33 -0700 Subject: [PATCH 084/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz The following trace is triggered when running ltp oom test cases: @@ -52,7 +52,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mm/memcontrol.c b/mm/memcontrol.c -index 3b78b6af353b..1323fa231eed 100644 +index aa730a3d5c25..cc920c15e5d7 100644 --- a/mm/memcontrol.c +++ b/mm/memcontrol.c @@ -2084,7 +2084,7 @@ static void drain_all_stock(struct mem_cgroup *root_memcg) 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 f5f0fb3d8..5244ba6d8 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 69fb6764651c58c99b1070f6046b16e4e29c8fe5 Mon Sep 17 00:00:00 2001 -Message-Id: <69fb6764651c58c99b1070f6046b16e4e29c8fe5.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 46cd5bef5cbeef69430f8243dffad3d6bf4d5f60 Mon Sep 17 00:00:00 2001 +Message-Id: <46cd5bef5cbeef69430f8243dffad3d6bf4d5f60.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 28 Jan 2015 17:14:16 +0100 Subject: [PATCH 085/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz There are a few local_irq_disable() which then take sleeping locks. This patch converts them local locks. @@ -17,7 +17,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 16 insertions(+), 8 deletions(-) diff --git a/mm/memcontrol.c b/mm/memcontrol.c -index 1323fa231eed..4156a4e766fb 100644 +index cc920c15e5d7..a54cfafba8ad 100644 --- a/mm/memcontrol.c +++ b/mm/memcontrol.c @@ -69,6 +69,7 @@ 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 f5355e7b3..97728572e 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 2f256596af09c555baff31bddcfa3d9225b94290 Mon Sep 17 00:00:00 2001 -Message-Id: <2f256596af09c555baff31bddcfa3d9225b94290.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b43b38e7434705ca1df250741a943f22c3aa3c4b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Mike Galbraith Date: Tue, 22 Mar 2016 11:16:09 +0100 Subject: [PATCH 086/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 49fe5c91f..fdc0760e8 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 395e14d873c2de95585f3329fc159f66af1ea647 Mon Sep 17 00:00:00 2001 -Message-Id: <395e14d873c2de95585f3329fc159f66af1ea647.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 618330e49648f0851200b9e4ca83e18dd4d07131 Mon Sep 17 00:00:00 2001 +Message-Id: <618330e49648f0851200b9e4ca83e18dd4d07131.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 11 Dec 2018 21:53:43 +0100 Subject: [PATCH 087/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 041906256..7385c8544 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 4d4de1a5469f2ae70c814580ff7c8b075cdbad99 Mon Sep 17 00:00:00 2001 -Message-Id: <4d4de1a5469f2ae70c814580ff7c8b075cdbad99.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 4ca4b11d8f733ff4a065686ddcb1221d5f4fbe21 Mon Sep 17 00:00:00 2001 +Message-Id: <4ca4b11d8f733ff4a065686ddcb1221d5f4fbe21.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 25 Jan 2017 16:34:27 +0100 Subject: [PATCH 088/329] radix-tree: use local locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 a6aa4ac22..b8dcca3f6 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 77025c9c9fdf7f20ce09e36a49b8da02a23cc6c5 Mon Sep 17 00:00:00 2001 -Message-Id: <77025c9c9fdf7f20ce09e36a49b8da02a23cc6c5.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From a3af87bbfafb04784c4c873c21c5aa1458ba7483 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:34 -0500 Subject: [PATCH 089/329] timers: Prepare for full preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 @@ -33,7 +33,7 @@ index 7b066fd38248..54627d046b3a 100644 #else # define del_timer_sync(t) del_timer(t) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 183881fe4aab..626fb9904ed1 100644 +index 541c7222ffc2..c0058e62a3fc 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -498,11 +498,14 @@ void resched_cpu(int cpu) @@ -63,7 +63,7 @@ index 183881fe4aab..626fb9904ed1 100644 } diff --git a/kernel/time/timer.c b/kernel/time/timer.c -index ae64cb819a9a..9019c9caf146 100644 +index 6c54cf481fde..458fa0189514 100644 --- a/kernel/time/timer.c +++ b/kernel/time/timer.c @@ -44,6 +44,7 @@ @@ -84,7 +84,7 @@ index ae64cb819a9a..9019c9caf146 100644 unsigned long clk; unsigned long next_expiry; unsigned int cpu; -@@ -1178,6 +1182,33 @@ void add_timer_on(struct timer_list *timer, int cpu) +@@ -1189,6 +1193,33 @@ void add_timer_on(struct timer_list *timer, int cpu) } EXPORT_SYMBOL_GPL(add_timer_on); @@ -118,7 +118,7 @@ index ae64cb819a9a..9019c9caf146 100644 /** * del_timer - deactivate a timer. * @timer: the timer to be deactivated -@@ -1233,7 +1264,7 @@ int try_to_del_timer_sync(struct timer_list *timer) +@@ -1244,7 +1275,7 @@ int try_to_del_timer_sync(struct timer_list *timer) } EXPORT_SYMBOL(try_to_del_timer_sync); @@ -127,7 +127,7 @@ index ae64cb819a9a..9019c9caf146 100644 /** * del_timer_sync - deactivate a timer and wait for the handler to finish. * @timer: the timer to be deactivated -@@ -1293,7 +1324,7 @@ int del_timer_sync(struct timer_list *timer) +@@ -1304,7 +1335,7 @@ int del_timer_sync(struct timer_list *timer) int ret = try_to_del_timer_sync(timer); if (ret >= 0) return ret; @@ -136,7 +136,7 @@ index ae64cb819a9a..9019c9caf146 100644 } } EXPORT_SYMBOL(del_timer_sync); -@@ -1354,13 +1385,16 @@ static void expire_timers(struct timer_base *base, struct hlist_head *head) +@@ -1365,13 +1396,16 @@ static void expire_timers(struct timer_base *base, struct hlist_head *head) fn = timer->function; @@ -154,7 +154,7 @@ index ae64cb819a9a..9019c9caf146 100644 raw_spin_lock_irq(&base->lock); } } -@@ -1683,8 +1717,8 @@ static inline void __run_timers(struct timer_base *base) +@@ -1694,8 +1728,8 @@ static inline void __run_timers(struct timer_base *base) while (levels--) expire_timers(base, heads + levels); } @@ -164,7 +164,7 @@ index ae64cb819a9a..9019c9caf146 100644 } /* -@@ -1929,6 +1963,9 @@ static void __init init_timer_cpu(int cpu) +@@ -1940,6 +1974,9 @@ static void __init init_timer_cpu(int cpu) base->cpu = cpu; raw_spin_lock_init(&base->lock); base->clk = jiffies; 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 10067c785..bff86b45f 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 6d433304f1894bb7aefb0b6e58e8e41e5e18a6b4 Mon Sep 17 00:00:00 2001 -Message-Id: <6d433304f1894bb7aefb0b6e58e8e41e5e18a6b4.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 80718f0b78e1f76c9b8937257215b63ed4355e23 Mon Sep 17 00:00:00 2001 +Message-Id: <80718f0b78e1f76c9b8937257215b63ed4355e23.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 6 Nov 2011 12:26:18 +0100 Subject: [PATCH 090/329] x86: kvm Require const tsc for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Non constant TSC is a nightmare on bare metal already, but with virtualization it becomes a complete disaster because the workarounds @@ -18,10 +18,10 @@ 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 0aa5c4134b90..5dcb794b88e2 100644 +index 5b2440e591fc..9fc847c237da 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c -@@ -6848,6 +6848,13 @@ int kvm_arch_init(void *opaque) +@@ -6850,6 +6850,13 @@ int kvm_arch_init(void *opaque) goto out; } 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 60ec0a0c9..f877131ad 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 b7bf15cc61470fee2fce877652d997f62af399c7 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 22fd004a43ed16303a43545c0d993ef12e1e5351 Mon Sep 17 00:00:00 2001 +Message-Id: <22fd004a43ed16303a43545c0d993ef12e1e5351.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 4 Oct 2017 10:24:23 +0200 Subject: [PATCH 091/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 613a2ea3e..20bed05f6 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 69db399dcf21576a7500c5ee619f2687a1199a37 Mon Sep 17 00:00:00 2001 -Message-Id: <69db399dcf21576a7500c5ee619f2687a1199a37.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From f441a761836590a8dfa82a921ab4940a1afae6f5 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 28 Oct 2013 12:19:57 +0100 Subject: [PATCH 092/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 3dabfb897..a02178675 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 4790a4aae67cb29ef058e2bc5f91ed61004957b6 Mon Sep 17 00:00:00 2001 -Message-Id: <4790a4aae67cb29ef058e2bc5f91ed61004957b6.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 5790c349caf92d7ae4663edbdf52dc8cc479ab24 Mon Sep 17 00:00:00 2001 +Message-Id: <5790c349caf92d7ae4663edbdf52dc8cc479ab24.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Daniel Wagner Date: Fri, 11 Jul 2014 15:26:11 +0200 Subject: [PATCH 093/329] work-simple: Simple work queue implemenation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 db64f4aa9..f2b5bc391 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 41f5d4a8c268864e3eec93d075dbb4c5bb4c7215 Mon Sep 17 00:00:00 2001 -Message-Id: <41f5d4a8c268864e3eec93d075dbb4c5bb4c7215.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 954eccfdee5c112121d31d3e5ed0732d7978155a Mon Sep 17 00:00:00 2001 +Message-Id: <954eccfdee5c112121d31d3e5ed0732d7978155a.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 10 Sep 2018 18:00:31 +0200 Subject: [PATCH 094/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 16dc15838..9dd61f461 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 dd8595e75900ac6512c872c76fb4a2843babfeb0 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 86023a52a1a1fd6885aca43b9e40ac1e7c2ae6f5 Mon Sep 17 00:00:00 2001 +Message-Id: <86023a52a1a1fd6885aca43b9e40ac1e7c2ae6f5.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 11 Jan 2013 11:23:51 +0100 Subject: [PATCH 095/329] completion: Use simple wait queues -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Completions have no long lasting callbacks and therefor do not need the complex waitqueue variant. Use simple waitqueues which reduces the @@ -323,10 +323,10 @@ index a1ad5b7d5521..755a58084978 100644 } EXPORT_SYMBOL(completion_done); diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 626fb9904ed1..dab0e4382492 100644 +index c0058e62a3fc..b32dfc96620d 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -7156,7 +7156,10 @@ void migrate_disable(void) +@@ -7158,7 +7158,10 @@ void migrate_disable(void) return; } #ifdef CONFIG_SCHED_DEBUG @@ -338,7 +338,7 @@ index 626fb9904ed1..dab0e4382492 100644 #endif if (p->migrate_disable) { -@@ -7186,7 +7189,10 @@ void migrate_enable(void) +@@ -7188,7 +7191,10 @@ void migrate_enable(void) } #ifdef CONFIG_SCHED_DEBUG 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 131ee3737..1b1a52c65 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 88725b3d530513773c06b5084302bf9ab7ce6118 Mon Sep 17 00:00:00 2001 -Message-Id: <88725b3d530513773c06b5084302bf9ab7ce6118.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ac293d2dacfe32627d56a7b5a926b134f703e50c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Feb 2015 18:49:10 +0100 Subject: [PATCH 096/329] fs/aio: simple simple work -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 f6bfbdb6d..099394a06 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 2f88e5f4c41b1ff5bf3338f2a8bd3f1ed178e2e3 Mon Sep 17 00:00:00 2001 -Message-Id: <2f88e5f4c41b1ff5bf3338f2a8bd3f1ed178e2e3.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c577359102ed6ef26386114e4ec850d686c8eb4e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 15 Nov 2017 17:29:51 +0100 Subject: [PATCH 097/329] time/hrtimer: avoid schedule_work() with interrupts disabled -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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. @@ -17,7 +17,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/kernel/time/timer.c b/kernel/time/timer.c -index 9019c9caf146..3fab1c50bf1b 100644 +index 458fa0189514..845f687d2d1c 100644 --- a/kernel/time/timer.c +++ b/kernel/time/timer.c @@ -217,8 +217,7 @@ static DEFINE_PER_CPU(struct timer_base, timer_bases[NR_BASES]); 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 a364e50fe..6d457241e 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 c8e3c8a75997d354c63d081c5a8aefaf2cb38797 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From a3e30f6b6a09d8c3ea8c0c96cc0cfc6cebdb6804 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 3 Jul 2018 11:25:41 +0200 Subject: [PATCH 098/329] hrtimer: consolidate hrtimer_init() + hrtimer_init_sleeper() calls -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 4e5422eb8..641ef5990 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 3119374a6d8237ba8047e076502efaafa2950a3b Mon Sep 17 00:00:00 2001 -Message-Id: <3119374a6d8237ba8047e076502efaafa2950a3b.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 21f166a2b78dcb4b748826540d1bdd84f0a164b3 Mon Sep 17 00:00:00 2001 +Message-Id: <21f166a2b78dcb4b748826540d1bdd84f0a164b3.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Ingo Molnar Date: Fri, 3 Jul 2009 08:29:34 -0500 Subject: [PATCH 099/329] hrtimers: Prepare full preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 e7e39531b..7f79fc69f 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 0438317cbda3b7d1f46b5e1e2fd0df0666c8a523 Mon Sep 17 00:00:00 2001 -Message-Id: <0438317cbda3b7d1f46b5e1e2fd0df0666c8a523.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 6c626da3237f042b61b9a0b31e7c73ac41842b08 Mon Sep 17 00:00:00 2001 +Message-Id: <6c626da3237f042b61b9a0b31e7c73ac41842b08.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 3 Jul 2009 08:44:31 -0500 Subject: [PATCH 100/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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. @@ -91,7 +91,7 @@ index a17e6302ded5..e3ea20b36776 100644 /* diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index dab0e4382492..dc70ec937317 100644 +index b32dfc96620d..a92d2dcdcdaf 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -315,7 +315,7 @@ static void hrtick_rq_init(struct rq *rq) @@ -117,7 +117,7 @@ index 311b3cf1270e..7d47c9b9726e 100644 } diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c -index 97de4ea7dbea..26ed8b64ebef 100644 +index 80289617ce3d..661b5d6d4197 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -4951,9 +4951,9 @@ void init_cfs_bandwidth(struct cfs_bandwidth *cfs_b) 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 4353bd1e6..f074e8e1f 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 49cc3d0703683e80b6ff4167bee12bdd3e8aceb5 Mon Sep 17 00:00:00 2001 -Message-Id: <49cc3d0703683e80b6ff4167bee12bdd3e8aceb5.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c7bb69d07655a229ad8ef92b216062c4d3bc11c2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 8 Jan 2019 12:31:06 +0100 Subject: [PATCH 101/329] sched/fair: Make the hrtimers non-hard again -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Since commit "sched/fair: Robustify CFS-bandwidth timer locking" both hrtimer can run in softirq context because now interrupts are disabled @@ -17,7 +17,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c -index 26ed8b64ebef..97de4ea7dbea 100644 +index 661b5d6d4197..80289617ce3d 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -4951,9 +4951,9 @@ void init_cfs_bandwidth(struct cfs_bandwidth *cfs_b) 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 441f4388b..0a61a63b8 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 b254e6884c3d1b9ea98c1aab9e5e280ccfa67cf7 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 3f9e3faece468f4feca7178ff48f4cc39dcc6226 Mon Sep 17 00:00:00 2001 +Message-Id: <3f9e3faece468f4feca7178ff48f4cc39dcc6226.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Yang Shi Date: Mon, 16 Sep 2013 14:09:19 -0700 Subject: [PATCH 102/329] hrtimer: Move schedule_work call to helper thread -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 43c100be2..3050ed6d9 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 c0c4f711bef214253f9e094a2aa8ec4a48b4bab3 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c6453deecbd7587b3ac13b1d97df049d73b95b1d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 6 Dec 2018 10:15:13 +0100 Subject: [PATCH 103/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 becc8c39c..1df70c790 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 4b6b43faa02b97fc9179319122bb014f65e235b5 Mon Sep 17 00:00:00 2001 -Message-Id: <4b6b43faa02b97fc9179319122bb014f65e235b5.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From a9c2c94b513530408d0bce3997002b5a1d0d89b2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: John Stultz Date: Fri, 3 Jul 2009 08:29:58 -0500 Subject: [PATCH 104/329] posix-timers: Thread posix-cpu-timers on -rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 355a8ac87..e9c92f182 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 75fee459d34af546834611d9cd9a2f002df91bf7 Mon Sep 17 00:00:00 2001 -Message-Id: <75fee459d34af546834611d9cd9a2f002df91bf7.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 37348ea2aae637f955a889e33b3ed77b3580b7ca Mon Sep 17 00:00:00 2001 +Message-Id: <37348ea2aae637f955a889e33b3ed77b3580b7ca.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 31 May 2011 16:59:16 +0200 Subject: [PATCH 105/329] sched: Move task_struct cleanup to RCU -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 a57b521d2..39dead58f 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 c6a92414419452341cd67f947084a2be110b7b33 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From bd488cd482611dcd51a961890ebd452844fba7ee Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 6 Jun 2011 12:12:51 +0200 Subject: [PATCH 106/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Put an upper limit on the number of tasks which are migrated per batch to avoid large latencies. @@ -16,7 +16,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 4 insertions(+) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index dc70ec937317..1fe932aac00f 100644 +index a92d2dcdcdaf..87c04b6a78d2 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -44,7 +44,11 @@ const_debug unsigned int sysctl_sched_features = 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 9c6b4429d..503d0de3c 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 d91e269d2b5e4934af93621c9b40c63bd78b7c4d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 7f1ff4cd6b39bf6153ba39335d5554d843345d68 Mon Sep 17 00:00:00 2001 +Message-Id: <7f1ff4cd6b39bf6153ba39335d5554d843345d68.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 6 Jun 2011 12:20:33 +0200 Subject: [PATCH 107/329] sched: Move mmdrop to RCU on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Takes sleeping locks and calls into the memory allocator, so nothing we want to do in task switch and oder atomic contexts. @@ -87,10 +87,10 @@ index 309f4a20d4ac..d4ec53c72577 100644 { struct mm_struct *mm; diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 1fe932aac00f..fae976506632 100644 +index 87c04b6a78d2..ec979c93a488 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -2729,9 +2729,13 @@ static struct rq *finish_task_switch(struct task_struct *prev) +@@ -2731,9 +2731,13 @@ static struct rq *finish_task_switch(struct task_struct *prev) * provided by mmdrop(), * - a sync_core for SYNC_CORE. */ @@ -105,7 +105,7 @@ index 1fe932aac00f..fae976506632 100644 } if (unlikely(prev_state == TASK_DEAD)) { if (prev->sched_class->task_dead) -@@ -5602,6 +5606,7 @@ void sched_setnuma(struct task_struct *p, int nid) +@@ -5604,6 +5608,7 @@ void sched_setnuma(struct task_struct *p, int nid) #endif /* CONFIG_NUMA_BALANCING */ #ifdef CONFIG_HOTPLUG_CPU 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 0aa802825..d0d076211 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 c8f01c68c10d0615999b6f7a53cc7a9238319c61 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From d0c187421ce1a2cb768296a6079d1914f00e1bf9 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 21 Nov 2016 19:31:08 +0100 Subject: [PATCH 108/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 @@ -49,10 +49,10 @@ index d4ec53c72577..29b54a64daf5 100644 task_numa_free(tsk, true); security_task_free(tsk); diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index fae976506632..7927ce657c44 100644 +index ec979c93a488..3600139cb690 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -2741,15 +2741,6 @@ static struct rq *finish_task_switch(struct task_struct *prev) +@@ -2743,15 +2743,6 @@ static struct rq *finish_task_switch(struct task_struct *prev) if (prev->sched_class->task_dead) prev->sched_class->task_dead(prev); 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 6d20343db..c16361476 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 3ba4d8eee40b02f3d072aa382b26c302b18a6e1e Mon Sep 17 00:00:00 2001 -Message-Id: <3ba4d8eee40b02f3d072aa382b26c302b18a6e1e.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 100c0ec5ffe14f7b9c0afb47d8cb6c08f249466c Mon Sep 17 00:00:00 2001 +Message-Id: <100c0ec5ffe14f7b9c0afb47d8cb6c08f249466c.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 25 Jun 2011 09:21:04 +0200 Subject: [PATCH 109/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 @@ -43,7 +43,7 @@ index 9a0e01e48602..42846a65df9a 100644 #ifdef CONFIG_SMP diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 7927ce657c44..dba77f924ec8 100644 +index 3600139cb690..53d9f8927619 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -1999,8 +1999,27 @@ try_to_wake_up(struct task_struct *p, unsigned int state, int wake_flags) 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 3177baaaa..1ad2e33c7 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 59eae7f9b913be891996c958eeb8bd21ac786558 Mon Sep 17 00:00:00 2001 -Message-Id: <59eae7f9b913be891996c958eeb8bd21ac786558.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 6b607c25ac8447822464e1b4d8a0c038d729bd88 Mon Sep 17 00:00:00 2001 +Message-Id: <6b607c25ac8447822464e1b4d8a0c038d729bd88.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 7 Jun 2011 09:19:06 +0200 Subject: [PATCH 110/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz RT changes the rcu_preempt_depth semantics, so we cannot check for it in might_sleep(). @@ -43,10 +43,10 @@ index 68cbe111420b..027c58cdbb6e 100644 /* Internal to kernel */ diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index dba77f924ec8..dec4822184bb 100644 +index 53d9f8927619..2aa1d2a9ee5e 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -6191,7 +6191,7 @@ void __init sched_init(void) +@@ -6193,7 +6193,7 @@ void __init sched_init(void) #ifdef CONFIG_DEBUG_ATOMIC_SLEEP static inline int preempt_count_equals(int preempt_offset) { 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 d89662473..258f1286d 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 36ddfc2bd31da8c0d0a868d6964b4bbe5bbe6dd2 Mon Sep 17 00:00:00 2001 -Message-Id: <36ddfc2bd31da8c0d0a868d6964b4bbe5bbe6dd2.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 776bb8cf3dc2e9af29075edc62e3d77709248eb0 Mon Sep 17 00:00:00 2001 +Message-Id: <776bb8cf3dc2e9af29075edc62e3d77709248eb0.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 22:51:33 +0200 Subject: [PATCH 111/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 fcd0c05b3..6b2fce293 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 fae184a847d770acc42344912d7a7ee4dd076e71 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From bc161171317ea0f7b246b0b110d3ebf1161c8230 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 13 Sep 2011 16:42:35 +0200 Subject: [PATCH 112/329] sched: Disable TTWU_QUEUE on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 0e1f0f2af..663d39a5a 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 88ad37991950318c862016a9beba42af7bfa91d4 Mon Sep 17 00:00:00 2001 -Message-Id: <88ad37991950318c862016a9beba42af7bfa91d4.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From a879ff2aabb742224696f251c36fb20327e91899 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Steven Rostedt Date: Mon, 18 Mar 2013 15:12:49 -0400 Subject: [PATCH 113/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 @@ -28,10 +28,10 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index dec4822184bb..7071cbc98e01 100644 +index 2aa1d2a9ee5e..be048e7066d1 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -3539,8 +3539,10 @@ static void __sched notrace __schedule(bool preempt) +@@ -3541,8 +3541,10 @@ static void __sched notrace __schedule(bool preempt) * If a worker went to sleep, notify and ask workqueue * whether it wants to wake up a task to maintain * concurrency. 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 e2484a787..e118f2db0 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 1e802fce8a92be8cf3b201d8c658def007b2cbde Mon Sep 17 00:00:00 2001 -Message-Id: <1e802fce8a92be8cf3b201d8c658def007b2cbde.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 460bf827ec9fafd856dda44b73ed5634efe3345e Mon Sep 17 00:00:00 2001 +Message-Id: <460bf827ec9fafd856dda44b73ed5634efe3345e.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Daniel Bristot de Oliveira Date: Mon, 26 Jun 2017 17:07:15 +0200 Subject: [PATCH 114/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 @@ -85,10 +85,10 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 44 insertions(+), 5 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 7071cbc98e01..3a9b540fd3b9 100644 +index be048e7066d1..25dd44553ea6 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -7178,6 +7178,47 @@ const u32 sched_prio_to_wmult[40] = { +@@ -7180,6 +7180,47 @@ const u32 sched_prio_to_wmult[40] = { #if defined(CONFIG_PREEMPT_COUNT) && defined(CONFIG_SMP) @@ -136,7 +136,7 @@ index 7071cbc98e01..3a9b540fd3b9 100644 void migrate_disable(void) { struct task_struct *p = current; -@@ -7201,10 +7242,9 @@ void migrate_disable(void) +@@ -7203,10 +7244,9 @@ void migrate_disable(void) } preempt_disable(); @@ -149,7 +149,7 @@ index 7071cbc98e01..3a9b540fd3b9 100644 preempt_enable(); } -@@ -7236,9 +7276,8 @@ void migrate_enable(void) +@@ -7238,9 +7278,8 @@ void migrate_enable(void) preempt_disable(); 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 53997f726..77db3e571 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 85c9e2d307b41b0004871e9161ac37b2f79d3405 Mon Sep 17 00:00:00 2001 -Message-Id: <85c9e2d307b41b0004871e9161ac37b2f79d3405.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From f1067b9d89bf2cca29e379c63773afec076b85a4 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 15 Jun 2011 12:36:06 +0200 Subject: [PATCH 115/329] hotplug: Lightweight get online cpus -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz get_online_cpus() is a heavy weight function which involves a global mutex. migrate_disable() wants a simpler construct which prevents only @@ -72,10 +72,10 @@ index 08b9d6ba0807..267fcad3a81e 100644 void cpus_read_lock(void) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 3a9b540fd3b9..09a3bd47ac4d 100644 +index 25dd44553ea6..2197f965f9bb 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -7242,6 +7242,7 @@ void migrate_disable(void) +@@ -7244,6 +7244,7 @@ void migrate_disable(void) } preempt_disable(); @@ -83,7 +83,7 @@ index 3a9b540fd3b9..09a3bd47ac4d 100644 migrate_disable_update_cpus_allowed(p); p->migrate_disable = 1; -@@ -7307,12 +7308,15 @@ void migrate_enable(void) +@@ -7309,12 +7310,15 @@ void migrate_enable(void) arg.task = p; arg.dest_cpu = dest_cpu; 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 53927ad36..f15e27ae3 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 4bf6bad97c9674124fcbb9e9a7296fb9ca3182b0 Mon Sep 17 00:00:00 2001 -Message-Id: <4bf6bad97c9674124fcbb9e9a7296fb9ca3182b0.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 0234a180c95c0b984b9eeca98ba314996616e9a9 Mon Sep 17 00:00:00 2001 +Message-Id: <0234a180c95c0b984b9eeca98ba314996616e9a9.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:56:42 +0200 Subject: [PATCH 116/329] trace: Add migrate-disabled counter to tracing output -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Signed-off-by: Thomas Gleixner --- diff --git a/debian/patches-rt/0117-lockdep-Make-it-RT-aware.patch b/debian/patches-rt/0117-lockdep-Make-it-RT-aware.patch index 97c8a433d..9b26abb2a 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 d95c9b99941927302bb971d15be6c1aa134b9651 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From d458fcd39ec186a4b8de8c0d4c94a2a6bee11606 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 18:51:23 +0200 Subject: [PATCH 117/329] lockdep: Make it RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 43eaf1952..72d0df6a8 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 768c87ca12f332fce71bd2761d907ac769c41dd1 Mon Sep 17 00:00:00 2001 -Message-Id: <768c87ca12f332fce71bd2761d907ac769c41dd1.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c8bb4949b65dad2103f2829601ae7c4e4f45743f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Ingo Molnar Date: Tue, 29 Nov 2011 20:18:22 -0500 Subject: [PATCH 118/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 f01f3c55a..ed231e39d 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 7bffa3aab272faffc0258ae1ac28130f1cb15e51 Mon Sep 17 00:00:00 2001 -Message-Id: <7bffa3aab272faffc0258ae1ac28130f1cb15e51.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 0718290d49d6f2ab8780c85b474f04aef7a460be Mon Sep 17 00:00:00 2001 +Message-Id: <0718290d49d6f2ab8780c85b474f04aef7a460be.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 13 Nov 2011 17:17:09 +0100 Subject: [PATCH 119/329] softirq: Check preemption after reenabling interrupts -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz raise_softirq_irqoff() disables interrupts and wakes the softirq daemon, but after reenabling interrupts there is no preemption check, 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 6f4255629..96deb4911 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 f81f11c9eed16e4c02170c311cb5e266f75739c6 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From fcf6b88da10c62871f28956a0390a19e3379b42e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 18 Jul 2011 13:59:17 +0200 Subject: [PATCH 120/329] softirq: Disable softirq stacks for RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Disable extra stacks for softirqs. We want to preempt softirqs and having them on special IRQ-stack does not make this easier. diff --git a/debian/patches-rt/0121-softirq-Split-softirq-locks.patch b/debian/patches-rt/0121-softirq-Split-softirq-locks.patch index 334855a70..8522e93ae 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 921b748460720ebd192635d0f95162867fcc3dc3 Mon Sep 17 00:00:00 2001 -Message-Id: <921b748460720ebd192635d0f95162867fcc3dc3.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c82069adfa44bb0c556ddb4e90b5c0b241366694 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 4 Oct 2012 14:20:47 +0100 Subject: [PATCH 121/329] softirq: Split softirq locks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 ec78f2312610..7c064c6aff55 100644 +index fdfef08da0c4..2180c6388eb9 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 b11d350da..00700b1d9 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 bcc13fe39aece97f424f3256e90a6cd0f17d7b01 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 740e990c07d7bbe8c56b3e0a8b24e11795958190 Mon Sep 17 00:00:00 2001 +Message-Id: <740e990c07d7bbe8c56b3e0a8b24e11795958190.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 16 Jun 2017 19:03:16 +0200 Subject: [PATCH 122/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 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 2338ba8d0..b18962ca0 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 e0f9b20c3185ff122ec48f9a7fa0cf02a075efe1 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b3780ae29e481b63d9dfe2ddb6cea8535e27d188 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 31 Jan 2012 13:01:27 +0100 Subject: [PATCH 123/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 @@ -72,10 +72,10 @@ index 6ecaf056ab63..d2487df7ae89 100644 #define IRQ_NO_BALANCING_MASK (IRQ_PER_CPU | IRQ_NO_BALANCING) diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c -index 0809bf7743af..ccd8af6fe49d 100644 +index b57d1a2d4d79..44ee91ca0088 100644 --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c -@@ -957,7 +957,15 @@ irq_forced_thread_fn(struct irq_desc *desc, struct irqaction *action) +@@ -990,7 +990,15 @@ irq_forced_thread_fn(struct irq_desc *desc, struct irqaction *action) atomic_inc(&desc->threads_handled); irq_finalize_oneshot(desc, action); @@ -92,7 +92,7 @@ index 0809bf7743af..ccd8af6fe49d 100644 return ret; } -@@ -1467,6 +1475,9 @@ __setup_irq(unsigned int irq, struct irq_desc *desc, struct irqaction *new) +@@ -1500,6 +1508,9 @@ __setup_irq(unsigned int irq, struct irq_desc *desc, struct irqaction *new) irqd_set(&desc->irq_data, IRQD_NO_BALANCING); } 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 1ec9feea8..76373adb4 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 feb3592a44d5482ae9e3a5b3812355048aba2956 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 3533db89c1aea4df835e65d57b772b401072c661 Mon Sep 17 00:00:00 2001 +Message-Id: <3533db89c1aea4df835e65d57b772b401072c661.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 20 Jan 2016 16:34:17 +0100 Subject: [PATCH 124/329] softirq: split timer softirqs out of ksoftirqd -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 bcf00b452..ec782600d 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 f148f4152b11a7592f60ca3e679b0c4a2a40c926 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 459bfeb44aa76d1d7baf88d6ba0c1f4b766405ee Mon Sep 17 00:00:00 2001 +Message-Id: <459bfeb44aa76d1d7baf88d6ba0c1f4b766405ee.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 18 Feb 2019 13:19:59 +0100 Subject: [PATCH 125/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 dac0df6a9..48f4d8839 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 dd2c7383373a393116806133cd2624132dd009f7 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 4eb4b9fdcc6c1cc28976d3b3a95a24a0c2af8229 Mon Sep 17 00:00:00 2001 +Message-Id: <4eb4b9fdcc6c1cc28976d3b3a95a24a0c2af8229.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Feb 2019 16:49:29 +0100 Subject: [PATCH 126/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 5fc034309..bf7f6059b 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 edb63219fb471886494b258e2730059c17e69b66 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From eaf38ce6817d9bc5517e9dede4ab98547f530d04 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 2 Dec 2015 11:34:07 +0100 Subject: [PATCH 127/329] rtmutex: trylock is okay on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 17603989b..43ab74998 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 0660dd90791122ae769e74eb63234c8565f67f15 Mon Sep 17 00:00:00 2001 -Message-Id: <0660dd90791122ae769e74eb63234c8565f67f15.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 21e6449d0b679f7ab9210981b73cd02ee9a037d3 Mon Sep 17 00:00:00 2001 +Message-Id: <21e6449d0b679f7ab9210981b73cd02ee9a037d3.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 15 Sep 2016 10:51:27 +0200 Subject: [PATCH 128/329] fs/nfs: turn rmdir_sem into a semaphore -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 c1d36ca2d..15b1bf16e 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 2bb0c729998289856cf8881739cd03f2f0e29d59 Mon Sep 17 00:00:00 2001 -Message-Id: <2bb0c729998289856cf8881739cd03f2f0e29d59.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 3f1a27b090d37cf4986c1588c14aa22737213e9d Mon Sep 17 00:00:00 2001 +Message-Id: <3f1a27b090d37cf4986c1588c14aa22737213e9d.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 10 Jun 2011 11:04:15 +0200 Subject: [PATCH 129/329] rtmutex: Handle the various new futex race conditions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 19b8db0c5..dfb02ec4e 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 d8bfdedb7844d7fca24293ca066b4ae5be9e2dea Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 44218ed88f0073fad6c8de029a1b14ef6a704714 Mon Sep 17 00:00:00 2001 +Message-Id: <44218ed88f0073fad6c8de029a1b14ef6a704714.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Steven Rostedt Date: Tue, 14 Jul 2015 14:26:34 +0200 Subject: [PATCH 130/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 cf75080f3..736a3cb7e 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 35273d49274c01ab03833c5219ce7b30f9f36cc1 Mon Sep 17 00:00:00 2001 -Message-Id: <35273d49274c01ab03833c5219ce7b30f9f36cc1.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From f615fa327f051cb858d6ff6c56a9993fbd566219 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 1 Mar 2013 11:17:42 +0100 Subject: [PATCH 131/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 56ae6b028..2e465401a 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 6b3e471581877b22e9fbfb1e6472956c9efa7705 Mon Sep 17 00:00:00 2001 -Message-Id: <6b3e471581877b22e9fbfb1e6472956c9efa7705.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 38e6ad787f77a62534738eca0093d24df844f869 Mon Sep 17 00:00:00 2001 +Message-Id: <38e6ad787f77a62534738eca0093d24df844f869.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Grygorii Strashko Date: Tue, 21 Jul 2015 19:43:56 +0300 Subject: [PATCH 132/329] pid.h: include atomic.h -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 a8ad13c40..9b8cb6dc5 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 704fd0762604e2bd369a99398fb96da26c8f1d39 Mon Sep 17 00:00:00 2001 -Message-Id: <704fd0762604e2bd369a99398fb96da26c8f1d39.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 275b49dcdf8d653c81c2d1e0bd159aabb887d672 Mon Sep 17 00:00:00 2001 +Message-Id: <275b49dcdf8d653c81c2d1e0bd159aabb887d672.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 22 Dec 2016 17:28:33 +0100 Subject: [PATCH 133/329] arm: include definition for cpumask_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 c9e6e5168..81c4199c7 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 abbf607d629b2a88c82356f6426e4589f261c906 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 99cd2070e221ec9d05b1918031951ff9cdefa221 Mon Sep 17 00:00:00 2001 +Message-Id: <99cd2070e221ec9d05b1918031951ff9cdefa221.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: "Wolfgang M. Reimer" Date: Tue, 21 Jul 2015 16:20:07 +0200 Subject: [PATCH 134/329] locking: locktorture: Do NOT include rwlock.h directly -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 0c546ffa1..63c911849 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 d46394be0b0a7972dc97ae036ab7dde4d540d863 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 6df4846a6a073e53b0fbb0f66e595b9027c04915 Mon Sep 17 00:00:00 2001 +Message-Id: <6df4846a6a073e53b0fbb0f66e595b9027c04915.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 9 Jun 2011 11:43:52 +0200 Subject: [PATCH 135/329] rtmutex: Add rtmutex_lock_killable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 b167e8dfb..96e46154a 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 494edddcde6065246e4fc06c04664a75f6544b33 Mon Sep 17 00:00:00 2001 -Message-Id: <494edddcde6065246e4fc06c04664a75f6544b33.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c0d925808e62d8cdd687069c3d5e349ecc66803f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 1 Apr 2017 12:50:59 +0200 Subject: [PATCH 136/329] rtmutex: Make lock_killable work -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 8257f9572..7c101eeee 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 8e8547bae6810bd2b32db0735d7e3607139f8177 Mon Sep 17 00:00:00 2001 -Message-Id: <8e8547bae6810bd2b32db0735d7e3607139f8177.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 01bba13d3844991e6086214cb2c2481265dd50bb Mon Sep 17 00:00:00 2001 +Message-Id: <01bba13d3844991e6086214cb2c2481265dd50bb.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 19:34:01 +0200 Subject: [PATCH 137/329] spinlock: Split the lock types header -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 22626ca73..56ad55fe0 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 79a9f81a780a4e0a5e3afdbeeb3a1428b7dbc41d Mon Sep 17 00:00:00 2001 -Message-Id: <79a9f81a780a4e0a5e3afdbeeb3a1428b7dbc41d.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 6d84cc2aff3c518753ade35902f64968cf928527 Mon Sep 17 00:00:00 2001 +Message-Id: <6d84cc2aff3c518753ade35902f64968cf928527.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 20:06:39 +0200 Subject: [PATCH 138/329] rtmutex: Avoid include hell -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 a8c817d61..802118650 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 300de200cee155efc83b8fd10740ca001f3e3a51 Mon Sep 17 00:00:00 2001 -Message-Id: <300de200cee155efc83b8fd10740ca001f3e3a51.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b778a880184bc3cc5338bbaed65315dc3a1b5e6d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 16:56:02 +0100 Subject: [PATCH 139/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 e3267a95b..06a7cc0fc 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 9a3c535ec26f02d03862284b47fa4a9633bbe69f Mon Sep 17 00:00:00 2001 -Message-Id: <9a3c535ec26f02d03862284b47fa4a9633bbe69f.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ae7ac78b4107170bec606678c9da742bd26d53a2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 16:14:22 +0200 Subject: [PATCH 140/329] rtmutex: Provide rt_mutex_slowlock_locked() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 e1118f050..426c41ddb 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 98b7618e6929d4516b5db099edde7d36b16bf26a Mon Sep 17 00:00:00 2001 -Message-Id: <98b7618e6929d4516b5db099edde7d36b16bf26a.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 0146796c4aec3c2be0dfa1587a466e7c7a8ea21e Mon Sep 17 00:00:00 2001 +Message-Id: <0146796c4aec3c2be0dfa1587a466e7c7a8ea21e.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 16:36:39 +0200 Subject: [PATCH 141/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 2ce4ead37..e0ff1e46a 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 8110c4679cb552291c1ba1765416e889d07ef28e Mon Sep 17 00:00:00 2001 -Message-Id: <8110c4679cb552291c1ba1765416e889d07ef28e.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 1d24f62a58831696d65827e9e59fd3723edca08f Mon Sep 17 00:00:00 2001 +Message-Id: <1d24f62a58831696d65827e9e59fd3723edca08f.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:11:19 +0200 Subject: [PATCH 142/329] rtmutex: add sleeping lock implementation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Signed-off-by: Thomas Gleixner Signed-off-by: Sebastian Andrzej Siewior @@ -1147,7 +1147,7 @@ index 5955ad2aa2a8..6fcf0a3e180d 100644 #ifdef CONFIG_DEBUG_RT_MUTEXES # include "rtmutex-debug.h" diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 09a3bd47ac4d..9c20e213ef80 100644 +index 2197f965f9bb..c94224ddfb73 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -401,9 +401,15 @@ static bool set_nr_if_polling(struct task_struct *p) 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 eec4dc875..2fd5887df 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 a0019036eea95155544ba06be73424ff9e1e4379 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From f4009c56f911f54e3e60e7f2bd6e3c124213078a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:17:03 +0200 Subject: [PATCH 143/329] rtmutex: add mutex implementation based on rtmutex -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 5cd4cfd02..649dfd8f4 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 a4852655557dde4109b2378072bad869e2b267c3 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From acb23c1b1a68937154eb5467e2e6007fef19194f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:28:34 +0200 Subject: [PATCH 144/329] rtmutex: add rwsem implementation based on rtmutex -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 637457f8d..1741a203d 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 f3395089197a2ac80e93ab91acaa78ad3b4ab440 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From d3a7157a94f3deb3010258fba05c16227c43f98e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:18:06 +0200 Subject: [PATCH 145/329] rtmutex: add rwlock implementation based on rtmutex -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 8fa4a4856..4d85c7aaa 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 43c60224c5e3818f45e5d36849f3992786957014 Mon Sep 17 00:00:00 2001 -Message-Id: <43c60224c5e3818f45e5d36849f3992786957014.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 1bf646bbe988fa7df03bc28495b7c1d741936dc6 Mon Sep 17 00:00:00 2001 +Message-Id: <1bf646bbe988fa7df03bc28495b7c1d741936dc6.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 11 Jan 2019 21:16:31 +0100 Subject: [PATCH 146/329] rtmutex/rwlock: preserve state like a sleeping lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 a7da866cc..626098595 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 7e66698daafdf89d7871244f5b5c6895770539eb Mon Sep 17 00:00:00 2001 -Message-Id: <7e66698daafdf89d7871244f5b5c6895770539eb.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 4d135acef36b84effe3d80323633a89735197d83 Mon Sep 17 00:00:00 2001 +Message-Id: <4d135acef36b84effe3d80323633a89735197d83.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 12 Oct 2017 17:31:14 +0200 Subject: [PATCH 147/329] rtmutex: wire up RT's locking -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 b6a37b61f..aff409152 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 84f4873145a5ecb8580b6760d0c24234123d376c Mon Sep 17 00:00:00 2001 -Message-Id: <84f4873145a5ecb8580b6760d0c24234123d376c.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 23e3e9450b17f5fc8e296f1c867a7389f97262a6 Mon Sep 17 00:00:00 2001 +Message-Id: <23e3e9450b17f5fc8e296f1c867a7389f97262a6.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Oct 2017 17:34:38 +0200 Subject: [PATCH 148/329] rtmutex: add ww_mutex addon for mutex-rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 365003343..296362f4d 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 06b2e087f467f71387b985149f4846c57aca20c5 Mon Sep 17 00:00:00 2001 -Message-Id: <06b2e087f467f71387b985149f4846c57aca20c5.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 0b16103582e7b3af05eef69306659b23027db026 Mon Sep 17 00:00:00 2001 +Message-Id: <0b16103582e7b3af05eef69306659b23027db026.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 29 Jun 2011 14:58:57 +0200 Subject: [PATCH 149/329] kconfig: Add PREEMPT_RT_FULL -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 8748631a9..40a03156a 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 4b309e818592cad0ffe36093f4f030325bd8115d Mon Sep 17 00:00:00 2001 -Message-Id: <4b309e818592cad0ffe36093f4f030325bd8115d.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 064f3508fa2222f59ae1db5a54d62aed64c8774f Mon Sep 17 00:00:00 2001 +Message-Id: <064f3508fa2222f59ae1db5a54d62aed64c8774f.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Mikulas Patocka Date: Mon, 13 Nov 2017 12:56:53 -0500 Subject: [PATCH 150/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 aea573398..babc24ebb 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 4662441f1be8cbd75c192c3a9734efbb3e4361c6 Mon Sep 17 00:00:00 2001 -Message-Id: <4662441f1be8cbd75c192c3a9734efbb3e4361c6.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 9a632f48608316f87e79b4c50c8fec1a0923f59f Mon Sep 17 00:00:00 2001 +Message-Id: <9a632f48608316f87e79b4c50c8fec1a0923f59f.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 4 Jan 2019 15:33:21 -0500 Subject: [PATCH 151/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 0decaa0ed..392e12514 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 138a7f568e0b6c6dde7b5fdddc00650ad8579dac Mon Sep 17 00:00:00 2001 -Message-Id: <138a7f568e0b6c6dde7b5fdddc00650ad8579dac.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 5b9a5316691f167599f18843a8e146af2e795f21 Mon Sep 17 00:00:00 2001 +Message-Id: <5b9a5316691f167599f18843a8e146af2e795f21.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 16 Nov 2017 16:48:48 +0100 Subject: [PATCH 152/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 322b0274a..8f4e30cfe 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 1c70b9f99adf1d6cb45b18b13c25d5afa92bcd90 Mon Sep 17 00:00:00 2001 -Message-Id: <1c70b9f99adf1d6cb45b18b13c25d5afa92bcd90.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b951831b474dba307b7a0e2a8df3f9636526348c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Aug 2013 18:21:04 +0200 Subject: [PATCH 153/329] ptrace: fix ptrace vs tasklist_lock race -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz As explained by Alexander Fyodorov : @@ -123,7 +123,7 @@ index b93eb4eaf7ac..a38b304fb9fd 100644 } spin_unlock_irq(&task->sighand->siglock); diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 9c20e213ef80..1fc8a3fcc34d 100644 +index c94224ddfb73..3128a5b95fd7 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -1349,6 +1349,18 @@ int migrate_swap(struct task_struct *cur, struct task_struct *p, 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 a3afd8e12..92c1927d3 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 d291ff6355cdb7f5887d00de427964e00c97201c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 076f3d83dbde0ce989d16b9fe260dd19abad7b1c Mon Sep 17 00:00:00 2001 +Message-Id: <076f3d83dbde0ce989d16b9fe260dd19abad7b1c.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 21 Sep 2017 14:25:13 +0200 Subject: [PATCH 154/329] rtmutex: annotate sleeping lock context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 @@ -253,10 +253,10 @@ index 5f6de49dc78e..35f3552b7463 100644 !t->rcu_read_unlock_special.b.blocked) { diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 1fc8a3fcc34d..e3f838371f94 100644 +index 3128a5b95fd7..d10698fa8cad 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -7347,4 +7347,49 @@ void migrate_enable(void) +@@ -7349,4 +7349,49 @@ void migrate_enable(void) preempt_enable(); } EXPORT_SYMBOL(migrate_enable); 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 4cf4e00e4..84174336d 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 9f19a10ac9dade26a00dc5f2858f6fcb7a8235c9 Mon Sep 17 00:00:00 2001 -Message-Id: <9f19a10ac9dade26a00dc5f2858f6fcb7a8235c9.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 810aea0ca134ee70c3386044bfa564eec19cd6bf Mon Sep 17 00:00:00 2001 +Message-Id: <810aea0ca134ee70c3386044bfa564eec19cd6bf.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 5 Jul 2018 14:44:51 +0200 Subject: [PATCH 155/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 @@ -97,7 +97,7 @@ index 50197f5c4506..4a4f03a8d8d4 100644 # endif #endif diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index e3f838371f94..20842da53a59 100644 +index d10698fa8cad..453e1a45dcbf 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -1031,7 +1031,7 @@ void set_cpus_allowed_common(struct task_struct *p, const struct cpumask *new_ma @@ -127,7 +127,7 @@ index e3f838371f94..20842da53a59 100644 if (__migrate_disabled(p)) { p->migrate_disable_update = 1; goto out; -@@ -7203,7 +7203,7 @@ const u32 sched_prio_to_wmult[40] = { +@@ -7205,7 +7205,7 @@ const u32 sched_prio_to_wmult[40] = { #undef CREATE_TRACE_POINTS @@ -136,7 +136,7 @@ index e3f838371f94..20842da53a59 100644 static inline void update_nr_migratory(struct task_struct *p, long delta) -@@ -7351,45 +7351,44 @@ EXPORT_SYMBOL(migrate_enable); +@@ -7353,45 +7353,44 @@ EXPORT_SYMBOL(migrate_enable); #elif !defined(CONFIG_SMP) && defined(CONFIG_PREEMPT_RT_BASE) void migrate_disable(void) { 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 f59f5c8bf..7d2913998 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 343e6dd66acb934255ba07ddff604b558d40751e Mon Sep 17 00:00:00 2001 -Message-Id: <343e6dd66acb934255ba07ddff604b558d40751e.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 3614213f60d3663b42b126bddd58028115a446ca Mon Sep 17 00:00:00 2001 +Message-Id: <3614213f60d3663b42b126bddd58028115a446ca.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 4 Aug 2017 17:40:42 +0200 Subject: [PATCH 156/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 0a0464d05..912eeee48 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 b7ea9b25eaaaacf87c1cebb2d36883c86df30481 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 7bd62defa46ace7255f7b62bc28863c1bb1d44e1 Mon Sep 17 00:00:00 2001 +Message-Id: <7bd62defa46ace7255f7b62bc28863c1bb1d44e1.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Peter Zijlstra Date: Sat, 13 Aug 2011 00:23:17 +0200 Subject: [PATCH 157/329] rcu: Frob softirq test -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 558db08a5..2bb48a58c 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 66676f91d51378b4c7544d4e54f3ba5c26e120e8 Mon Sep 17 00:00:00 2001 -Message-Id: <66676f91d51378b4c7544d4e54f3ba5c26e120e8.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 9118ae152c3ef6428fce024051c2eed3b0e1b1ce Mon Sep 17 00:00:00 2001 +Message-Id: <9118ae152c3ef6428fce024051c2eed3b0e1b1ce.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 5 Oct 2011 11:59:38 -0700 Subject: [PATCH 158/329] rcu: Merge RCU-bh into RCU-preempt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 15e284543..bf9de54f7 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 4bb3f9983975f5f2ca73d8e9fd18e9ba57ad2796 Mon Sep 17 00:00:00 2001 -Message-Id: <4bb3f9983975f5f2ca73d8e9fd18e9ba57ad2796.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 3f287b9dab00c201ffe7712b2070c8d3532b51de Mon Sep 17 00:00:00 2001 +Message-Id: <3f287b9dab00c201ffe7712b2070c8d3532b51de.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Wed, 5 Oct 2011 11:45:18 -0700 Subject: [PATCH 159/329] rcu: Make ksoftirqd do RCU quiescent states -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 ce6551fbc..865a71289 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 f465587e9d7d48453b9aa5d1ade43668a249ebd5 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ecca310500e8f26b98c45931b09a60141db87b87 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: "Paul E. McKenney" Date: Mon, 4 Nov 2013 13:21:10 -0800 Subject: [PATCH 160/329] rcu: Eliminate softirq processing from rcutree -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 94ba5eae5..79e569d27 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 433eb289b0a03c71187d7162e27e401d25e018dc Mon Sep 17 00:00:00 2001 -Message-Id: <433eb289b0a03c71187d7162e27e401d25e018dc.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 2c38ac8778a152f8f7bb227416c86efe5898ecbc Mon Sep 17 00:00:00 2001 +Message-Id: <2c38ac8778a152f8f7bb227416c86efe5898ecbc.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Sep 2017 14:43:41 +0200 Subject: [PATCH 161/329] srcu: use cpu_online() instead custom check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 0b61e3e21..8a025e885 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 c927dddeac30d11dedfdfa416dd4a8051fa286b0 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 3431f65041d5f4a33169c2acf14ba2157d546f7b Mon Sep 17 00:00:00 2001 +Message-Id: <3431f65041d5f4a33169c2acf14ba2157d546f7b.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Oct 2017 18:37:12 +0200 Subject: [PATCH 162/329] srcu: replace local_irqsave() with a locallock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 c29daf934..d671c2b51 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 085e670eecb4db25794213a9542406e046922a31 Mon Sep 17 00:00:00 2001 -Message-Id: <085e670eecb4db25794213a9542406e046922a31.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 65160311d558fbe5d0aaae8a03ecbf56a42ff10c Mon Sep 17 00:00:00 2001 +Message-Id: <65160311d558fbe5d0aaae8a03ecbf56a42ff10c.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Julia Cartwright Date: Wed, 12 Oct 2016 11:21:14 -0500 Subject: [PATCH 163/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 1eac28db8..fbc93cbb0 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 79dd3527650081cf9b3cc4d470db9c8a4fcb0d7b Mon Sep 17 00:00:00 2001 -Message-Id: <79dd3527650081cf9b3cc4d470db9c8a4fcb0d7b.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 837f9ac5cf843158a80eed6d60166ee7c9716c1a Mon Sep 17 00:00:00 2001 +Message-Id: <837f9ac5cf843158a80eed6d60166ee7c9716c1a.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 28 Jul 2011 13:32:57 +0200 Subject: [PATCH 164/329] tty/serial/omap: Make the locking RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 77fe65c0e..3b9c4a09f 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 babf19bf397f7038e36dc8cb488e1ee5b6c4831e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 36ca3c9c25fab5bab99fc8d570a19957883cf187 Mon Sep 17 00:00:00 2001 +Message-Id: <36ca3c9c25fab5bab99fc8d570a19957883cf187.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 8 Jan 2013 21:36:51 +0100 Subject: [PATCH 165/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 068b4b996..69df58018 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 51000d5e4bc5e53af304187eeda891f18bd39bd5 Mon Sep 17 00:00:00 2001 -Message-Id: <51000d5e4bc5e53af304187eeda891f18bd39bd5.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 5efe8f58b68a6c29e56e1f8d2ee649f9fd51556c Mon Sep 17 00:00:00 2001 +Message-Id: <5efe8f58b68a6c29e56e1f8d2ee649f9fd51556c.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Kurt Kanzenbach Date: Mon, 24 Sep 2018 10:29:01 +0200 Subject: [PATCH 166/329] tty: serial: pl011: explicitly initialize the flags @@ -9,7 +9,7 @@ Subject: [PATCH 166/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 d0a9f43bf..8df01ace6 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 41302d99ac548fedf44695f87b6b1ce57dacdd80 Mon Sep 17 00:00:00 2001 -Message-Id: <41302d99ac548fedf44695f87b6b1ce57dacdd80.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From d3da9ac80ca53a41300046b8235d29328fbc0679 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Ingo Molnar Date: Wed, 14 Dec 2011 13:05:54 +0100 Subject: [PATCH 167/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Beyond the warning: @@ -24,7 +24,7 @@ Signed-off-by: Thomas Gleixner 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/drivers/tty/serial/8250/8250_core.c b/drivers/tty/serial/8250/8250_core.c -index b9567ef843fc..155ee2a54e25 100644 +index e1a5887b6d91..129c9383f96c 100644 --- a/drivers/tty/serial/8250/8250_core.c +++ b/drivers/tty/serial/8250/8250_core.c @@ -54,7 +54,16 @@ static struct uart_driver serial8250_reg; 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 7aafa5226..74d59cc90 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 f8c85fb82569dd9308b23d290202f33397e0cc14 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From a68d879da540e988c941ac8378c651d3c016d365 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Apr 2016 16:55:02 +0200 Subject: [PATCH 168/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 db1017132..15e99ef8b 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 76ccd8ea14e8bdcfe51bcd1e20122f86109be038 Mon Sep 17 00:00:00 2001 -Message-Id: <76ccd8ea14e8bdcfe51bcd1e20122f86109be038.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 3b4b838f82c5d2d97cb8b4b8f076171728bfdf16 Mon Sep 17 00:00:00 2001 +Message-Id: <3b4b838f82c5d2d97cb8b4b8f076171728bfdf16.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Peter Zijlstra Date: Wed, 23 Nov 2016 16:29:32 +0100 Subject: [PATCH 169/329] locking/percpu-rwsem: Remove preempt_disable variants -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 9ff28eca5..fbc8540ca 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 bb72cd110fa9e55b0ed7606b0e034779f9896a62 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 7cc501339a265ddc15181e7a2ef2a02fe41dcda2 Mon Sep 17 00:00:00 2001 +Message-Id: <7cc501339a265ddc15181e7a2ef2a02fe41dcda2.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Yong Zhang Date: Tue, 15 May 2012 13:53:56 +0800 Subject: [PATCH 170/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz User preempt_*_rt instead of local_irq_*_rt or otherwise there will be warning on ARM like below: diff --git a/debian/patches-rt/0171-fs-dcache-bring-back-explicit-INIT_HLIST_BL_HEAD-ini.patch b/debian/patches-rt/0171-fs-dcache-bring-back-explicit-INIT_HLIST_BL_HEAD-ini.patch index cf15f2e4b..0f54ef72d 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 6fd83f37a592b5eda452cf36f468429a232c8a32 Mon Sep 17 00:00:00 2001 -Message-Id: <6fd83f37a592b5eda452cf36f468429a232c8a32.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 4ce6c433bcbb3858fcb29399ff85bdec545ee086 Mon Sep 17 00:00:00 2001 +Message-Id: <4ce6c433bcbb3858fcb29399ff85bdec545ee086.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Sep 2017 12:32:34 +0200 Subject: [PATCH 171/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 62af2a6ca..747951b49 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 335e9df9c9c22975b4405ed6477dd63fd399fe04 Mon Sep 17 00:00:00 2001 -Message-Id: <335e9df9c9c22975b4405ed6477dd63fd399fe04.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 8a569194eac8203dcaf7b82b233db67ecd27ee3d Mon Sep 17 00:00:00 2001 +Message-Id: <8a569194eac8203dcaf7b82b233db67ecd27ee3d.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 20 Oct 2017 11:29:53 +0200 Subject: [PATCH 172/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz i_dir_seq is an opencoded seqcounter. Based on the code it looks like we could have two writers in parallel despite the fact that the d_lock is diff --git a/debian/patches-rt/0173-squashfs-make-use-of-local-lock-in-multi_cpu-decompr.patch b/debian/patches-rt/0173-squashfs-make-use-of-local-lock-in-multi_cpu-decompr.patch index 7d2b74644..fb416f002 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 7eeaa5c0f5e63f15e6236775aaef5f8d535e5be3 Mon Sep 17 00:00:00 2001 -Message-Id: <7eeaa5c0f5e63f15e6236775aaef5f8d535e5be3.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 52ac8bec759bebef11e9f40442b77963632790e7 Mon Sep 17 00:00:00 2001 +Message-Id: <52ac8bec759bebef11e9f40442b77963632790e7.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Julia Cartwright Date: Mon, 7 May 2018 08:58:57 -0500 Subject: [PATCH 173/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 e4c874171..602c0aa1a 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 2fd2eba107e61d67901cd29d4bc3f0d21bb3dce9 Mon Sep 17 00:00:00 2001 -Message-Id: <2fd2eba107e61d67901cd29d4bc3f0d21bb3dce9.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 8af460950014ad92c770eb80d2ecb12033a60462 Mon Sep 17 00:00:00 2001 +Message-Id: <8af460950014ad92c770eb80d2ecb12033a60462.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Daniel Wagner Date: Tue, 17 Feb 2015 09:37:44 +0100 Subject: [PATCH 174/329] thermal: Defer thermal wakups to threads -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 e32285323..744fb3120 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 63f7c8cd3071ae8436b4e39ef5726408e93d41d6 Mon Sep 17 00:00:00 2001 -Message-Id: <63f7c8cd3071ae8436b4e39ef5726408e93d41d6.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 464c8fff871a40fb5eee0b896bc42d7d82249e1d Mon Sep 17 00:00:00 2001 +Message-Id: <464c8fff871a40fb5eee0b896bc42d7d82249e1d.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 11 Dec 2018 15:10:33 +0100 Subject: [PATCH 175/329] x86/fpu: Disable preemption around local_bh_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 35305f52d..7ecf159a2 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 6317fef46866121b7eab68a622598ca77470d59f Mon Sep 17 00:00:00 2001 -Message-Id: <6317fef46866121b7eab68a622598ca77470d59f.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 788d683b8d541f598c2897f18a334fb760a490a3 Mon Sep 17 00:00:00 2001 +Message-Id: <788d683b8d541f598c2897f18a334fb760a490a3.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 8 Jul 2011 16:35:35 +0200 Subject: [PATCH 176/329] fs/epoll: Do not disable preemption on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 0e1503645..acf713029 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 44ae1705bf3af875ebd758f32b6f19ccdef487e4 Mon Sep 17 00:00:00 2001 -Message-Id: <44ae1705bf3af875ebd758f32b6f19ccdef487e4.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b78529ca6a695c4b328e2cb24eb16b3d8dfe0b27 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 12 Jul 2011 11:39:36 +0200 Subject: [PATCH 177/329] mm/vmalloc: Another preempt disable region which sucks -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 eec405ba2..b9dd26142 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 eed61e74c9c138e4fe1b7c02ee7bb6c8008854ad Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 5e14cf2663847cee57f9a268fd3bebd21c472c9c Mon Sep 17 00:00:00 2001 +Message-Id: <5e14cf2663847cee57f9a268fd3bebd21c472c9c.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 9 Apr 2014 10:37:23 +0200 Subject: [PATCH 178/329] block: mq: use cpu_light() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 60adf0a8a..b964d614d 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 7dd73c22c07933b49db85d4fd3ccb9d06bc7b3b0 Mon Sep 17 00:00:00 2001 -Message-Id: <7dd73c22c07933b49db85d4fd3ccb9d06bc7b3b0.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 677ff20989e2beb0c44e527e4afdc6546184b114 Mon Sep 17 00:00:00 2001 +Message-Id: <677ff20989e2beb0c44e527e4afdc6546184b114.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 14 Jul 2015 14:26:34 +0200 Subject: [PATCH 179/329] block/mq: do not invoke preempt_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 2e4898af9..25b5f7f3b 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 d2a94af9dad45378ad5e7103644fd879afb93599 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 721e60329048d1c2fda3de758e76658ea5d5dc37 Mon Sep 17 00:00:00 2001 +Message-Id: <721e60329048d1c2fda3de758e76658ea5d5dc37.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 29 Jan 2015 15:10:08 +0100 Subject: [PATCH 180/329] block/mq: don't complete requests via IPI -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 e5e3db9e3..16e4a1f67 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 2b7bb0e5b7caeb66dc770e424e5b57da568c3737 Mon Sep 17 00:00:00 2001 -Message-Id: <2b7bb0e5b7caeb66dc770e424e5b57da568c3737.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b2aeaa1a249302dd3bc1766644f1f74ec75bbcfa Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 6 Apr 2010 16:51:31 +0200 Subject: [PATCH 181/329] md: raid5: Make raid5_percpu handling RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 d5de17162..303bcf307 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 aa951c4b35370e250c8fd654b973285076a18d62 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 79310ccfbc479a33513e1d64bbc830a5232a2a55 Mon Sep 17 00:00:00 2001 +Message-Id: <79310ccfbc479a33513e1d64bbc830a5232a2a55.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 20:51:03 +0100 Subject: [PATCH 182/329] rt: Introduce cpu_chill() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 eca1b26d1..6e8a521bd 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 39b74757b00dbf719b56fa969a4f09f37c6dee83 Mon Sep 17 00:00:00 2001 -Message-Id: <39b74757b00dbf719b56fa969a4f09f37c6dee83.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 709122e50c844dce09298e7854c1481f09354625 Mon Sep 17 00:00:00 2001 +Message-Id: <709122e50c844dce09298e7854c1481f09354625.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Feb 2019 16:59:15 +0100 Subject: [PATCH 183/329] hrtimer: Don't lose state in cpu_chill() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 8b89eb9c4..34e8b393a 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 e41d0c353762bfc29c92a680d650263a70df9af3 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 8dc2cf0ef8a9324af222b8dbe2a3ca02a50963a8 Mon Sep 17 00:00:00 2001 +Message-Id: <8dc2cf0ef8a9324af222b8dbe2a3ca02a50963a8.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 12:31:10 +0100 Subject: [PATCH 184/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 c5f5c0285..bcf172b44 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 b7202b3b5aaf5b71c64a48c27f30abbe91a7074e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 0b6eefa7f5c4c981e7c755ef69e6f365954e4092 Mon Sep 17 00:00:00 2001 +Message-Id: <0b6eefa7f5c4c981e7c755ef69e6f365954e4092.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Mar 2018 13:49:16 +0100 Subject: [PATCH 185/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 5b1a94627..e330f0f32 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 d27e692a2248426b3026df987eb302cd03ef3c7e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 18910a5357a094c2633239a2f877b65d5ab09c88 Mon Sep 17 00:00:00 2001 +Message-Id: <18910a5357a094c2633239a2f877b65d5ab09c88.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 20 Dec 2012 18:28:26 +0100 Subject: [PATCH 186/329] block: Use cpu_chill() for retry loops -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 9553f51be..b719aae99 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 e326a5665a08f08494ed0e379ad1d2acaa01a98e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c082103a839ea32123df10e13e1e40a70034d4d8 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 21:00:34 +0100 Subject: [PATCH 187/329] fs: dcache: Use cpu_chill() in trylock loops -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 0ed5d9895..81ae4f79a 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 6f1f94b1535092a8e77b019ca372fe612e46284a Mon Sep 17 00:00:00 2001 -Message-Id: <6f1f94b1535092a8e77b019ca372fe612e46284a.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ea7fc68722cbdf96fc7ff457f7da14a3a1a8d15d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 7 Mar 2012 21:10:04 +0100 Subject: [PATCH 188/329] net: Use cpu_chill() instead of cpu_relax() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 f5ce9e124..aa8bb4101 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 63bf7c61a6cfcad6e5c1ddeb1159d816922cf00f Mon Sep 17 00:00:00 2001 -Message-Id: <63bf7c61a6cfcad6e5c1ddeb1159d816922cf00f.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 9b95ce168a72f1f027fa44e3c906746c97713422 Mon Sep 17 00:00:00 2001 +Message-Id: <9b95ce168a72f1f027fa44e3c906746c97713422.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Sep 2016 14:35:49 +0200 Subject: [PATCH 189/329] fs/dcache: use swait_queue instead of waitqueue -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 d7e0115aa..f0b92e1e3 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 64a91064b24a6f930c3d94ca1eb20013ac5b7b01 Mon Sep 17 00:00:00 2001 -Message-Id: <64a91064b24a6f930c3d94ca1eb20013ac5b7b01.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b81673e7d867b1cea414f6eac4999b4800a35954 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 24 Jul 2013 15:26:54 +0200 Subject: [PATCH 190/329] workqueue: Use normal rcu -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 7141b3029..5de3010e1 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 15ef64c24647a083189bfcd22970da29aa874403 Mon Sep 17 00:00:00 2001 -Message-Id: <15ef64c24647a083189bfcd22970da29aa874403.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From a37af2de095fe55ea6ed55df2a3887795f35f46e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:42:26 +0200 Subject: [PATCH 191/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 257507745..02645571b 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 970283b4b3180ec25600afde5aac8ff16e1b8ee7 Mon Sep 17 00:00:00 2001 -Message-Id: <970283b4b3180ec25600afde5aac8ff16e1b8ee7.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c8558170db4f3c1bba19fcfe00524e64c5591697 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Mon, 1 Jul 2013 11:02:42 +0200 Subject: [PATCH 192/329] workqueue: Prevent workqueue versus ata-piix livelock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 2ead9fc23..49d883f70 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 02ccdd4922231b1b1a76a561568592b01e107498 Mon Sep 17 00:00:00 2001 -Message-Id: <02ccdd4922231b1b1a76a561568592b01e107498.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 97664a8a1bc64c04079d93ee8aaa75191067f57a Mon Sep 17 00:00:00 2001 +Message-Id: <97664a8a1bc64c04079d93ee8aaa75191067f57a.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 22 Jun 2011 19:47:03 +0200 Subject: [PATCH 193/329] sched: Distangle worker accounting from rqlock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 @@ -37,7 +37,7 @@ Signed-off-by: Sebastian Andrzej Siewior 3 files changed, 47 insertions(+), 100 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 20842da53a59..1abd32af7918 100644 +index 453e1a45dcbf..f13cc0073bbc 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -1704,10 +1704,6 @@ static inline void ttwu_activate(struct rq *rq, struct task_struct *p, int en_fl @@ -108,7 +108,7 @@ index 20842da53a59..1abd32af7918 100644 /** * wake_up_process - Wake up a specific process * @p: The process to be woken up. -@@ -3561,21 +3507,6 @@ static void __sched notrace __schedule(bool preempt) +@@ -3563,21 +3509,6 @@ static void __sched notrace __schedule(bool preempt) atomic_inc(&rq->nr_iowait); delayacct_blkio_start(); } @@ -130,7 +130,7 @@ index 20842da53a59..1abd32af7918 100644 } switch_count = &prev->nvcsw; } -@@ -3635,6 +3566,20 @@ static inline void sched_submit_work(struct task_struct *tsk) +@@ -3637,6 +3568,20 @@ static inline void sched_submit_work(struct task_struct *tsk) { if (!tsk->state || tsk_is_pi_blocked(tsk)) return; @@ -151,7 +151,7 @@ index 20842da53a59..1abd32af7918 100644 /* * If we are going to sleep and we have plugged IO queued, * make sure to submit it to avoid deadlocks. -@@ -3643,6 +3588,12 @@ static inline void sched_submit_work(struct task_struct *tsk) +@@ -3645,6 +3590,12 @@ static inline void sched_submit_work(struct task_struct *tsk) blk_schedule_flush_plug(tsk); } @@ -164,7 +164,7 @@ index 20842da53a59..1abd32af7918 100644 asmlinkage __visible void __sched schedule(void) { struct task_struct *tsk = current; -@@ -3653,6 +3604,7 @@ asmlinkage __visible void __sched schedule(void) +@@ -3655,6 +3606,7 @@ asmlinkage __visible void __sched schedule(void) __schedule(false); sched_preempt_enable_no_resched(); } while (need_resched()); diff --git a/debian/patches-rt/0194-debugobjects-Make-RT-aware.patch b/debian/patches-rt/0194-debugobjects-Make-RT-aware.patch index b682612fd..6196c1ce1 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 e2fc6d404d64720a63039f4e1b7bfe25e1c6e7a1 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From e7072860b9c7a16ca8c94ee50df14e16360fbda0 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 17 Jul 2011 21:41:35 +0200 Subject: [PATCH 194/329] debugobjects: Make RT aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 a7679635b..f53719122 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 8cc7c1e95ea40b40a3103e616773ba1ed1fe6d0b Mon Sep 17 00:00:00 2001 -Message-Id: <8cc7c1e95ea40b40a3103e616773ba1ed1fe6d0b.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From f3e78f2a54c0638b47530adea622dd556b3a5f99 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 22 Feb 2012 12:03:30 +0100 Subject: [PATCH 195/329] seqlock: Prevent rt starvation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 200616903..79078e979 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 03378d7b8239e5f03dcd6c1cd14d6d96d104da43 Mon Sep 17 00:00:00 2001 -Message-Id: <03378d7b8239e5f03dcd6c1cd14d6d96d104da43.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 60ebd21c82b8a2b837e17e68e1efb49f47b2eac8 Mon Sep 17 00:00:00 2001 +Message-Id: <60ebd21c82b8a2b837e17e68e1efb49f47b2eac8.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 18 Feb 2015 16:05:28 +0100 Subject: [PATCH 196/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 aae3e6f08..be0ab1ca2 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 34aa1240e0fefa206ce5a66d24bb25db3ec59e91 Mon Sep 17 00:00:00 2001 -Message-Id: <34aa1240e0fefa206ce5a66d24bb25db3ec59e91.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 7fe369968dc32769c83f1b4ac3951b64dd72f608 Mon Sep 17 00:00:00 2001 +Message-Id: <7fe369968dc32769c83f1b4ac3951b64dd72f608.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 12 Jul 2011 15:38:34 +0200 Subject: [PATCH 197/329] net: Use skbufhead with raw lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 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 5bb9a9037..130ab6e38 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 4b967e907820a2c6af47ee605519c24058ee7cb0 Mon Sep 17 00:00:00 2001 -Message-Id: <4b967e907820a2c6af47ee605519c24058ee7cb0.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c0bfbcad9424479746dc43df9e6ebc33a184a039 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 13 Jan 2016 15:55:02 +0100 Subject: [PATCH 198/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 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 d19f49bc9..9aeb54554 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 0bbd884e945ff83b97fe56eb4f263f5b13e4c18c Mon Sep 17 00:00:00 2001 -Message-Id: <0bbd884e945ff83b97fe56eb4f263f5b13e4c18c.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 302b4d04008563db6601953efc2267fb2b5f2d63 Mon Sep 17 00:00:00 2001 +Message-Id: <302b4d04008563db6601953efc2267fb2b5f2d63.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 20 Jan 2016 15:39:05 +0100 Subject: [PATCH 199/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 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 30d1332a8..e784b233c 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 e5db5e7b0b1b099d4e824f40be24d27887cf8660 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From bf1b7f42bc9f739693ff39eb8fc4cc2acb239c0b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 30 Mar 2016 13:36:29 +0200 Subject: [PATCH 200/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 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 3f4a0e37a..3b6bced7f 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 2d33d1be07519caccf9a62439568d2ab8cf9223f Mon Sep 17 00:00:00 2001 -Message-Id: <2d33d1be07519caccf9a62439568d2ab8cf9223f.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 307d91a60bbff9f248431ca7631279e7c8b10780 Mon Sep 17 00:00:00 2001 +Message-Id: <307d91a60bbff9f248431ca7631279e7c8b10780.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Sep 2016 17:36:35 +0200 Subject: [PATCH 201/329] net/Qdisc: use a seqlock instead seqcount -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 617f5753d..4ab70384f 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 8458acc14dc949f69fe7ff87873ce4766546ae35 Mon Sep 17 00:00:00 2001 -Message-Id: <8458acc14dc949f69fe7ff87873ce4766546ae35.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 75ab59215ef16d8816003c3ae3f11c25bcee980f Mon Sep 17 00:00:00 2001 +Message-Id: <75ab59215ef16d8816003c3ae3f11c25bcee980f.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 31 Aug 2016 17:21:56 +0200 Subject: [PATCH 202/329] net: add back the missing serialization in @@ -9,7 +9,7 @@ Subject: [PATCH 202/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 @@ -46,7 +46,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 6 insertions(+) diff --git a/net/ipv4/tcp_ipv4.c b/net/ipv4/tcp_ipv4.c -index 6da393016c11..105e94ff1095 100644 +index 7536f4c0bbf4..a33756f9b73e 100644 --- a/net/ipv4/tcp_ipv4.c +++ b/net/ipv4/tcp_ipv4.c @@ -62,6 +62,7 @@ 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 6a2987993..7ecd41d6c 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 124c292b3e4280412282c44269af2f36acf7d4b1 Mon Sep 17 00:00:00 2001 -Message-Id: <124c292b3e4280412282c44269af2f36acf7d4b1.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 4187c597c0695b2c1b8d8d8d41c36fd92a5ae958 Mon Sep 17 00:00:00 2001 +Message-Id: <4187c597c0695b2c1b8d8d8d41c36fd92a5ae958.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 31 Aug 2016 17:54:09 +0200 Subject: [PATCH 203/329] net: add a lock around icmp_sk() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 bbefbc650..fb1f0f714 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 f7dcbdf784d3f4e7d270e9206fd593e94474333f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From aa23415173800a6c4d7352d5c14fd59562015bd6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Steven Rostedt Date: Tue, 6 Dec 2016 17:50:30 -0500 Subject: [PATCH 204/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz A customer hit a crash where the napi sd->poll_list became corrupted. The customer had the bnx2x driver, which does a 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 e1ab571cd..ad8ee3605 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 3aed2fcc4d4450f9800232001c493c228ca96317 Mon Sep 17 00:00:00 2001 -Message-Id: <3aed2fcc4d4450f9800232001c493c228ca96317.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c599564b3ab6da0f861bcbae9b50ea2eb810ff0f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 23 Jun 2015 15:32:51 +0200 Subject: [PATCH 205/329] irqwork: push most work into softirq context -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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. @@ -250,10 +250,10 @@ index 2b0ddd50e879..4d31ec98e968 100644 /* diff --git a/kernel/time/timer.c b/kernel/time/timer.c -index 3fab1c50bf1b..2fcd56aa6092 100644 +index 845f687d2d1c..a4279d24b438 100644 --- a/kernel/time/timer.c +++ b/kernel/time/timer.c -@@ -1735,6 +1735,8 @@ static __latent_entropy void run_timer_softirq(struct softirq_action *h) +@@ -1746,6 +1746,8 @@ static __latent_entropy void run_timer_softirq(struct softirq_action *h) { struct timer_base *base = this_cpu_ptr(&timer_bases[BASE_STD]); diff --git a/debian/patches-rt/0206-printk-Make-rt-aware.patch b/debian/patches-rt/0206-printk-Make-rt-aware.patch index b0b388b57..ae432fc1f 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 ab44380ba163c844ae524ec2a604b54e2b4b074c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c294bdb762f1c945845389df3e0f803a9a3f2c52 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 19 Sep 2012 14:50:37 +0200 Subject: [PATCH 206/329] printk: Make rt aware -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Drop the lock before calling the console driver and do not disable interrupts while printing to a serial console. @@ -16,10 +16,10 @@ Signed-off-by: Thomas Gleixner 1 file changed, 30 insertions(+), 3 deletions(-) diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c -index f934baed564d..c927f89961a8 100644 +index e582817249ce..1eb212298f95 100644 --- a/kernel/printk/printk.c +++ b/kernel/printk/printk.c -@@ -1624,6 +1624,7 @@ SYSCALL_DEFINE3(syslog, int, type, char __user *, buf, int, len) +@@ -1652,6 +1652,7 @@ SYSCALL_DEFINE3(syslog, int, type, char __user *, buf, int, len) return do_syslog(type, buf, len, SYSLOG_FROM_READER); } @@ -27,7 +27,7 @@ index f934baed564d..c927f89961a8 100644 /* * Special console_lock variants that help to reduce the risk of soft-lockups. * They allow to pass console_lock to another printk() call using a busy wait. -@@ -1764,6 +1765,15 @@ static int console_trylock_spinning(void) +@@ -1792,6 +1793,15 @@ static int console_trylock_spinning(void) return 1; } @@ -43,7 +43,7 @@ index f934baed564d..c927f89961a8 100644 /* * Call the console drivers, asking them to write out * log_buf[start] to log_buf[end - 1]. -@@ -1779,6 +1789,7 @@ static void call_console_drivers(const char *ext_text, size_t ext_len, +@@ -1807,6 +1817,7 @@ static void call_console_drivers(const char *ext_text, size_t ext_len, if (!console_drivers) return; @@ -51,7 +51,7 @@ index f934baed564d..c927f89961a8 100644 for_each_console(con) { if (exclusive_console && con != exclusive_console) continue; -@@ -1794,6 +1805,7 @@ static void call_console_drivers(const char *ext_text, size_t ext_len, +@@ -1822,6 +1833,7 @@ static void call_console_drivers(const char *ext_text, size_t ext_len, else con->write(con, text, len); } @@ -59,7 +59,7 @@ index f934baed564d..c927f89961a8 100644 } int printk_delay_msec __read_mostly; -@@ -1988,20 +2000,30 @@ asmlinkage int vprintk_emit(int facility, int level, +@@ -2016,20 +2028,30 @@ asmlinkage int vprintk_emit(int facility, int level, /* If called from the scheduler, we can not call up(). */ if (!in_sched && pending_output) { @@ -93,7 +93,7 @@ index f934baed564d..c927f89961a8 100644 } if (pending_output) -@@ -2463,6 +2485,10 @@ void console_unlock(void) +@@ -2491,6 +2513,10 @@ void console_unlock(void) console_seq++; raw_spin_unlock(&logbuf_lock); @@ -104,7 +104,7 @@ index f934baed564d..c927f89961a8 100644 /* * While actively printing out messages, if another printk() * were to occur on another CPU, it may wait for this one to -@@ -2481,6 +2507,7 @@ void console_unlock(void) +@@ -2509,6 +2535,7 @@ void console_unlock(void) } printk_safe_exit_irqrestore(flags); 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 099115e9a..003db606f 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 aed7d2859938ca00a4ea530983068d30e89efd95 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 0b98bff7eda15d4a236d8587b6baab352fd5facd Mon Sep 17 00:00:00 2001 +Message-Id: <0b98bff7eda15d4a236d8587b6baab352fd5facd.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 19 May 2016 17:45:27 +0200 Subject: [PATCH 207/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 @@ -19,10 +19,10 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 10 insertions(+) diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c -index c927f89961a8..49ea374ba8ea 100644 +index 1eb212298f95..c5fbc51e61ed 100644 --- a/kernel/printk/printk.c +++ b/kernel/printk/printk.c -@@ -1789,6 +1789,11 @@ static void call_console_drivers(const char *ext_text, size_t ext_len, +@@ -1817,6 +1817,11 @@ static void call_console_drivers(const char *ext_text, size_t ext_len, if (!console_drivers) return; @@ -34,7 +34,7 @@ index c927f89961a8..49ea374ba8ea 100644 migrate_disable(); for_each_console(con) { if (exclusive_console && con != exclusive_console) -@@ -2555,6 +2560,11 @@ void console_unblank(void) +@@ -2583,6 +2588,11 @@ void console_unblank(void) { struct console *c; 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 8d15be329..bab07ebaf 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 eb4479ec80ada455dbd83964ab79b4aef7264b72 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 897315108800613002880d07fd0a2eb085146696 Mon Sep 17 00:00:00 2001 +Message-Id: <897315108800613002880d07fd0a2eb085146696.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 21 Mar 2013 19:01:05 +0100 Subject: [PATCH 208/329] printk: Drop the logbuf_lock more often -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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. @@ -16,10 +16,10 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 28 insertions(+) diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c -index 49ea374ba8ea..acef3657a316 100644 +index c5fbc51e61ed..4ac542763a09 100644 --- a/kernel/printk/printk.c +++ b/kernel/printk/printk.c -@@ -1427,12 +1427,23 @@ static int syslog_print_all(char __user *buf, int size, bool clear) +@@ -1455,12 +1455,23 @@ static int syslog_print_all(char __user *buf, int size, bool clear) u64 next_seq; u64 seq; u32 idx; @@ -43,7 +43,7 @@ index 49ea374ba8ea..acef3657a316 100644 /* * Find first record that fits, including all following records, * into the user-provided buffer for this dump. -@@ -1445,6 +1456,14 @@ static int syslog_print_all(char __user *buf, int size, bool clear) +@@ -1473,6 +1484,14 @@ static int syslog_print_all(char __user *buf, int size, bool clear) len += msg_print_text(msg, true, NULL, 0); idx = log_next(idx); seq++; @@ -58,7 +58,7 @@ index 49ea374ba8ea..acef3657a316 100644 } /* move first record forward until length fits into the buffer */ -@@ -1456,6 +1475,14 @@ static int syslog_print_all(char __user *buf, int size, bool clear) +@@ -1484,6 +1503,14 @@ static int syslog_print_all(char __user *buf, int size, bool clear) len -= msg_print_text(msg, true, NULL, 0); idx = log_next(idx); seq++; @@ -73,7 +73,7 @@ index 49ea374ba8ea..acef3657a316 100644 } /* last message fitting into this dump */ -@@ -1493,6 +1520,7 @@ static int syslog_print_all(char __user *buf, int size, bool clear) +@@ -1521,6 +1548,7 @@ static int syslog_print_all(char __user *buf, int size, bool clear) clear_seq = log_next_seq; clear_idx = log_next_idx; } 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 bafb39e43..70b251b16 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 a869b73cd786f0dc6b2c442613e2ecf794862a8b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 5f72f11e2a069acf5de031f6179b02ac5a016817 Mon Sep 17 00:00:00 2001 +Message-Id: <5f72f11e2a069acf5de031f6179b02ac5a016817.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: "Yadi.hu" Date: Wed, 10 Dec 2014 10:32:09 +0800 Subject: [PATCH 209/329] ARM: enable irq in translation/section permission @@ -9,7 +9,7 @@ Subject: [PATCH 209/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 2170f85e2..c8a9182b0 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 90682cd2350b918100574977bab35dfd116fcf32 Mon Sep 17 00:00:00 2001 -Message-Id: <90682cd2350b918100574977bab35dfd116fcf32.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 16775ca6e980eaa415c3e9b3df3027832ed0d91b Mon Sep 17 00:00:00 2001 +Message-Id: <16775ca6e980eaa415c3e9b3df3027832ed0d91b.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 11 Feb 2016 11:54:00 -0600 Subject: [PATCH 210/329] genirq: update irq_set_irqchip_state documentation -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 @@ -18,10 +18,10 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c -index ccd8af6fe49d..1a3cf77b11f8 100644 +index 44ee91ca0088..09147749657f 100644 --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c -@@ -2283,7 +2283,7 @@ EXPORT_SYMBOL_GPL(irq_get_irqchip_state); +@@ -2316,7 +2316,7 @@ EXPORT_SYMBOL_GPL(irq_get_irqchip_state); * This call sets the internal irqchip state of an interrupt, * depending on the value of @which. * 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 2ce0b3b3d..183ea733d 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 bdd4c581af7a4bba838e5a79d74b26440557da11 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 951d0da6fc249f03da0113a4b571d04be867ea80 Mon Sep 17 00:00:00 2001 +Message-Id: <951d0da6fc249f03da0113a4b571d04be867ea80.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Josh Cartwright Date: Thu, 11 Feb 2016 11:54:01 -0600 Subject: [PATCH 211/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 08af28f04..77ade08d0 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 710a279c8260c953083bdb35f6c9dea06c68355a Mon Sep 17 00:00:00 2001 -Message-Id: <710a279c8260c953083bdb35f6c9dea06c68355a.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 39d41edf73a8f9e1e705f64bc12e033d2d03f3d7 Mon Sep 17 00:00:00 2001 +Message-Id: <39d41edf73a8f9e1e705f64bc12e033d2d03f3d7.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 25 Jul 2018 14:02:38 +0200 Subject: [PATCH 212/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 c2fb8ccbd..3927b0c57 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 ebfbbd01a70adc51b3752dbe136c06ec25baee4b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 545e447ad9fe203b26f09142f9c30d4691b3e503 Mon Sep 17 00:00:00 2001 +Message-Id: <545e447ad9fe203b26f09142f9c30d4691b3e503.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Jason Wessel Date: Thu, 28 Jul 2011 12:42:23 -0500 Subject: [PATCH 213/329] kgdb/serial: Short term workaround -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 544908d3b..f8be9a117 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 2b79d1f51fed6a5007974ef9097554f96946a485 Mon Sep 17 00:00:00 2001 -Message-Id: <2b79d1f51fed6a5007974ef9097554f96946a485.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 2eecd7a65459b0ccdc26142cf47005022c38f903 Mon Sep 17 00:00:00 2001 +Message-Id: <2eecd7a65459b0ccdc26142cf47005022c38f903.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Clark Williams Date: Sat, 30 Jul 2011 21:55:53 -0500 Subject: [PATCH 214/329] sysfs: Add /sys/kernel/realtime entry -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 7f4d8c06b..aa7bf6cd2 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 b6601317729507f7c3909cfbc339cb143a0793a5 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 00a85fc7a892ec7212dd0059a4f4fcab888a7ab6 Mon Sep 17 00:00:00 2001 +Message-Id: <00a85fc7a892ec7212dd0059a4f4fcab888a7ab6.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Peter Zijlstra Date: Thu, 28 Jul 2011 10:43:51 +0200 Subject: [PATCH 215/329] mm, rt: kmap_atomic scheduling -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 f8047fda9..7d3d607ae 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 31b1a084913d3fc2f1704608432942b23f8c11b8 Mon Sep 17 00:00:00 2001 -Message-Id: <31b1a084913d3fc2f1704608432942b23f8c11b8.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 4234f529d91f856a90ed13d0c337fa18b8ae5723 Mon Sep 17 00:00:00 2001 +Message-Id: <4234f529d91f856a90ed13d0c337fa18b8ae5723.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Mar 2013 17:09:55 +0100 Subject: [PATCH 216/329] x86/highmem: Add a "already used pte" check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 ccf9a6388..a728fb84b 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 7c823937cacb93dac8c04dedcde80169b6148b0f Mon Sep 17 00:00:00 2001 -Message-Id: <7c823937cacb93dac8c04dedcde80169b6148b0f.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 9b59ba6c7b0a844b03878eda2b6cf8cd46655af5 Mon Sep 17 00:00:00 2001 +Message-Id: <9b59ba6c7b0a844b03878eda2b6cf8cd46655af5.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 11 Mar 2013 21:37:27 +0100 Subject: [PATCH 217/329] arm/highmem: Flush tlb on unmap -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 c994d7771..ba5f25961 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 4b5c00cb0fe2083a089d10e255c93ad861a81281 Mon Sep 17 00:00:00 2001 -Message-Id: <4b5c00cb0fe2083a089d10e255c93ad861a81281.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 0af49b5bd27c7cd6162d3aae8b725e3326cfa61c Mon Sep 17 00:00:00 2001 +Message-Id: <0af49b5bd27c7cd6162d3aae8b725e3326cfa61c.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 13 Feb 2013 11:03:11 +0100 Subject: [PATCH 218/329] arm: Enable highmem for rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 bd9d30b86..814770d8c 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 f7ff442a59c1345be55873e574297f4925eb0c88 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From fb2ca2f8dd0beedbe0243207adb1d39453e67ff2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sat, 12 Nov 2011 14:00:48 +0100 Subject: [PATCH 219/329] scsi/fcoe: Make RT aware. -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 93bc14b86..c1c4770c3 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 2ee9e0150ed5068610d747d116fd9d0db9bd8118 Mon Sep 17 00:00:00 2001 -Message-Id: <2ee9e0150ed5068610d747d116fd9d0db9bd8118.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b78cffc4084058a9d449692c7464f86d3ff85e8d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 14 Nov 2011 18:19:27 +0100 Subject: [PATCH 220/329] x86: crypto: Reduce preempt disabled regions -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 63b31d498..b0e30b4d2 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 077d0a933649fc9074955902f183b159e13f3bc6 Mon Sep 17 00:00:00 2001 -Message-Id: <077d0a933649fc9074955902f183b159e13f3bc6.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 96985e31d9bc25b62a3b93b24529d87a5c776eab Mon Sep 17 00:00:00 2001 +Message-Id: <96985e31d9bc25b62a3b93b24529d87a5c776eab.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2014 17:24:04 +0100 Subject: [PATCH 221/329] crypto: Reduce preempt disabled regions, more algos -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 f18ef8d4b..ecd1bb413 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 eed1ca4daba6f786f2579aa6e5c11a212fb410ec Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 024d112320340c333d6cab3cf22ffd0be7c05c9d Mon Sep 17 00:00:00 2001 +Message-Id: <024d112320340c333d6cab3cf22ffd0be7c05c9d.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 30 Nov 2017 13:40:10 +0100 Subject: [PATCH 222/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 13894f29b..15dd9f8f4 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 3de9de18f73fba591806c8e766c9df12d1ec5e64 Mon Sep 17 00:00:00 2001 -Message-Id: <3de9de18f73fba591806c8e766c9df12d1ec5e64.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 299f82e40eca11d9634aa6ceb0f82fc77beab2db Mon Sep 17 00:00:00 2001 +Message-Id: <299f82e40eca11d9634aa6ceb0f82fc77beab2db.1596234183.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 11 Jul 2018 17:14:47 +0200 Subject: [PATCH 223/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 1ed8164df..5741b69ce 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 1d0c968640cfdcf077654aa9b74d8bc1b1403e96 Mon Sep 17 00:00:00 2001 -Message-Id: <1d0c968640cfdcf077654aa9b74d8bc1b1403e96.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From a9e4f25711136eee5cc164319c127617c034fe3c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 26 Jul 2018 18:52:00 +0200 Subject: [PATCH 224/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 6368f2246..fab569347 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 0eedfca7cf11a79698e6925457c1a1c06e0d2c62 Mon Sep 17 00:00:00 2001 -Message-Id: <0eedfca7cf11a79698e6925457c1a1c06e0d2c62.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 0dde5f058582ef2cd8c77c6802ad36e5cbc3f660 Mon Sep 17 00:00:00 2001 +Message-Id: <0dde5f058582ef2cd8c77c6802ad36e5cbc3f660.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 14 Jul 2015 14:26:34 +0200 Subject: [PATCH 225/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 1b22f0ba4..87834b345 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 a1b041fed8f43cf88ee0bdea6caee42b3ab96eee Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From f44b5e07c4f50ed3bfd80541ebf701a40dc4bf13 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 16 Dec 2010 14:25:18 +0100 Subject: [PATCH 226/329] x86: stackprotector: Avoid random pool on rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz CPU bringup calls into the random pool to initialize the stack canary. During boot that works nicely even on RT as the might sleep diff --git a/debian/patches-rt/0227-random-Make-it-work-on-rt.patch b/debian/patches-rt/0227-random-Make-it-work-on-rt.patch index b3418f5a8..9d5ab233e 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 23ffee65aa85e7f8a6ebfcbb8f4c1901a7435cdf Mon Sep 17 00:00:00 2001 -Message-Id: <23ffee65aa85e7f8a6ebfcbb8f4c1901a7435cdf.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From d783906c07ac0e58cfedb0067b6e9f7b8274157c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 21 Aug 2012 20:38:50 +0200 Subject: [PATCH 227/329] random: Make it work on rt -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Delegate the random insertion to the forced threaded interrupt handler. Store the return IP of the hard interrupt handler in the irq @@ -149,10 +149,10 @@ index 38554bc35375..06a80bbf78af 100644 if (!noirqdebug) note_interrupt(desc, retval); diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c -index 1a3cf77b11f8..9591a451e05a 100644 +index 09147749657f..81434d90786f 100644 --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c -@@ -1063,6 +1063,12 @@ static int irq_thread(void *data) +@@ -1096,6 +1096,12 @@ static int irq_thread(void *data) if (action_ret == IRQ_WAKE_THREAD) irq_wake_secondary(desc, action); 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 e50601e4d..453499a19 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 d7b6dfb25c0b54a721120d4838218d8d6b2567fa Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 7f59f74c91f59c1fd2eb43ca335a841592fb2002 Mon Sep 17 00:00:00 2001 +Message-Id: <7f59f74c91f59c1fd2eb43ca335a841592fb2002.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 19 Jul 2017 17:31:20 +0200 Subject: [PATCH 228/329] cpu/hotplug: Implement CPU pinning -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 6a3e7b664..ea367111c 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 316706beeb9c64804201fd12d6777b9c638c4a16 Mon Sep 17 00:00:00 2001 -Message-Id: <316706beeb9c64804201fd12d6777b9c638c4a16.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From bb2fa11047eb9b638f318dbca6d46c8abdae5931 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 19 Aug 2018 08:28:35 +0200 Subject: [PATCH 229/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Since commit 7af443ee16976 ("sched/core: Require cpu_active() in select_task_rq(), for user tasks") select_fallback_rq() will BUG() if @@ -25,7 +25,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 1abd32af7918..173557e65689 100644 +index f13cc0073bbc..297934719db9 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -904,7 +904,7 @@ static inline bool is_cpu_allowed(struct task_struct *p, int cpu) 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 b264dce47..be0e1e75f 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 570093b6173e0ce8345757a125ceb51bf117b847 Mon Sep 17 00:00:00 2001 -Message-Id: <570093b6173e0ce8345757a125ceb51bf117b847.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From cc724c29d2cb4ced6712c1d3d72e6dc0a142c765 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 4 Aug 2017 18:31:00 +0200 Subject: [PATCH 230/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 f316446c5..ec316b34f 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 5c6867fa8aa3dc6fa2aa3e332bafcd0a6b3beea7 Mon Sep 17 00:00:00 2001 -Message-Id: <5c6867fa8aa3dc6fa2aa3e332bafcd0a6b3beea7.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From d2d996436a3b96c91964a8e728bfe926824e63a8 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Priyanka Jain Date: Thu, 17 May 2012 09:35:11 +0530 Subject: [PATCH 231/329] net: Remove preemption disabling in netif_rx() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz 1)enqueue_to_backlog() (called from netif_rx) should be bind to a particluar CPU. This can be achieved by 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 443b2cfe3..537ee5599 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 0b21d43e6d2bb8d0c26d4246ed9842bad0159a65 Mon Sep 17 00:00:00 2001 -Message-Id: <0b21d43e6d2bb8d0c26d4246ed9842bad0159a65.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 2368c6033f87efcb5b6a0ce41578038b648ec2c0 Mon Sep 17 00:00:00 2001 +Message-Id: <2368c6033f87efcb5b6a0ce41578038b648ec2c0.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 26 Sep 2012 16:21:08 +0200 Subject: [PATCH 232/329] net: Another local_irq_disable/kmalloc headache -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 1039c5d6e..316498132 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 f71a2204c447e6c9806131df8822ef87d5ae206c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From d68c697225a753c6cbfbd8ac77a77b6d0f47d688 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 15 Jan 2016 16:33:34 +0100 Subject: [PATCH 233/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 2b54d0059..d9cf081ff 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 784d866ac4b6a418130e86aba8622fdccfb8eea3 Mon Sep 17 00:00:00 2001 -Message-Id: <784d866ac4b6a418130e86aba8622fdccfb8eea3.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 08ccb72c4947bcf731754a2a2bab816a4bbbe39c Mon Sep 17 00:00:00 2001 +Message-Id: <08ccb72c4947bcf731754a2a2bab816a4bbbe39c.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Sun, 28 Oct 2012 11:18:08 +0100 Subject: [PATCH 234/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch b/debian/patches-rt/0235-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch index 4c212c53d..a814b95d0 100644 --- a/debian/patches-rt/0235-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch +++ b/debian/patches-rt/0235-lockdep-selftest-Only-do-hardirq-context-test-for-ra.patch @@ -1,12 +1,12 @@ -From e1efe44daaa675ca34964e23b52808054e162163 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 450945cde1764a9faad30035c50d3b004038a593 Mon Sep 17 00:00:00 2001 +Message-Id: <450945cde1764a9faad30035c50d3b004038a593.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Yong Zhang Date: Mon, 16 Apr 2012 15:01:56 +0800 Subject: [PATCH 235/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0236-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch b/debian/patches-rt/0236-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch index 8a8152f57..1ad20bfa3 100644 --- a/debian/patches-rt/0236-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch +++ b/debian/patches-rt/0236-lockdep-selftest-fix-warnings-due-to-missing-PREEMPT.patch @@ -1,12 +1,12 @@ -From 795f4f26c793011ea39217a2574fed283502fa8c Mon Sep 17 00:00:00 2001 -Message-Id: <795f4f26c793011ea39217a2574fed283502fa8c.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From de78b9d4720eb62b7b56177ed994451d340b8480 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Josh Cartwright Date: Wed, 28 Jan 2015 13:08:45 -0600 Subject: [PATCH 236/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0237-sched-Add-support-for-lazy-preemption.patch b/debian/patches-rt/0237-sched-Add-support-for-lazy-preemption.patch index 7577423ab..c1105bf5b 100644 --- a/debian/patches-rt/0237-sched-Add-support-for-lazy-preemption.patch +++ b/debian/patches-rt/0237-sched-Add-support-for-lazy-preemption.patch @@ -1,11 +1,11 @@ -From 99005508ed83579a749756069a0aacb2a0274dc6 Mon Sep 17 00:00:00 2001 -Message-Id: <99005508ed83579a749756069a0aacb2a0274dc6.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 2c07898b589abf34dde2538a5c56bedf99533dab Mon Sep 17 00:00:00 2001 +Message-Id: <2c07898b589abf34dde2538a5c56bedf99533dab.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 26 Oct 2012 18:50:54 +0100 Subject: [PATCH 237/329] sched: Add support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz It has become an obsession to mitigate the determinism vs. throughput loss of RT. Looking at the mainline semantics of preemption points @@ -266,7 +266,7 @@ index 8f5b80c0743b..0d3cf1654318 100644 __read_rt_unlock(cpuhp_pin); goto again; diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 173557e65689..14964f9d778c 100644 +index 297934719db9..64edaf6fe151 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -493,6 +493,48 @@ void resched_curr(struct rq *rq) @@ -318,7 +318,7 @@ index 173557e65689..14964f9d778c 100644 void resched_cpu(int cpu) { struct rq *rq = cpu_rq(cpu); -@@ -2405,6 +2447,9 @@ int sched_fork(unsigned long clone_flags, struct task_struct *p) +@@ -2406,6 +2448,9 @@ int sched_fork(unsigned long clone_flags, struct task_struct *p) p->on_cpu = 0; #endif init_task_preempt_count(p); @@ -328,7 +328,7 @@ index 173557e65689..14964f9d778c 100644 #ifdef CONFIG_SMP plist_node_init(&p->pushable_tasks, MAX_PRIO); RB_CLEAR_NODE(&p->pushable_dl_tasks); -@@ -3513,6 +3558,7 @@ static void __sched notrace __schedule(bool preempt) +@@ -3515,6 +3560,7 @@ static void __sched notrace __schedule(bool preempt) next = pick_next_task(rq, prev, &rf); clear_tsk_need_resched(prev); @@ -336,7 +336,7 @@ index 173557e65689..14964f9d778c 100644 clear_preempt_need_resched(); if (likely(prev != next)) { -@@ -3693,6 +3739,30 @@ static void __sched notrace preempt_schedule_common(void) +@@ -3695,6 +3741,30 @@ static void __sched notrace preempt_schedule_common(void) } while (need_resched()); } @@ -367,7 +367,7 @@ index 173557e65689..14964f9d778c 100644 #ifdef CONFIG_PREEMPT /* * this is the entry point to schedule() from in-kernel preemption -@@ -3707,7 +3777,8 @@ asmlinkage __visible void __sched notrace preempt_schedule(void) +@@ -3709,7 +3779,8 @@ asmlinkage __visible void __sched notrace preempt_schedule(void) */ if (likely(!preemptible())) return; @@ -377,7 +377,7 @@ index 173557e65689..14964f9d778c 100644 preempt_schedule_common(); } NOKPROBE_SYMBOL(preempt_schedule); -@@ -3734,6 +3805,9 @@ asmlinkage __visible void __sched notrace preempt_schedule_notrace(void) +@@ -3736,6 +3807,9 @@ asmlinkage __visible void __sched notrace preempt_schedule_notrace(void) if (likely(!preemptible())) return; @@ -387,7 +387,7 @@ index 173557e65689..14964f9d778c 100644 do { /* * Because the function tracer can trace preempt_count_sub() -@@ -5504,7 +5578,9 @@ void init_idle(struct task_struct *idle, int cpu) +@@ -5506,7 +5580,9 @@ void init_idle(struct task_struct *idle, int cpu) /* Set the preempt count _outside_ the spinlocks! */ init_idle_preempt_count(idle, cpu); @@ -398,7 +398,7 @@ index 173557e65689..14964f9d778c 100644 /* * The idle tasks have their own, simple scheduling class: */ -@@ -7221,6 +7297,7 @@ void migrate_disable(void) +@@ -7223,6 +7299,7 @@ void migrate_disable(void) } preempt_disable(); @@ -406,7 +406,7 @@ index 173557e65689..14964f9d778c 100644 pin_current_cpu(); migrate_disable_update_cpus_allowed(p); -@@ -7288,6 +7365,7 @@ void migrate_enable(void) +@@ -7290,6 +7367,7 @@ void migrate_enable(void) arg.dest_cpu = dest_cpu; unpin_current_cpu(); @@ -414,7 +414,7 @@ index 173557e65689..14964f9d778c 100644 preempt_enable(); stop_one_cpu(task_cpu(p), migration_cpu_stop, &arg); tlb_migrate_finish(p->mm); -@@ -7296,6 +7374,7 @@ void migrate_enable(void) +@@ -7298,6 +7376,7 @@ void migrate_enable(void) } } unpin_current_cpu(); @@ -423,7 +423,7 @@ index 173557e65689..14964f9d778c 100644 } EXPORT_SYMBOL(migrate_enable); diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c -index 97de4ea7dbea..03b7a81ab058 100644 +index 80289617ce3d..627cd3961268 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -4104,7 +4104,7 @@ check_preempt_tick(struct cfs_rq *cfs_rq, struct sched_entity *curr) @@ -480,7 +480,7 @@ index 97de4ea7dbea..03b7a81ab058 100644 /* * Only set the backward buddy when the current task is still * on the rq. This can happen when a wakeup gets interleaved -@@ -9826,7 +9826,7 @@ static void task_fork_fair(struct task_struct *p) +@@ -9834,7 +9834,7 @@ static void task_fork_fair(struct task_struct *p) * 'current' within the tree based on its new key value. */ swap(curr->vruntime, se->vruntime); @@ -489,7 +489,7 @@ index 97de4ea7dbea..03b7a81ab058 100644 } se->vruntime -= cfs_rq->min_vruntime; -@@ -9850,7 +9850,7 @@ prio_changed_fair(struct rq *rq, struct task_struct *p, int oldprio) +@@ -9858,7 +9858,7 @@ prio_changed_fair(struct rq *rq, struct task_struct *p, int oldprio) */ if (rq->curr == p) { if (p->prio > oldprio) diff --git a/debian/patches-rt/0238-ftrace-Fix-trace-header-alignment.patch b/debian/patches-rt/0238-ftrace-Fix-trace-header-alignment.patch index 052786200..9f9dcfdde 100644 --- a/debian/patches-rt/0238-ftrace-Fix-trace-header-alignment.patch +++ b/debian/patches-rt/0238-ftrace-Fix-trace-header-alignment.patch @@ -1,11 +1,11 @@ -From f941fff9d260bfa7c701fa5c173ffe3dbc8c5e6c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 4b94593405e073b8c06f10adcf8b18ee59c856df Mon Sep 17 00:00:00 2001 +Message-Id: <4b94593405e073b8c06f10adcf8b18ee59c856df.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 16 Oct 2016 05:08:30 +0200 Subject: [PATCH 238/329] ftrace: Fix trace header alignment -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Line up helper arrows to the right column. diff --git a/debian/patches-rt/0239-x86-Support-for-lazy-preemption.patch b/debian/patches-rt/0239-x86-Support-for-lazy-preemption.patch index bcbc2a96d..c99134d2d 100644 --- a/debian/patches-rt/0239-x86-Support-for-lazy-preemption.patch +++ b/debian/patches-rt/0239-x86-Support-for-lazy-preemption.patch @@ -1,11 +1,11 @@ -From edda41e1a73853a8a6703c4e692a98653d1f008d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 20b11bc2d3602b8b334aa82b0e9567fe42c45747 Mon Sep 17 00:00:00 2001 +Message-Id: <20b11bc2d3602b8b334aa82b0e9567fe42c45747.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 1 Nov 2012 11:03:47 +0100 Subject: [PATCH 239/329] x86: Support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Implement the x86 pieces for lazy preempt. diff --git a/debian/patches-rt/0240-x86-lazy-preempt-properly-check-against-preempt-mask.patch b/debian/patches-rt/0240-x86-lazy-preempt-properly-check-against-preempt-mask.patch index 2ee3f35e4..ef5f3df52 100644 --- a/debian/patches-rt/0240-x86-lazy-preempt-properly-check-against-preempt-mask.patch +++ b/debian/patches-rt/0240-x86-lazy-preempt-properly-check-against-preempt-mask.patch @@ -1,12 +1,12 @@ -From c94eee1a9ae1745a805eeb2d8d218b0c2c8dba2f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b1ee2a3de2cff388f708279f7f832ba76782e9ef Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 18 Feb 2019 16:57:09 +0100 Subject: [PATCH 240/329] x86: lazy-preempt: properly check against preempt-mask -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0241-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch b/debian/patches-rt/0241-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch index 95609c4af..d09b2946d 100644 --- a/debian/patches-rt/0241-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch +++ b/debian/patches-rt/0241-x86-lazy-preempt-use-proper-return-label-on-32bit-x8.patch @@ -1,12 +1,12 @@ -From 3359648051d20d9c9a72570516dc6d9008e385d5 Mon Sep 17 00:00:00 2001 -Message-Id: <3359648051d20d9c9a72570516dc6d9008e385d5.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From afdfaa64a3ab73b35cf0f8dc9d7345eaaa61fe75 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Feb 2019 14:53:49 +0100 Subject: [PATCH 241/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0242-arm-Add-support-for-lazy-preemption.patch b/debian/patches-rt/0242-arm-Add-support-for-lazy-preemption.patch index af9d8409f..934e1af03 100644 --- a/debian/patches-rt/0242-arm-Add-support-for-lazy-preemption.patch +++ b/debian/patches-rt/0242-arm-Add-support-for-lazy-preemption.patch @@ -1,11 +1,11 @@ -From 33921563e87daa42262c4f5f948cbc362563a5da Mon Sep 17 00:00:00 2001 -Message-Id: <33921563e87daa42262c4f5f948cbc362563a5da.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 012d63f25f97a06484e0f04b545cac31c34c39c1 Mon Sep 17 00:00:00 2001 +Message-Id: <012d63f25f97a06484e0f04b545cac31c34c39c1.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 31 Oct 2012 12:04:11 +0100 Subject: [PATCH 242/329] arm: Add support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Implement the arm pieces for lazy preempt. diff --git a/debian/patches-rt/0243-powerpc-Add-support-for-lazy-preemption.patch b/debian/patches-rt/0243-powerpc-Add-support-for-lazy-preemption.patch index 574bbbcda..dcbbe66bc 100644 --- a/debian/patches-rt/0243-powerpc-Add-support-for-lazy-preemption.patch +++ b/debian/patches-rt/0243-powerpc-Add-support-for-lazy-preemption.patch @@ -1,11 +1,11 @@ -From 260ef32879562ed3b79470a7b376e0016b2f2d5a Mon Sep 17 00:00:00 2001 -Message-Id: <260ef32879562ed3b79470a7b376e0016b2f2d5a.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b92073bdc2225792633135f50dd9122ccdb5e326 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Thu, 1 Nov 2012 10:14:11 +0100 Subject: [PATCH 243/329] powerpc: Add support for lazy preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Implement the powerpc pieces for lazy preempt. diff --git a/debian/patches-rt/0244-arch-arm64-Add-lazy-preempt-support.patch b/debian/patches-rt/0244-arch-arm64-Add-lazy-preempt-support.patch index acd637534..113be6ccc 100644 --- a/debian/patches-rt/0244-arch-arm64-Add-lazy-preempt-support.patch +++ b/debian/patches-rt/0244-arch-arm64-Add-lazy-preempt-support.patch @@ -1,11 +1,11 @@ -From cca2e5549775271cf1c2a99dfc80aa845c721961 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 13a39715a42e35d2c746f27c7393b833270b2605 Mon Sep 17 00:00:00 2001 +Message-Id: <13a39715a42e35d2c746f27c7393b833270b2605.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Anders Roxell Date: Thu, 14 May 2015 17:52:17 +0200 Subject: [PATCH 244/329] arch/arm64: Add lazy preempt support -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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, @@ -36,7 +36,7 @@ index 1fe3e5cb2927..6cbaf00c14ca 100644 select HAVE_RCU_TABLE_FREE select HAVE_RSEQ diff --git a/arch/arm64/include/asm/thread_info.h b/arch/arm64/include/asm/thread_info.h -index cb2c10a8f0a8..f1820f7318b6 100644 +index 69ac5262cccd..39e921817f28 100644 --- a/arch/arm64/include/asm/thread_info.h +++ b/arch/arm64/include/asm/thread_info.h @@ -43,6 +43,7 @@ struct thread_info { @@ -63,7 +63,7 @@ index cb2c10a8f0a8..f1820f7318b6 100644 #define _TIF_NOHZ (1 << TIF_NOHZ) #define _TIF_SYSCALL_TRACE (1 << TIF_SYSCALL_TRACE) #define _TIF_SYSCALL_AUDIT (1 << TIF_SYSCALL_AUDIT) -@@ -106,8 +109,9 @@ void arch_release_task_struct(struct task_struct *tsk); +@@ -107,8 +110,9 @@ void arch_release_task_struct(struct task_struct *tsk); #define _TIF_WORK_MASK (_TIF_NEED_RESCHED | _TIF_SIGPENDING | \ _TIF_NOTIFY_RESUME | _TIF_FOREIGN_FPSTATE | \ @@ -119,10 +119,10 @@ index 5f800384cb9a..b582580c8c4c 100644 #endif diff --git a/arch/arm64/kernel/signal.c b/arch/arm64/kernel/signal.c -index 5dcc942906db..4fec251fe147 100644 +index ca565853dea6..3f321daa7702 100644 --- a/arch/arm64/kernel/signal.c +++ b/arch/arm64/kernel/signal.c -@@ -926,7 +926,7 @@ asmlinkage void do_notify_resume(struct pt_regs *regs, +@@ -919,7 +919,7 @@ asmlinkage void do_notify_resume(struct pt_regs *regs, /* Check valid user FS if needed */ addr_limit_user_check(); diff --git a/debian/patches-rt/0245-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch b/debian/patches-rt/0245-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch index 957797ee9..ca1969797 100644 --- a/debian/patches-rt/0245-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch +++ b/debian/patches-rt/0245-connector-cn_proc-Protect-send_msg-with-a-local-lock.patch @@ -1,12 +1,12 @@ -From 419a95ed6b9f18684a98f763a2a71bd326e1d57b Mon Sep 17 00:00:00 2001 -Message-Id: <419a95ed6b9f18684a98f763a2a71bd326e1d57b.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 832390aa2ac43656ac56b1966a21c93616650b3b Mon Sep 17 00:00:00 2001 +Message-Id: <832390aa2ac43656ac56b1966a21c93616650b3b.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 16 Oct 2016 05:11:54 +0200 Subject: [PATCH 245/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0246-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch b/debian/patches-rt/0246-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch index fabb1c16e..18e81ecc8 100644 --- a/debian/patches-rt/0246-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch +++ b/debian/patches-rt/0246-drivers-block-zram-Replace-bit-spinlocks-with-rtmute.patch @@ -1,12 +1,12 @@ -From ceeee0d5920e787c297fc85ca0f50d08b5e0c87e Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ce6f30f35d4a32ddcea1038f5940d07dbebbab4c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Mike Galbraith Date: Thu, 31 Mar 2016 04:08:28 +0200 Subject: [PATCH 246/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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. @@ -19,7 +19,7 @@ Signed-off-by: Sebastian Andrzej Siewior 2 files changed, 41 insertions(+) diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c -index 76abe40bfa83..d6cf9508b80d 100644 +index 52850c10165e..95b28f842533 100644 --- a/drivers/block/zram/zram_drv.c +++ b/drivers/block/zram/zram_drv.c @@ -53,6 +53,40 @@ static size_t huge_class_size; diff --git a/debian/patches-rt/0247-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch b/debian/patches-rt/0247-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch index 7376d980d..48b8d9ece 100644 --- a/debian/patches-rt/0247-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch +++ b/debian/patches-rt/0247-drivers-zram-Don-t-disable-preemption-in-zcomp_strea.patch @@ -1,12 +1,12 @@ -From fd8b3b3e54ec20a55a36728795deff41ca074496 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From f85ce070074ba7b5622da31d4053eb15bca8e873 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Mike Galbraith Date: Thu, 20 Oct 2016 11:15:22 +0200 Subject: [PATCH 247/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 @@ -70,7 +70,7 @@ index 41c1002a7d7d..d424eafcbf8e 100644 /* dynamic per-device compression frontend */ diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c -index d6cf9508b80d..71520199226a 100644 +index 95b28f842533..98bf78861e52 100644 --- a/drivers/block/zram/zram_drv.c +++ b/drivers/block/zram/zram_drv.c @@ -1028,6 +1028,7 @@ static int __zram_bvec_read(struct zram *zram, struct page *page, u32 index, diff --git a/debian/patches-rt/0248-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch b/debian/patches-rt/0248-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch index 5e33d3c2c..2cd30b797 100644 --- a/debian/patches-rt/0248-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch +++ b/debian/patches-rt/0248-drivers-zram-fix-zcomp_stream_get-smp_processor_id-u.patch @@ -1,12 +1,12 @@ -From f884b4196f226bd7c13172b1c28eec0cd9fcf2e3 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 25b5849184aea44973866a18fef8361277469583 Mon Sep 17 00:00:00 2001 +Message-Id: <25b5849184aea44973866a18fef8361277469583.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Mike Galbraith Date: Wed, 23 Aug 2017 11:57:29 +0200 Subject: [PATCH 248/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0249-tpm_tis-fix-stall-after-iowrite-s.patch b/debian/patches-rt/0249-tpm_tis-fix-stall-after-iowrite-s.patch index 1dd8fb7d8..207d4802d 100644 --- a/debian/patches-rt/0249-tpm_tis-fix-stall-after-iowrite-s.patch +++ b/debian/patches-rt/0249-tpm_tis-fix-stall-after-iowrite-s.patch @@ -1,11 +1,11 @@ -From d3528791e1126dc31428038909485f38f30c755b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 3062d321fb92c454c4d6faffe10fe4b56dbf8d07 Mon Sep 17 00:00:00 2001 +Message-Id: <3062d321fb92c454c4d6faffe10fe4b56dbf8d07.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Haris Okanovic Date: Tue, 15 Aug 2017 15:13:08 -0500 Subject: [PATCH 249/329] tpm_tis: fix stall after iowrite*()s -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0250-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch b/debian/patches-rt/0250-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch index 054cf6398..071558321 100644 --- a/debian/patches-rt/0250-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch +++ b/debian/patches-rt/0250-watchdog-prevent-deferral-of-watchdogd-wakeup-on-RT.patch @@ -1,11 +1,11 @@ -From cc76e3461b86d564e0fe0a8eded6357a6a6feea3 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From d6406eb550b1c69e5082bd418ff0fd43ef572436 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Julia Cartwright Date: Fri, 28 Sep 2018 21:03:51 +0000 Subject: [PATCH 250/329] watchdog: prevent deferral of watchdogd wakeup on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0251-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch b/debian/patches-rt/0251-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch index 6f845c96f..7155afd31 100644 --- a/debian/patches-rt/0251-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch +++ b/debian/patches-rt/0251-drm-radeon-i915-Use-preempt_disable-enable_rt-where-.patch @@ -1,12 +1,12 @@ -From a8807e9c95add534929192facd840e504e31311c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 97ccfd88d0c6abe6c94a4bef6322da580f960e5f Mon Sep 17 00:00:00 2001 +Message-Id: <97ccfd88d0c6abe6c94a4bef6322da580f960e5f.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Mike Galbraith Date: Sat, 27 Feb 2016 08:09:11 +0100 Subject: [PATCH 251/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz DRM folks identified the spots, so use them. diff --git a/debian/patches-rt/0252-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch b/debian/patches-rt/0252-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch index 8f0551e94..702bc3d9e 100644 --- a/debian/patches-rt/0252-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch +++ b/debian/patches-rt/0252-drm-i915-Use-local_lock-unlock_irq-in-intel_pipe_upd.patch @@ -1,12 +1,12 @@ -From d2f572428eb2121a8e698318d5880c10b0e6a5d6 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From cbcedbe458c342c08552f499f686b0f78db20c57 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Mike Galbraith Date: Sat, 27 Feb 2016 09:01:42 +0100 Subject: [PATCH 252/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0253-drm-i915-disable-tracing-on-RT.patch b/debian/patches-rt/0253-drm-i915-disable-tracing-on-RT.patch index 1804ae7d6..941d79085 100644 --- a/debian/patches-rt/0253-drm-i915-disable-tracing-on-RT.patch +++ b/debian/patches-rt/0253-drm-i915-disable-tracing-on-RT.patch @@ -1,11 +1,11 @@ -From e0bd919791b22815f94a9f79bf7e6542fa250d40 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 57ba9581c24d9a89c0e2c95bb5ce60905f7fdc27 Mon Sep 17 00:00:00 2001 +Message-Id: <57ba9581c24d9a89c0e2c95bb5ce60905f7fdc27.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 6 Dec 2018 09:52:20 +0100 Subject: [PATCH 253/329] drm/i915: disable tracing on -RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Luca Abeni reported this: | BUG: scheduling while atomic: kworker/u8:2/15203/0x00000003 diff --git a/debian/patches-rt/0254-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch b/debian/patches-rt/0254-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch index f12cb5a87..679b66bdb 100644 --- a/debian/patches-rt/0254-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch +++ b/debian/patches-rt/0254-drm-i915-skip-DRM_I915_LOW_LEVEL_TRACEPOINTS-with-NO.patch @@ -1,12 +1,12 @@ -From 57d48ffba436c769ba80b0500a99edee90200554 Mon Sep 17 00:00:00 2001 -Message-Id: <57d48ffba436c769ba80b0500a99edee90200554.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From dea92d5c52462df2f9d8a27620bffb0460010d0a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 19 Dec 2018 10:47:02 +0100 Subject: [PATCH 254/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0255-cgroups-use-simple-wait-in-css_release.patch b/debian/patches-rt/0255-cgroups-use-simple-wait-in-css_release.patch index 13017c869..521c06967 100644 --- a/debian/patches-rt/0255-cgroups-use-simple-wait-in-css_release.patch +++ b/debian/patches-rt/0255-cgroups-use-simple-wait-in-css_release.patch @@ -1,11 +1,11 @@ -From d284a7137ca6403eea4e26b9f26b49bd9143011c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From efea562234e9594e7ef12a742934c2cef5a02880 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 13 Feb 2015 15:52:24 +0100 Subject: [PATCH 255/329] cgroups: use simple wait in css_release() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz To avoid: |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:914 @@ -38,7 +38,7 @@ Signed-off-by: Sebastian Andrzej Siewior 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/include/linux/cgroup-defs.h b/include/linux/cgroup-defs.h -index a01ebb630abc..34fb541e90be 100644 +index f92264d1ed4f..cc912f3dc203 100644 --- a/include/linux/cgroup-defs.h +++ b/include/linux/cgroup-defs.h @@ -20,6 +20,7 @@ @@ -58,7 +58,7 @@ index a01ebb630abc..34fb541e90be 100644 /* diff --git a/kernel/cgroup/cgroup.c b/kernel/cgroup/cgroup.c -index 877ba6dacca8..97ff80283248 100644 +index 6ae98c714edd..32a4b0e73ed0 100644 --- a/kernel/cgroup/cgroup.c +++ b/kernel/cgroup/cgroup.c @@ -4680,10 +4680,10 @@ static void css_free_rwork_fn(struct work_struct *work) diff --git a/debian/patches-rt/0256-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch b/debian/patches-rt/0256-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch index 4f678444b..44ef42789 100644 --- a/debian/patches-rt/0256-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch +++ b/debian/patches-rt/0256-cpuset-Convert-callback_lock-to-raw_spinlock_t.patch @@ -1,11 +1,11 @@ -From 93f84cfa94d44ee4e709a49c512af51e3a4303c2 Mon Sep 17 00:00:00 2001 -Message-Id: <93f84cfa94d44ee4e709a49c512af51e3a4303c2.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ccaeee7e528b0640b85ed16bf3e904813007359d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Mike Galbraith Date: Sun, 8 Jan 2017 09:32:25 +0100 Subject: [PATCH 256/329] cpuset: Convert callback_lock to raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz The two commits below add up to a cpuset might_sleep() splat for RT: diff --git a/debian/patches-rt/0257-apparmor-use-a-locallock-instead-preempt_disable.patch b/debian/patches-rt/0257-apparmor-use-a-locallock-instead-preempt_disable.patch index 8e330e839..b26c9acad 100644 --- a/debian/patches-rt/0257-apparmor-use-a-locallock-instead-preempt_disable.patch +++ b/debian/patches-rt/0257-apparmor-use-a-locallock-instead-preempt_disable.patch @@ -1,11 +1,11 @@ -From 1bee9a8581a1d461d22fd5fe2c4048b60958a3eb Mon Sep 17 00:00:00 2001 -Message-Id: <1bee9a8581a1d461d22fd5fe2c4048b60958a3eb.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 8f87d239f6657f4d4b44d4416acf227ea03ed64c Mon Sep 17 00:00:00 2001 +Message-Id: <8f87d239f6657f4d4b44d4416acf227ea03ed64c.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 11 Oct 2017 17:43:49 +0200 Subject: [PATCH 257/329] apparmor: use a locallock instead preempt_disable() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0258-workqueue-Prevent-deadlock-stall-on-RT.patch b/debian/patches-rt/0258-workqueue-Prevent-deadlock-stall-on-RT.patch index 55e0d278a..3b899cba8 100644 --- a/debian/patches-rt/0258-workqueue-Prevent-deadlock-stall-on-RT.patch +++ b/debian/patches-rt/0258-workqueue-Prevent-deadlock-stall-on-RT.patch @@ -1,11 +1,11 @@ -From 3233bad46473f1379d6f60644f62563894c066a2 Mon Sep 17 00:00:00 2001 -Message-Id: <3233bad46473f1379d6f60644f62563894c066a2.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 34b852bfa79162dde3e9eda062390595365df54a Mon Sep 17 00:00:00 2001 +Message-Id: <34b852bfa79162dde3e9eda062390595365df54a.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 27 Jun 2014 16:24:52 +0200 Subject: [PATCH 258/329] workqueue: Prevent deadlock/stall on RT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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. @@ -46,10 +46,10 @@ Cc: Steven Rostedt 2 files changed, 51 insertions(+), 15 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 14964f9d778c..d25017e931c6 100644 +index 64edaf6fe151..8d2452cb5793 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -3610,9 +3610,8 @@ void __noreturn do_task_dead(void) +@@ -3612,9 +3612,8 @@ void __noreturn do_task_dead(void) static inline void sched_submit_work(struct task_struct *tsk) { @@ -60,7 +60,7 @@ index 14964f9d778c..d25017e931c6 100644 /* * If a worker went to sleep, notify and ask workqueue whether * it wants to wake up a task to maintain concurrency. -@@ -3626,6 +3625,9 @@ static inline void sched_submit_work(struct task_struct *tsk) +@@ -3628,6 +3627,9 @@ static inline void sched_submit_work(struct task_struct *tsk) preempt_enable_no_resched(); } diff --git a/debian/patches-rt/0259-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch b/debian/patches-rt/0259-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch index 2360b4361..ac8937c15 100644 --- a/debian/patches-rt/0259-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch +++ b/debian/patches-rt/0259-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch @@ -1,11 +1,11 @@ -From d4f7db2d31d500b49410233187d1b42ab749e6d9 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From bc0a957ff263743367ac579797050dd0d424512b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 3 Jul 2009 08:44:56 -0500 Subject: [PATCH 259/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz To avoid allocation allow rt tasks to cache one sigqueue struct in task struct. diff --git a/debian/patches-rt/0260-Add-localversion-for-RT-release.patch b/debian/patches-rt/0260-Add-localversion-for-RT-release.patch index c4730a816..dee6ba302 100644 --- a/debian/patches-rt/0260-Add-localversion-for-RT-release.patch +++ b/debian/patches-rt/0260-Add-localversion-for-RT-release.patch @@ -1,11 +1,11 @@ -From 48c859ef09c1e493cb3e170ff0dc40c3c1c476b5 Mon Sep 17 00:00:00 2001 -Message-Id: <48c859ef09c1e493cb3e170ff0dc40c3c1c476b5.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From cb3085166d917b84231899ebe30c352c766e8da2 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Fri, 8 Jul 2011 20:25:16 +0200 Subject: [PATCH 260/329] Add localversion for -RT release -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Signed-off-by: Thomas Gleixner --- diff --git a/debian/patches-rt/0261-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch b/debian/patches-rt/0261-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch index e8e32d96e..39d4d1e3b 100644 --- a/debian/patches-rt/0261-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch +++ b/debian/patches-rt/0261-powerpc-pseries-iommu-Use-a-locallock-instead-local_.patch @@ -1,12 +1,12 @@ -From 61719bd674ea378eb95e24b6af330f8c016491a2 Mon Sep 17 00:00:00 2001 -Message-Id: <61719bd674ea378eb95e24b6af330f8c016491a2.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 8c54cb57167c953f8fbe9f9fd297ac9763591d74 Mon Sep 17 00:00:00 2001 +Message-Id: <8c54cb57167c953f8fbe9f9fd297ac9763591d74.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 26 Mar 2019 18:31:54 +0100 Subject: [PATCH 261/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0262-powerpc-reshuffle-TIF-bits.patch b/debian/patches-rt/0262-powerpc-reshuffle-TIF-bits.patch index af70e30a7..f13f838d3 100644 --- a/debian/patches-rt/0262-powerpc-reshuffle-TIF-bits.patch +++ b/debian/patches-rt/0262-powerpc-reshuffle-TIF-bits.patch @@ -1,11 +1,11 @@ -From 6bc0b1e4bce625606b9748ef597130a9759f85eb Mon Sep 17 00:00:00 2001 -Message-Id: <6bc0b1e4bce625606b9748ef597130a9759f85eb.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 37a56eaba0c00116aa3d3130200ae6d5d3561ca8 Mon Sep 17 00:00:00 2001 +Message-Id: <37a56eaba0c00116aa3d3130200ae6d5d3561ca8.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 22 Mar 2019 17:15:58 +0100 Subject: [PATCH 262/329] powerpc: reshuffle TIF bits -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0263-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch b/debian/patches-rt/0263-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch index 08fc6ced5..875e16b9f 100644 --- a/debian/patches-rt/0263-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch +++ b/debian/patches-rt/0263-tty-sysrq-Convert-show_lock-to-raw_spinlock_t.patch @@ -1,11 +1,11 @@ -From e1f7b9e1eddc425d8cc697726b124efab2f2bae3 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ea3af8328b32575df8c85280eae6bedadd942e2f Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 13 Mar 2019 11:40:34 +0000 Subject: [PATCH 263/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0264-drm-i915-Don-t-disable-interrupts-independently-of-t.patch b/debian/patches-rt/0264-drm-i915-Don-t-disable-interrupts-independently-of-t.patch index 6652e2822..9db34c8d1 100644 --- a/debian/patches-rt/0264-drm-i915-Don-t-disable-interrupts-independently-of-t.patch +++ b/debian/patches-rt/0264-drm-i915-Don-t-disable-interrupts-independently-of-t.patch @@ -1,12 +1,12 @@ -From 3e245283e3b4a92c8e9cf5f69af29712990ef2b5 Mon Sep 17 00:00:00 2001 -Message-Id: <3e245283e3b4a92c8e9cf5f69af29712990ef2b5.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 99725bf891380f1d31ccb9a0cd85e686d8c1fffc Mon Sep 17 00:00:00 2001 +Message-Id: <99725bf891380f1d31ccb9a0cd85e686d8c1fffc.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 10 Apr 2019 11:01:37 +0200 Subject: [PATCH 264/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0265-sched-completion-Fix-a-lockup-in-wait_for_completion.patch b/debian/patches-rt/0265-sched-completion-Fix-a-lockup-in-wait_for_completion.patch index 606c287cb..3f2ff3243 100644 --- a/debian/patches-rt/0265-sched-completion-Fix-a-lockup-in-wait_for_completion.patch +++ b/debian/patches-rt/0265-sched-completion-Fix-a-lockup-in-wait_for_completion.patch @@ -1,12 +1,12 @@ -From 9058e40d61d3df656608abb1afacce8903781751 Mon Sep 17 00:00:00 2001 -Message-Id: <9058e40d61d3df656608abb1afacce8903781751.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 5ad84d4b59fd5dac1aebc8c300a707baba9d1498 Mon Sep 17 00:00:00 2001 +Message-Id: <5ad84d4b59fd5dac1aebc8c300a707baba9d1498.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Corey Minyard Date: Thu, 9 May 2019 14:33:20 -0500 Subject: [PATCH 265/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Consider following race: diff --git a/debian/patches-rt/0266-kthread-add-a-global-worker-thread.patch b/debian/patches-rt/0266-kthread-add-a-global-worker-thread.patch index b3782d532..9a87e4182 100644 --- a/debian/patches-rt/0266-kthread-add-a-global-worker-thread.patch +++ b/debian/patches-rt/0266-kthread-add-a-global-worker-thread.patch @@ -1,11 +1,11 @@ -From 7f76ec5f80e3f2615dc4d1c5c95ce8f88e22412b Mon Sep 17 00:00:00 2001 -Message-Id: <7f76ec5f80e3f2615dc4d1c5c95ce8f88e22412b.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 2be03ce4173c7b8223c55b2a37708463ffd169f4 Mon Sep 17 00:00:00 2001 +Message-Id: <2be03ce4173c7b8223c55b2a37708463ffd169f4.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 12 Feb 2019 15:09:38 +0100 Subject: [PATCH 266/329] kthread: add a global worker thread. -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 7c064c6aff55..064bdf98544b 100644 +index 2180c6388eb9..7b173ca08e22 100644 --- a/init/main.c +++ b/init/main.c -@@ -1131,6 +1131,7 @@ static noinline void __init kernel_init_freeable(void) +@@ -1130,6 +1130,7 @@ static noinline void __init kernel_init_freeable(void) smp_prepare_cpus(setup_max_cpus); workqueue_init(); diff --git a/debian/patches-rt/0267-arm-imx6-cpuidle-Use-raw_spinlock_t.patch b/debian/patches-rt/0267-arm-imx6-cpuidle-Use-raw_spinlock_t.patch index 5681299e0..5655363bb 100644 --- a/debian/patches-rt/0267-arm-imx6-cpuidle-Use-raw_spinlock_t.patch +++ b/debian/patches-rt/0267-arm-imx6-cpuidle-Use-raw_spinlock_t.patch @@ -1,11 +1,11 @@ -From 98a1f056e6fe5b7b5d9db8cfc3a6f24a6bec4386 Mon Sep 17 00:00:00 2001 -Message-Id: <98a1f056e6fe5b7b5d9db8cfc3a6f24a6bec4386.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 486078890cca7e30efddb5383879ad96aae8f0bf Mon Sep 17 00:00:00 2001 +Message-Id: <486078890cca7e30efddb5383879ad96aae8f0bf.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 14 May 2019 17:07:44 +0200 Subject: [PATCH 267/329] arm: imx6: cpuidle: Use raw_spinlock_t -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 40d0332ec8312e9c090f0a5414d9c90e12b13611 ] diff --git a/debian/patches-rt/0268-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch b/debian/patches-rt/0268-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch index f1c98e230..859357b7d 100644 --- a/debian/patches-rt/0268-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch +++ b/debian/patches-rt/0268-rcu-Don-t-allow-to-change-rcu_normal_after_boot-on-R.patch @@ -1,12 +1,12 @@ -From 6ac59ffb1fd38d1523c9426b1084fd65206e40f4 Mon Sep 17 00:00:00 2001 -Message-Id: <6ac59ffb1fd38d1523c9426b1084fd65206e40f4.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From debddd2c9f8b9b92a77b4e692564a08b21571a51 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 18:29:13 +0200 Subject: [PATCH 268/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit c6c058c10577815a2491ce661876cff00a4c3b15 ] diff --git a/debian/patches-rt/0269-pci-switchtec-fix-stream_open.cocci-warnings.patch b/debian/patches-rt/0269-pci-switchtec-fix-stream_open.cocci-warnings.patch index 7b95410fe..56472e54d 100644 --- a/debian/patches-rt/0269-pci-switchtec-fix-stream_open.cocci-warnings.patch +++ b/debian/patches-rt/0269-pci-switchtec-fix-stream_open.cocci-warnings.patch @@ -1,11 +1,11 @@ -From bfe24ab61ba1de950c24c40f3cc16e232e8f513b Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 139fcd6df14d4169fd00bb504ebb202fe4167c94 Mon Sep 17 00:00:00 2001 +Message-Id: <139fcd6df14d4169fd00bb504ebb202fe4167c94.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: kbuild test robot Date: Sat, 13 Apr 2019 11:22:51 +0800 Subject: [PATCH 269/329] pci/switchtec: fix stream_open.cocci warnings -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 9462c69e29307adc95c289f50839d5d683973891 ] diff --git a/debian/patches-rt/0270-sched-core-Drop-a-preempt_disable_rt-statement.patch b/debian/patches-rt/0270-sched-core-Drop-a-preempt_disable_rt-statement.patch index b73942e70..fd9859f50 100644 --- a/debian/patches-rt/0270-sched-core-Drop-a-preempt_disable_rt-statement.patch +++ b/debian/patches-rt/0270-sched-core-Drop-a-preempt_disable_rt-statement.patch @@ -1,11 +1,11 @@ -From 6bcf841f99e62dd5c548e5f16bbe0f70000d41ac Mon Sep 17 00:00:00 2001 -Message-Id: <6bcf841f99e62dd5c548e5f16bbe0f70000d41ac.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 06c646b5acbda25c7ebb05d9cf4f2de77a534a23 Mon Sep 17 00:00:00 2001 +Message-Id: <06c646b5acbda25c7ebb05d9cf4f2de77a534a23.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 19:33:16 +0200 Subject: [PATCH 270/329] sched/core: Drop a preempt_disable_rt() statement -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 761126efdcbe3fa3e99c9079fa0ad6eca2f251f2 ] @@ -19,7 +19,7 @@ Signed-off-by: Steven Rostedt (VMware) 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index d25017e931c6..5bfe4eab5b0a 100644 +index 8d2452cb5793..9337303a9f43 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -558,14 +558,11 @@ void resched_cpu(int cpu) diff --git a/debian/patches-rt/0271-timers-Redo-the-notification-of-canceling-timers-on-.patch b/debian/patches-rt/0271-timers-Redo-the-notification-of-canceling-timers-on-.patch index 5a9543f5f..ba290cb6f 100644 --- a/debian/patches-rt/0271-timers-Redo-the-notification-of-canceling-timers-on-.patch +++ b/debian/patches-rt/0271-timers-Redo-the-notification-of-canceling-timers-on-.patch @@ -1,12 +1,12 @@ -From 9c88015bd83ae931c56e9e5454d4d7a04f620556 Mon Sep 17 00:00:00 2001 -Message-Id: <9c88015bd83ae931c56e9e5454d4d7a04f620556.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 50c77b51735c142605d4621a971453a3705eb233 Mon Sep 17 00:00:00 2001 +Message-Id: <50c77b51735c142605d4621a971453a3705eb233.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 24 Jun 2019 19:39:06 +0200 Subject: [PATCH 271/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit c71273154c2ad12e13333aada340ff30e826a11b ] @@ -464,7 +464,7 @@ index ddb21145211a..725bd230a8db 100644 void common_timer_get(struct k_itimer *timr, struct itimerspec64 *cur_setting); diff --git a/kernel/time/timer.c b/kernel/time/timer.c -index 2fcd56aa6092..1c67aab34ff5 100644 +index a4279d24b438..0e33ced0404b 100644 --- a/kernel/time/timer.c +++ b/kernel/time/timer.c @@ -44,7 +44,6 @@ @@ -486,7 +486,7 @@ index 2fcd56aa6092..1c67aab34ff5 100644 unsigned long clk; unsigned long next_expiry; unsigned int cpu; -@@ -1189,33 +1186,6 @@ void add_timer_on(struct timer_list *timer, int cpu) +@@ -1200,33 +1197,6 @@ void add_timer_on(struct timer_list *timer, int cpu) } EXPORT_SYMBOL_GPL(add_timer_on); @@ -520,7 +520,7 @@ index 2fcd56aa6092..1c67aab34ff5 100644 /** * del_timer - deactivate a timer. * @timer: the timer to be deactivated -@@ -1245,14 +1215,8 @@ int del_timer(struct timer_list *timer) +@@ -1256,14 +1226,8 @@ int del_timer(struct timer_list *timer) } EXPORT_SYMBOL(del_timer); @@ -537,7 +537,7 @@ index 2fcd56aa6092..1c67aab34ff5 100644 { struct timer_base *base; unsigned long flags; -@@ -1260,7 +1224,7 @@ int try_to_del_timer_sync(struct timer_list *timer) +@@ -1271,7 +1235,7 @@ int try_to_del_timer_sync(struct timer_list *timer) debug_assert_init(timer); @@ -546,7 +546,7 @@ index 2fcd56aa6092..1c67aab34ff5 100644 if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); -@@ -1269,9 +1233,42 @@ int try_to_del_timer_sync(struct timer_list *timer) +@@ -1280,9 +1244,42 @@ int try_to_del_timer_sync(struct timer_list *timer) return ret; } @@ -589,7 +589,7 @@ index 2fcd56aa6092..1c67aab34ff5 100644 /** * del_timer_sync - deactivate a timer and wait for the handler to finish. * @timer: the timer to be deactivated -@@ -1327,12 +1324,8 @@ int del_timer_sync(struct timer_list *timer) +@@ -1338,12 +1335,8 @@ int del_timer_sync(struct timer_list *timer) * could lead to deadlock. */ WARN_ON(in_irq() && !(timer->flags & TIMER_IRQSAFE)); @@ -604,7 +604,7 @@ index 2fcd56aa6092..1c67aab34ff5 100644 } EXPORT_SYMBOL(del_timer_sync); #endif -@@ -1397,11 +1390,15 @@ static void expire_timers(struct timer_base *base, struct hlist_head *head) +@@ -1408,11 +1401,15 @@ static void expire_timers(struct timer_base *base, struct hlist_head *head) raw_spin_unlock(&base->lock); call_timer_fn(timer, fn); base->running_timer = NULL; @@ -620,7 +620,7 @@ index 2fcd56aa6092..1c67aab34ff5 100644 raw_spin_lock_irq(&base->lock); } } -@@ -1698,6 +1695,7 @@ static inline void __run_timers(struct timer_base *base) +@@ -1709,6 +1706,7 @@ static inline void __run_timers(struct timer_base *base) if (!time_after_eq(jiffies, base->clk)) return; @@ -628,7 +628,7 @@ index 2fcd56aa6092..1c67aab34ff5 100644 raw_spin_lock_irq(&base->lock); /* -@@ -1725,7 +1723,7 @@ static inline void __run_timers(struct timer_base *base) +@@ -1736,7 +1734,7 @@ static inline void __run_timers(struct timer_base *base) expire_timers(base, heads + levels); } raw_spin_unlock_irq(&base->lock); @@ -637,7 +637,7 @@ index 2fcd56aa6092..1c67aab34ff5 100644 } /* -@@ -1972,9 +1970,7 @@ static void __init init_timer_cpu(int cpu) +@@ -1983,9 +1981,7 @@ static void __init init_timer_cpu(int cpu) base->cpu = cpu; raw_spin_lock_init(&base->lock); base->clk = jiffies; diff --git a/debian/patches-rt/0272-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch b/debian/patches-rt/0272-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch index 3f2c5fe38..45311289e 100644 --- a/debian/patches-rt/0272-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch +++ b/debian/patches-rt/0272-Revert-futex-Ensure-lock-unlock-symetry-versus-pi_lo.patch @@ -1,12 +1,12 @@ -From 66c7cf6b753c67f143e2c6dc61729be2e1d530e0 Mon Sep 17 00:00:00 2001 -Message-Id: <66c7cf6b753c67f143e2c6dc61729be2e1d530e0.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 238295e1edf9f6aba72d570e8afee2ecec56a1fc Mon Sep 17 00:00:00 2001 +Message-Id: <238295e1edf9f6aba72d570e8afee2ecec56a1fc.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:13 +0200 Subject: [PATCH 272/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 6a773b70cf105b46298ed3b44e77c102ce31d9ec ] diff --git a/debian/patches-rt/0273-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch b/debian/patches-rt/0273-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch index 81bcda154..de4d9f2d1 100644 --- a/debian/patches-rt/0273-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch +++ b/debian/patches-rt/0273-Revert-futex-Fix-bug-on-when-a-requeued-RT-task-time.patch @@ -1,12 +1,12 @@ -From ec21b8604b8cfbf7df298fd12651aee03bbaf287 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ec233e4cdfa4650c3fe7354d1c4bb3e0917a5adc Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:18 +0200 Subject: [PATCH 273/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit f1a170cb3289a48df26cae3c60d77608f7a988bb ] diff --git a/debian/patches-rt/0274-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch b/debian/patches-rt/0274-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch index 3117c0986..eb06ca485 100644 --- a/debian/patches-rt/0274-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch +++ b/debian/patches-rt/0274-Revert-rtmutex-Handle-the-various-new-futex-race-con.patch @@ -1,12 +1,12 @@ -From 52fc3041fc0bb78f7ef6ba817fc1221e201ae18b Mon Sep 17 00:00:00 2001 -Message-Id: <52fc3041fc0bb78f7ef6ba817fc1221e201ae18b.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 874b31bc115070b4ba01c5f28b9625cf48df4b84 Mon Sep 17 00:00:00 2001 +Message-Id: <874b31bc115070b4ba01c5f28b9625cf48df4b84.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:21 +0200 Subject: [PATCH 274/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 9e0265c21af4d6388d47dcd5ce20f76ec3a2e468 ] diff --git a/debian/patches-rt/0275-Revert-futex-workaround-migrate_disable-enable-in-di.patch b/debian/patches-rt/0275-Revert-futex-workaround-migrate_disable-enable-in-di.patch index 054a75f34..3f89abfa7 100644 --- a/debian/patches-rt/0275-Revert-futex-workaround-migrate_disable-enable-in-di.patch +++ b/debian/patches-rt/0275-Revert-futex-workaround-migrate_disable-enable-in-di.patch @@ -1,12 +1,12 @@ -From e10aae6f56724e12b9041d6537c8017feeda4673 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 531431494e1213abbd6a92a48b448fdd3df28433 Mon Sep 17 00:00:00 2001 +Message-Id: <531431494e1213abbd6a92a48b448fdd3df28433.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 17:44:27 +0200 Subject: [PATCH 275/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit a71221d81cc4873891ae44f3aa02df596079b786 ] diff --git a/debian/patches-rt/0276-futex-Make-the-futex_hash_bucket-lock-raw.patch b/debian/patches-rt/0276-futex-Make-the-futex_hash_bucket-lock-raw.patch index b08c74449..a08a6db63 100644 --- a/debian/patches-rt/0276-futex-Make-the-futex_hash_bucket-lock-raw.patch +++ b/debian/patches-rt/0276-futex-Make-the-futex_hash_bucket-lock-raw.patch @@ -1,11 +1,11 @@ -From cc64cc4873a174bf683de80aedfa267684c45f8d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ad8b2825cc455ee16207c3fa6d9ed361b6abb69b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 26 Jun 2019 11:59:44 +0200 Subject: [PATCH 276/329] futex: Make the futex_hash_bucket lock raw -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit f646521aadedab78801c9befe193e2e8a0c99298 ] diff --git a/debian/patches-rt/0277-futex-Delay-deallocation-of-pi_state.patch b/debian/patches-rt/0277-futex-Delay-deallocation-of-pi_state.patch index 0f2493d23..4865ce6bd 100644 --- a/debian/patches-rt/0277-futex-Delay-deallocation-of-pi_state.patch +++ b/debian/patches-rt/0277-futex-Delay-deallocation-of-pi_state.patch @@ -1,11 +1,11 @@ -From 7ea839d3cfee1e926c2f5ca18563b43f291ed7a5 Mon Sep 17 00:00:00 2001 -Message-Id: <7ea839d3cfee1e926c2f5ca18563b43f291ed7a5.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From be64455cbe25f39319588bbcd8a3807a9c3041cd Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Wed, 26 Jun 2019 13:35:36 +0200 Subject: [PATCH 277/329] futex: Delay deallocation of pi_state -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit d7c7cf8cb68b7df17e6e50be1f25f35d83e686c7 ] diff --git a/debian/patches-rt/0278-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch b/debian/patches-rt/0278-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch index 3f83b771b..56c04c1ce 100644 --- a/debian/patches-rt/0278-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch +++ b/debian/patches-rt/0278-mm-zswap-Do-not-disable-preemption-in-zswap_frontswa.patch @@ -1,12 +1,12 @@ -From b9d0bb82934cd695ce548a4cf3c16d095dda7b8d Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 50d889cc089b60e7b0e3074cc4aba0c34edad9e8 Mon Sep 17 00:00:00 2001 +Message-Id: <50d889cc089b60e7b0e3074cc4aba0c34edad9e8.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: "Luis Claudio R. Goncalves" Date: Tue, 25 Jun 2019 11:28:04 -0300 Subject: [PATCH 278/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 4e4cf4be79635e67144632d9135286381acbc95a ] diff --git a/debian/patches-rt/0279-revert-aio.patch b/debian/patches-rt/0279-revert-aio.patch index fa85b0ea3..3fd23267c 100644 --- a/debian/patches-rt/0279-revert-aio.patch +++ b/debian/patches-rt/0279-revert-aio.patch @@ -1,11 +1,11 @@ -From 6574af8b225694bd4a227fa89704d70fafee693d Mon Sep 17 00:00:00 2001 -Message-Id: <6574af8b225694bd4a227fa89704d70fafee693d.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ecfc93f81c64db7dd6a1afc3ca455826dc3da90c Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:53 -0400 Subject: [PATCH 279/329] revert-aio -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz revert: fs/aio: simple simple work diff --git a/debian/patches-rt/0280-fs-aio-simple-simple-work.patch b/debian/patches-rt/0280-fs-aio-simple-simple-work.patch index 8da023ee3..ec83cc412 100644 --- a/debian/patches-rt/0280-fs-aio-simple-simple-work.patch +++ b/debian/patches-rt/0280-fs-aio-simple-simple-work.patch @@ -1,11 +1,11 @@ -From 191295eec9afa0d2c09df90b7950c341e377d05f Mon Sep 17 00:00:00 2001 -Message-Id: <191295eec9afa0d2c09df90b7950c341e377d05f.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From cfe97d98afc97b52fdf8b31f2533822c43cb7d99 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Feb 2015 18:49:10 +0100 Subject: [PATCH 280/329] fs/aio: simple simple work -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 1a142116f6435ef070ecebb66d2d599507c10601 ] diff --git a/debian/patches-rt/0281-revert-thermal.patch b/debian/patches-rt/0281-revert-thermal.patch index c90754ce3..3f678bcb9 100644 --- a/debian/patches-rt/0281-revert-thermal.patch +++ b/debian/patches-rt/0281-revert-thermal.patch @@ -1,11 +1,11 @@ -From 5fca7a6ba8c06862d345cb2ac9ef002a94430652 Mon Sep 17 00:00:00 2001 -Message-Id: <5fca7a6ba8c06862d345cb2ac9ef002a94430652.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 827e824dc6fb2dc5565ce71889e5b536bf0bcef5 Mon Sep 17 00:00:00 2001 +Message-Id: <827e824dc6fb2dc5565ce71889e5b536bf0bcef5.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:53 -0400 Subject: [PATCH 281/329] revert-thermal -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Revert: thermal: Defer thermal wakups to threads diff --git a/debian/patches-rt/0282-thermal-Defer-thermal-wakups-to-threads.patch b/debian/patches-rt/0282-thermal-Defer-thermal-wakups-to-threads.patch index fca8c2f3e..56871fc0a 100644 --- a/debian/patches-rt/0282-thermal-Defer-thermal-wakups-to-threads.patch +++ b/debian/patches-rt/0282-thermal-Defer-thermal-wakups-to-threads.patch @@ -1,11 +1,11 @@ -From 25341b5143a591d82378be71ba1be67a69ea9731 Mon Sep 17 00:00:00 2001 -Message-Id: <25341b5143a591d82378be71ba1be67a69ea9731.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 4d078a228363c14bf55bf35f93a8a792e934e2d5 Mon Sep 17 00:00:00 2001 +Message-Id: <4d078a228363c14bf55bf35f93a8a792e934e2d5.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Daniel Wagner Date: Tue, 17 Feb 2015 09:37:44 +0100 Subject: [PATCH 282/329] thermal: Defer thermal wakups to threads -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit ad2408dc248fe58536eef5b2b5734d8f9d3a280b ] diff --git a/debian/patches-rt/0283-revert-block.patch b/debian/patches-rt/0283-revert-block.patch index 823539b48..c8c381bc2 100644 --- a/debian/patches-rt/0283-revert-block.patch +++ b/debian/patches-rt/0283-revert-block.patch @@ -1,11 +1,11 @@ -From ab81e84c1791a02eb1efe5eafb7dda84a67bb17f Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 8f06e654ed2fb162be1139cc81a0ad83d93d5e4c Mon Sep 17 00:00:00 2001 +Message-Id: <8f06e654ed2fb162be1139cc81a0ad83d93d5e4c.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Fri, 20 Sep 2019 17:50:54 -0400 Subject: [PATCH 283/329] revert-block -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Revert swork version of: block: blk-mq: move blk_queue_usage_counter_release() into process context diff --git a/debian/patches-rt/0284-block-blk-mq-move-blk_queue_usage_counter_release-in.patch b/debian/patches-rt/0284-block-blk-mq-move-blk_queue_usage_counter_release-in.patch index 92ada59b2..2768e92fd 100644 --- a/debian/patches-rt/0284-block-blk-mq-move-blk_queue_usage_counter_release-in.patch +++ b/debian/patches-rt/0284-block-blk-mq-move-blk_queue_usage_counter_release-in.patch @@ -1,12 +1,12 @@ -From f3341ec1d01c68f154e6804208950561843d5345 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b0fdee1cb6e573830e4d6b87aa23beaa4e011be6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Mar 2018 13:49:16 +0100 Subject: [PATCH 284/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 61c928ecf4fe200bda9b49a0813b5ba0f43995b5 ] diff --git a/debian/patches-rt/0285-workqueue-rework.patch b/debian/patches-rt/0285-workqueue-rework.patch index c11aa71c4..f02b7ef9a 100644 --- a/debian/patches-rt/0285-workqueue-rework.patch +++ b/debian/patches-rt/0285-workqueue-rework.patch @@ -1,11 +1,11 @@ -From 415fbb6671284badb2bdd179a9dc07264c96ab79 Mon Sep 17 00:00:00 2001 -Message-Id: <415fbb6671284badb2bdd179a9dc07264c96ab79.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c299ecfceaecc3c8f2f73a87329f827d35bd675d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 29 May 2019 18:52:27 +0200 Subject: [PATCH 285/329] workqueue: rework -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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 064bdf98544b..7c064c6aff55 100644 +index 7b173ca08e22..2180c6388eb9 100644 --- a/init/main.c +++ b/init/main.c -@@ -1131,7 +1131,6 @@ static noinline void __init kernel_init_freeable(void) +@@ -1130,7 +1130,6 @@ static noinline void __init kernel_init_freeable(void) smp_prepare_cpus(setup_max_cpus); workqueue_init(); @@ -356,10 +356,10 @@ index 9db017761a1f..5641b55783a6 100644 /** * kthread_associate_blkcg - associate blkcg to current kthread diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 5bfe4eab5b0a..083e8f55c220 100644 +index 9337303a9f43..c9a83db14cde 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -3607,6 +3607,7 @@ static inline void sched_submit_work(struct task_struct *tsk) +@@ -3609,6 +3609,7 @@ static inline void sched_submit_work(struct task_struct *tsk) { if (!tsk->state) return; diff --git a/debian/patches-rt/0286-i2c-exynos5-Remove-IRQF_ONESHOT.patch b/debian/patches-rt/0286-i2c-exynos5-Remove-IRQF_ONESHOT.patch index c5e998fb4..f3205a25d 100644 --- a/debian/patches-rt/0286-i2c-exynos5-Remove-IRQF_ONESHOT.patch +++ b/debian/patches-rt/0286-i2c-exynos5-Remove-IRQF_ONESHOT.patch @@ -1,11 +1,11 @@ -From 94af52bb2fd890ab8f8a396016ae0c1cfaf69e82 Mon Sep 17 00:00:00 2001 -Message-Id: <94af52bb2fd890ab8f8a396016ae0c1cfaf69e82.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From a5b3c13b8b07661c1ab1ae30a568f361272e4145 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Aug 2019 12:30:12 +0200 Subject: [PATCH 286/329] i2c: exynos5: Remove IRQF_ONESHOT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 4b217df0ab3f7910c96e42091cc7d9f221d05f01 ] diff --git a/debian/patches-rt/0287-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch b/debian/patches-rt/0287-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch index 7cad9c123..92945b1fc 100644 --- a/debian/patches-rt/0287-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch +++ b/debian/patches-rt/0287-i2c-hix5hd2-Remove-IRQF_ONESHOT.patch @@ -1,11 +1,11 @@ -From bf082b8dc94201b06e0c0d2476b1125e630de281 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 5df2eda24988ceace781372da79730c8bbe39808 Mon Sep 17 00:00:00 2001 +Message-Id: <5df2eda24988ceace781372da79730c8bbe39808.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 13 Aug 2019 12:30:37 +0200 Subject: [PATCH 287/329] i2c: hix5hd2: Remove IRQF_ONESHOT -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit e88b481f3f86f11e3243e0808a830e5ca5782a9d ] diff --git a/debian/patches-rt/0288-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch b/debian/patches-rt/0288-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch index 9c243a3e6..21f6d77b5 100644 --- a/debian/patches-rt/0288-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch +++ b/debian/patches-rt/0288-sched-deadline-Ensure-inactive_timer-runs-in-hardirq.patch @@ -1,12 +1,12 @@ -From fd634980c408102eba50d12441ecd6bfd5aed6ff Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b01de7d61b20c86fad00d89bd7a5505f546a5dcc Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Juri Lelli Date: Wed, 31 Jul 2019 12:37:15 +0200 Subject: [PATCH 288/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit ba94e7aed7405c58251b1380e6e7d73aa8284b41 ] diff --git a/debian/patches-rt/0289-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch b/debian/patches-rt/0289-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch index a3b27846a..51a958e2d 100644 --- a/debian/patches-rt/0289-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch +++ b/debian/patches-rt/0289-thermal-x86_pkg_temp-make-pkg_temp_lock-a-raw-spinlo.patch @@ -1,12 +1,12 @@ -From 1c58dfe5587a70a9765f147703ba498b86b5847d Mon Sep 17 00:00:00 2001 -Message-Id: <1c58dfe5587a70a9765f147703ba498b86b5847d.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 220a9e0e5624b02be7ffbb9bd0db1812d5841417 Mon Sep 17 00:00:00 2001 +Message-Id: <220a9e0e5624b02be7ffbb9bd0db1812d5841417.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Clark Williams Date: Mon, 15 Jul 2019 15:25:00 -0500 Subject: [PATCH 289/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 8b03bb3ea7861b70b506199a69b1c8f81fe2d4d0 ] diff --git a/debian/patches-rt/0290-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch b/debian/patches-rt/0290-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch index 5d641bd8d..c0b09c969 100644 --- a/debian/patches-rt/0290-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch +++ b/debian/patches-rt/0290-dma-buf-Use-seqlock_t-instread-disabling-preemption.patch @@ -1,11 +1,11 @@ -From 7be655e87046989c0790c608d35c4b2fcc7611a6 Mon Sep 17 00:00:00 2001 -Message-Id: <7be655e87046989c0790c608d35c4b2fcc7611a6.1594742966.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c29a897e88337a1bdb5c51e37c00006bc25b9fb8 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Aug 2019 16:38:43 +0200 Subject: [PATCH 290/329] dma-buf: Use seqlock_t instread disabling preemption -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 240610aa31094f51f299f06eb8dae8d4cd8d4500 ] diff --git a/debian/patches-rt/0291-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch b/debian/patches-rt/0291-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch index 153ceb0a4..4c287b436 100644 --- a/debian/patches-rt/0291-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch +++ b/debian/patches-rt/0291-KVM-arm-arm64-Let-the-timer-expire-in-hardirq-contex.patch @@ -1,12 +1,12 @@ -From 055f45867c70f621e52595c51a8d955744da33c9 Mon Sep 17 00:00:00 2001 -Message-Id: <055f45867c70f621e52595c51a8d955744da33c9.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From cfc38e9c7db1a17a4542c4b10acbc963225db908 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Thomas Gleixner Date: Tue, 13 Aug 2019 14:29:41 +0200 Subject: [PATCH 291/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 719cc080c914045a6e35787bf4dc3ba91cfd3efb ] diff --git a/debian/patches-rt/0292-x86-preempt-Check-preemption-level-before-looking-at.patch b/debian/patches-rt/0292-x86-preempt-Check-preemption-level-before-looking-at.patch index f250f794d..66c45aa47 100644 --- a/debian/patches-rt/0292-x86-preempt-Check-preemption-level-before-looking-at.patch +++ b/debian/patches-rt/0292-x86-preempt-Check-preemption-level-before-looking-at.patch @@ -1,12 +1,12 @@ -From a9a22d10e0e74af195da95b4f00677180324aa11 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From a3e7fef6c2dbb2a0819df49bf67439311afc5316 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 14 Aug 2019 17:08:58 +0200 Subject: [PATCH 292/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 19fc8557f2323c52b26561651ed4d51fc688a740 ] diff --git a/debian/patches-rt/0293-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch b/debian/patches-rt/0293-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch index 663137f80..4872cb8c4 100644 --- a/debian/patches-rt/0293-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch +++ b/debian/patches-rt/0293-hrtimer-Use-READ_ONCE-to-access-timer-base-in-hrimer.patch @@ -1,12 +1,12 @@ -From 4bc23ad21f1b95dfd44f9b20a26ade533cceae3e Mon Sep 17 00:00:00 2001 -Message-Id: <4bc23ad21f1b95dfd44f9b20a26ade533cceae3e.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 6c5cfa0b2bf6c2aee38e6fe0d3ea198eeda6332f Mon Sep 17 00:00:00 2001 +Message-Id: <6c5cfa0b2bf6c2aee38e6fe0d3ea198eeda6332f.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:07 +0100 Subject: [PATCH 293/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 2c8fdbe7ef0ad06c1a326886c5954e117b5657d6 ] diff --git a/debian/patches-rt/0294-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch b/debian/patches-rt/0294-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch index 83d82ea2a..c0e59e91e 100644 --- a/debian/patches-rt/0294-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch +++ b/debian/patches-rt/0294-hrtimer-Don-t-grab-the-expiry-lock-for-non-soft-hrti.patch @@ -1,12 +1,12 @@ -From 1d51a48b53ef01bf731c8f40ad2b79e3fc5f003a Mon Sep 17 00:00:00 2001 -Message-Id: <1d51a48b53ef01bf731c8f40ad2b79e3fc5f003a.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From bae02b374cefc85b456d4f78b380baf045d8cb44 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:08 +0100 Subject: [PATCH 294/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit fd420354bea2f57c11f3de191dffdeea76531e76 ] diff --git a/debian/patches-rt/0295-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch b/debian/patches-rt/0295-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch index f8c42df71..937da7f3d 100644 --- a/debian/patches-rt/0295-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch +++ b/debian/patches-rt/0295-hrtimer-Prevent-using-hrtimer_grab_expiry_lock-on-mi.patch @@ -1,12 +1,12 @@ -From a0d27480eabfc2a30bc50c6ceae95292283ee355 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From a2596b6ffdfe09b8fe9acdf939d4d52a56c0d8f8 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Julien Grall Date: Wed, 21 Aug 2019 10:24:09 +0100 Subject: [PATCH 295/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit cef1b87f98823af923a386f3f69149acb212d4a1 ] diff --git a/debian/patches-rt/0296-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch b/debian/patches-rt/0296-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch index cc894879b..572447835 100644 --- a/debian/patches-rt/0296-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch +++ b/debian/patches-rt/0296-hrtimer-Add-a-missing-bracket-and-hide-migration_bas.patch @@ -1,12 +1,12 @@ -From fffd19b6c2a4c20d2683b78df76194cb5227b8eb Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 95c322dc50246713694a3901e2e8a23886c68e85 Mon Sep 17 00:00:00 2001 +Message-Id: <95c322dc50246713694a3901e2e8a23886c68e85.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 4 Sep 2019 16:55:27 +0200 Subject: [PATCH 296/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 47b6de0b7f22c28b40275aeede3993d807668c3b ] diff --git a/debian/patches-rt/0297-posix-timers-Unlock-expiry-lock-in-the-early-return.patch b/debian/patches-rt/0297-posix-timers-Unlock-expiry-lock-in-the-early-return.patch index 437f79a27..70e6191a2 100644 --- a/debian/patches-rt/0297-posix-timers-Unlock-expiry-lock-in-the-early-return.patch +++ b/debian/patches-rt/0297-posix-timers-Unlock-expiry-lock-in-the-early-return.patch @@ -1,11 +1,11 @@ -From e280c53167ba340fe0e7384060784ecefd602240 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From cd3d3f85e82d6ce73b27aee9a55556bed8003e2d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 16 Sep 2019 12:33:59 +0200 Subject: [PATCH 297/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 356a2781375ec58521a9bc3f500488745990c242 ] diff --git a/debian/patches-rt/0298-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch b/debian/patches-rt/0298-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch index 07c356c7b..45f073d8d 100644 --- a/debian/patches-rt/0298-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch +++ b/debian/patches-rt/0298-sched-migrate_dis-enable-Use-sleeping_lock-to-annota.patch @@ -1,7 +1,7 @@ -From 95cca5d507581b837f2f755e5e8c5f4037ce5390 Mon Sep 17 00:00:00 2001 -Message-Id: <95cca5d507581b837f2f755e5e8c5f4037ce5390.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 0ad2bb6569107bdd69298922a9beb905f629637d Mon Sep 17 00:00:00 2001 +Message-Id: <0ad2bb6569107bdd69298922a9beb905f629637d.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Scott Wood Date: Tue, 24 Sep 2019 14:36:41 +0200 Subject: [PATCH 298/329] =?UTF-8?q?sched:=20migrate=5Fdis/enable:=20Use=20?= @@ -9,7 +9,7 @@ Subject: [PATCH 298/329] =?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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 4230dd3824c3e1785504e6f757ce79a4b55651fa ] @@ -42,10 +42,10 @@ index 0d3cf1654318..0fec4bb3d79b 100644 preempt_disable(); preempt_lazy_disable(); diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 083e8f55c220..593aa5c2f394 100644 +index c9a83db14cde..07b70eb3660f 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -7365,7 +7365,10 @@ void migrate_enable(void) +@@ -7367,7 +7367,10 @@ void migrate_enable(void) unpin_current_cpu(); preempt_lazy_enable(); preempt_enable(); diff --git a/debian/patches-rt/0299-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch b/debian/patches-rt/0299-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch index 196ff916e..566735f47 100644 --- a/debian/patches-rt/0299-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch +++ b/debian/patches-rt/0299-sched-__set_cpus_allowed_ptr-Check-cpus_mask-not-cpu.patch @@ -1,12 +1,12 @@ -From d21255321c6af2fa14dc3c940f2da153d911a4f7 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 0635a14374a6d7f32aeca74959baf1f0062b06d9 Mon Sep 17 00:00:00 2001 +Message-Id: <0635a14374a6d7f32aeca74959baf1f0062b06d9.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:32 -0500 Subject: [PATCH 299/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit e5606fb7b042db634ed62b4dd733d62e050e468f ] @@ -25,7 +25,7 @@ Signed-off-by: Steven Rostedt (VMware) 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 593aa5c2f394..c2aebfab8556 100644 +index 07b70eb3660f..357bf627799f 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -1157,7 +1157,7 @@ static int __set_cpus_allowed_ptr(struct task_struct *p, diff --git a/debian/patches-rt/0300-sched-Remove-dead-__migrate_disabled-check.patch b/debian/patches-rt/0300-sched-Remove-dead-__migrate_disabled-check.patch index 67c3c3225..b16915286 100644 --- a/debian/patches-rt/0300-sched-Remove-dead-__migrate_disabled-check.patch +++ b/debian/patches-rt/0300-sched-Remove-dead-__migrate_disabled-check.patch @@ -1,11 +1,11 @@ -From fbec2a140d52ca45636c2d61324f2062efe02530 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 80c7dc1ac20f64951c4b5590b65b0db2a5b20880 Mon Sep 17 00:00:00 2001 +Message-Id: <80c7dc1ac20f64951c4b5590b65b0db2a5b20880.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:33 -0500 Subject: [PATCH 300/329] sched: Remove dead __migrate_disabled() check -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 14d9272d534ea91262e15db99443fc5995c7c016 ] @@ -20,7 +20,7 @@ Signed-off-by: Steven Rostedt (VMware) 1 file changed, 7 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index c2aebfab8556..03b3ff43d39f 100644 +index 357bf627799f..7109b23c7a60 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -1182,13 +1182,6 @@ static int __set_cpus_allowed_ptr(struct task_struct *p, diff --git a/debian/patches-rt/0301-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch b/debian/patches-rt/0301-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch index 1e6ac5a36..f4a6ce140 100644 --- a/debian/patches-rt/0301-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch +++ b/debian/patches-rt/0301-sched-migrate-disable-Protect-cpus_ptr-with-lock.patch @@ -1,11 +1,11 @@ -From f5bd71472372edd09e275283f6c5bc42b66514eb Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ae143b3d8ef01a023b736cd5c959b3c6ec78c362 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 27 Jul 2019 00:56:34 -0500 Subject: [PATCH 301/329] sched: migrate disable: Protect cpus_ptr with lock -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 27ee52a891ed2c7e2e2c8332ccae0de7c2674b09 ] @@ -20,10 +20,10 @@ Signed-off-by: Steven Rostedt (VMware) 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 03b3ff43d39f..c03ad7ae5f96 100644 +index 7109b23c7a60..0d64d14f0b39 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -7243,9 +7243,8 @@ migrate_disable_update_cpus_allowed(struct task_struct *p) +@@ -7245,9 +7245,8 @@ migrate_disable_update_cpus_allowed(struct task_struct *p) struct rq *rq; struct rq_flags rf; @@ -34,7 +34,7 @@ index 03b3ff43d39f..c03ad7ae5f96 100644 update_nr_migratory(p, -1); p->nr_cpus_allowed = 1; task_rq_unlock(rq, p, &rf); -@@ -7257,9 +7256,8 @@ migrate_enable_update_cpus_allowed(struct task_struct *p) +@@ -7259,9 +7258,8 @@ migrate_enable_update_cpus_allowed(struct task_struct *p) struct rq *rq; struct rq_flags rf; diff --git a/debian/patches-rt/0302-lib-smp_processor_id-Don-t-use-cpumask_equal.patch b/debian/patches-rt/0302-lib-smp_processor_id-Don-t-use-cpumask_equal.patch index b0aff346f..4f7cdac76 100644 --- a/debian/patches-rt/0302-lib-smp_processor_id-Don-t-use-cpumask_equal.patch +++ b/debian/patches-rt/0302-lib-smp_processor_id-Don-t-use-cpumask_equal.patch @@ -1,11 +1,11 @@ -From 3df3c9149f18b2e3acaee0522e78d1c101a936ca Mon Sep 17 00:00:00 2001 -Message-Id: <3df3c9149f18b2e3acaee0522e78d1c101a936ca.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c9bb6d07b4c6dd5039684c55f1d7d0689e754e88 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Waiman Long Date: Thu, 3 Oct 2019 16:36:08 -0400 Subject: [PATCH 302/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 659252061477862f45b79e1de169e6030f5c8918 ] diff --git a/debian/patches-rt/0303-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch b/debian/patches-rt/0303-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch index 6bb60faa7..71dc74199 100644 --- a/debian/patches-rt/0303-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch +++ b/debian/patches-rt/0303-futex-Make-the-futex_hash_bucket-spinlock_t-again-an.patch @@ -1,12 +1,12 @@ -From 0ded75d93b687fbf9d416919fb391965fa7dc814 Mon Sep 17 00:00:00 2001 -Message-Id: <0ded75d93b687fbf9d416919fb391965fa7dc814.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 94d05b44a1358e4c36ebeb94f70e92c96fee93c2 Mon Sep 17 00:00:00 2001 +Message-Id: <94d05b44a1358e4c36ebeb94f70e92c96fee93c2.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Mon, 7 Oct 2019 16:45:18 +0200 Subject: [PATCH 303/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 954ad80c23edfe71f4e8ce70b961eac884320c3a ] diff --git a/debian/patches-rt/0304-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch b/debian/patches-rt/0304-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch index fe30dfe68..cd56fbdf3 100644 --- a/debian/patches-rt/0304-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch +++ b/debian/patches-rt/0304-locking-rtmutex-Clean-pi_blocked_on-in-the-error-cas.patch @@ -1,12 +1,12 @@ -From 975fb6888fb8ff9a169eccce767acffd9e5d6256 Mon Sep 17 00:00:00 2001 -Message-Id: <975fb6888fb8ff9a169eccce767acffd9e5d6256.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b25448c96680e78daea8fa6f29c51dde80b7652b Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Peter Zijlstra Date: Mon, 30 Sep 2019 18:15:44 +0200 Subject: [PATCH 304/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 0be4ea6e3ce693101be0fbd55a0cc7ce238ab2eb ] diff --git a/debian/patches-rt/0305-lib-ubsan-Don-t-seralize-UBSAN-report.patch b/debian/patches-rt/0305-lib-ubsan-Don-t-seralize-UBSAN-report.patch index 687ae7f87..6722d4b22 100644 --- a/debian/patches-rt/0305-lib-ubsan-Don-t-seralize-UBSAN-report.patch +++ b/debian/patches-rt/0305-lib-ubsan-Don-t-seralize-UBSAN-report.patch @@ -1,11 +1,11 @@ -From dcf4e30144145c806db929db0179208bf981abd4 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From c1ae4b6599bc5dbcae80dc79e16f5e409be3d901 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Julien Grall Date: Fri, 20 Sep 2019 11:08:35 +0100 Subject: [PATCH 305/329] lib/ubsan: Don't seralize UBSAN report -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 4702c28ac777b27acb499cbd5e8e787ce1a7d82d ] diff --git a/debian/patches-rt/0306-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch b/debian/patches-rt/0306-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch index 317aa4bd0..8084b0ad1 100644 --- a/debian/patches-rt/0306-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch +++ b/debian/patches-rt/0306-kmemleak-Change-the-lock-of-kmemleak_object-to-raw_s.patch @@ -1,12 +1,12 @@ -From fbe1e13bc339273bf35100490001df4ac3c6df25 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 4c11da463b4e3bbc6b6cfffefdae8e856de7175e Mon Sep 17 00:00:00 2001 +Message-Id: <4c11da463b4e3bbc6b6cfffefdae8e856de7175e.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Liu Haitao Date: Fri, 27 Sep 2019 16:22:30 +0800 Subject: [PATCH 306/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 217847f57119b5fdd377bfa3d344613ddb98d9fc ] diff --git a/debian/patches-rt/0307-sched-migrate_enable-Use-select_fallback_rq.patch b/debian/patches-rt/0307-sched-migrate_enable-Use-select_fallback_rq.patch index eafc83bcf..a70632d17 100644 --- a/debian/patches-rt/0307-sched-migrate_enable-Use-select_fallback_rq.patch +++ b/debian/patches-rt/0307-sched-migrate_enable-Use-select_fallback_rq.patch @@ -1,11 +1,11 @@ -From 3fe7b5d0fa57658cdb38f471f350a94cdfe2daeb Mon Sep 17 00:00:00 2001 -Message-Id: <3fe7b5d0fa57658cdb38f471f350a94cdfe2daeb.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 982b58008d818a65ebb1aec041f55448f0a25074 Mon Sep 17 00:00:00 2001 +Message-Id: <982b58008d818a65ebb1aec041f55448f0a25074.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:12 -0500 Subject: [PATCH 307/329] sched: migrate_enable: Use select_fallback_rq() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit adfa969d4cfcc995a9d866020124e50f1827d2d1 ] @@ -22,10 +22,10 @@ Signed-off-by: Steven Rostedt (VMware) 1 file changed, 10 insertions(+), 15 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index c03ad7ae5f96..366a0cb64774 100644 +index 0d64d14f0b39..c5685d5d9526 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -7328,6 +7328,7 @@ void migrate_enable(void) +@@ -7330,6 +7330,7 @@ void migrate_enable(void) if (p->migrate_disable_update) { struct rq *rq; struct rq_flags rf; @@ -33,7 +33,7 @@ index c03ad7ae5f96..366a0cb64774 100644 rq = task_rq_lock(p, &rf); update_rq_clock(rq); -@@ -7337,21 +7338,15 @@ void migrate_enable(void) +@@ -7339,21 +7340,15 @@ void migrate_enable(void) p->migrate_disable_update = 0; diff --git a/debian/patches-rt/0308-sched-Lazy-migrate_disable-processing.patch b/debian/patches-rt/0308-sched-Lazy-migrate_disable-processing.patch index a32fab52d..79f23734f 100644 --- a/debian/patches-rt/0308-sched-Lazy-migrate_disable-processing.patch +++ b/debian/patches-rt/0308-sched-Lazy-migrate_disable-processing.patch @@ -1,11 +1,11 @@ -From 6330fae2d363892a27bb557508374c631fcf214b Mon Sep 17 00:00:00 2001 -Message-Id: <6330fae2d363892a27bb557508374c631fcf214b.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ffad6ee3464e615d4a7df13467c6082f5feca3b6 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:13 -0500 Subject: [PATCH 308/329] sched: Lazy migrate_disable processing -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 425c5b38779a860062aa62219dc920d374b13c17 ] @@ -282,7 +282,7 @@ index 0fec4bb3d79b..bf698d84ac2a 100644 /* Interrupts are moved away from the dying cpu, reenable alloc/free */ irq_unlock_sparse(); diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 366a0cb64774..2349e0b4ed68 100644 +index c5685d5d9526..bbde7b29dee2 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -1065,7 +1065,8 @@ static int migration_cpu_stop(void *data) @@ -336,7 +336,7 @@ index 366a0cb64774..2349e0b4ed68 100644 goto out; if (task_running(rq, p) || p->state == TASK_WAKING) { -@@ -3454,6 +3441,8 @@ pick_next_task(struct rq *rq, struct task_struct *prev, struct rq_flags *rf) +@@ -3456,6 +3443,8 @@ pick_next_task(struct rq *rq, struct task_struct *prev, struct rq_flags *rf) BUG(); } @@ -345,7 +345,7 @@ index 366a0cb64774..2349e0b4ed68 100644 /* * __schedule() is the main scheduler function. * -@@ -3524,6 +3513,9 @@ static void __sched notrace __schedule(bool preempt) +@@ -3526,6 +3515,9 @@ static void __sched notrace __schedule(bool preempt) rq_lock(rq, &rf); smp_mb__after_spinlock(); @@ -355,7 +355,7 @@ index 366a0cb64774..2349e0b4ed68 100644 /* Promote REQ to ACT */ rq->clock_update_flags <<= 1; update_rq_clock(rq); -@@ -5776,6 +5768,8 @@ static void migrate_tasks(struct rq *dead_rq, struct rq_flags *rf) +@@ -5778,6 +5770,8 @@ static void migrate_tasks(struct rq *dead_rq, struct rq_flags *rf) BUG_ON(!next); put_prev_task(rq, next); @@ -364,7 +364,7 @@ index 366a0cb64774..2349e0b4ed68 100644 /* * Rules for changing task_struct::cpus_mask are holding * both pi_lock and rq->lock, such that holding either -@@ -7240,14 +7234,9 @@ update_nr_migratory(struct task_struct *p, long delta) +@@ -7242,14 +7236,9 @@ update_nr_migratory(struct task_struct *p, long delta) static inline void migrate_disable_update_cpus_allowed(struct task_struct *p) { @@ -379,7 +379,7 @@ index 366a0cb64774..2349e0b4ed68 100644 } static inline void -@@ -7265,54 +7254,35 @@ migrate_enable_update_cpus_allowed(struct task_struct *p) +@@ -7267,54 +7256,35 @@ migrate_enable_update_cpus_allowed(struct task_struct *p) void migrate_disable(void) { @@ -450,7 +450,7 @@ index 366a0cb64774..2349e0b4ed68 100644 WARN_ON_ONCE(p->migrate_disable <= 0); if (p->migrate_disable > 1) { -@@ -7322,67 +7292,69 @@ void migrate_enable(void) +@@ -7324,67 +7294,69 @@ void migrate_enable(void) preempt_disable(); @@ -560,7 +560,7 @@ index 366a0cb64774..2349e0b4ed68 100644 #endif barrier(); } -@@ -7393,20 +7365,14 @@ void migrate_enable(void) +@@ -7395,20 +7367,14 @@ void migrate_enable(void) #ifdef CONFIG_SCHED_DEBUG struct task_struct *p = current; diff --git a/debian/patches-rt/0309-sched-migrate_enable-Use-stop_one_cpu_nowait.patch b/debian/patches-rt/0309-sched-migrate_enable-Use-stop_one_cpu_nowait.patch index e191ee37c..4681f5e7a 100644 --- a/debian/patches-rt/0309-sched-migrate_enable-Use-stop_one_cpu_nowait.patch +++ b/debian/patches-rt/0309-sched-migrate_enable-Use-stop_one_cpu_nowait.patch @@ -1,11 +1,11 @@ -From 74f441aad80898e8f2b41661b279c4e2502b029e Mon Sep 17 00:00:00 2001 -Message-Id: <74f441aad80898e8f2b41661b279c4e2502b029e.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 3f33033a2b5811104fb7eb031ec18c15b71b6485 Mon Sep 17 00:00:00 2001 +Message-Id: <3f33033a2b5811104fb7eb031ec18c15b71b6485.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Scott Wood Date: Sat, 12 Oct 2019 01:52:14 -0500 Subject: [PATCH 309/329] sched: migrate_enable: Use stop_one_cpu_nowait() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 6b39a1fa8c53cae08dc03afdae193b7d3a78a173 ] @@ -38,7 +38,7 @@ index 6d3635c86dbe..82fc686ddd9e 100644 int stop_one_cpu(unsigned int cpu, cpu_stop_fn_t fn, void *arg); diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 2349e0b4ed68..bfd63e873fdc 100644 +index bbde7b29dee2..10c7412bb012 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -990,6 +990,7 @@ static struct rq *move_queued_task(struct rq *rq, struct rq_flags *rf, @@ -73,7 +73,7 @@ index 2349e0b4ed68..bfd63e873fdc 100644 } rq_unlock(rq, &rf); raw_spin_unlock(&p->pi_lock); -@@ -7315,6 +7321,7 @@ void migrate_enable(void) +@@ -7317,6 +7323,7 @@ void migrate_enable(void) WARN_ON(smp_processor_id() != cpu); if (!is_cpu_allowed(p, cpu)) { struct migration_arg arg = { p }; @@ -81,7 +81,7 @@ index 2349e0b4ed68..bfd63e873fdc 100644 struct rq_flags rf; rq = task_rq_lock(p, &rf); -@@ -7322,15 +7329,11 @@ void migrate_enable(void) +@@ -7324,15 +7331,11 @@ void migrate_enable(void) arg.dest_cpu = select_fallback_rq(cpu, p); task_rq_unlock(rq, p, &rf); diff --git a/debian/patches-rt/0310-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch b/debian/patches-rt/0310-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch index ca011a5dd..ecbec9f1b 100644 --- a/debian/patches-rt/0310-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch +++ b/debian/patches-rt/0310-Revert-ARM-Initialize-split-page-table-locks-for-vec.patch @@ -1,12 +1,12 @@ -From 80e65b14339d324ee5558ecf6b199ef64761ce76 Mon Sep 17 00:00:00 2001 -Message-Id: <80e65b14339d324ee5558ecf6b199ef64761ce76.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 9b3236a5554beebe5de6c21cda4f225b289b8fd1 Mon Sep 17 00:00:00 2001 +Message-Id: <9b3236a5554beebe5de6c21cda4f225b289b8fd1.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 18 Oct 2019 13:04:15 +0200 Subject: [PATCH 310/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 247074c44d8c3e619dfde6404a52295d8d671d38 ] diff --git a/debian/patches-rt/0311-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch b/debian/patches-rt/0311-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch index 296d7bbf2..44ea563bd 100644 --- a/debian/patches-rt/0311-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch +++ b/debian/patches-rt/0311-locking-Make-spinlock_t-and-rwlock_t-a-RCU-section-o.patch @@ -1,12 +1,12 @@ -From 25675e02a214f24d8189c701d68bd1ad1c544627 Mon Sep 17 00:00:00 2001 -Message-Id: <25675e02a214f24d8189c701d68bd1ad1c544627.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b47230da29518bb738c585cc695cea8aaf2c7d9d Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 19 Nov 2019 09:25:04 +0100 Subject: [PATCH 311/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 84440022a0e1c8c936d61f8f97593674a295d409 ] diff --git a/debian/patches-rt/0312-sched-core-migrate_enable-must-access-takedown_cpu_t.patch b/debian/patches-rt/0312-sched-core-migrate_enable-must-access-takedown_cpu_t.patch index 60333d432..cfdfb6c89 100644 --- a/debian/patches-rt/0312-sched-core-migrate_enable-must-access-takedown_cpu_t.patch +++ b/debian/patches-rt/0312-sched-core-migrate_enable-must-access-takedown_cpu_t.patch @@ -1,12 +1,12 @@ -From 7fcb4239e885a460ec9192646fca21fc64abf882 Mon Sep 17 00:00:00 2001 -Message-Id: <7fcb4239e885a460ec9192646fca21fc64abf882.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 534b0ff2eae518304d125c3f0076f11807576eec Mon Sep 17 00:00:00 2001 +Message-Id: <534b0ff2eae518304d125c3f0076f11807576eec.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 29 Nov 2019 17:24:55 +0100 Subject: [PATCH 312/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit a61d1977f692e46bad99a100f264981ba08cb4bd ] @@ -38,10 +38,10 @@ index bf698d84ac2a..0651576f9974 100644 static int takedown_cpu(unsigned int cpu) { diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index bfd63e873fdc..8f0870474a82 100644 +index 10c7412bb012..2509cb37531d 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -7307,9 +7307,11 @@ void migrate_enable(void) +@@ -7309,9 +7309,11 @@ void migrate_enable(void) p->migrate_disable = 0; rq->nr_pinned--; diff --git a/debian/patches-rt/0313-lib-smp_processor_id-Adjust-check_preemption_disable.patch b/debian/patches-rt/0313-lib-smp_processor_id-Adjust-check_preemption_disable.patch index 61bb99c7a..5ef17848e 100644 --- a/debian/patches-rt/0313-lib-smp_processor_id-Adjust-check_preemption_disable.patch +++ b/debian/patches-rt/0313-lib-smp_processor_id-Adjust-check_preemption_disable.patch @@ -1,12 +1,12 @@ -From 97da0132d57541883b7539c120ac03d114bf1fb3 Mon Sep 17 00:00:00 2001 -Message-Id: <97da0132d57541883b7539c120ac03d114bf1fb3.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 828eac8d8bfdf4a596da67680c29e5477b6557b5 Mon Sep 17 00:00:00 2001 +Message-Id: <828eac8d8bfdf4a596da67680c29e5477b6557b5.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Daniel Wagner Date: Mon, 16 Dec 2019 16:15:57 +0100 Subject: [PATCH 313/329] lib/smp_processor_id: Adjust check_preemption_disabled() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit af3c1c5fdf177870fb5e6e16b24e374696ab28f5 ] diff --git a/debian/patches-rt/0314-sched-migrate_enable-Busy-loop-until-the-migration-r.patch b/debian/patches-rt/0314-sched-migrate_enable-Busy-loop-until-the-migration-r.patch index 9e2f7f84d..99a4859ec 100644 --- a/debian/patches-rt/0314-sched-migrate_enable-Busy-loop-until-the-migration-r.patch +++ b/debian/patches-rt/0314-sched-migrate_enable-Busy-loop-until-the-migration-r.patch @@ -1,12 +1,12 @@ -From 18a4d5ba2aee960585e70cbbb404d7607da4a434 Mon Sep 17 00:00:00 2001 -Message-Id: <18a4d5ba2aee960585e70cbbb404d7607da4a434.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From e5b5609c5e20caa3855d7d984bbde3981cb40280 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 12 Dec 2019 10:53:59 +0100 Subject: [PATCH 314/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 140d7f54a5fff02898d2ca9802b39548bf7455f1 ] @@ -31,10 +31,10 @@ Signed-off-by: Steven Rostedt (VMware) 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 8f0870474a82..fee3b5427f8b 100644 +index 2509cb37531d..ab34c573b79c 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -7322,7 +7322,7 @@ void migrate_enable(void) +@@ -7324,7 +7324,7 @@ void migrate_enable(void) WARN_ON(smp_processor_id() != cpu); if (!is_cpu_allowed(p, cpu)) { @@ -43,7 +43,7 @@ index 8f0870474a82..fee3b5427f8b 100644 struct cpu_stop_work work; struct rq_flags rf; -@@ -7335,7 +7335,10 @@ void migrate_enable(void) +@@ -7337,7 +7337,10 @@ void migrate_enable(void) &arg, &work); tlb_migrate_finish(p->mm); __schedule(true); diff --git a/debian/patches-rt/0315-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch b/debian/patches-rt/0315-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch index 710ec7731..f64766d5f 100644 --- a/debian/patches-rt/0315-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch +++ b/debian/patches-rt/0315-userfaultfd-Use-a-seqlock-instead-of-seqcount.patch @@ -1,11 +1,11 @@ -From a60366ea1aea5d5f878e8a8bed7b5d2049133e0c Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 7ad42fb21af7d2c868e03da21a2843444fcde799 Mon Sep 17 00:00:00 2001 +Message-Id: <7ad42fb21af7d2c868e03da21a2843444fcde799.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Wed, 18 Dec 2019 12:25:09 +0100 Subject: [PATCH 315/329] userfaultfd: Use a seqlock instead of seqcount -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit dc952a564d02997330654be9628bbe97ba2a05d3 ] diff --git a/debian/patches-rt/0316-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch b/debian/patches-rt/0316-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch index da4f800e8..2dfa37f85 100644 --- a/debian/patches-rt/0316-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch +++ b/debian/patches-rt/0316-sched-migrate_enable-Use-per-cpu-cpu_stop_work.patch @@ -1,11 +1,11 @@ -From 0b0d315243f08fd0410bbec37ac1b8a0cd986912 Mon Sep 17 00:00:00 2001 -Message-Id: <0b0d315243f08fd0410bbec37ac1b8a0cd986912.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 949f595834ceeed4fca1778592017a0e1257ad98 Mon Sep 17 00:00:00 2001 +Message-Id: <949f595834ceeed4fca1778592017a0e1257ad98.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 24 Jan 2020 06:11:46 -0500 Subject: [PATCH 316/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 2dcd94b443c5dcbc20281666321b7f025f9cc85c ] @@ -33,10 +33,10 @@ Signed-off-by: Steven Rostedt (VMware) 1 file changed, 14 insertions(+), 8 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index fee3b5427f8b..859e141cc2a7 100644 +index ab34c573b79c..098e88f7a216 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -7284,6 +7284,9 @@ static void migrate_disabled_sched(struct task_struct *p) +@@ -7286,6 +7286,9 @@ static void migrate_disabled_sched(struct task_struct *p) p->migrate_disable_scheduled = 1; } @@ -46,7 +46,7 @@ index fee3b5427f8b..859e141cc2a7 100644 void migrate_enable(void) { struct task_struct *p = current; -@@ -7322,23 +7325,26 @@ void migrate_enable(void) +@@ -7324,23 +7327,26 @@ void migrate_enable(void) WARN_ON(smp_processor_id() != cpu); if (!is_cpu_allowed(p, cpu)) { diff --git a/debian/patches-rt/0317-sched-migrate_enable-Remove-__schedule-call.patch b/debian/patches-rt/0317-sched-migrate_enable-Remove-__schedule-call.patch index 3c5b59273..2bb03405e 100644 --- a/debian/patches-rt/0317-sched-migrate_enable-Remove-__schedule-call.patch +++ b/debian/patches-rt/0317-sched-migrate_enable-Remove-__schedule-call.patch @@ -1,11 +1,11 @@ -From 176485e6e9cf1d4ede4ca5bdf09584a1398dc2e1 Mon Sep 17 00:00:00 2001 -Message-Id: <176485e6e9cf1d4ede4ca5bdf09584a1398dc2e1.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 14901df46a327f7b019ebd9897e5adabf6e08fff Mon Sep 17 00:00:00 2001 +Message-Id: <14901df46a327f7b019ebd9897e5adabf6e08fff.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Scott Wood Date: Fri, 24 Jan 2020 06:11:47 -0500 Subject: [PATCH 317/329] sched: migrate_enable: Remove __schedule() call -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit b8162e61e9a33bd1de6452eb838fbf50a93ddd9a ] @@ -28,10 +28,10 @@ Signed-off-by: Steven Rostedt (VMware) 1 file changed, 1 deletion(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c -index 859e141cc2a7..f161ad9365b5 100644 +index 098e88f7a216..0fa94ebdce85 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c -@@ -7344,7 +7344,6 @@ void migrate_enable(void) +@@ -7346,7 +7346,6 @@ void migrate_enable(void) stop_one_cpu_nowait(task_cpu(p), migration_cpu_stop, arg, work); tlb_migrate_finish(p->mm); diff --git a/debian/patches-rt/0318-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch b/debian/patches-rt/0318-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch index 6c3f33523..25ffe16f4 100644 --- a/debian/patches-rt/0318-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch +++ b/debian/patches-rt/0318-mm-memcontrol-Move-misplaced-local_unlock_irqrestore.patch @@ -1,12 +1,12 @@ -From 1926409737d11d6e33791301a0b7e30ff77b9d37 Mon Sep 17 00:00:00 2001 -Message-Id: <1926409737d11d6e33791301a0b7e30ff77b9d37.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From eda7bf1eb4235f95f7b9a7c6f1b16ce0c2aea8cc Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Matt Fleming Date: Sun, 26 Jan 2020 21:19:45 +0000 Subject: [PATCH 318/329] mm/memcontrol: Move misplaced local_unlock_irqrestore() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 071a1d6a6e14d0dec240a8c67b425140d7f92f6a ] @@ -25,7 +25,7 @@ Signed-off-by: Sebastian Andrzej Siewior 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/memcontrol.c b/mm/memcontrol.c -index 4156a4e766fb..d059e2a99441 100644 +index a54cfafba8ad..7b506d178aa0 100644 --- a/mm/memcontrol.c +++ b/mm/memcontrol.c @@ -6538,10 +6538,10 @@ void mem_cgroup_swapout(struct page *page, swp_entry_t entry) diff --git a/debian/patches-rt/0319-locallock-Include-header-for-the-current-macro.patch b/debian/patches-rt/0319-locallock-Include-header-for-the-current-macro.patch index ad582cd4e..2c417b236 100644 --- a/debian/patches-rt/0319-locallock-Include-header-for-the-current-macro.patch +++ b/debian/patches-rt/0319-locallock-Include-header-for-the-current-macro.patch @@ -1,11 +1,11 @@ -From 02b6495d76a106ea7570038b44d1335bc5e4c052 Mon Sep 17 00:00:00 2001 -Message-Id: <02b6495d76a106ea7570038b44d1335bc5e4c052.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 0c141dbe4d90b21c4b7d25f14f300ad5a4e2f2c3 Mon Sep 17 00:00:00 2001 +Message-Id: <0c141dbe4d90b21c4b7d25f14f300ad5a4e2f2c3.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Tue, 4 Feb 2020 13:29:50 +0100 Subject: [PATCH 319/329] locallock: Include header for the `current' macro -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit e693075a5fd852043fa8d2b0467e078d9e5cb782 ] diff --git a/debian/patches-rt/0320-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch b/debian/patches-rt/0320-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch index 87ec4f062..73cfc79fd 100644 --- a/debian/patches-rt/0320-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch +++ b/debian/patches-rt/0320-drm-vmwgfx-Drop-preempt_disable-in-vmw_fifo_ping_hos.patch @@ -1,12 +1,12 @@ -From b1c465b150f9a4b0580ccab1679788b31affb601 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 8005272375459065fb1c2210b7c638d2efca9be6 Mon Sep 17 00:00:00 2001 +Message-Id: <8005272375459065fb1c2210b7c638d2efca9be6.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2020 18:57:11 +0100 Subject: [PATCH 320/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit b901491e7b9b7a676818d84e482b69be72fc142f ] diff --git a/debian/patches-rt/0321-tracing-make-preempt_lazy-and-migrate_disable-counte.patch b/debian/patches-rt/0321-tracing-make-preempt_lazy-and-migrate_disable-counte.patch index 5152b953e..4be82e037 100644 --- a/debian/patches-rt/0321-tracing-make-preempt_lazy-and-migrate_disable-counte.patch +++ b/debian/patches-rt/0321-tracing-make-preempt_lazy-and-migrate_disable-counte.patch @@ -1,12 +1,12 @@ -From 5d7e2f8aa80e5ea2ac44e85121a1c7e0d6d962ee Mon Sep 17 00:00:00 2001 -Message-Id: <5d7e2f8aa80e5ea2ac44e85121a1c7e0d6d962ee.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 72f14300c084d95060cc958277f83f2f15f88de3 Mon Sep 17 00:00:00 2001 +Message-Id: <72f14300c084d95060cc958277f83f2f15f88de3.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Fri, 21 Feb 2020 18:15:15 +0100 Subject: [PATCH 321/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit dd430bf5ecb40f9a89679c85868826475d71de54 ] diff --git a/debian/patches-rt/0322-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch b/debian/patches-rt/0322-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch index 0a5509f57..b34fcb39c 100644 --- a/debian/patches-rt/0322-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch +++ b/debian/patches-rt/0322-lib-ubsan-Remove-flags-parameter-from-calls-to-ubsan.patch @@ -1,12 +1,12 @@ -From d8c03d329cd69a71d0969580b01dc12368e4b2e4 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ac710d63435b035c7ba9f2a384ccc67a86f8531e Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Tiejun Chen Date: Mon, 30 Mar 2020 18:45:23 -0400 Subject: [PATCH 322/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Fails to build with CONFIG_UBSAN=y diff --git a/debian/patches-rt/0323-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch b/debian/patches-rt/0323-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch index 002c75dcf..dca5ac602 100644 --- a/debian/patches-rt/0323-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch +++ b/debian/patches-rt/0323-irq_work-Fix-checking-of-IRQ_WORK_LAZY-flag-set-on-n.patch @@ -1,12 +1,12 @@ -From a4e9d54ffdf4911e94d6f4fa6885f2d8ef61da82 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From fdc910588fec4961eec90c82c6278bf4ff2aba4a Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: "Steven Rostedt (VMware)" Date: Sun, 22 Mar 2020 00:00:28 +0100 Subject: [PATCH 323/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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/0324-tasklet-Address-a-race-resulting-in-double-enqueue.patch b/debian/patches-rt/0324-tasklet-Address-a-race-resulting-in-double-enqueue.patch index c32b4c6ca..72165918c 100644 --- a/debian/patches-rt/0324-tasklet-Address-a-race-resulting-in-double-enqueue.patch +++ b/debian/patches-rt/0324-tasklet-Address-a-race-resulting-in-double-enqueue.patch @@ -1,11 +1,11 @@ -From 591b7e192d87ceb2e8a89aedff2aeb5a9091f63e Mon Sep 17 00:00:00 2001 -Message-Id: <591b7e192d87ceb2e8a89aedff2aeb5a9091f63e.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 601fd52f2bc463a20024b3c51bde9aa111815a2f Mon Sep 17 00:00:00 2001 +Message-Id: <601fd52f2bc463a20024b3c51bde9aa111815a2f.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Zhang Xiao Date: Tue, 17 Mar 2020 12:47:43 +0100 Subject: [PATCH 324/329] tasklet: Address a race resulting in double-enqueue -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz The kernel bugzilla has the following race condition reported: diff --git a/debian/patches-rt/0325-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch b/debian/patches-rt/0325-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch index e0652f723..49575e13a 100644 --- a/debian/patches-rt/0325-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch +++ b/debian/patches-rt/0325-hrtimer-fix-logic-for-when-grabbing-softirq_expiry_l.patch @@ -1,12 +1,12 @@ -From b3fffb921d90cab941c78afed33ef847ee4b1553 Mon Sep 17 00:00:00 2001 -Message-Id: -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From 44cbc6f537c24d27d6e1b7544ac5138fa6707e1c Mon Sep 17 00:00:00 2001 +Message-Id: <44cbc6f537c24d27d6e1b7544ac5138fa6707e1c.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Rasmus Villemoes Date: Tue, 28 Apr 2020 16:40:26 +0200 Subject: [PATCH 325/329] 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.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz Commit diff --git a/debian/patches-rt/0326-fs-dcache-Include-swait.h-header.patch b/debian/patches-rt/0326-fs-dcache-Include-swait.h-header.patch index f5c8b91f9..1abbc7169 100644 --- a/debian/patches-rt/0326-fs-dcache-Include-swait.h-header.patch +++ b/debian/patches-rt/0326-fs-dcache-Include-swait.h-header.patch @@ -1,11 +1,11 @@ -From 4b0033a519e40f691f601265914225ee885f76ca Mon Sep 17 00:00:00 2001 -Message-Id: <4b0033a519e40f691f601265914225ee885f76ca.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From ae11303b32f822790ea5838254b2231882515f06 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Sebastian Andrzej Siewior Date: Thu, 16 Apr 2020 12:42:15 +0200 Subject: [PATCH 326/329] fs/dcache: Include swait.h header -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 279f90ddf53cd6bd3c203fbbf488d642ea2603de ] diff --git a/debian/patches-rt/0327-mm-slub-Always-flush-the-delayed-empty-slubs-in-flus.patch b/debian/patches-rt/0327-mm-slub-Always-flush-the-delayed-empty-slubs-in-flus.patch index e15301b26..ebf4cb1a5 100644 --- a/debian/patches-rt/0327-mm-slub-Always-flush-the-delayed-empty-slubs-in-flus.patch +++ b/debian/patches-rt/0327-mm-slub-Always-flush-the-delayed-empty-slubs-in-flus.patch @@ -1,12 +1,12 @@ -From 292a3677c908c9cea53c8105ae6a6571831d26f0 Mon Sep 17 00:00:00 2001 -Message-Id: <292a3677c908c9cea53c8105ae6a6571831d26f0.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From b83418550e2a28c5378d9067977963137c0c7901 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Kevin Hao Date: Mon, 4 May 2020 11:34:07 +0800 Subject: [PATCH 327/329] mm: slub: Always flush the delayed empty slubs in flush_all() -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz [ Upstream commit 23a2c31b19e99beaf5107071b0f32a596202cdae ] diff --git a/debian/patches-rt/0328-tasklet-Fix-UP-case-for-tasklet-CHAINED-state.patch b/debian/patches-rt/0328-tasklet-Fix-UP-case-for-tasklet-CHAINED-state.patch index 47944c94e..497731b46 100644 --- a/debian/patches-rt/0328-tasklet-Fix-UP-case-for-tasklet-CHAINED-state.patch +++ b/debian/patches-rt/0328-tasklet-Fix-UP-case-for-tasklet-CHAINED-state.patch @@ -1,11 +1,11 @@ -From 5b67a99900fb4d7e4e94029ec496e7f148ad9c74 Mon Sep 17 00:00:00 2001 -Message-Id: <5b67a99900fb4d7e4e94029ec496e7f148ad9c74.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> +From f5e1979b23fc83cc6f9b42871b103613bf3196e3 Mon Sep 17 00:00:00 2001 +Message-Id: +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> From: Tom Zanussi Date: Tue, 9 Jun 2020 11:04:08 -0500 Subject: [PATCH 328/329] tasklet: Fix UP case for tasklet CHAINED state -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.tar.xz +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.tar.xz commit 62d0a2a30cd0 (tasklet: Address a race resulting in double-enqueue) addresses a problem that can result in a tasklet being diff --git a/debian/patches-rt/0329-Linux-4.19.132-rt59-REBASE.patch b/debian/patches-rt/0329-Linux-4.19.132-rt59-REBASE.patch deleted file mode 100644 index 6a334c76a..000000000 --- a/debian/patches-rt/0329-Linux-4.19.132-rt59-REBASE.patch +++ /dev/null @@ -1,24 +0,0 @@ -From 6265ef0553174b6089ea56bc534d3c517b67d4cb Mon Sep 17 00:00:00 2001 -Message-Id: <6265ef0553174b6089ea56bc534d3c517b67d4cb.1594742967.git.zanussi@kernel.org> -In-Reply-To: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -References: <832f7d97d6b989a5b4860dd2dbec58ad6ad5ab81.1594742966.git.zanussi@kernel.org> -From: Tom Zanussi -Date: Tue, 14 Jul 2020 10:31:04 -0500 -Subject: [PATCH 329/329] Linux 4.19.132-rt59 REBASE -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.132-rt59.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..8cdeb45db6e2 100644 ---- a/localversion-rt -+++ b/localversion-rt -@@ -1 +1 @@ ---rt16 -+-rt59 --- -2.17.1 - diff --git a/debian/patches-rt/0329-Linux-4.19.135-rt60-REBASE.patch b/debian/patches-rt/0329-Linux-4.19.135-rt60-REBASE.patch new file mode 100644 index 000000000..222c8fcab --- /dev/null +++ b/debian/patches-rt/0329-Linux-4.19.135-rt60-REBASE.patch @@ -0,0 +1,24 @@ +From 3b8f4a03dd51a7974cc8fae71168fc50965ac3b3 Mon Sep 17 00:00:00 2001 +Message-Id: <3b8f4a03dd51a7974cc8fae71168fc50965ac3b3.1596234184.git.zanussi@kernel.org> +In-Reply-To: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +References: <378ee68279f6a7631221f2670a9298620148690d.1596234183.git.zanussi@kernel.org> +From: Tom Zanussi +Date: Fri, 31 Jul 2020 17:18:15 -0500 +Subject: [PATCH 329/329] Linux 4.19.135-rt60 REBASE +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patches-4.19.135-rt60.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..66fa05e70f29 100644 +--- a/localversion-rt ++++ b/localversion-rt +@@ -1 +1 @@ +--rt16 ++-rt60 +-- +2.17.1 + diff --git a/debian/patches-rt/series b/debian/patches-rt/series index 79a59690d..85c588b37 100644 --- a/debian/patches-rt/series +++ b/debian/patches-rt/series @@ -326,4 +326,4 @@ 0326-fs-dcache-Include-swait.h-header.patch 0327-mm-slub-Always-flush-the-delayed-empty-slubs-in-flus.patch 0328-tasklet-Fix-UP-case-for-tasklet-CHAINED-state.patch -0329-Linux-4.19.132-rt59-REBASE.patch +0329-Linux-4.19.135-rt60-REBASE.patch