update -rt to 4.14.63-rt40

Signed-off-by: Tiejun Chen <tiejunc@vmware.com>

examples/rt-for-vmware.yml

@@ -1,5 +1,5 @@
 kernel:
-  image: linuxkit/kernel:4.14.59-rt
+  image: linuxkit/kernel:4.14.63-rt
   cmdline: "console=tty0"
 init:
   - linuxkit/init:v0.6

kernel/Makefile

@@ -263,14 +263,14 @@ $(eval $(call kernel,4.18.1,4.18.x,$(EXTRA),$(DEBUG)))
 $(eval $(call kernel,4.17.15,4.17.x,$(EXTRA),$(DEBUG)))
 $(eval $(call kernel,4.14.63,4.14.x,$(EXTRA),$(DEBUG)))
 $(eval $(call kernel,4.14.63,4.14.x,,-dbg))
-$(eval $(call kernel,4.14.59,4.14.x,-rt,))
+$(eval $(call kernel,4.14.63,4.14.x,-rt,))
 $(eval $(call kernel,4.9.120,4.9.x,$(EXTRA),$(DEBUG)))
 $(eval $(call kernel,4.4.148,4.4.x,$(EXTRA),$(DEBUG)))
 
 else ifeq ($(ARCH),aarch64)
 $(eval $(call kernel,4.18.1,4.18.x,$(EXTRA),$(DEBUG)))
 $(eval $(call kernel,4.14.63,4.14.x,$(EXTRA),$(DEBUG)))
-$(eval $(call kernel,4.14.59,4.14.x,-rt,))
+$(eval $(call kernel,4.14.63,4.14.x,-rt,))
 
 else ifeq ($(ARCH),s390x)
 $(eval $(call kernel,4.18.1,4.18.x,$(EXTRA),$(DEBUG)))

kernel/patches-4.14.x-rt/0001-rtmutex-Make-rt_mutex_futex_unlock-safe-for-irq-off-.patch

@@ -1,7 +1,7 @@
-From 9d9b5967777fb3b9f3ad66dd4d63967edfc6caa0 Mon Sep 17 00:00:00 2001
+From f32c0ebd27d45b33cf1bdd575a9587a30db705a7 Mon Sep 17 00:00:00 2001
 From: Boqun Feng <boqun.feng@gmail.com>
 Date: Fri, 9 Mar 2018 14:56:28 +0800
-Subject: [PATCH 001/414] rtmutex: Make rt_mutex_futex_unlock() safe for
+Subject: [PATCH 001/413] rtmutex: Make rt_mutex_futex_unlock() safe for
  irq-off callsites
 
 Upstream commit 6b0ef92fee2a3189eba6d6b827b247cb4f6da7e9

kernel/patches-4.14.x-rt/0002-rcu-Suppress-lockdep-false-positive-boost_mtx-compla.patch

@@ -1,7 +1,7 @@
-From 32b98fe0f6614f935a87a50cc5a400bec339aac5 Mon Sep 17 00:00:00 2001
+From 52ab7f8907e4d09a203c9f4c6864456f4dbb74af Mon Sep 17 00:00:00 2001
 From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
 Date: Tue, 19 Sep 2017 15:36:42 -0700
-Subject: [PATCH 002/414] rcu: Suppress lockdep false-positive ->boost_mtx
+Subject: [PATCH 002/413] rcu: Suppress lockdep false-positive ->boost_mtx
  complaints
 
 Upstream commit bcda31a2659497df39d6bedfbdf17498b4f4ac89

kernel/patches-4.14.x-rt/0003-brd-remove-unused-brd_mutex.patch

@@ -1,7 +1,7 @@
-From 98fa7ef5ce9171e243c5ca9cc0a15d4a027d3991 Mon Sep 17 00:00:00 2001
+From 1104c43e61c583b6885fdaed7128e493befd0c5c Mon Sep 17 00:00:00 2001
 From: Mikulas Patocka <mpatocka@redhat.com>
 Date: Fri, 10 Nov 2017 12:29:34 -0500
-Subject: [PATCH 003/414] brd: remove unused brd_mutex
+Subject: [PATCH 003/413] brd: remove unused brd_mutex
 
 Upstream commit 15f7b41f70ddcca3b555bd0fdc7c8da7466b517e
 

kernel/patches-4.14.x-rt/0004-KVM-arm-arm64-Remove-redundant-preemptible-checks.patch

@@ -1,7 +1,7 @@
-From 0004e477787106d2bd6ab82800935f0854d81c39 Mon Sep 17 00:00:00 2001
+From 62c7e1e5244db424f8beff313bbe0e498330e910 Mon Sep 17 00:00:00 2001
 From: Christoffer Dall <christoffer.dall@linaro.org>
 Date: Fri, 8 Sep 2017 07:07:13 -0700
-Subject: [PATCH 004/414] KVM: arm/arm64: Remove redundant preemptible checks
+Subject: [PATCH 004/413] KVM: arm/arm64: Remove redundant preemptible checks
 
 Upstream commit 5a24575032971c5a9a4580417a791c427ebdb8e5
 

kernel/patches-4.14.x-rt/0005-iommu-amd-Use-raw-locks-on-atomic-context-paths.patch

@@ -1,7 +1,7 @@
-From 7958cf73713cfa4e11a497f1f955d60e529813d4 Mon Sep 17 00:00:00 2001
+From 1c24fc48416055e67d7995c90db527f1ebb26ba4 Mon Sep 17 00:00:00 2001
 From: Scott Wood <swood@redhat.com>
 Date: Sun, 21 Jan 2018 03:28:54 -0600
-Subject: [PATCH 005/414] iommu/amd: Use raw locks on atomic context paths
+Subject: [PATCH 005/413] iommu/amd: Use raw locks on atomic context paths
 
 Upstream commit 27790398c2aed917828dc3c6f81240d57f1584c9
 

kernel/patches-4.14.x-rt/0006-iommu-amd-Don-t-use-dev_data-in-irte_ga_set_affinity.patch

@@ -1,7 +1,7 @@
-From 510666f0989481bcf0f5d642294c86d8d9b7283a Mon Sep 17 00:00:00 2001
+From f4854290ac0421066bb86324a0a3d9b4019b7d80 Mon Sep 17 00:00:00 2001
 From: Scott Wood <swood@redhat.com>
 Date: Sun, 28 Jan 2018 14:22:19 -0600
-Subject: [PATCH 006/414] iommu/amd: Don't use dev_data in
+Subject: [PATCH 006/413] iommu/amd: Don't use dev_data in
  irte_ga_set_affinity()
 
 Upstream commit 01ee04badefd296eb7a4430497373be9b7b16783

kernel/patches-4.14.x-rt/0007-iommu-amd-Avoid-locking-get_irq_table-from-atomic-co.patch

@@ -1,7 +1,7 @@
-From 8a351e0d8d77d77a91a01f5d6b29a644b4a4325d Mon Sep 17 00:00:00 2001
+From 3fbd8e3a71166bdf55537b1d24f4adfe83a32495 Mon Sep 17 00:00:00 2001
 From: Scott Wood <swood@redhat.com>
 Date: Wed, 14 Feb 2018 17:36:28 -0600
-Subject: [PATCH 007/414] iommu/amd: Avoid locking get_irq_table() from atomic
+Subject: [PATCH 007/413] iommu/amd: Avoid locking get_irq_table() from atomic
  context
 
 Upstream commit df42a04b15f19a842393dc98a84cbc52b1f8ed49

kernel/patches-4.14.x-rt/0008-iommu-amd-Turn-dev_data_list-into-a-lock-less-list.patch

@@ -1,7 +1,7 @@
-From 0d2bddd253183e23f224fcda3b7b34d27ebc106e Mon Sep 17 00:00:00 2001
+From bba6248dc05bcfad8e8ef21a22bd6e63cadd953d Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Thu, 22 Mar 2018 16:22:34 +0100
-Subject: [PATCH 008/414] iommu/amd: Turn dev_data_list into a lock less list
+Subject: [PATCH 008/413] iommu/amd: Turn dev_data_list into a lock less list
 
 Upstream commit 779da73273fc4c4c6f41579a95e4fb7880a1720e
 

kernel/patches-4.14.x-rt/0009-iommu-amd-Split-domain-id-out-of-amd_iommu_devtable_.patch

@@ -1,7 +1,7 @@
-From 83b51c4f5ff1be7f15efde56b978914d0895996e Mon Sep 17 00:00:00 2001
+From bb893b3f9364003820ea8219a69afbed2cf45001 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Thu, 22 Mar 2018 16:22:35 +0100
-Subject: [PATCH 009/414] iommu/amd: Split domain id out of
+Subject: [PATCH 009/413] iommu/amd: Split domain id out of
  amd_iommu_devtable_lock
 
 Upstream commit 2bc00180890427dcc092b2f2b0d03c904bcade29

kernel/patches-4.14.x-rt/0010-iommu-amd-Split-irq_lookup_table-out-of-the-amd_iomm.patch

@@ -1,7 +1,7 @@
-From a1336d2a2a1c04e806f89a36985b5cb1344567e7 Mon Sep 17 00:00:00 2001
+From ae5816d77220aaccf245674b852facf09822b534 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Thu, 22 Mar 2018 16:22:36 +0100
-Subject: [PATCH 010/414] iommu/amd: Split irq_lookup_table out of the
+Subject: [PATCH 010/413] iommu/amd: Split irq_lookup_table out of the
  amd_iommu_devtable_lock
 
 Upstream commit ea6166f4b83e9cfba1c18f46a764d50045682fe5

kernel/patches-4.14.x-rt/0011-iommu-amd-Remove-the-special-case-from-alloc_irq_tab.patch

@@ -1,7 +1,7 @@
-From c5569e1ca0250dcc293232513ad75aae8047f6ba Mon Sep 17 00:00:00 2001
+From f9e7252eb1c41def5d916de943ec2277b7cb7495 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Thu, 22 Mar 2018 16:22:37 +0100
-Subject: [PATCH 011/414] iommu/amd: Remove the special case from
+Subject: [PATCH 011/413] iommu/amd: Remove the special case from
  alloc_irq_table()
 
 Upstream commit fde65dd3d3096e8f6ecc7bbe544eb91f4220772c

kernel/patches-4.14.x-rt/0012-iommu-amd-Use-table-instead-irt-as-variable-name-in-.patch

@@ -1,7 +1,7 @@
-From 4e6605ab50457816d0579a016417ed1a530cee8c Mon Sep 17 00:00:00 2001
+From b19751cfe856edcbf65bad62e566f458cbf7fb97 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Thu, 22 Mar 2018 16:22:38 +0100
-Subject: [PATCH 012/414] iommu/amd: Use `table' instead `irt' as variable name
+Subject: [PATCH 012/413] iommu/amd: Use `table' instead `irt' as variable name
  in amd_iommu_update_ga()
 
 Upstream commit 4fde541c9dc114c5b448ad34b0286fe8b7c550f1

kernel/patches-4.14.x-rt/0013-iommu-amd-Factor-out-setting-the-remap-table-for-a-d.patch

@@ -1,7 +1,7 @@
-From 2a7c51fa6a76aa7cca7455ef6c1363fc7cb9ec6f Mon Sep 17 00:00:00 2001
+From 1fd7be1ae38c27e7d631068ecb594c17e39035b5 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Thu, 22 Mar 2018 16:22:39 +0100
-Subject: [PATCH 013/414] iommu/amd: Factor out setting the remap table for a
+Subject: [PATCH 013/413] iommu/amd: Factor out setting the remap table for a
  devid
 
 Upstream commit 2fcc1e8ac4a8514c64f946178fc36c2e30e56a41

kernel/patches-4.14.x-rt/0014-iommu-amd-Drop-the-lock-while-allocating-new-irq-rem.patch

@@ -1,7 +1,7 @@
-From 78aff31b5badc9ef5def900f4eeb1e47f24134aa Mon Sep 17 00:00:00 2001
+From 7567c98c4ad5710bae08f45a10e7bf22833d1644 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Thu, 22 Mar 2018 16:22:40 +0100
-Subject: [PATCH 014/414] iommu/amd: Drop the lock while allocating new irq
+Subject: [PATCH 014/413] iommu/amd: Drop the lock while allocating new irq
  remap table
 
 Upstream commit 993ca6e063a69a0c65ca42ed449b6bc1b3844151

kernel/patches-4.14.x-rt/0015-iommu-amd-Make-amd_iommu_devtable_lock-a-spin_lock.patch

