[OS-BUILD PATCH] [redhat] New configs in drivers/crypto
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_ZCRYPT_DEBUG:
Say 'Y' here to enable some additional debug features on the
s390 cryptographic adapters driver.
There will be some more sysfs attributes displayed for ap cards
and queues and some flags on crypto requests are interpreted as
debugging messages to force error injection.
Do not enable on production level kernel build.
If unsure, say N.
Symbol: ZCRYPT_DEBUG [=n]
Type : bool
Defined at drivers/crypto/Kconfig:78
Prompt: Enable debug features for s390 cryptographic adapters
Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && DEBUG_KERNEL [=y] && ZCRYPT [=m]
Location:
-> Cryptographic API (CRYPTO [=y])
-> Hardware crypto devices (CRYPTO_HW [=y])
-> Support for s390 cryptographic adapters (ZCRYPT [=m])
---
Cc: Herbert Xu <herbert.xu(a)redhat.com>
Cc: "David S. Miller" <davem(a)redhat.com>
Cc: Ondrej Mosnacek <omosnace(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_ZCRYPT_DEBUG | 1 +
.../generic/CONFIG_ZCRYPT_DEBUG | 26 -------------------
2 files changed, 1 insertion(+), 26 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_ZCRYPT_DEBUG
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ZCRYPT_DEBUG
diff --git a/redhat/configs/common/generic/CONFIG_ZCRYPT_DEBUG b/redhat/configs/common/generic/CONFIG_ZCRYPT_DEBUG
new file mode 100644
index 000000000000..4e0e29a35496
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ZCRYPT_DEBUG
@@ -0,0 +1 @@
+# CONFIG_ZCRYPT_DEBUG is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_ZCRYPT_DEBUG b/redhat/configs/pending-common/generic/CONFIG_ZCRYPT_DEBUG
deleted file mode 100644
index b0a111e75605..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ZCRYPT_DEBUG
+++ /dev/null
@@ -1,26 +0,0 @@
-# CONFIG_ZCRYPT_DEBUG:
-#
-# Say 'Y' here to enable some additional debug features on the
-# s390 cryptographic adapters driver.
-#
-# There will be some more sysfs attributes displayed for ap cards
-# and queues and some flags on crypto requests are interpreted as
-# debugging messages to force error injection.
-#
-# Do not enable on production level kernel build.
-#
-# If unsure, say N.
-#
-# Symbol: ZCRYPT_DEBUG [=n]
-# Type : bool
-# Defined at drivers/crypto/Kconfig:78
-# Prompt: Enable debug features for s390 cryptographic adapters
-# Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && DEBUG_KERNEL [=y] && ZCRYPT [=m]
-# Location:
-# -> Cryptographic API (CRYPTO [=y])
-# -> Hardware crypto devices (CRYPTO_HW [=y])
-# -> Support for s390 cryptographic adapters (ZCRYPT [=m])
-#
-#
-#
-# CONFIG_ZCRYPT_DEBUG is not set
--
GitLab
3 years, 3 months
[OS-BUILD PATCH] [redhat] New configs in drivers/vfio
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_VFIO_PCI_ZDEV:
Enabling this option exposes VFIO capabilities containing hardware
configuration for zPCI devices. This enables userspace (e.g. QEMU)
to supply proper configuration values instead of hard-coded defaults
for zPCI devices passed through via VFIO on s390.
Say Y here.
Symbol: VFIO_PCI_ZDEV [=y]
Type : bool
Defined at drivers/vfio/pci/Kconfig:49
Prompt: VFIO PCI ZPCI device CLP support
Depends on: VFIO_PCI [=m] && S390 [=y]
Location:
-> Device Drivers
-> VFIO Non-Privileged userspace driver framework (VFIO [=m])
-> VFIO support for PCI devices (VFIO_PCI [=m])
---
Cc: Alex Williamson <alex.williamson(a)redhat.com>
Cc: Eric Auger <eric.auger(a)redhat.com>
Cc: rhvirt-patches(a)redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_VFIO_PCI_ZDEV | 1 +
.../generic/CONFIG_VFIO_PCI_ZDEV | 22 -------------------
2 files changed, 1 insertion(+), 22 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_VFIO_PCI_ZDEV
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_VFIO_PCI_ZDEV
diff --git a/redhat/configs/common/generic/CONFIG_VFIO_PCI_ZDEV b/redhat/configs/common/generic/CONFIG_VFIO_PCI_ZDEV
new file mode 100644
index 000000000000..ffc34457516a
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_VFIO_PCI_ZDEV
@@ -0,0 +1 @@
+CONFIG_VFIO_PCI_ZDEV=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_VFIO_PCI_ZDEV b/redhat/configs/pending-common/generic/CONFIG_VFIO_PCI_ZDEV
deleted file mode 100644
index 7040692bbc15..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_VFIO_PCI_ZDEV
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_VFIO_PCI_ZDEV:
-#
-# Enabling this option exposes VFIO capabilities containing hardware
-# configuration for zPCI devices. This enables userspace (e.g. QEMU)
-# to supply proper configuration values instead of hard-coded defaults
-# for zPCI devices passed through via VFIO on s390.
-#
-# Say Y here.
-#
-# Symbol: VFIO_PCI_ZDEV [=y]
-# Type : bool
-# Defined at drivers/vfio/pci/Kconfig:49
-# Prompt: VFIO PCI ZPCI device CLP support
-# Depends on: VFIO_PCI [=m] && S390 [=y]
-# Location:
-# -> Device Drivers
-# -> VFIO Non-Privileged userspace driver framework (VFIO [=m])
-# -> VFIO support for PCI devices (VFIO_PCI [=m])
-#
-#
-#
-CONFIG_VFIO_PCI_ZDEV=y
--
GitLab
3 years, 3 months
[OS-BUILD PATCH] [redhat] New configs in arch/arm64
by GitLab Bridge on behalf of redhat-patchlab
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_ARCH_BCM4908:
This enables support for the Broadcom BCM4906, BCM4908 and
BCM49408 SoCs. These SoCs use Brahma-B53 cores and can be
found in home routers.
Symbol: ARCH_BCM4908 [=n]
Type : bool
Defined at arch/arm64/Kconfig.platforms:46
Prompt: Broadcom BCM4908 family
Location:
-> Platform selection
Selects: GPIOLIB [=y]
---
Cc: Mark Salter <msalter(a)redhat.com>
Cc: Mark Langsdorf <mlangsdo(a)redhat.com>
Cc: Jeremy Linton <jlinton(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../configs/common/generic/CONFIG_ARCH_BCM4908 | 1 +
.../pending-common/generic/CONFIG_ARCH_BCM4908 | 17 -----------------
2 files changed, 1 insertion(+), 17 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_ARCH_BCM4908
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ARCH_BCM4908
diff --git a/redhat/configs/common/generic/CONFIG_ARCH_BCM4908 b/redhat/configs/common/generic/CONFIG_ARCH_BCM4908
new file mode 100644
index 000000000000..6bffc2d6910f
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ARCH_BCM4908
@@ -0,0 +1 @@
+# CONFIG_ARCH_BCM4908 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_ARCH_BCM4908 b/redhat/configs/pending-common/generic/CONFIG_ARCH_BCM4908
deleted file mode 100644
index 2f383b3f7bf6..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ARCH_BCM4908
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_ARCH_BCM4908:
-#
-# This enables support for the Broadcom BCM4906, BCM4908 and
-# BCM49408 SoCs. These SoCs use Brahma-B53 cores and can be
-# found in home routers.
-#
-# Symbol: ARCH_BCM4908 [=n]
-# Type : bool
-# Defined at arch/arm64/Kconfig.platforms:46
-# Prompt: Broadcom BCM4908 family
-# Location:
-# -> Platform selection
-# Selects: GPIOLIB [=y]
-#
-#
-#
-# CONFIG_ARCH_BCM4908 is not set
--
GitLab
3 years, 3 months
[OS-BUILD PATCH] [redhat] New configs in drivers/hid
by GitLab Bridge on behalf of redhat-patchlab
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_AMD_SFH_HID:
If you say yes to this option, support will be included for the
AMD Sensor Fusion Hub.
This driver will enable sensors functionality on AMD platforms
starting from 17h family of RYZEN parts.
This driver can also be built as a module. If so, the module will
be called amd-sfh.
Say Y or M here if you want to support AMD SFH. If unsure, say N.
Symbol: AMD_SFH_HID [=n]
Type : tristate
Defined at drivers/hid/amd-sfh-hid/Kconfig:7
Prompt: AMD Sensor Fusion Hub
Depends on: INPUT [=y] && (X86_64 [=y] || COMPILE_TEST [=n]) && PCI [=y] && HID [=y]
Location:
-> Device Drivers
-> HID support
-> AMD SFH HID Support
---
Cc: Benjamin Tissoires <benjamin.tissoires(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../configs/common/generic/CONFIG_AMD_SFH_HID | 1 +
.../pending-common/generic/CONFIG_AMD_SFH_HID | 23 -------------------
2 files changed, 1 insertion(+), 23 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_AMD_SFH_HID
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_AMD_SFH_HID
diff --git a/redhat/configs/common/generic/CONFIG_AMD_SFH_HID b/redhat/configs/common/generic/CONFIG_AMD_SFH_HID
new file mode 100644
index 000000000000..166fa39b1cc2
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_AMD_SFH_HID
@@ -0,0 +1 @@
+# CONFIG_AMD_SFH_HID is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_AMD_SFH_HID b/redhat/configs/pending-common/generic/CONFIG_AMD_SFH_HID
deleted file mode 100644
index 015f8184dc2b..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_AMD_SFH_HID
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_AMD_SFH_HID:
-#
-# If you say yes to this option, support will be included for the
-# AMD Sensor Fusion Hub.
-# This driver will enable sensors functionality on AMD platforms
-# starting from 17h family of RYZEN parts.
-#
-# This driver can also be built as a module. If so, the module will
-# be called amd-sfh.
-# Say Y or M here if you want to support AMD SFH. If unsure, say N.
-# Symbol: AMD_SFH_HID [=n]
-# Type : tristate
-# Defined at drivers/hid/amd-sfh-hid/Kconfig:7
-# Prompt: AMD Sensor Fusion Hub
-# Depends on: INPUT [=y] && (X86_64 [=y] || COMPILE_TEST [=n]) && PCI [=y] && HID [=y]
-# Location:
-# -> Device Drivers
-# -> HID support
-# -> AMD SFH HID Support
-#
-#
-#
-# CONFIG_AMD_SFH_HID is not set
--
GitLab
3 years, 3 months
[OS-BUILD PATCH] [redhat] New configs in drivers/virtio
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_VIRTIO_MEM:
This driver provides access to virtio-mem paravirtualized memory
devices, allowing to hotplug and hotunplug memory.
This driver was only tested under x86-64, but should theoretically
work on all architectures that support memory hotplug and hotremove.
If unsure, say M.
Symbol: VIRTIO_MEM [=m]
Type : tristate
Defined at drivers/virtio/Kconfig:81
Prompt: Virtio mem driver
Depends on: VIRTIO_MENU [=y] && X86_64 [=y] && VIRTIO [=y] && MEMORY_HOTPLUG_SPARSE [=y] && MEMORY_HOTREMOVE [=y]
Location:
-> Device Drivers
-> Virtio drivers (VIRTIO_MENU [=y])
Selects: CONTIG_ALLOC [=y]
---
Cc: "Michael S. Tsirkin" <mst(a)redhat.com>
Cc: Jason Wang <jasowang(a)redhat.com>
Cc: rhvirt-patches(a)redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../configs/common/generic/CONFIG_VIRTIO_MEM | 1 +
.../pending-common/generic/CONFIG_VIRTIO_MEM | 23 -------------------
2 files changed, 1 insertion(+), 23 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_VIRTIO_MEM
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_VIRTIO_MEM
diff --git a/redhat/configs/common/generic/CONFIG_VIRTIO_MEM b/redhat/configs/common/generic/CONFIG_VIRTIO_MEM
new file mode 100644
index 000000000000..3780f32af7be
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_VIRTIO_MEM
@@ -0,0 +1 @@
+CONFIG_VIRTIO_MEM=m
diff --git a/redhat/configs/pending-common/generic/CONFIG_VIRTIO_MEM b/redhat/configs/pending-common/generic/CONFIG_VIRTIO_MEM
deleted file mode 100644
index d5500a9c6c1e..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_VIRTIO_MEM
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_VIRTIO_MEM:
-#
-# This driver provides access to virtio-mem paravirtualized memory
-# devices, allowing to hotplug and hotunplug memory.
-#
-# This driver was only tested under x86-64, but should theoretically
-# work on all architectures that support memory hotplug and hotremove.
-#
-# If unsure, say M.
-#
-# Symbol: VIRTIO_MEM [=m]
-# Type : tristate
-# Defined at drivers/virtio/Kconfig:81
-# Prompt: Virtio mem driver
-# Depends on: VIRTIO_MENU [=y] && X86_64 [=y] && VIRTIO [=y] && MEMORY_HOTPLUG_SPARSE [=y] && MEMORY_HOTREMOVE [=y]
-# Location:
-# -> Device Drivers
-# -> Virtio drivers (VIRTIO_MENU [=y])
-# Selects: CONTIG_ALLOC [=y]
-#
-#
-#
-CONFIG_VIRTIO_MEM=m
--
2.27.0
3 years, 3 months
[OS-BUILD PATCH] irq: export irq_check_status_bit
by GitLab Bridge on behalf of jmflinuxtx
From: Levi Yun <ppbuk5246(a)gmail.com>
Because of missing export symbol for irq_chekc_status_bit,
Building arm_spe_pmu.ko is failure on modpost step.
below is error message what i saw:
ERROR:modpost: "irq_check_status_bit" [drivers/perf/arm_spe_pmu.ko] undefined!
make[4]: *** [scripts/Makefile.modpost:111: Module.symvers] Error 1
make[4]: *** Deleting file 'Module.symvers'
make[3]: *** [Makefile:1396: modules] Error 2
make[2]: *** [debian/rules:7: build-arch] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
make[1]: *** [scripts/Makefile.package:83: bindeb-pkg] Error 2
Signed-off-by: Levi Yun <ppbuk5246(a)gmail.com>
---
kernel/irq/manage.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index ab8567f32501..dec3f73e8db9 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -2859,3 +2859,4 @@ bool irq_check_status_bit(unsigned int irq, unsigned int bitmask)
rcu_read_unlock();
return res;
}
+EXPORT_SYMBOL_GPL(irq_check_status_bit);
--
GitLab
3 years, 3 months
[OS-BUILD PATCH] [redhat] New configs in drivers/perf
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_ARM_CMN:
Support for PMU events monitoring on the Arm CMN-600 Coherent Mesh
Network interconnect.
Symbol: ARM_CMN [=n]
Type : tristate
Defined at drivers/perf/Kconfig:44
Prompt: Arm CMN-600 PMU support
Depends on: PERF_EVENTS [=y] && (ARM64 [=y] || COMPILE_TEST [=n] && 64BIT [=y])
Location:
-> Device Drivers
-> Performance monitor support
---
Cc: Mark Salter <msalter(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_ARM_CMN | 1 +
.../pending-common/generic/CONFIG_ARM_CMN | 17 -----------------
2 files changed, 1 insertion(+), 17 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_ARM_CMN
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ARM_CMN
diff --git a/redhat/configs/common/generic/CONFIG_ARM_CMN b/redhat/configs/common/generic/CONFIG_ARM_CMN
new file mode 100644
index 000000000000..08b81d7dcde5
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ARM_CMN
@@ -0,0 +1 @@
+# CONFIG_ARM_CMN is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_ARM_CMN b/redhat/configs/pending-common/generic/CONFIG_ARM_CMN
deleted file mode 100644
index f39b12ecfed0..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ARM_CMN
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_ARM_CMN:
-#
-# Support for PMU events monitoring on the Arm CMN-600 Coherent Mesh
-# Network interconnect.
-#
-# Symbol: ARM_CMN [=n]
-# Type : tristate
-# Defined at drivers/perf/Kconfig:44
-# Prompt: Arm CMN-600 PMU support
-# Depends on: PERF_EVENTS [=y] && (ARM64 [=y] || COMPILE_TEST [=n] && 64BIT [=y])
-# Location:
-# -> Device Drivers
-# -> Performance monitor support
-#
-#
-#
-# CONFIG_ARM_CMN is not set
--
GitLab
3 years, 3 months
[OS-BUILD PATCH] New configs in drivers/vdpa
by GitLab Bridge on behalf of jmflinuxtx
From: "Justin M. Forbes" <jforbes(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_VDPA:
Enable this module to support vDPA device that uses a
datapath which complies with virtio specifications with
vendor specific control path.
Symbol: VDPA [=n]
Type : tristate
Defined at drivers/vdpa/Kconfig:2
Prompt: vDPA drivers
Location:
-> Device Drivers
Cc: "Michael S. Tsirkin" <mst(a)redhat.com>
Cc: Jason Wang <jasowang(a)redhat.com>
Cc: rhvirt-patches(a)redhat.com
---
redhat/configs/common/generic/CONFIG_VDPA | 1 +
.../configs/pending-common/generic/CONFIG_VDPA | 16 ----------------
2 files changed, 1 insertion(+), 16 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_VDPA
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_VDPA
diff --git a/redhat/configs/common/generic/CONFIG_VDPA b/redhat/configs/common/generic/CONFIG_VDPA
new file mode 100644
index 000000000000..1cf31b087898
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_VDPA
@@ -0,0 +1 @@
+# CONFIG_VDPA is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_VDPA b/redhat/configs/pending-common/generic/CONFIG_VDPA
deleted file mode 100644
index 5d9d107e760b..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_VDPA
+++ /dev/null
@@ -1,16 +0,0 @@
-# CONFIG_VDPA:
-#
-# Enable this module to support vDPA device that uses a
-# datapath which complies with virtio specifications with
-# vendor specific control path.
-#
-# Symbol: VDPA [=n]
-# Type : tristate
-# Defined at drivers/vdpa/Kconfig:2
-# Prompt: vDPA drivers
-# Location:
-# -> Device Drivers
-#
-#
-#
-# CONFIG_VDPA is not set
--
GitLab
3 years, 3 months
[OS-BUILD PATCH] [redhat] New configs in kernel/dma
by GitLab Bridge on behalf of redhat-patchlab
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_DMA_MAP_BENCHMARK:
Provides /sys/kernel/debug/dma_map_benchmark that helps with testing
performance of dma_(un)map_page.
See tools/testing/selftests/dma/dma_map_benchmark.c
Symbol: DMA_MAP_BENCHMARK [=n]
Type : bool
Defined at kernel/dma/Kconfig:228
Prompt: Enable benchmarking of streaming DMA mapping
Depends on: DEBUG_FS [=y]
Location:
-> Library routines
---
Cc: Jerry Snitselaar <jsnitsel(a)redhat.com>
Cc: Donald Dutile <ddutile(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_DMA_MAP_BENCHMARK | 1 +
.../generic/CONFIG_DMA_MAP_BENCHMARK | 18 ------------------
2 files changed, 1 insertion(+), 18 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_DMA_MAP_BENCHMARK
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DMA_MAP_BENCHMARK
diff --git a/redhat/configs/common/generic/CONFIG_DMA_MAP_BENCHMARK b/redhat/configs/common/generic/CONFIG_DMA_MAP_BENCHMARK
new file mode 100644
index 000000000000..c168b4b6cd69
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DMA_MAP_BENCHMARK
@@ -0,0 +1 @@
+# CONFIG_DMA_MAP_BENCHMARK is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DMA_MAP_BENCHMARK b/redhat/configs/pending-common/generic/CONFIG_DMA_MAP_BENCHMARK
deleted file mode 100644
index f1027b4c046f..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DMA_MAP_BENCHMARK
+++ /dev/null
@@ -1,18 +0,0 @@
-# CONFIG_DMA_MAP_BENCHMARK:
-#
-# Provides /sys/kernel/debug/dma_map_benchmark that helps with testing
-# performance of dma_(un)map_page.
-#
-# See tools/testing/selftests/dma/dma_map_benchmark.c
-#
-# Symbol: DMA_MAP_BENCHMARK [=n]
-# Type : bool
-# Defined at kernel/dma/Kconfig:228
-# Prompt: Enable benchmarking of streaming DMA mapping
-# Depends on: DEBUG_FS [=y]
-# Location:
-# -> Library routines
-#
-#
-#
-# CONFIG_DMA_MAP_BENCHMARK is not set
--
GitLab
3 years, 3 months
✅ PASS: Test report for kernel 5.10.10-200.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.10.10-200.fc33
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=60391043
The results of these automated tests are provided below.
Overall result: PASSED
Tests: OK
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
For the full detail on our testing procedures, please scroll to the bottom of
this message.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Hardware testing
----------------
We booted each kernel and ran the following tests:
aarch64:
Host 1:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ✅ Storage: swraid mdadm raid_module test
Host 2:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
ppc64le:
Host 1:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
Host 2:
✅ Boot test
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ✅ Storage: swraid mdadm raid_module test
s390x:
Host 1:
✅ Boot test
✅ kdump - sysrq-c
Host 2:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ Storage blktests
🚧 ❌ Storage nvme - tcp
🚧 ✅ Storage: swraid mdadm raid_module test
Host 3:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
x86_64:
Host 1:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
Host 2:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 3:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ❌ xfstests - nfsv4.2
🚧 ✅ xfstests - cifsv3.11
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ✅ Storage: swraid mdadm raid_module test
Test sources: https://gitlab.com/cki-project/kernel-tests
💚 Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with ⚡⚡⚡.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with 🚧. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with ⏱.
3 years, 3 months