@@ -1,7 +1,7 @@
-From 37d2bc916fbc0c736b9c764ebbf176d915f35763 Mon Sep 17 00:00:00 2001
+From 5fe259167e7969e2f51f10b7261498ddc6cd028c Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Thu, 22 Mar 2018 16:22:41 +0100
-Subject: [PATCH 015/414] iommu/amd: Make amd_iommu_devtable_lock a spin_lock
+Subject: [PATCH 015/413] iommu/amd: Make amd_iommu_devtable_lock a spin_lock
 
 Upstream commit 2cd1083d79a0a8c223af430ca97884c28a1e2fc0
 

kernel/patches-4.14.x-rt/0016-iommu-amd-Return-proper-error-code-in-irq_remapping_.patch

@@ -1,7 +1,7 @@
-From 23f1a4c0eaf25e45ba512b80df021765e5f8c0c4 Mon Sep 17 00:00:00 2001
+From 12b7908685ca79009ebad69a4b409300629aeafd Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Thu, 22 Mar 2018 16:22:42 +0100
-Subject: [PATCH 016/414] iommu/amd: Return proper error code in
+Subject: [PATCH 016/413] iommu/amd: Return proper error code in
  irq_remapping_alloc()
 
 Upstream commit 29d049be9438278c47253a74cf8d0ddf36bd5d68

kernel/patches-4.14.x-rt/0017-timers-Use-static-keys-for-migrate_enable-nohz_activ.patch

@@ -1,7 +1,7 @@
-From 4ac5106b58007df574bf75e8043b3956cca1fafc Mon Sep 17 00:00:00 2001
+From b3ad0d0a382ccacf4b70d284f293ff109701d0bf Mon Sep 17 00:00:00 2001
 From: Thomas Gleixner <tglx@linutronix.de>
 Date: Wed, 20 Dec 2017 17:12:50 +0100
-Subject: [PATCH 017/414] timers: Use static keys for
+Subject: [PATCH 017/413] timers: Use static keys for
  migrate_enable/nohz_active
 
 The members migrate_enable and nohz_active in the timer/hrtimer per CPU
@@ -121,7 +121,7 @@ index f8e1845aa464..4ac74dff59f0 100644
  
  DECLARE_PER_CPU(struct hrtimer_cpu_base, hrtimer_bases);
 diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
-index bb2af74e6b62..9a372e16791c 100644
+index ea3c062e7e1c..7f924eba78da 100644
 --- a/kernel/time/tick-sched.c
 +++ b/kernel/time/tick-sched.c
 @@ -1132,7 +1132,7 @@ static inline void tick_nohz_activate(struct tick_sched *ts, int mode)

kernel/patches-4.14.x-rt/0018-hrtimer-Correct-blantanly-wrong-comment.patch

@@ -1,7 +1,7 @@
-From 18e4a446ba1b09e37ccda5b5c9a185dd4008cfd5 Mon Sep 17 00:00:00 2001
+From ed3375830e0a42c193e8c5c89990d1d09db6c2ee Mon Sep 17 00:00:00 2001
 From: Thomas Gleixner <tglx@linutronix.de>
 Date: Wed, 20 Dec 2017 17:12:51 +0100
-Subject: [PATCH 018/414] hrtimer: Correct blantanly wrong comment
+Subject: [PATCH 018/413] hrtimer: Correct blantanly wrong comment
 
 The protection of a hrtimer which runs its callback against migration to a
 different CPU has nothing to do with hard interrupt context.

kernel/patches-4.14.x-rt/0019-hrtimer-Fix-kerneldoc-for-struct-hrtimer_cpu_base.patch

@@ -1,7 +1,7 @@
-From 3417b2f612ef8cb6484f68dc8521ad9f2340c5cb Mon Sep 17 00:00:00 2001
+From e18c0b4a7e4a4c18c9a89c44cfcbbf16d3161a04 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:12:52 +0100
-Subject: [PATCH 019/414] hrtimer: Fix kerneldoc for struct hrtimer_cpu_base
+Subject: [PATCH 019/413] hrtimer: Fix kerneldoc for struct hrtimer_cpu_base
 
 The sequence '/**' marks the start of a struct description. Add the
 missing second asterisk. While at it adapt the ordering of the struct

kernel/patches-4.14.x-rt/0020-hrtimer-Cleanup-clock-argument-in-schedule_hrtimeout.patch

@@ -1,7 +1,7 @@
-From 431cc332cba05e8803b5d67fd5ccf89c22cdb0a2 Mon Sep 17 00:00:00 2001
+From 7cd020dedd871257e6ca7c9782d1ac151e1b9899 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:12:53 +0100
-Subject: [PATCH 020/414] hrtimer: Cleanup clock argument in
+Subject: [PATCH 020/413] hrtimer: Cleanup clock argument in
  schedule_hrtimeout_range_clock()
 
 schedule_hrtimeout_range_clock() uses an integer for the clock id

kernel/patches-4.14.x-rt/0021-hrtimer-Fix-hrtimer-function-description.patch

@@ -1,7 +1,7 @@
-From 53ec81b3e2722efde34e962102444261a5b6572a Mon Sep 17 00:00:00 2001
+From bf593b81a69f815100e8fd6fe44010b85d856c61 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:12:54 +0100
-Subject: [PATCH 021/414] hrtimer: Fix hrtimer function description
+Subject: [PATCH 021/413] hrtimer: Fix hrtimer function description
 
 The hrtimer_start[_range_ns]() starts a timer reliable on this CPU only
 when HRTIMER_MODE_PINNED is set. Furthermore the HRTIMER_MODE_PINNED mode

kernel/patches-4.14.x-rt/0022-hrtimer-Cleanup-hrtimer_mode-enum.patch

@@ -1,7 +1,7 @@
-From a28f838542f4a5b318acfd07e94dc83e2583dff3 Mon Sep 17 00:00:00 2001
+From 263d78ecb76fc93322cdf5bcfd3615b96fbd4262 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:12:56 +0100
-Subject: [PATCH 022/414] hrtimer: Cleanup hrtimer_mode enum
+Subject: [PATCH 022/413] hrtimer: Cleanup hrtimer_mode enum
 
 It's not obvious that the HRTIMER_MODE variants are bit combinations
 because all modes are hard coded constants.

kernel/patches-4.14.x-rt/0023-tracing-hrtimer-Print-hrtimer-mode-in-hrtimer_start-.patch

@@ -1,7 +1,7 @@
-From a15b4fcd0054369d94b97a2064b930b23eeeac9c Mon Sep 17 00:00:00 2001
+From 6f84153b211f7fb270f43e7636a68bce4241df30 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:12:58 +0100
-Subject: [PATCH 023/414] tracing/hrtimer: Print hrtimer mode in hrtimer_start
+Subject: [PATCH 023/413] tracing/hrtimer: Print hrtimer mode in hrtimer_start
  tracepoint
 
 The hrtimer_start tracepoint lacks the mode information. The mode is

kernel/patches-4.14.x-rt/0024-hrtimer-Switch-for-loop-to-_ffs-evaluation.patch

@@ -1,7 +1,7 @@
-From ea534b414933b99a3a5b729a4112b28d33160529 Mon Sep 17 00:00:00 2001
+From 73a81054586a0dccb601a8454b905b8d33b619d8 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:12:59 +0100
-Subject: [PATCH 024/414] hrtimer: Switch for loop to _ffs() evaluation
+Subject: [PATCH 024/413] hrtimer: Switch for loop to _ffs() evaluation
 
 Looping over all clock bases to find active bits is suboptimal if not all
 bases are active.

kernel/patches-4.14.x-rt/0025-hrtimer-Store-running-timer-in-hrtimer_clock_base.patch

@@ -1,7 +1,7 @@
-From bcc3e93255cf34cf11886ae5cd1704571fba59d6 Mon Sep 17 00:00:00 2001
+From 0eb80ff2452afbdeb89fe23de78ae2aa5768f48b Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:00 +0100
-Subject: [PATCH 025/414] hrtimer: Store running timer in hrtimer_clock_base
+Subject: [PATCH 025/413] hrtimer: Store running timer in hrtimer_clock_base
 
 The pointer to the currently running timer is stored in hrtimer_cpu_base
 before the base lock is dropped and the callback is invoked.

kernel/patches-4.14.x-rt/0026-hrtimer-Make-room-in-struct-hrtimer_cpu_base.patch

@@ -1,7 +1,7 @@
-From ba87bcb39f4bc26a0e1022597a49ba1b10c9ec95 Mon Sep 17 00:00:00 2001
+From 17f57d21ba2f7e1c8a3b0d9af131fa1ccfa9dd6a Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:01 +0100
-Subject: [PATCH 026/414] hrtimer: Make room in struct hrtimer_cpu_base
+Subject: [PATCH 026/413] hrtimer: Make room in struct hrtimer_cpu_base
 
 The upcoming softirq based hrtimers support requires an additional field in
 the hrtimer_cpu_base struct, which would grow the struct size beyond a

kernel/patches-4.14.x-rt/0027-hrtimer-Reduce-conditional-code-hres_active.patch

@@ -1,7 +1,7 @@
-From afb485a8f0c8869ab0a04383719c67c272b653e7 Mon Sep 17 00:00:00 2001
+From f3202ee4dafba5d63ef6159a6f99ca69156cf9e1 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:02 +0100
-Subject: [PATCH 027/414] hrtimer: Reduce conditional code (hres_active)
+Subject: [PATCH 027/413] hrtimer: Reduce conditional code (hres_active)
 
 The hrtimer_cpu_base struct has the CONFIG_HIGH_RES_TIMERS conditional
 struct member hres_active. All related functions to this member are

kernel/patches-4.14.x-rt/0028-hrtimer-Use-accesor-functions-instead-of-direct-acce.patch

@@ -1,7 +1,7 @@
-From 934a2dcf8cb9c83bbe08d6a2a8f0d7a8c6dcb392 Mon Sep 17 00:00:00 2001
+From 4497ed468019c6d815cae26a937cd45dead9b101 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:03 +0100
-Subject: [PATCH 028/414] hrtimer: Use accesor functions instead of direct
+Subject: [PATCH 028/413] hrtimer: Use accesor functions instead of direct
  access
 
 __hrtimer_hres_active() is now available unconditionally. Replace the

kernel/patches-4.14.x-rt/0029-hrtimer-Make-the-remote-enqueue-check-unconditional.patch

@@ -1,7 +1,7 @@
-From c9dadfb4f40895a2ea72698e2cb1bba1757b9a90 Mon Sep 17 00:00:00 2001
+From f44ff83daacbd575e62c7c496fae6918b9e02072 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:04 +0100
-Subject: [PATCH 029/414] hrtimer: Make the remote enqueue check unconditional
+Subject: [PATCH 029/413] hrtimer: Make the remote enqueue check unconditional
 
 hrtimer_cpu_base.expires_next is used to cache the next event armed in the
 timer hardware. The value is used to check whether an hrtimer can be

kernel/patches-4.14.x-rt/0030-hrtimer-Make-hrtimer_cpu_base.next_timer-handling-un.patch

@@ -1,7 +1,7 @@
-From d6c371590a1cf3f3c9568b182d8e1cb2dfaceadf Mon Sep 17 00:00:00 2001
+From 2897f3039bcafac1de0a3d9bd819790d02348bc4 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:05 +0100
-Subject: [PATCH 030/414] hrtimer: Make hrtimer_cpu_base.next_timer handling
+Subject: [PATCH 030/413] hrtimer: Make hrtimer_cpu_base.next_timer handling
  unconditional
 
 hrtimer_cpu_base.next_timer stores the pointer to the next expiring timer

kernel/patches-4.14.x-rt/0031-hrtimer-Make-hrtimer_reprogramm-unconditional.patch

@@ -1,7 +1,7 @@
-From 5c8f8eaa36b00eac21e3f19049e7a7402bc02381 Mon Sep 17 00:00:00 2001
+From 8b971457c51090aad6385968f41074b8d5610fde Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:06 +0100
-Subject: [PATCH 031/414] hrtimer: Make hrtimer_reprogramm() unconditional
+Subject: [PATCH 031/413] hrtimer: Make hrtimer_reprogramm() unconditional
 
 hrtimer_reprogram() needs to be available unconditionally for softirq based
 hrtimers. Move the function and all required struct members out of the

kernel/patches-4.14.x-rt/0032-hrtimer-Make-hrtimer_force_reprogramm-unconditionall.patch

@@ -1,7 +1,7 @@
-From 71378ed1a6a72a2c8e010fb9353fba8df488df7b Mon Sep 17 00:00:00 2001
+From 9ee0b0d8cdc3d1166b79d7ce508206c0712a7d58 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:07 +0100
-Subject: [PATCH 032/414] hrtimer: Make hrtimer_force_reprogramm()
+Subject: [PATCH 032/413] hrtimer: Make hrtimer_force_reprogramm()
  unconditionally available
 
 hrtimer_force_reprogram() needs to be available unconditionally for softirq

kernel/patches-4.14.x-rt/0033-hrtimer-Unify-handling-of-hrtimer-remove.patch

@@ -1,7 +1,7 @@
-From 177cbb8e5db3c0e4dd323a6a653e5a363c85f5cf Mon Sep 17 00:00:00 2001
+From a54d37065d2922d1d67d38fa44394f54b0bcb68c Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:08 +0100
-Subject: [PATCH 033/414] hrtimer: Unify handling of hrtimer remove
+Subject: [PATCH 033/413] hrtimer: Unify handling of hrtimer remove
 
 When the first hrtimer on the current CPU is removed,
 hrtimer_force_reprogram() is invoked but only when

kernel/patches-4.14.x-rt/0034-hrtimer-Unify-handling-of-remote-enqueue.patch

@@ -1,7 +1,7 @@
-From 248f9a304f527cd8253fbd1c8f35ae35dc1caa47 Mon Sep 17 00:00:00 2001
+From dde2d69a6a4c73667c805b32876febf324c9c002 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:09 +0100
-Subject: [PATCH 034/414] hrtimer: Unify handling of remote enqueue
+Subject: [PATCH 034/413] hrtimer: Unify handling of remote enqueue
 
 hrtimer_reprogram() is conditionally invoked from hrtimer_start_range_ns()
 when hrtimer_cpu_base.hres_active is true.

kernel/patches-4.14.x-rt/0035-hrtimer-Make-remote-enqueue-decision-less-restrictiv.patch

@@ -1,7 +1,7 @@
-From 2dc46ebab983cc8b2cfd85cc0eef716a7a660d46 Mon Sep 17 00:00:00 2001
+From b6f4ff863d93350c0645a418b579466396f804bb Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:10 +0100
-Subject: [PATCH 035/414] hrtimer: Make remote enqueue decision less
+Subject: [PATCH 035/413] hrtimer: Make remote enqueue decision less
  restrictive
 
 The current decision whether a timer can be queued on a remote CPU checks

kernel/patches-4.14.x-rt/0036-hrtimer-Remove-base-argument-from-hrtimer_reprogram.patch

@@ -1,7 +1,7 @@
-From aafe75f039f4e96b2c6c1d3c0032af678591e28d Mon Sep 17 00:00:00 2001
+From 4bb86bcae586476f20ddc1a154a7de89aa263cd2 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:11 +0100
-Subject: [PATCH 036/414] hrtimer: Remove base argument from
+Subject: [PATCH 036/413] hrtimer: Remove base argument from
  hrtimer_reprogram()
 
 hrtimer_reprogram() must have access to the hrtimer_clock_base of the new

kernel/patches-4.14.x-rt/0037-hrtimer-Split-hrtimer_start_range_ns.patch

@@ -1,7 +1,7 @@
-From 2d39cd422d4266f02d8d95eef439e2ad508f8c8a Mon Sep 17 00:00:00 2001
+From 064b4807c34c9806e7b47112691b8e2879e60c18 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:12 +0100
-Subject: [PATCH 037/414] hrtimer: Split hrtimer_start_range_ns()
+Subject: [PATCH 037/413] hrtimer: Split hrtimer_start_range_ns()
 
 Preparatory patch for softirq based hrtimers to avoid code duplication. No
 functional change.

kernel/patches-4.14.x-rt/0038-hrtimer-Split-__hrtimer_get_next_event.patch

@@ -1,7 +1,7 @@
-From d9e7ac76b7cef3f0b79a63864c6473b6e158c49a Mon Sep 17 00:00:00 2001
+From 70d21872a9b1a71675676eb4d42218d89787d845 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:13 +0100
-Subject: [PATCH 038/414] hrtimer: Split __hrtimer_get_next_event()
+Subject: [PATCH 038/413] hrtimer: Split __hrtimer_get_next_event()
 
 Preparatory patch for softirq based hrtimers to avoid code duplication. No
 functional change.

kernel/patches-4.14.x-rt/0039-hrtimer-Use-irqsave-irqrestore-around-__run_hrtimer.patch

@@ -1,7 +1,7 @@
-From 96fbdc5365e4b933549b3f2428b08f4bc9e7bfa6 Mon Sep 17 00:00:00 2001
+From 6228d88fd2fa50ac7785f0f0acb373dc81ecd735 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:14 +0100
-Subject: [PATCH 039/414] hrtimer: Use irqsave/irqrestore around
+Subject: [PATCH 039/413] hrtimer: Use irqsave/irqrestore around
  __run_hrtimer()
 
 __run_hrtimer() is called with the hrtimer_cpu_base.lock held and

kernel/patches-4.14.x-rt/0040-hrtimer-Add-clock-bases-and-hrtimer-mode-for-soft-ir.patch

@@ -1,7 +1,7 @@
-From 6c1a903df466a3e6485160185d29c569e98392a4 Mon Sep 17 00:00:00 2001
+From 5ebee81db54159612d178a5b77f2e4e6e8028a56 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:15 +0100
-Subject: [PATCH 040/414] hrtimer: Add clock bases and hrtimer mode for soft
+Subject: [PATCH 040/413] hrtimer: Add clock bases and hrtimer mode for soft
  irq context
 
 hrtimer callback functions are always executed in hard interrupt

kernel/patches-4.14.x-rt/0041-hrtimer-Prepare-handling-of-hard-and-softirq-based-h.patch

@@ -1,7 +1,7 @@
-From 0aaa599ac85c7489588544feee2d007de1249786 Mon Sep 17 00:00:00 2001
+From 9b0bb3e5f3f980c8c18ea14a8adbcead2a93e286 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:16 +0100
-Subject: [PATCH 041/414] hrtimer: Prepare handling of hard and softirq based
+Subject: [PATCH 041/413] hrtimer: Prepare handling of hard and softirq based
  hrtimers
 
 The softirq based hrtimer can utilize most of the existing hrtimers

kernel/patches-4.14.x-rt/0042-hrtimer-Implement-support-for-softirq-based-hrtimers.patch

@@ -1,7 +1,7 @@
-From 77008f1277d442b0d4320218ce6bff4b100bd4f4 Mon Sep 17 00:00:00 2001
+From ef22defd5fa82e8e8837e8c1047c4f2c902f1480 Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:17 +0100
-Subject: [PATCH 042/414] hrtimer: Implement support for softirq based hrtimers
+Subject: [PATCH 042/413] hrtimer: Implement support for softirq based hrtimers
 
 hrtimer callbacks are always invoked in hard interrupt context. Several
 users in tree require soft interrupt context for their callbacks and

kernel/patches-4.14.x-rt/0043-hrtimer-Implement-SOFT-HARD-clock-base-selection.patch

@@ -1,7 +1,7 @@
-From 995d50bf0d967649155d26a1c5518ff2055164bb Mon Sep 17 00:00:00 2001
+From e00aad52582b4b7bc8cb583a826c30e05dfe5c3b Mon Sep 17 00:00:00 2001
 From: Anna-Maria Gleixner <anna-maria@linutronix.de>
 Date: Wed, 20 Dec 2017 17:13:18 +0100
-Subject: [PATCH 043/414] hrtimer: Implement SOFT/HARD clock base selection
+Subject: [PATCH 043/413] hrtimer: Implement SOFT/HARD clock base selection
 
 All prerequisites to handle hrtimers for expiry in either hard or soft
 interrupt context are in place.

kernel/patches-4.14.x-rt/0044-can-bcm-Replace-hrtimer_tasklet-with-softirq-based-h.patch

@@ -1,7 +1,7 @@
-From e41462750d62f1c41fd2d31c4c9b48de2d81b25f Mon Sep 17 00:00:00 2001
+From b127459a9003fd794f5ff33cff10094b24d81b2c Mon Sep 17 00:00:00 2001
 From: Thomas Gleixner <tglx@linutronix.de>
 Date: Thu, 23 Nov 2017 16:39:11 +0100
-Subject: [PATCH 044/414] can/bcm: Replace hrtimer_tasklet with softirq based
+Subject: [PATCH 044/413] can/bcm: Replace hrtimer_tasklet with softirq based
  hrtimer
 
 Switch the timer to HRTIMER_MODE_SOFT, which executed the timer

kernel/patches-4.14.x-rt/0045-mac80211_hwsim-Replace-hrtimer-tasklet-with-softirq-.patch

@@ -1,7 +1,7 @@
-From cc601ebcb4fc381d3a6fd809da4103f6af90f83c Mon Sep 17 00:00:00 2001
+From 6266b3f9a910cc55009474c96d3e1058cc423efa Mon Sep 17 00:00:00 2001
 From: Thomas Gleixner <tglx@linutronix.de>
 Date: Thu, 23 Nov 2017 16:39:12 +0100
-Subject: [PATCH 045/414] mac80211_hwsim: Replace hrtimer tasklet with softirq
+Subject: [PATCH 045/413] mac80211_hwsim: Replace hrtimer tasklet with softirq
  hrtimer
 
 Switch the timer to HRTIMER_MODE_SOFT, which executed the timer

kernel/patches-4.14.x-rt/0046-xfrm-Replace-hrtimer-tasklet-with-softirq-hrtimer.patch

@@ -1,7 +1,7 @@
-From 8c0e9dad7cd8996721f69a508203e8f6bfa12b7f Mon Sep 17 00:00:00 2001
+From 295973f9eae37222414abe12d242898237230c9b Mon Sep 17 00:00:00 2001
 From: Thomas Gleixner <tglx@linutronix.de>
 Date: Thu, 23 Nov 2017 16:39:13 +0100
-Subject: [PATCH 046/414] xfrm: Replace hrtimer tasklet with softirq hrtimer
+Subject: [PATCH 046/413] xfrm: Replace hrtimer tasklet with softirq hrtimer
 
 Switch the timer to HRTIMER_MODE_SOFT, which executed the timer
 callback in softirq context and remove the hrtimer_tasklet.

kernel/patches-4.14.x-rt/0047-softirq-Remove-tasklet_hrtimer.patch

@@ -1,7 +1,7 @@
-From 84d22944bf656ca6957cc58ceba1a8f489ead682 Mon Sep 17 00:00:00 2001
+From 5c03f39867b511e7be17cb632d82d052779ea74d Mon Sep 17 00:00:00 2001
 From: Thomas Gleixner <tglx@linutronix.de>
 Date: Thu, 23 Nov 2017 16:39:14 +0100
-Subject: [PATCH 047/414] softirq: Remove tasklet_hrtimer
+Subject: [PATCH 047/413] softirq: Remove tasklet_hrtimer
 
 There are no more tasklet_hrtimer users of this interface.
 Remove it.
@@ -51,10 +51,10 @@ index 69c238210325..af15bfd89598 100644
   * Autoprobing for irqs:
   *
 diff --git a/kernel/softirq.c b/kernel/softirq.c
-index e89c3b0cff6d..359cec869172 100644
+index a4c87cf27f9d..1a5dfc8dcf49 100644
 --- a/kernel/softirq.c
 +++ b/kernel/softirq.c
-@@ -584,57 +584,6 @@ void tasklet_kill(struct tasklet_struct *t)
+@@ -588,57 +588,6 @@ void tasklet_kill(struct tasklet_struct *t)
  }
  EXPORT_SYMBOL(tasklet_kill);
  

kernel/patches-4.14.x-rt/0048-ALSA-dummy-Replace-tasklet-with-softirq-hrtimer.patch

@@ -1,7 +1,7 @@
-From 51d1d147b7b1fad19cb92eaea249838277c9f067 Mon Sep 17 00:00:00 2001
+From 4435bcc7e189b8d5b5afb71535a36c937937d4ed Mon Sep 17 00:00:00 2001
 From: Thomas Gleixner <tglx@linutronix.de>
 Date: Thu, 23 Nov 2017 16:39:15 +0100
-Subject: [PATCH 048/414] ALSA/dummy: Replace tasklet with softirq hrtimer
+Subject: [PATCH 048/413] ALSA/dummy: Replace tasklet with softirq hrtimer
 
 The tasklet is used to defer the execution of snd_pcm_period_elapsed() to
 the softirq context. Using the HRTIMER_MODE_SOFT mode invokes the timer

kernel/patches-4.14.x-rt/0049-usb-gadget-NCM-Replace-tasklet-with-softirq-hrtimer.patch

@@ -1,7 +1,7 @@
-From d9fc17e1bbc04f471ec7070c7788f3e8b1087f59 Mon Sep 17 00:00:00 2001
+From d33f6f8b7d73de2a918cf0c98de41258a27d335a Mon Sep 17 00:00:00 2001
 From: Thomas Gleixner <tglx@linutronix.de>
 Date: Thu, 23 Nov 2017 16:39:16 +0100
-Subject: [PATCH 049/414] usb/gadget/NCM: Replace tasklet with softirq hrtimer
+Subject: [PATCH 049/413] usb/gadget/NCM: Replace tasklet with softirq hrtimer
 
 The tx_tasklet tasklet is used in invoke the hrtimer (task_timer) in
 softirq context. This can be also achieved without the tasklet but

kernel/patches-4.14.x-rt/0050-net-mvpp2-Replace-tasklet-with-softirq-hrtimer.patch

@@ -1,7 +1,7 @@
-From b9d178d6751f0bf94bd26aacb8c0c694ac92d123 Mon Sep 17 00:00:00 2001
+From 2112223f97d7ac6c162b9a5228692761fc23b592 Mon Sep 17 00:00:00 2001
 From: Thomas Gleixner <tglx@linutronix.de>
 Date: Thu, 23 Nov 2017 16:39:17 +0100
-Subject: [PATCH 050/414] net/mvpp2: Replace tasklet with softirq hrtimer
+Subject: [PATCH 050/413] net/mvpp2: Replace tasklet with softirq hrtimer
 
 The tx_done_tasklet tasklet is used in invoke the hrtimer
 (mvpp2_hr_timer_cb) in softirq context. This can be also achieved without

kernel/patches-4.14.x-rt/0051-arm-at91-do-not-disable-enable-clocks-in-a-row.patch

@@ -1,7 +1,7 @@
-From 727e4f53abcedadc467084c8a89aa37d235bd637 Mon Sep 17 00:00:00 2001
+From 2b498ad21a6aba531148a6f8d5b1555f71a88b21 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Wed, 9 Mar 2016 10:51:06 +0100
-Subject: [PATCH 051/414] arm: at91: do not disable/enable clocks in a row
+Subject: [PATCH 051/413] arm: at91: do not disable/enable clocks in a row
 
 Currently the driver will disable the clock and enable it one line later
 if it is switching from periodic mode into one shot.

kernel/patches-4.14.x-rt/0052-ARM-smp-Move-clear_tasks_mm_cpumask-call-to-__cpu_di.patch

@@ -1,7 +1,7 @@
-From 8f4e789c87e029c3c7d429e6e28d0eb937ca7346 Mon Sep 17 00:00:00 2001
+From 36957734aaba76d52eced69c50daa274e334faaa Mon Sep 17 00:00:00 2001
 From: Grygorii Strashko <grygorii.strashko@ti.com>
 Date: Fri, 11 Sep 2015 21:21:23 +0300
-Subject: [PATCH 052/414] ARM: smp: Move clear_tasks_mm_cpumask() call to
+Subject: [PATCH 052/413] ARM: smp: Move clear_tasks_mm_cpumask() call to
  __cpu_die()
 
 When running with the RT-kernel (4.1.5-rt5) on TI OMAP dra7-evm and trying

kernel/patches-4.14.x-rt/0053-rtmutex-Handle-non-enqueued-waiters-gracefully.patch

@@ -1,7 +1,7 @@
-From 64c4c76f4ac141722a1ba1fbcc2d41a50ba0e2c7 Mon Sep 17 00:00:00 2001
+From 92418d20f8e7dd36adbab3a4bcf93662c3a078f6 Mon Sep 17 00:00:00 2001
 From: Thomas Gleixner <tglx@linutronix.de>
 Date: Fri, 6 Nov 2015 18:51:03 +0100
-Subject: [PATCH 053/414] rtmutex: Handle non enqueued waiters gracefully
+Subject: [PATCH 053/413] rtmutex: Handle non enqueued waiters gracefully
 
 Yimin debugged that in case of a PI wakeup in progress when
 rt_mutex_start_proxy_lock() calls task_blocks_on_rt_mutex() the latter

kernel/patches-4.14.x-rt/0054-rbtree-include-rcu.h-because-we-use-it.patch

@@ -1,7 +1,7 @@
-From 99ec286b59c1a09247a3a5753385ea1c936079ee Mon Sep 17 00:00:00 2001
+From 2faab80428c8d44783448c6131cc8282b71c16a6 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Wed, 14 Sep 2016 11:52:17 +0200
-Subject: [PATCH 054/414] rbtree: include rcu.h because we use it
+Subject: [PATCH 054/413] rbtree: include rcu.h because we use it
 
 Since commit c1adf20052d8 ("Introduce rb_replace_node_rcu()")
 rbtree_augmented.h uses RCU related data structures but does not include

kernel/patches-4.14.x-rt/0055-rxrpc-remove-unused-static-variables.patch

@@ -1,7 +1,7 @@
-From cb4cd2c91b5cd0e8d23767e051c92b7f9d277aa7 Mon Sep 17 00:00:00 2001
+From 57dd454f351897f664765ea248bd047991104193 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Fri, 21 Oct 2016 10:54:50 +0200
-Subject: [PATCH 055/414] rxrpc: remove unused static variables
+Subject: [PATCH 055/413] rxrpc: remove unused static variables
 
 The rxrpc_security_methods and rxrpc_security_sem user has been removed
 in 648af7fca159 ("rxrpc: Absorb the rxkad security module"). This was

kernel/patches-4.14.x-rt/0056-mfd-syscon-atmel-smc-include-string.h.patch

@@ -1,7 +1,7 @@
-From 3d173b2cddbb8f72c1a8e412a9e13b7d69b4af6b Mon Sep 17 00:00:00 2001
+From 9f0770f9b7e16ce7f97f29560777ff0ec657af1f Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Wed, 4 Oct 2017 09:55:58 +0200
-Subject: [PATCH 056/414] mfd: syscon: atmel-smc: include string.h
+Subject: [PATCH 056/413] mfd: syscon: atmel-smc: include string.h
 
 The string.h header file is needed for the memset() definition. The RT
 build fails because it is not pulled in via other header files.

kernel/patches-4.14.x-rt/0057-sched-swait-include-wait.h.patch

@@ -1,7 +1,7 @@
-From dad4995002c053a2d75ed9aadd02146a9e5b9d1e Mon Sep 17 00:00:00 2001
+From 643507ddc97f2bbb7721f6ff5698c506b4422c6f Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Mon, 4 Dec 2017 13:11:10 +0100
-Subject: [PATCH 057/414] sched/swait: include wait.h
+Subject: [PATCH 057/413] sched/swait: include wait.h
 
 kbuild bot reported against an intermediate RT patch that the build
 fails with:

kernel/patches-4.14.x-rt/0058-NFSv4-replace-seqcount_t-with-a-seqlock_t.patch

@@ -1,7 +1,7 @@
-From 87c7c17c4d4cfca00f604c9d4fd6ad9a983801de Mon Sep 17 00:00:00 2001
+From 49fad3878c49d387a502caae3693bbeaf0fd3706 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Fri, 28 Oct 2016 23:05:11 +0200
-Subject: [PATCH 058/414] NFSv4: replace seqcount_t with a seqlock_t
+Subject: [PATCH 058/413] NFSv4: replace seqcount_t with a seqlock_t
 
 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
@@ -57,10 +57,10 @@ index a73144b3cb8c..0c403d280b96 100644
  };
  
 diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
-index 928bbc397818..c2b9d5d6e6cb 100644
+index 43fbf4495090..751063bd6211 100644
 --- a/fs/nfs/nfs4proc.c
 +++ b/fs/nfs/nfs4proc.c
-@@ -2686,7 +2686,7 @@ static int _nfs4_open_and_get_state(struct nfs4_opendata *opendata,
+@@ -2689,7 +2689,7 @@ static int _nfs4_open_and_get_state(struct nfs4_opendata *opendata,
  	unsigned int seq;
  	int ret;
  
@@ -69,7 +69,7 @@ index 928bbc397818..c2b9d5d6e6cb 100644
  
  	ret = _nfs4_proc_open(opendata);
  	if (ret != 0)
-@@ -2724,7 +2724,7 @@ static int _nfs4_open_and_get_state(struct nfs4_opendata *opendata,
+@@ -2727,7 +2727,7 @@ static int _nfs4_open_and_get_state(struct nfs4_opendata *opendata,
  
  	if (d_inode(dentry) == state->inode) {
  		nfs_inode_attach_open_context(ctx);

kernel/patches-4.14.x-rt/0059-Bluetooth-avoid-recursive-locking-in-hci_send_to_cha.patch

@@ -1,7 +1,7 @@
-From 26e3f4a085d447ef75cc202750c0a97e4686257d Mon Sep 17 00:00:00 2001
+From 84b282efc3f74ec3ad5b30c6c07e2165670faf47 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Thu, 21 Sep 2017 15:35:57 +0200
-Subject: [PATCH 059/414] Bluetooth: avoid recursive locking in
+Subject: [PATCH 059/413] Bluetooth: avoid recursive locking in
  hci_send_to_channel()
 
 Mart reported a deadlock in -RT in the call path:

kernel/patches-4.14.x-rt/0060-iommu-iova-Use-raw_cpu_ptr-instead-of-get_cpu_ptr-fo.patch

@@ -1,7 +1,7 @@
-From 8fdda08777908ad7a6172ce415ec5703f9b0faff Mon Sep 17 00:00:00 2001
+From c120a8611a24911e2fecf862bbe3ae2579ccbcc2 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Thu, 21 Sep 2017 17:21:40 +0200
-Subject: [PATCH 060/414] iommu/iova: Use raw_cpu_ptr() instead of
+Subject: [PATCH 060/413] iommu/iova: Use raw_cpu_ptr() instead of
  get_cpu_ptr() for ->fq
 
 get_cpu_ptr() disabled preemption and returns the ->fq object of the

kernel/patches-4.14.x-rt/0061-greybus-audio-don-t-inclide-rwlock.h-directly.patch

@@ -1,7 +1,7 @@
-From ff6ce9f69a7f509c0e10bd78c0dc1d9bacde185a Mon Sep 17 00:00:00 2001
+From b5f1bb4aa1185c26be47996d4bf22239070b4e3b Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Thu, 5 Oct 2017 14:38:52 +0200
-Subject: [PATCH 061/414] greybus: audio: don't inclide rwlock.h directly.
+Subject: [PATCH 061/413] greybus: audio: don't inclide rwlock.h directly.
 
 rwlock.h should not be included directly. Instead linux/splinlock.h
 should be included. One thing it does is to break the RT build.

kernel/patches-4.14.x-rt/0062-xen-9pfs-don-t-inclide-rwlock.h-directly.patch

@@ -1,7 +1,7 @@
-From 57aadd3335c145d39a4e3ced1de6e220f793e224 Mon Sep 17 00:00:00 2001
+From 59713b0380114cd3191016cd76a177fddd7803bc Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Thu, 5 Oct 2017 14:38:52 +0200
-Subject: [PATCH 062/414] xen/9pfs: don't inclide rwlock.h directly.
+Subject: [PATCH 062/413] xen/9pfs: don't inclide rwlock.h directly.
 
 rwlock.h should not be included directly. Instead linux/splinlock.h
 should be included. One thing it does is to break the RT build.

kernel/patches-4.14.x-rt/0063-drm-i915-properly-init-lockdep-class.patch

@@ -1,7 +1,7 @@
-From d3d5a7b7f58b32f9c1418d8350a895c3e130a54b Mon Sep 17 00:00:00 2001
+From b6275ffe0ac1a982ef49d560bf8d14b98eec055b Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Thu, 30 Nov 2017 16:06:13 +0100
-Subject: [PATCH 063/414] drm/i915: properly init lockdep class
+Subject: [PATCH 063/413] drm/i915: properly init lockdep class
 
 The code has an ifdef and uses two functions to either init the bare
 spinlock or init it and set a lock-class. It is possible to do the same

kernel/patches-4.14.x-rt/0064-timerqueue-Document-return-values-of-timerqueue_add-.patch

@@ -1,7 +1,7 @@
-From 8ec366eaf670a24ee71b4c406d6526e0055da290 Mon Sep 17 00:00:00 2001
+From 58ab0f67ec601164cce1d01624202a38dd4d1c66 Mon Sep 17 00:00:00 2001
 From: Thomas Gleixner <tglx@linutronix.de>
 Date: Fri, 22 Dec 2017 15:51:15 +0100
-Subject: [PATCH 064/414] timerqueue: Document return values of
+Subject: [PATCH 064/413] timerqueue: Document return values of
  timerqueue_add/del()
 
 The return values of timerqueue_add/del() are not documented in the kernel doc

kernel/patches-4.14.x-rt/0065-sparc64-use-generic-rwsem-spinlocks-rt.patch

@@ -1,7 +1,7 @@
-From d6d57ba863defd4ff1388c7dcc8323925065347b Mon Sep 17 00:00:00 2001
+From a038ba15d573f92bc217dad93dc4b1399b1288a0 Mon Sep 17 00:00:00 2001
 From: Allen Pais <allen.pais@oracle.com>
 Date: Fri, 13 Dec 2013 09:44:41 +0530
-Subject: [PATCH 065/414] sparc64: use generic rwsem spinlocks rt
+Subject: [PATCH 065/413] sparc64: use generic rwsem spinlocks rt
 
 Signed-off-by: Allen Pais <allen.pais@oracle.com>
 Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>

kernel/patches-4.14.x-rt/0066-kernel-SRCU-provide-a-static-initializer.patch

@@ -1,7 +1,7 @@
-From b3f979f24ccd48b0c93d73294c35380c42bcd39d Mon Sep 17 00:00:00 2001
+From 76cc7af748db49faf5d5215d6e7c3e3a9278eb2b Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Tue, 19 Mar 2013 14:44:30 +0100
-Subject: [PATCH 066/414] kernel/SRCU: provide a static initializer
+Subject: [PATCH 066/413] kernel/SRCU: provide a static initializer
 
 There are macros for static initializer for the three out of four
 possible notifier types, that are:

kernel/patches-4.14.x-rt/0067-target-drop-spin_lock_assert-irqs_disabled-combo-che.patch

@@ -1,7 +1,7 @@
-From d05bcd29edaa799b4225174339015b255c66a2a4 Mon Sep 17 00:00:00 2001
+From d2ec59058e734354ec4b8374a79bc7fa2325be87 Mon Sep 17 00:00:00 2001
 From: "bigeasy@linutronix.de" <bigeasy@linutronix.de>
 Date: Fri, 23 Mar 2018 18:17:36 +0100
-Subject: [PATCH 067/414] target: drop spin_lock_assert() + irqs_disabled()
+Subject: [PATCH 067/413] target: drop spin_lock_assert() + irqs_disabled()
  combo checks
 
 There are a few functions which check for if the lock is held

kernel/patches-4.14.x-rt/0068-kernel-sched-Provide-a-pointer-to-the-valid-CPU-mask.patch

@@ -1,7 +1,7 @@
-From 1a58613ad9bf0d2488507ae6733e7cbb69853812 Mon Sep 17 00:00:00 2001
+From d7c5c11bebb377880836dbca53cd81aca444b56a Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Tue, 4 Apr 2017 12:50:16 +0200
-Subject: [PATCH 068/414] kernel: sched: Provide a pointer to the valid CPU
+Subject: [PATCH 068/413] kernel: sched: Provide a pointer to the valid CPU
  mask
 MIME-Version: 1.0
 Content-Type: text/plain; charset=UTF-8
@@ -361,10 +361,10 @@ index 4657e2924ecb..7bb7384b543a 100644
  }
  
 diff --git a/kernel/fork.c b/kernel/fork.c
-index 98c91bd341b4..04c3ebd7a9a9 100644
+index 91907a3701ce..d146f616bf9e 100644
 --- a/kernel/fork.c
 +++ b/kernel/fork.c
-@@ -564,7 +564,8 @@ static struct task_struct *dup_task_struct(struct task_struct *orig, int node)
+@@ -563,7 +563,8 @@ static struct task_struct *dup_task_struct(struct task_struct *orig, int node)
  #ifdef CONFIG_CC_STACKPROTECTOR
  	tsk->stack_canary = get_random_canary();
  #endif
@@ -375,7 +375,7 @@ index 98c91bd341b4..04c3ebd7a9a9 100644
  	 * One for us, one for whoever does the "release_task()" (usually
  	 * parent)
 diff --git a/kernel/sched/core.c b/kernel/sched/core.c
-index 31615d1ae44c..d5d8244d780b 100644
+index 4e89ed8a0fb2..f2d6db386613 100644
 --- a/kernel/sched/core.c
 +++ b/kernel/sched/core.c
 @@ -912,7 +912,7 @@ static inline bool is_per_cpu_kthread(struct task_struct *p)
@@ -613,7 +613,7 @@ index 501f17c642ab..a55cb8ce395d 100644
  				     !dl_task(task) ||
  				     !task_on_rq_queued(task))) {
 diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
-index 5c09ddf8c832..d1916d33f7ff 100644
+index 0cc7098c6dfd..4388c2b26f70 100644
 --- a/kernel/sched/fair.c
 +++ b/kernel/sched/fair.c
 @@ -1596,7 +1596,7 @@ static void task_numa_compare(struct task_numa_env *env,
@@ -652,7 +652,7 @@ index 5c09ddf8c832..d1916d33f7ff 100644
  		if (idle_cpu(i)) {
  			struct rq *rq = cpu_rq(i);
  			struct cpuidle_state *idle = idle_get_state(rq);
-@@ -5697,7 +5697,7 @@ static int select_idle_core(struct task_struct *p, struct sched_domain *sd, int
+@@ -5698,7 +5698,7 @@ static int select_idle_core(struct task_struct *p, struct sched_domain *sd, int
  	if (!test_idle_cores(target, false))
  		return -1;
  
@@ -661,7 +661,7 @@ index 5c09ddf8c832..d1916d33f7ff 100644
  
  	for_each_cpu_wrap(core, cpus, target) {
  		bool idle = true;
-@@ -5731,7 +5731,7 @@ static int select_idle_smt(struct task_struct *p, struct sched_domain *sd, int t
+@@ -5732,7 +5732,7 @@ static int select_idle_smt(struct task_struct *p, struct sched_domain *sd, int t
  		return -1;
  
  	for_each_cpu(cpu, cpu_smt_mask(target)) {
@@ -670,7 +670,7 @@ index 5c09ddf8c832..d1916d33f7ff 100644
  			continue;
  		if (idle_cpu(cpu))
  			return cpu;
-@@ -5794,7 +5794,7 @@ static int select_idle_cpu(struct task_struct *p, struct sched_domain *sd, int t
+@@ -5795,7 +5795,7 @@ static int select_idle_cpu(struct task_struct *p, struct sched_domain *sd, int t
  	for_each_cpu_wrap(cpu, sched_domain_span(sd), target) {
  		if (!--nr)
  			return -1;
@@ -679,7 +679,7 @@ index 5c09ddf8c832..d1916d33f7ff 100644
  			continue;
  		if (idle_cpu(cpu))
  			break;
-@@ -5949,7 +5949,7 @@ select_task_rq_fair(struct task_struct *p, int prev_cpu, int sd_flag, int wake_f
+@@ -5950,7 +5950,7 @@ select_task_rq_fair(struct task_struct *p, int prev_cpu, int sd_flag, int wake_f
  	if (sd_flag & SD_BALANCE_WAKE) {
  		record_wakee(p);
  		want_affine = !wake_wide(p) && !wake_cap(p, cpu, prev_cpu)
@@ -688,7 +688,7 @@ index 5c09ddf8c832..d1916d33f7ff 100644
  	}
  
  	rcu_read_lock();
-@@ -6698,14 +6698,14 @@ int can_migrate_task(struct task_struct *p, struct lb_env *env)
+@@ -6699,14 +6699,14 @@ int can_migrate_task(struct task_struct *p, struct lb_env *env)
  	/*
  	 * We do not migrate tasks that are:
  	 * 1) throttled_lb_pair, or
@@ -705,7 +705,7 @@ index 5c09ddf8c832..d1916d33f7ff 100644
  		int cpu;
  
  		schedstat_inc(p->se.statistics.nr_failed_migrations_affine);
-@@ -6725,7 +6725,7 @@ int can_migrate_task(struct task_struct *p, struct lb_env *env)
+@@ -6726,7 +6726,7 @@ int can_migrate_task(struct task_struct *p, struct lb_env *env)
  
  		/* Prevent to re-select dst_cpu via env's cpus */
  		for_each_cpu_and(cpu, env->dst_grpmask, env->cpus) {
@@ -714,7 +714,7 @@ index 5c09ddf8c832..d1916d33f7ff 100644
  				env->flags |= LBF_DST_PINNED;
  				env->new_dst_cpu = cpu;
  				break;
-@@ -7294,7 +7294,7 @@ check_cpu_capacity(struct rq *rq, struct sched_domain *sd)
+@@ -7295,7 +7295,7 @@ check_cpu_capacity(struct rq *rq, struct sched_domain *sd)
  
  /*
   * Group imbalance indicates (and tries to solve) the problem where balancing
@@ -723,7 +723,7 @@ index 5c09ddf8c832..d1916d33f7ff 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.
-@@ -7870,7 +7870,7 @@ static struct sched_group *find_busiest_group(struct lb_env *env)
+@@ -7871,7 +7871,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
@@ -732,7 +732,7 @@ index 5c09ddf8c832..d1916d33f7ff 100644
  	 */
  	if (busiest->group_type == group_imbalanced)
  		goto force_balance;
-@@ -8262,7 +8262,7 @@ static int load_balance(int this_cpu, struct rq *this_rq,
+@@ -8263,7 +8263,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
  			 */

kernel/patches-4.14.x-rt/0069-kernel-sched-core-add-migrate_disable.patch

@@ -1,7 +1,7 @@
-From 3d187a141e0e95a0e5e378f67dfc05ddad388e0f Mon Sep 17 00:00:00 2001
+From 9d513f6df015915b0bb5c92f1f36c914b5918824 Mon Sep 17 00:00:00 2001
 From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
 Date: Sat, 27 May 2017 19:02:06 +0200
-Subject: [PATCH 069/414] kernel/sched/core: add migrate_disable()
+Subject: [PATCH 069/413] kernel/sched/core: add migrate_disable()
 
 ---
  include/linux/preempt.h |  23 +++++++
@@ -85,7 +85,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 d5d8244d780b..f62dd754def1 100644
+index f2d6db386613..40a07276d5a3 100644
 --- a/kernel/sched/core.c
 +++ b/kernel/sched/core.c
 @@ -1042,7 +1042,15 @@ void set_cpus_allowed_common(struct task_struct *p, const struct cpumask *new_ma
@@ -144,7 +144,7 @@ index d5d8244d780b..f62dd754def1 100644
  	dest_cpu = cpumask_any_and(cpu_valid_mask, new_mask);
  	if (task_running(rq, p) || p->state == TASK_WAKING) {
  		struct migration_arg arg = { p, dest_cpu };
-@@ -6762,3 +6791,100 @@ const u32 sched_prio_to_wmult[40] = {
+@@ -6756,3 +6785,100 @@ const u32 sched_prio_to_wmult[40] = {
   /*  10 */  39045157,  49367440,  61356676,  76695844,  95443717,
   /*  15 */ 119304647, 148102320, 186737708, 238609294, 286331153,
  };

kernel/patches-4.14.x-rt/0070-tracing-Reverse-the-order-of-trace_types_lock-and-ev.patch

@@ -1,7 +1,7 @@
-From 40be7b1c2167a4798c6c84cd1c8a059efe5025d1 Mon Sep 17 00:00:00 2001
+From cd42f05eb5aae88394b423c9f216321cfefac5db Mon Sep 17 00:00:00 2001
 From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
 Date: Thu, 21 Sep 2017 16:22:49 -0400
-Subject: [PATCH 070/414] tracing: Reverse the order of trace_types_lock and
+Subject: [PATCH 070/413] tracing: Reverse the order of trace_types_lock and
  event_mutex
 
 In order to make future changes where we need to call
@@ -22,10 +22,10 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
  2 files changed, 20 insertions(+), 16 deletions(-)
 
 diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
-index e268750bd4ad..26ec13580069 100644
+index 20919489883f..c3d9b89a8267 100644
 --- a/kernel/trace/trace.c
 +++ b/kernel/trace/trace.c
-@@ -7671,6 +7671,7 @@ static int instance_mkdir(const char *name)
+@@ -7677,6 +7677,7 @@ static int instance_mkdir(const char *name)
  	struct trace_array *tr;
  	int ret;
  
@@ -33,7 +33,7 @@ index e268750bd4ad..26ec13580069 100644
  	mutex_lock(&trace_types_lock);
  
  	ret = -EEXIST;
-@@ -7726,6 +7727,7 @@ static int instance_mkdir(const char *name)
+@@ -7732,6 +7733,7 @@ static int instance_mkdir(const char *name)
  	list_add(&tr->list, &ftrace_trace_arrays);
  
  	mutex_unlock(&trace_types_lock);
@@ -41,7 +41,7 @@ index e268750bd4ad..26ec13580069 100644
  
  	return 0;
  
-@@ -7737,6 +7739,7 @@ static int instance_mkdir(const char *name)
+@@ -7743,6 +7745,7 @@ static int instance_mkdir(const char *name)
  
   out_unlock:
  	mutex_unlock(&trace_types_lock);
@@ -49,7 +49,7 @@ index e268750bd4ad..26ec13580069 100644
  
  	return ret;
  
-@@ -7749,6 +7752,7 @@ static int instance_rmdir(const char *name)
+@@ -7755,6 +7758,7 @@ static int instance_rmdir(const char *name)
  	int ret;
  	int i;
  
@@ -57,7 +57,7 @@ index e268750bd4ad..26ec13580069 100644
  	mutex_lock(&trace_types_lock);
  
  	ret = -ENODEV;
-@@ -7794,6 +7798,7 @@ static int instance_rmdir(const char *name)
+@@ -7800,6 +7804,7 @@ static int instance_rmdir(const char *name)
  
   out_unlock:
  	mutex_unlock(&trace_types_lock);

kernel/patches-4.14.x-rt/0071-ring-buffer-Rewrite-trace_recursive_-un-lock-to-be-s.patch

@@ -1,7 +1,7 @@
-From 09a24cd34c2b11f8fd56430f66f86f4ae2eae03c Mon Sep 17 00:00:00 2001
+From bd51d40fd53281d79e88bb1bd96a9a3b58fd89f9 Mon Sep 17 00:00:00 2001
 From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
 Date: Fri, 22 Sep 2017 16:59:02 -0400
-Subject: [PATCH 071/414] ring-buffer: Rewrite trace_recursive_(un)lock() to be
+Subject: [PATCH 071/413] ring-buffer: Rewrite trace_recursive_(un)lock() to be
  simpler
 
 The current method to prevent the ring buffer from entering into a recursize
@@ -28,7 +28,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
  1 file changed, 17 insertions(+), 47 deletions(-)
 
 diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
-index 36f018b15392..29bad749560a 100644
+index fd7809004297..c3b6b47fd44a 100644
 --- a/kernel/trace/ring_buffer.c
 +++ b/kernel/trace/ring_buffer.c
 @@ -2545,61 +2545,29 @@ rb_wakeups(struct ring_buffer *buffer, struct ring_buffer_per_cpu *cpu_buffer)

kernel/patches-4.14.x-rt/0072-tracing-Remove-lookups-from-tracing_map-hitcount.patch

@@ -1,7 +1,7 @@
-From c00d7b1f0af177496a3f9e87952bc632ed961af7 Mon Sep 17 00:00:00 2001
+From 1df3ab2ba2d95d9623be62bcc4eb8e54837a00c1 Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Fri, 22 Sep 2017 14:58:18 -0500
-Subject: [PATCH 072/414] tracing: Remove lookups from tracing_map hitcount
+Subject: [PATCH 072/413] tracing: Remove lookups from tracing_map hitcount
 
 Lookups inflate the hitcount, making it essentially useless.  Only
 inserts and updates should really affect the hitcount anyway, so

kernel/patches-4.14.x-rt/0073-tracing-Increase-tracing-map-KEYS_MAX-size.patch

@@ -1,7 +1,7 @@
-From 9cd219e6bbcfbb790039a30af4a0fe80c84a2d6c Mon Sep 17 00:00:00 2001
+From 20520cafc810815c7b14dc1257ed12729b378f54 Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Fri, 22 Sep 2017 14:58:19 -0500
-Subject: [PATCH 073/414] tracing: Increase tracing map KEYS_MAX size
+Subject: [PATCH 073/413] tracing: Increase tracing map KEYS_MAX size
 
 The current default for the number of subkeys in a compound key is 2,
 which is too restrictive.  Increase it to a more realistic value of 3.

kernel/patches-4.14.x-rt/0074-tracing-Make-traceprobe-parsing-code-reusable.patch

@@ -1,7 +1,7 @@
-From b64a31d00a26eafa511f2aa7b28416d42459fe0f Mon Sep 17 00:00:00 2001
+From 272b77138a9e6e7785e46cac33ed5badfe04d601 Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Fri, 22 Sep 2017 14:58:20 -0500
-Subject: [PATCH 074/414] tracing: Make traceprobe parsing code reusable
+Subject: [PATCH 074/413] tracing: Make traceprobe parsing code reusable
 
 traceprobe_probes_write() and traceprobe_command() actually contain
 nothing that ties them to kprobes - the code is generically useful for
@@ -28,10 +28,10 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
  6 files changed, 103 insertions(+), 103 deletions(-)
 
 diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
-index 26ec13580069..5aea670a9b7e 100644
+index c3d9b89a8267..99b415e5cd11 100644
 --- a/kernel/trace/trace.c
 +++ b/kernel/trace/trace.c
-@@ -8265,6 +8265,92 @@ void ftrace_dump(enum ftrace_dump_mode oops_dump_mode)
+@@ -8271,6 +8271,92 @@ void ftrace_dump(enum ftrace_dump_mode oops_dump_mode)
  }
  EXPORT_SYMBOL_GPL(ftrace_dump);
  
@@ -143,10 +143,10 @@ index 851cd1605085..221591636530 100644
   * Normal trace_printk() and friends allocates special buffers
   * to do the manipulation, as well as saves the print formats
 diff --git a/kernel/trace/trace_kprobe.c b/kernel/trace/trace_kprobe.c
-index f8d3bd974bcc..1f8b72d82ad9 100644
+index ea20274a105a..3c40d4174052 100644
 --- a/kernel/trace/trace_kprobe.c
 +++ b/kernel/trace/trace_kprobe.c
-@@ -907,8 +907,8 @@ static int probes_open(struct inode *inode, struct file *file)
+@@ -918,8 +918,8 @@ static int probes_open(struct inode *inode, struct file *file)
  static ssize_t probes_write(struct file *file, const char __user *buffer,
  			    size_t count, loff_t *ppos)
  {
@@ -157,7 +157,7 @@ index f8d3bd974bcc..1f8b72d82ad9 100644
  }
  
  static const struct file_operations kprobe_events_ops = {
-@@ -1433,9 +1433,9 @@ static __init int kprobe_trace_self_tests_init(void)
+@@ -1444,9 +1444,9 @@ static __init int kprobe_trace_self_tests_init(void)
  
  	pr_info("Testing kprobe tracing: ");
  
@@ -170,7 +170,7 @@ index f8d3bd974bcc..1f8b72d82ad9 100644
  	if (WARN_ON_ONCE(ret)) {
  		pr_warn("error on probing function entry.\n");
  		warn++;
-@@ -1455,8 +1455,8 @@ static __init int kprobe_trace_self_tests_init(void)
+@@ -1466,8 +1466,8 @@ static __init int kprobe_trace_self_tests_init(void)
  		}
  	}
  
@@ -181,7 +181,7 @@ index f8d3bd974bcc..1f8b72d82ad9 100644
  	if (WARN_ON_ONCE(ret)) {
  		pr_warn("error on probing function return.\n");
  		warn++;
-@@ -1526,13 +1526,13 @@ static __init int kprobe_trace_self_tests_init(void)
+@@ -1537,13 +1537,13 @@ static __init int kprobe_trace_self_tests_init(void)
  			disable_trace_kprobe(tk, file);
  	}
  

kernel/patches-4.14.x-rt/0075-tracing-Clean-up-hist_field_flags-enum.patch

@@ -1,7 +1,7 @@
-From cc804e77781f5e47c444176f0a871549a0f25492 Mon Sep 17 00:00:00 2001
+From 7aa3241e49aeb877d3b6db85db821702a5c87b7b Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Fri, 22 Sep 2017 14:58:21 -0500
-Subject: [PATCH 075/414] tracing: Clean up hist_field_flags enum
+Subject: [PATCH 075/413] tracing: Clean up hist_field_flags enum
 
 As we add more flags, specifying explicit integers for the flag values
 becomes more unwieldy and error-prone - switch them over to left-shift

kernel/patches-4.14.x-rt/0076-tracing-Add-hist_field_name-accessor.patch

@@ -1,7 +1,7 @@
-From 2a62bdf95f1c277759cae29536ab66e885943504 Mon Sep 17 00:00:00 2001
+From 1d446035c5e9360d34385d7a9925752c12afd229 Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Fri, 22 Sep 2017 14:58:22 -0500
-Subject: [PATCH 076/414] tracing: Add hist_field_name() accessor
+Subject: [PATCH 076/413] tracing: Add hist_field_name() accessor
 
 In preparation for hist_fields that won't be strictly based on
 trace_event_fields, add a new hist_field_name() accessor to allow that

kernel/patches-4.14.x-rt/0077-tracing-Reimplement-log2.patch

@@ -1,7 +1,7 @@
-From 9fd54977344b5c297402ac7f6cf443e700716eff Mon Sep 17 00:00:00 2001
+From 24c189923ec2a18ec59f026a61de134ab839fc8a Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Fri, 22 Sep 2017 14:58:23 -0500
-Subject: [PATCH 077/414] tracing: Reimplement log2
+Subject: [PATCH 077/413] tracing: Reimplement log2
 
 log2 as currently implemented applies only to u64 trace_event_field
 derived fields, and assumes that anything it's applied to is a u64

kernel/patches-4.14.x-rt/0078-tracing-Move-hist-trigger-Documentation-to-histogram.patch

@@ -1,7 +1,7 @@
-From a4ed86cabdf2c718ad372bf20e04a55b78065622 Mon Sep 17 00:00:00 2001
+From dcc5cc2dd6f46960cd168e8329c85d33cc500cc6 Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:35 -0600
-Subject: [PATCH 078/414] tracing: Move hist trigger Documentation to
+Subject: [PATCH 078/413] tracing: Move hist trigger Documentation to
  histogram.txt
 
 The hist trigger Documentation takes up a large part of events.txt -

kernel/patches-4.14.x-rt/0079-tracing-Add-Documentation-for-log2-modifier.patch

@@ -1,7 +1,7 @@
-From e43a043fd5f52fca34d9e4f66b8ed112bf069d9b Mon Sep 17 00:00:00 2001
+From 90ec131e92fd943ca8250811af309bf97438c17f Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:36 -0600
-Subject: [PATCH 079/414] tracing: Add Documentation for log2 modifier
+Subject: [PATCH 079/413] tracing: Add Documentation for log2 modifier
 
 Add a line for the log2 modifier, to keep it aligned with
 tracing/README.

kernel/patches-4.14.x-rt/0080-tracing-Add-support-to-detect-and-avoid-duplicates.patch

@@ -1,7 +1,7 @@
-From 390fbcbd4c9d4dc44196020c7a094f0fc98a32fb Mon Sep 17 00:00:00 2001
+From 004c8777f5674a0e505eae0860dbb9c007a3b428 Mon Sep 17 00:00:00 2001
 From: Vedang Patel <vedang.patel@intel.com>
 Date: Mon, 15 Jan 2018 20:51:37 -0600
-Subject: [PATCH 080/414] tracing: Add support to detect and avoid duplicates
+Subject: [PATCH 080/413] tracing: Add support to detect and avoid duplicates
 
 A duplicate in the tracing_map hash table is when 2 different entries
 have the same key and, as a result, the key_hash. This is possible due

kernel/patches-4.14.x-rt/0081-tracing-Remove-code-which-merges-duplicates.patch

@@ -1,7 +1,7 @@
-From bdfbdb272b3738f1c7c94af976c1441d33290db9 Mon Sep 17 00:00:00 2001
+From 31f4fd0e513378bc4d9b302657fa4ce577e4e27e Mon Sep 17 00:00:00 2001
 From: Vedang Patel <vedang.patel@intel.com>
 Date: Mon, 15 Jan 2018 20:51:38 -0600
-Subject: [PATCH 081/414] tracing: Remove code which merges duplicates
+Subject: [PATCH 081/413] tracing: Remove code which merges duplicates
 
 We now have the logic to detect and remove duplicates in the
 tracing_map hash table. The code which merges duplicates in the

kernel/patches-4.14.x-rt/0082-ring-buffer-Add-interface-for-setting-absolute-time-.patch

@@ -1,7 +1,7 @@
-From 06f1ea65611d18c2fce8e1c4fed1671f95d35702 Mon Sep 17 00:00:00 2001
+From 340a244f82269fcefc375632ede3243326f403ee Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:39 -0600
-Subject: [PATCH 082/414] ring-buffer: Add interface for setting absolute time
+Subject: [PATCH 082/413] ring-buffer: Add interface for setting absolute time
  stamps
 
 Define a new function, tracing_set_time_stamp_abs(), which can be used
@@ -26,10 +26,10 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
  4 files changed, 48 insertions(+), 1 deletion(-)
 
 diff --git a/include/linux/ring_buffer.h b/include/linux/ring_buffer.h
-index 289e4d54e3e0..42b626aa88c7 100644
+index 5caa062a02b2..adffb56bae8f 100644
 --- a/include/linux/ring_buffer.h
 +++ b/include/linux/ring_buffer.h
-@@ -178,6 +178,8 @@ void ring_buffer_normalize_time_stamp(struct ring_buffer *buffer,
+@@ -179,6 +179,8 @@ void ring_buffer_normalize_time_stamp(struct ring_buffer *buffer,
  				      int cpu, u64 *ts);
  void ring_buffer_set_clock(struct ring_buffer *buffer,
  			   u64 (*clock)(void));
@@ -39,7 +39,7 @@ index 289e4d54e3e0..42b626aa88c7 100644
  size_t ring_buffer_page_len(void *page);
  
 diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
-index 29bad749560a..2be361b63c7b 100644
+index c3b6b47fd44a..dc6f47802d02 100644
 --- a/kernel/trace/ring_buffer.c
 +++ b/kernel/trace/ring_buffer.c
 @@ -488,6 +488,7 @@ struct ring_buffer {
@@ -68,10 +68,10 @@ index 29bad749560a..2be361b63c7b 100644
  
  static inline unsigned long rb_page_entries(struct buffer_page *bpage)
 diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
-index 5aea670a9b7e..f75eb0df7dd9 100644
+index 99b415e5cd11..e64ba2addfe7 100644
 --- a/kernel/trace/trace.c
 +++ b/kernel/trace/trace.c
-@@ -2269,7 +2269,7 @@ trace_event_buffer_lock_reserve(struct ring_buffer **current_rb,
+@@ -2275,7 +2275,7 @@ trace_event_buffer_lock_reserve(struct ring_buffer **current_rb,
  
  	*current_rb = trace_file->tr->trace_buffer.buffer;
  
@@ -80,7 +80,7 @@ index 5aea670a9b7e..f75eb0df7dd9 100644
  	     (EVENT_FILE_FL_SOFT_DISABLED | EVENT_FILE_FL_FILTERED)) &&
  	    (entry = this_cpu_read(trace_buffered_event))) {
  		/* Try to use the per cpu buffer first */
-@@ -6287,6 +6287,37 @@ static int tracing_clock_open(struct inode *inode, struct file *file)
+@@ -6293,6 +6293,37 @@ static int tracing_clock_open(struct inode *inode, struct file *file)
  	return ret;
  }
  

kernel/patches-4.14.x-rt/0083-ring-buffer-Redefine-the-unimplemented-RINGBUF_TYPE_.patch

@@ -1,7 +1,7 @@
-From 9f67e02e27ed28e415ea0e2b36e3ed12113bdb37 Mon Sep 17 00:00:00 2001
+From 84238420757684f86aa07eca0f5fc81fffdaeb27 Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:40 -0600
-Subject: [PATCH 083/414] ring-buffer: Redefine the unimplemented
+Subject: [PATCH 083/413] ring-buffer: Redefine the unimplemented
  RINGBUF_TYPE_TIME_STAMP
 
 RINGBUF_TYPE_TIME_STAMP is defined but not used, and from what I can
@@ -33,7 +33,7 @@ Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
  2 files changed, 83 insertions(+), 33 deletions(-)
 
 diff --git a/include/linux/ring_buffer.h b/include/linux/ring_buffer.h
-index 42b626aa88c7..b37a5df05e81 100644
+index adffb56bae8f..6c2a6b3f3c6d 100644
 --- a/include/linux/ring_buffer.h
 +++ b/include/linux/ring_buffer.h
 @@ -34,10 +34,12 @@ struct ring_buffer_event {
@@ -68,7 +68,7 @@ index 42b626aa88c7..b37a5df05e81 100644
  /*
   * ring_buffer_discard_commit will remove an event that has not
 diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
-index 2be361b63c7b..e48989ff0427 100644
+index dc6f47802d02..a9cb4359c280 100644
 --- a/kernel/trace/ring_buffer.c
 +++ b/kernel/trace/ring_buffer.c
 @@ -41,6 +41,8 @@ int ring_buffer_print_entry_header(struct trace_seq *s)
@@ -230,7 +230,7 @@ index 2be361b63c7b..e48989ff0427 100644
  		info.delta = diff;
  		if (unlikely(test_time_stamp(info.delta)))
  			rb_handle_timestamp(cpu_buffer, &info);
-@@ -3424,14 +3459,13 @@ rb_update_read_stamp(struct ring_buffer_per_cpu *cpu_buffer,
+@@ -3440,14 +3475,13 @@ rb_update_read_stamp(struct ring_buffer_per_cpu *cpu_buffer,
  		return;
  
  	case RINGBUF_TYPE_TIME_EXTEND:
@@ -248,7 +248,7 @@ index 2be361b63c7b..e48989ff0427 100644
  		return;
  
  	case RINGBUF_TYPE_DATA:
-@@ -3455,14 +3489,13 @@ rb_update_iter_read_stamp(struct ring_buffer_iter *iter,
+@@ -3471,14 +3505,13 @@ rb_update_iter_read_stamp(struct ring_buffer_iter *iter,
  		return;
  
  	case RINGBUF_TYPE_TIME_EXTEND:
@@ -266,7 +266,7 @@ index 2be361b63c7b..e48989ff0427 100644
  		return;
  
  	case RINGBUF_TYPE_DATA:
-@@ -3686,6 +3719,8 @@ rb_buffer_peek(struct ring_buffer_per_cpu *cpu_buffer, u64 *ts,
+@@ -3702,6 +3735,8 @@ rb_buffer_peek(struct ring_buffer_per_cpu *cpu_buffer, u64 *ts,
  	struct buffer_page *reader;
  	int nr_loops = 0;
  
@@ -275,7 +275,7 @@ index 2be361b63c7b..e48989ff0427 100644
   again:
  	/*
  	 * We repeat when a time extend is encountered.
-@@ -3722,12 +3757,17 @@ rb_buffer_peek(struct ring_buffer_per_cpu *cpu_buffer, u64 *ts,
+@@ -3738,12 +3773,17 @@ rb_buffer_peek(struct ring_buffer_per_cpu *cpu_buffer, u64 *ts,
  		goto again;
  
  	case RINGBUF_TYPE_TIME_STAMP:
@@ -295,7 +295,7 @@ index 2be361b63c7b..e48989ff0427 100644
  			*ts = cpu_buffer->read_stamp + event->time_delta;
  			ring_buffer_normalize_time_stamp(cpu_buffer->buffer,
  							 cpu_buffer->cpu, ts);
-@@ -3752,6 +3792,9 @@ rb_iter_peek(struct ring_buffer_iter *iter, u64 *ts)
+@@ -3768,6 +3808,9 @@ rb_iter_peek(struct ring_buffer_iter *iter, u64 *ts)
  	struct ring_buffer_event *event;
  	int nr_loops = 0;
  
@@ -305,7 +305,7 @@ index 2be361b63c7b..e48989ff0427 100644
  	cpu_buffer = iter->cpu_buffer;
  	buffer = cpu_buffer->buffer;
  
-@@ -3804,12 +3847,17 @@ rb_iter_peek(struct ring_buffer_iter *iter, u64 *ts)
+@@ -3820,12 +3863,17 @@ rb_iter_peek(struct ring_buffer_iter *iter, u64 *ts)
  		goto again;
  
  	case RINGBUF_TYPE_TIME_STAMP:

kernel/patches-4.14.x-rt/0084-tracing-Add-timestamp_mode-trace-file.patch

@@ -1,7 +1,7 @@
-From 15e2d254eb4b12f827423744fe5e69ce42507f2c Mon Sep 17 00:00:00 2001
+From 91cf6512ab5c35ffa8de75ccea423edd949d0bf2 Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:41 -0600
-Subject: [PATCH 084/414] tracing: Add timestamp_mode trace file
+Subject: [PATCH 084/413] tracing: Add timestamp_mode trace file
 
 Add a new option flag indicating whether or not the ring buffer is in
 'absolute timestamp' mode.
@@ -62,10 +62,10 @@ index d4601df6e72e..54213e5c23f6 100644
  
  	Directory for the Hardware Latency Detector.
 diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
-index f75eb0df7dd9..ed50ecb0592b 100644
+index e64ba2addfe7..b101ccf0b9fb 100644
 --- a/kernel/trace/trace.c
 +++ b/kernel/trace/trace.c
-@@ -4520,6 +4520,9 @@ static const char readme_msg[] =
+@@ -4526,6 +4526,9 @@ static const char readme_msg[] =
  #ifdef CONFIG_X86_64
  	"     x86-tsc:   TSC cycle counter\n"
  #endif
@@ -75,7 +75,7 @@ index f75eb0df7dd9..ed50ecb0592b 100644
  	"\n  trace_marker\t\t- Writes into this file writes into the kernel buffer\n"
  	"\n  trace_marker_raw\t\t- Writes into this file writes binary data into the kernel buffer\n"
  	"  tracing_cpumask\t- Limit which CPUs to trace\n"
-@@ -6287,6 +6290,40 @@ static int tracing_clock_open(struct inode *inode, struct file *file)
+@@ -6293,6 +6296,40 @@ static int tracing_clock_open(struct inode *inode, struct file *file)
  	return ret;
  }
  
@@ -116,7 +116,7 @@ index f75eb0df7dd9..ed50ecb0592b 100644
  int tracing_set_time_stamp_abs(struct trace_array *tr, bool abs)
  {
  	int ret = 0;
-@@ -6565,6 +6602,13 @@ static const struct file_operations trace_clock_fops = {
+@@ -6571,6 +6608,13 @@ static const struct file_operations trace_clock_fops = {
  	.write		= tracing_clock_write,
  };
  
@@ -130,7 +130,7 @@ index f75eb0df7dd9..ed50ecb0592b 100644
  #ifdef CONFIG_TRACER_SNAPSHOT
  static const struct file_operations snapshot_fops = {
  	.open		= tracing_snapshot_open,
-@@ -7887,6 +7931,9 @@ init_tracer_tracefs(struct trace_array *tr, struct dentry *d_tracer)
+@@ -7893,6 +7937,9 @@ init_tracer_tracefs(struct trace_array *tr, struct dentry *d_tracer)
  	trace_create_file("tracing_on", 0644, d_tracer,
  			  tr, &rb_simple_fops);
  

kernel/patches-4.14.x-rt/0085-tracing-Give-event-triggers-access-to-ring_buffer_ev.patch

@@ -1,7 +1,7 @@
-From 88ddb6459b76ae7f56abd46e62b976906d96701c Mon Sep 17 00:00:00 2001
+From 794e7fb5827ff40ea3d54b8e4a1ce42d0fec1fc2 Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:42 -0600
-Subject: [PATCH 085/414] tracing: Give event triggers access to
+Subject: [PATCH 085/413] tracing: Give event triggers access to
  ring_buffer_event
 
 The ring_buffer event can provide a timestamp that may be useful to
@@ -137,7 +137,7 @@ index c57e5369b0c2..77079c79b6d4 100644
  
  static struct event_trigger_ops hist_enable_trigger_ops = {
 diff --git a/kernel/trace/trace_events_trigger.c b/kernel/trace/trace_events_trigger.c
-index b413fab7d75b..9dd8b9ce2594 100644
+index 43254c5e7e16..4c269f2e00a4 100644
 --- a/kernel/trace/trace_events_trigger.c
 +++ b/kernel/trace/trace_events_trigger.c
 @@ -63,7 +63,8 @@ void trigger_data_free(struct event_trigger_data *data)
@@ -186,7 +186,7 @@ index b413fab7d75b..9dd8b9ce2594 100644
  	}
  }
  EXPORT_SYMBOL_GPL(event_triggers_post_call);
-@@ -911,7 +912,8 @@ void set_named_trigger_data(struct event_trigger_data *data,
+@@ -915,7 +916,8 @@ void set_named_trigger_data(struct event_trigger_data *data,
  }
  
  static void
@@ -196,7 +196,7 @@ index b413fab7d75b..9dd8b9ce2594 100644
  {
  	if (tracing_is_on())
  		return;
-@@ -920,7 +922,8 @@ traceon_trigger(struct event_trigger_data *data, void *rec)
+@@ -924,7 +926,8 @@ traceon_trigger(struct event_trigger_data *data, void *rec)
  }
  
  static void
@@ -206,7 +206,7 @@ index b413fab7d75b..9dd8b9ce2594 100644
  {
  	if (tracing_is_on())
  		return;
-@@ -935,7 +938,8 @@ traceon_count_trigger(struct event_trigger_data *data, void *rec)
+@@ -939,7 +942,8 @@ traceon_count_trigger(struct event_trigger_data *data, void *rec)
  }
  
  static void
@@ -216,7 +216,7 @@ index b413fab7d75b..9dd8b9ce2594 100644
  {
  	if (!tracing_is_on())
  		return;
-@@ -944,7 +948,8 @@ traceoff_trigger(struct event_trigger_data *data, void *rec)
+@@ -948,7 +952,8 @@ traceoff_trigger(struct event_trigger_data *data, void *rec)
  }
  
  static void
@@ -226,7 +226,7 @@ index b413fab7d75b..9dd8b9ce2594 100644
  {
  	if (!tracing_is_on())
  		return;
-@@ -1041,7 +1046,8 @@ static struct event_command trigger_traceoff_cmd = {
+@@ -1045,7 +1050,8 @@ static struct event_command trigger_traceoff_cmd = {
  
  #ifdef CONFIG_TRACER_SNAPSHOT
  static void
@@ -236,7 +236,7 @@ index b413fab7d75b..9dd8b9ce2594 100644
  {
  	struct trace_event_file *file = data->private_data;
  
-@@ -1052,7 +1058,8 @@ snapshot_trigger(struct event_trigger_data *data, void *rec)
+@@ -1056,7 +1062,8 @@ snapshot_trigger(struct event_trigger_data *data, void *rec)
  }
  
  static void
@@ -246,7 +246,7 @@ index b413fab7d75b..9dd8b9ce2594 100644
  {
  	if (!data->count)
  		return;
-@@ -1060,7 +1067,7 @@ snapshot_count_trigger(struct event_trigger_data *data, void *rec)
+@@ -1064,7 +1071,7 @@ snapshot_count_trigger(struct event_trigger_data *data, void *rec)
  	if (data->count != -1)
  		(data->count)--;
  
@@ -255,7 +255,7 @@ index b413fab7d75b..9dd8b9ce2594 100644
  }
  
  static int
-@@ -1139,13 +1146,15 @@ static __init int register_trigger_snapshot_cmd(void) { return 0; }
+@@ -1143,13 +1150,15 @@ static __init int register_trigger_snapshot_cmd(void) { return 0; }
  #define STACK_SKIP 3
  
  static void
@@ -273,7 +273,7 @@ index b413fab7d75b..9dd8b9ce2594 100644
  {
  	if (!data->count)
  		return;
-@@ -1153,7 +1162,7 @@ stacktrace_count_trigger(struct event_trigger_data *data, void *rec)
+@@ -1157,7 +1166,7 @@ stacktrace_count_trigger(struct event_trigger_data *data, void *rec)
  	if (data->count != -1)
  		(data->count)--;
  
@@ -282,7 +282,7 @@ index b413fab7d75b..9dd8b9ce2594 100644
  }
  
  static int
-@@ -1215,7 +1224,8 @@ static __init void unregister_trigger_traceon_traceoff_cmds(void)
+@@ -1219,7 +1228,8 @@ static __init void unregister_trigger_traceon_traceoff_cmds(void)
  }
  
  static void
@@ -292,7 +292,7 @@ index b413fab7d75b..9dd8b9ce2594 100644
  {
  	struct enable_trigger_data *enable_data = data->private_data;
  
-@@ -1226,7 +1236,8 @@ event_enable_trigger(struct event_trigger_data *data, void *rec)
+@@ -1230,7 +1240,8 @@ event_enable_trigger(struct event_trigger_data *data, void *rec)
  }
  
  static void
@@ -302,7 +302,7 @@ index b413fab7d75b..9dd8b9ce2594 100644
  {
  	struct enable_trigger_data *enable_data = data->private_data;
  
-@@ -1240,7 +1251,7 @@ event_enable_count_trigger(struct event_trigger_data *data, void *rec)
+@@ -1244,7 +1255,7 @@ event_enable_count_trigger(struct event_trigger_data *data, void *rec)
  	if (data->count != -1)
  		(data->count)--;
  

kernel/patches-4.14.x-rt/0086-tracing-Add-ring-buffer-event-param-to-hist-field-fu.patch

@@ -1,7 +1,7 @@
-From e2a4c5f3252c8e72a9f2a7936708cb76bdc67e58 Mon Sep 17 00:00:00 2001
+From 61f2ce425bc32c663a1d89fa603d0dc3906ab88d Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:43 -0600
-Subject: [PATCH 086/414] tracing: Add ring buffer event param to hist field
+Subject: [PATCH 086/413] tracing: Add ring buffer event param to hist field
  functions
 
 Some events such as timestamps require access to a ring_buffer_event

kernel/patches-4.14.x-rt/0087-tracing-Break-out-hist-trigger-assignment-parsing.patch

@@ -1,7 +1,7 @@
-From 8c0e516c256760a737c21d9e830df9d5d586bba8 Mon Sep 17 00:00:00 2001
+From fe44332c3b607f3d93463a5a61faa65eda660a5a Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:44 -0600
-Subject: [PATCH 087/414] tracing: Break out hist trigger assignment parsing
+Subject: [PATCH 087/413] tracing: Break out hist trigger assignment parsing
 
 This will make it easier to add variables, and makes the parsing code
 cleaner regardless.

kernel/patches-4.14.x-rt/0088-tracing-Add-hist-trigger-timestamp-support.patch

@@ -1,7 +1,7 @@
-From f5fc85120c33816190064e90232e0e70723df981 Mon Sep 17 00:00:00 2001
+From da1d8b0719fef4b967e297068245144456a8e3a3 Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:45 -0600
-Subject: [PATCH 088/414] tracing: Add hist trigger timestamp support
+Subject: [PATCH 088/413] tracing: Add hist trigger timestamp support
 
 Add support for a timestamp event field.  This is actually a 'pseudo-'
 event field in that it behaves like it's part of the event record, but

kernel/patches-4.14.x-rt/0089-tracing-Add-per-element-variable-support-to-tracing_.patch

@@ -1,7 +1,7 @@
-From 45a3b7f05299ff169006f2aa6449ecd9de7abbb3 Mon Sep 17 00:00:00 2001
+From d955af7c03a290cac89faa263eaf599af12faa44 Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:46 -0600
-Subject: [PATCH 089/414] tracing: Add per-element variable support to
+Subject: [PATCH 089/413] tracing: Add per-element variable support to
  tracing_map
 
 In order to allow information to be passed between trace events, add

kernel/patches-4.14.x-rt/0090-tracing-Add-hist_data-member-to-hist_field.patch

@@ -1,7 +1,7 @@
-From df2a37f4a941491dde3d94a72010c3504b11ead3 Mon Sep 17 00:00:00 2001
+From 31100a21a9f76a38e09616077600214a62799b53 Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:47 -0600
-Subject: [PATCH 090/414] tracing: Add hist_data member to hist_field
+Subject: [PATCH 090/413] tracing: Add hist_data member to hist_field
 
 Allow hist_data access via hist_field.  Some users of hist_fields
 require or will require more access to the associated hist_data.

kernel/patches-4.14.x-rt/0091-tracing-Add-usecs-modifier-for-hist-trigger-timestam.patch

@@ -1,7 +1,7 @@
-From 2613c3be2bd48363cb6be506c88749dfc3134e8d Mon Sep 17 00:00:00 2001
+From 5aaa61969c551722784944cbb9586c489ca210d7 Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:48 -0600
-Subject: [PATCH 091/414] tracing: Add usecs modifier for hist trigger
+Subject: [PATCH 091/413] tracing: Add usecs modifier for hist trigger
  timestamps
 
 Appending .usecs onto a common_timestamp field will cause the
@@ -41,7 +41,7 @@ index a4143f04a097..25c94730d3fe 100644
    Note that in general the semantics of a given field aren't
    interpreted when applying a modifier to it, but there are some
 diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
-index ed50ecb0592b..3cefb457970e 100644
+index b101ccf0b9fb..49d2457947f5 100644
 --- a/kernel/trace/trace.c
 +++ b/kernel/trace/trace.c
 @@ -1170,6 +1170,14 @@ static struct {
@@ -59,7 +59,7 @@ index ed50ecb0592b..3cefb457970e 100644
  /*
   * trace_parser_get_init - gets the buffer for trace parser
   */
-@@ -4699,8 +4707,9 @@ static const char readme_msg[] =
+@@ -4705,8 +4713,9 @@ static const char readme_msg[] =
  	"\t            .sym        display an address as a symbol\n"
  	"\t            .sym-offset display an address as a symbol and offset\n"
  	"\t            .execname   display a common_pid as a program name\n"

kernel/patches-4.14.x-rt/0092-tracing-Add-variable-support-to-hist-triggers.patch

@@ -1,7 +1,7 @@
-From f2dc1339a756443004b858f819f0ab4fb85ea91a Mon Sep 17 00:00:00 2001
+From e625c5a90ca52df684096746d21dd42d88b7746f Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:49 -0600
-Subject: [PATCH 092/414] tracing: Add variable support to hist triggers
+Subject: [PATCH 092/413] tracing: Add variable support to hist triggers
 
 Add support for saving the value of a current event's event field by
 assigning it to a variable that can be read by a subsequent event.

kernel/patches-4.14.x-rt/0093-tracing-Account-for-variables-in-named-trigger-compa.patch

@@ -1,7 +1,7 @@
-From 00e76e4674dcb08f980b20339bd1e0df0bac774d Mon Sep 17 00:00:00 2001
+From 73c0b87644cdbf798e5f4de966debbc39c770b08 Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:50 -0600
-Subject: [PATCH 093/414] tracing: Account for variables in named trigger
+Subject: [PATCH 093/413] tracing: Account for variables in named trigger
  compatibility
 
 Named triggers must also have the same set of variables in order to be

kernel/patches-4.14.x-rt/0094-tracing-Move-get_hist_field_flags.patch

@@ -1,7 +1,7 @@
-From ce02f3f1b893b14481591ea65b0f9ed04a804824 Mon Sep 17 00:00:00 2001
+From 0b4fd077fb3691992a3bdc061531582eaeed8d8b Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:51 -0600
-Subject: [PATCH 094/414] tracing: Move get_hist_field_flags()
+Subject: [PATCH 094/413] tracing: Move get_hist_field_flags()
 
 Move get_hist_field_flags() to make it more easily accessible for new
 code (and keep the move separate from new functionality).

kernel/patches-4.14.x-rt/0095-tracing-Add-simple-expression-support-to-hist-trigge.patch

@@ -1,7 +1,7 @@
-From 13e83fbfc0915adadbca222e863f7d93958bf009 Mon Sep 17 00:00:00 2001
+From 9ec4b3b72eb7ad4a5f464146950e03a33868154c Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:52 -0600
-Subject: [PATCH 095/414] tracing: Add simple expression support to hist
+Subject: [PATCH 095/413] tracing: Add simple expression support to hist
  triggers
 
 Add support for simple addition, subtraction, and unary expressions

kernel/patches-4.14.x-rt/0096-tracing-Generalize-per-element-hist-trigger-data.patch

@@ -1,7 +1,7 @@
-From c90c725c2ac00315e80251d6ed44bb3860b6484f Mon Sep 17 00:00:00 2001
+From d95785f49fa17053815aaf4aa879b0bb5f680b8c Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:53 -0600
-Subject: [PATCH 096/414] tracing: Generalize per-element hist trigger data
+Subject: [PATCH 096/413] tracing: Generalize per-element hist trigger data
 
 Up until now, hist triggers only needed per-element support for saving
 'comm' data, which was saved directly as a private data pointer.

kernel/patches-4.14.x-rt/0097-tracing-Pass-tracing_map_elt-to-hist_field-accessor-.patch

@@ -1,7 +1,7 @@
-From f685a8ce4ebde4bae2faed2f1ceecfb86e752f9d Mon Sep 17 00:00:00 2001
+From 8166b214eed5311463c837dc24b349d65f06b9f0 Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:54 -0600
-Subject: [PATCH 097/414] tracing: Pass tracing_map_elt to hist_field accessor
+Subject: [PATCH 097/413] tracing: Pass tracing_map_elt to hist_field accessor
  functions
 
 Some accessor functions, such as for variable references, require

kernel/patches-4.14.x-rt/0098-tracing-Add-hist_field-type-field.patch

@@ -1,7 +1,7 @@
-From 42196fbffec1f62007e444960ea133ce362e4980 Mon Sep 17 00:00:00 2001
+From 4a62814a84d553e653af96d3ac62631711d0e5ad Mon Sep 17 00:00:00 2001
 From: Tom Zanussi <tom.zanussi@linux.intel.com>
 Date: Mon, 15 Jan 2018 20:51:55 -0600
-Subject: [PATCH 098/414] tracing: Add hist_field 'type' field
+Subject: [PATCH 098/413] tracing: Add hist_field 'type' field
 
 Future support for synthetic events requires hist_field 'type'
 information, so add a field for that.