make dist-srpm-gcov failed to do the expected thing. It appears changes
from commit 2d525ab424 forced a second run of dist-sources. This
second run regenerated the kernel.spec without the gcov pieces because
the env variables were not defined.
Fix this by setting the BUILDOPTS variable to global for the target.
Then simplify the target by leveraging the dist-srpm target.
Now dist-srpm-gcov just sets BUILDID and BUILDOPTS and then calls
dist-srpm to do the expected thing.
Tested by running 'make dist-srpm-gcov' and checking the resulting
redhat/rpm/SOURCES/kernel.spec file for the '_with_gcov 1' definition.
Signed-off-by: Don Zickus <dzickus@redhat.com>
MR 1422 enabled a number of kunit tests in the config including
CONFIG_KFENCE_KUNIT_TEST, but this test does not build in RHEL configs
because KFENCE itself it turned off. As a result, the module for the
test was not added to mod-internal.list causing depmod to fail on Fedora
builds. This simply adds the module to the internal list so that it
filters properly.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
ARK is currently has CONFIG_NODES_SHIFT=6 where Fedora is set
to 9. Let's simplify things and share the Fedora config with
ARK.
Signed-off-by: Mark Salter <msalter@redhat.com>
This commit will enable KUNIT tests to be compiled as modules and
packaged into the kernel-modules-internal package.
Signed-off-by: Nico Pache <npache@redhat.com>
MR 1413 added some new arguments to genspec.sh, but BUILDID must be the
last argument as it can be empty, and is for official builds. This
simply fixes the ordering so that BUILDID is last again.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
If the Lenovo BIOS lock-bootorder option is enabled then fwupd
cannot install EFI capsule updates as those require adding
temporary boot-option pointing to the update.
The latest fwupd code has support for detecting this through the
think-lmi kernel module, so this should be enabled for full
fwupd functionality.
And this is also something which I expect Lenovo to want to have
enabled in RHEL kernels in general.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
---
Changes in v2:
-Move CONFIG_THINKPAD_LMI to configs/common/generic/x86
Bugzilla: INTERNAL
Upstream Status: RHEL-only
The emptyrpm test is asking today for verification of *-matched empty meta
packages. Those are meta packages and are intended to be empty (without
files). Thus add these to the exclusion list for emptyrpm rpminspect
test.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
The addition of gitlab centos dist-git sync added a typo, plus
the dist-git check about the GL_DISTGIT_USER setting was verbose,
make it silent now.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
For some reason the bpf selftest is failing only on ppc64le. Adding
FORCE_TARGETS=1 fixes the issue, and was taken from RHEL 9.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
Right now there is no way dist-brew/dist-koji can build against the
CentOS koji instance. Add support so that if DISTRO=centos is given
on the command line, dist-brew/koji will use the stream profile and
build against CentOS koji (this requires centpkg to be installed in
the system).
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
The centos-stream-9 (c9s) [1] repository contains files for both RHEL and
Fedora configs. The Fedora configs will never be updated, and will
quickly be out-of-date with respect to upstream. Having the files in
place causes confusion having the Fedora files causes for engineers and
contributors.
Add include_fedora and include_rhel variables. These can be set in
Makefile.variables to include or exclude RHEL or Fedora-specific files.
These are enabled for ARK, and include_fedora can be disabled for c9s.
[1] https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
The kernel-local file is applied on both rhel and fedora builds. Make it
a global file instead of in the fedora_files dir.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
While CPU_FREQ_GOV_SCHEDUTIL was reviewed and turned off some time ago,
X86_INTEL_PSTATE was reviewed and turned on for x86. With commit
a00ec3874e these options are now conflicting as X86_INTEL_PSTATE
selects pstate as the default governor now. We have been building this
way for quite some time, but because an MR was never created to get
reviews, it has not been formalized. This seeks to rectify that.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
Upstream change 701dc81e74 removed the fake numa support on s390. As
a result, though some generic structure was left in place for
applications that expect NUMA interfaces to exist. The current reviewed
and approved setting for NODES_SHIFT on s390 is 4, but that is no longer
valid. The only valid options are 1 or turning off numa completely
which can be problematic for some applications.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
While the configs for CRYPTO_SHA3_512_S390 and CRYPTO_SHA3_256_S390 were
reviewed and set to a module, the zfcpdump kernel does not support
modules. We have to either build them inline (as we have been for a
while) or we need to turn them off all together for the zfcpdump kernel.
This MR exists because it was created in pending and got dropped without
a proper MR to review and decide on the proper solution. I have set them
to build inline, but am happy to change them based on review.
Signed-off-by: Justin M. Forbes <jforbes@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.
Symbol: TEST_SCANF [=n]
Type : tristate
Defined at lib/Kconfig.debug:2181
Prompt: Test scanf() family of functions at runtime
Depends on: RUNTIME_TESTING_MENU [=y]
Location:
-> Kernel hacking
-> Kernel Testing and Coverage
-> Runtime Testing (RUNTIME_TESTING_MENU [=y])
---
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Aristeu Rozanski <arozansk@redhat.com>
Cc: Christoph von Recklinghausen <crecklin@redhat.com>
Cc: Eugene Syromiatnikov <esyromia@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Nico Pache <npache@redhat.com>
Cc: Oleg Nesterov <onestero@redhat.com>
Cc: Rafael Aquini <aquini@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: VHOST_MENU [=y]
Type : bool
Defined at drivers/vhost/Kconfig:23
Prompt: VHOST drivers
Location:
-> Device Drivers
---
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: DRM_PANEL_SAMSUNG_S6E88A0_AMS452EF01 [=n]
Type : tristate
Defined at drivers/gpu/drm/panel/Kconfig:436
Prompt: Samsung AMS452EF01 panel with S6E88A0 DSI video mode controller
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_PANEL [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Panels
Selects: DRM_MIPI_DSI [=n] && VIDEOMODE_HELPERS [=n]
---
Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Cc: "Michel Dänzer" <mdaenzer@redhat.com>
Cc: "Jérôme Glisse" <jglisse@redhat.com>
Cc: Karol Herbst <kherbst@redhat.com>
Cc: Ben Skeggs <bskeggs@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: GPIO_CDEV_V1 [=y]
Type : bool
Defined at drivers/gpio/Kconfig:86
Prompt: Support GPIO ABI Version 1
Depends on: GPIOLIB [=y] && GPIO_CDEV [=y]
Location:
-> Device Drivers
-> GPIO Support (GPIOLIB [=y])
-> Character device (/dev/gpiochipN) support (GPIO_CDEV [=y])
---
Cc: Brian Masney <bmasney@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: ZRAM_DEF_COMP_842 [=n]
Type : bool
Defined at drivers/block/zram/Kconfig:42
Prompt: 842
Depends on: <choice> && CRYPTO_842 [=m]
Location:
-> Device Drivers
-> Block devices (BLK_DEV [=y])
-> Compressed RAM block device support (ZRAM [=m])
-> Default zram compressor (<choice> [=y])
---
Symbol: ZRAM_DEF_COMP_LZO [=n]
Type : bool
Defined at drivers/block/zram/Kconfig:34
Prompt: lzo
Depends on: <choice> && CRYPTO_LZO [=y]
Location:
-> Device Drivers
-> Block devices (BLK_DEV [=y])
-> Compressed RAM block device support (ZRAM [=m])
-> Default zram compressor (<choice> [=y])
---
Symbol: ZRAM_DEF_COMP_LZORLE [=y]
Type : bool
Defined at drivers/block/zram/Kconfig:22
Prompt: lzo-rle
Depends on: <choice> && CRYPTO_LZO [=y]
Location:
-> Device Drivers
-> Block devices (BLK_DEV [=y])
-> Compressed RAM block device support (ZRAM [=m])
-> Default zram compressor (<choice> [=y])
---
Cc: Ming Lei <ming.lei@redhat.com>
Cc: Jeff Moyer <jmoyer@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: CRYPTO_CURVE25519 [=n]
Type : tristate
Defined at crypto/Kconfig:285
Prompt: Curve25519 algorithm
Depends on: CRYPTO [=y]
Location:
-> Cryptographic API (CRYPTO [=y])
Selects: CRYPTO_KPP [=y] && CRYPTO_LIB_CURVE25519_GENERIC [=m]
Selected by [n]:
- CRYPTO_DEV_HISI_HPRE [=n] && CRYPTO [=y] && CRYPTO_HW [=y] && PCI [=y] && PCI_MSI [=y] && (UACCE [=n] || UACCE [=n]=n) && (ARM64 || COMPILE_TEST [=n] && 64BIT [=y]) && ACPI [=y]
---
Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Phil Auld <pauld@redhat.com>
Cc: Vladis Dronov <vdronov@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: ACPI_PRMT [=y]
Type : bool
Defined at drivers/acpi/Kconfig:550
Prompt: Platform Runtime Mechanism Support
Depends on: EFI [=y] && X86_64 [=y]
Location:
-> Power management and ACPI options
---
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: ARM64_MTE [=y]
Type : bool
Defined at arch/arm64/Kconfig:1647
Prompt: Memory Tagging Extension support
Depends on: ARM64_AS_HAS_MTE [=y] && ARM64_TAGGED_ADDR_ABI [=y] && AS_HAS_ARMV8_5 [=y] && AS_HAS_LSE_ATOMICS [=y] && ARM64_PAN [=y]
Location:
-> Kernel Features
-> ARMv8.5 architectural features
Selects: ARCH_USES_HIGH_VMA_FLAGS [=y]
---
Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: LTO_NONE [=y]
Type : bool
Defined at arch/Kconfig:665
Prompt: None
Depends on: <choice>
Location:
-> General architecture-dependent options
-> Link Time Optimization (LTO) (<choice> [=y])
---
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
The DIST value is dynamically detected on ARK, but it can be set to a
fixed value for a branch which forks from it (as some branches are built
only for a given distro and we don't want the DIST value to change even
if building eg. the src.rpm in a different environment). So it makes sense
in this case to move it to the Makefile.variables file.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Now that "redhat: bump RHEL_MAJOR and add the changelog file for it" was
applied, we can drop this old changelog file, the new kernel.changelog-9.99
is being used now.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2006813
Upstream Status: RHEL only
Tested: After "make dist-configs", both CONFIG_BLK_CGROUP_IOLATENCY and
CONFIG_BLK_CGROUP_FC_APPID are turned on in all config files.
RHEL8 has CONFIG_BLK_CGROUP_IOLATENCY enabled, so kernel-ark must have
this config option enabled too to provide equivalent functionality.
CONFIG_BLK_CGROUP_FC_APPID should be enabled too as it is for the VMID
feature that will allow RHV to assign an ID so that the FC switches
can identify the flows from different VMs (or containers, even). It is
a feature requested by Broadcom.
The new configs are enabled under the common directory. The ones under
the ark or pending-common directory are removed.
Signed-off-by: Waiman Long <longman@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1998953
Upstream Status: RHEL-only
Kdump will use ZSTD as the default method for initrd squashfs compression. It is helpful
for reducing the vmcore dump and read time consumption while keeping a good compression
ratio on machines with large memories. Fedora has already enabled CONFIG_SQUASHFS_ZSTD,
this patch enables CONFIG_SQUASHFS_ZSTD for RHEL by removing configs/ark/generic/CONFIG_SQUASHFS_ZSTD
and moving configs/fedora/generic/CONFIG_SQUASHFS_ZSTD to configs/common/generic.
Signed-off-by: Tao Liu <ltao@redhat.com>
We do not need to use the rhel version in the file name to look for the
RHDISTGIT_CACHE value. Usually this file is used by the maintainers for
configuring the location of the dist-git cache (the dist-git repo can
be big so this saves time in the dist-git sync operation). But having
the version in the name means bumping/changing the major each release,
we do not need to do it: if the maintainer has to maintain different
majors in the same stream, he will use the same dist-git repo/cache for
it. In the case different dist-git repos are needed or the dist-git
repos differ (are not synced between them), the .rhpkg.mk can have if
statements to single out the repos.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
kernel-ark does not track anymore work for RHEL 9/CentOS Stream 9. We look
forward to the next major. While "8.99" was chosen as the version for
the work preceding RHEL 9, bump the major so the considered version now is
"9.99". I'm intentionally not removing redhat/kernel.changelog-8.99 yet
in this commit, to avoid any conflicts while this isn't merged. When
this change goes in, I'll propose a new merge request for the removal of
this old changelog file.
Also I'm not including/moving all old changelog entries into the new file,
to avoid conflicts in the next os-build rebase. So when this is included/merged
the first time, no old entries before last release commit will be in the
changelog. However, all changelog entries will be picked up with the first
release commit in the next os-build rebase.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976884
Upstream Status: RHEL-only
Tested: by IBM
Conflicts: None
This commit fixes a regression from RHEL8, where the following CONFIG
entries were created in order to support secure IPL on s390x
Signed-off-by: Claudio Imbrenda <cimbrend@redhat.com>
We have been rebasing os-build lately on each new major Linux upstream
release. Add general instructions/guideline on how to do the rebase
process on top of last upstream tag/commit.
This also provides an explanation on why we are doing the rebase,
provided by Don Zickus. Added some of his suggestions as well on
the rebase process instructions.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Upstream Status: RHEL-only
INTEGRITY_PLATFORM_KEYRING which depends on SYSTEM_BLACKLIST_KEYRING is
needed to make use of the .platform keyring to verify kdump kernel image
signature. By removing configs/ark/generic/CONFIG_SYSTEM_BLACKLIST_KEYRING,
configs/common/generic/CONFIG_SYSTEM_BLACKLIST_KEYRING which has
CONFIG_SYSTEM_BLACKLIST_KEYRING=y will take precedence.
Suggested-by: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Coiby Xu <coxu@redhat.com>
We have had a few requests to bring back the kernel-doc package for
Fedora. While I wanted to bring it into kernel-tools so that it was
built less frequently, it is already being maintained in the kernel spec
so let's just add noarch to Fedora so that it builds there too.
Signed-off-by: Justin M. Forbes <jforbes@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.
Symbol: DMA_RESTRICTED_POOL [=n]
Type : bool
Defined at kernel/dma/Kconfig:83
Prompt: DMA Restricted Pool
Depends on: OF [=y] && OF_RESERVED_MEM [=y] && SWIOTLB [=y]
Location:
-> Library routines
---
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Donald Dutile <ddutile@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Joel Savitz <jsavitz@redhat.com>
Cc: Lucas Zampieri <lzampier@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: AMD_PTDMA [=n]
Type : tristate
Defined at drivers/dma/ptdma/Kconfig:2
Prompt: AMD PassThru DMA Engine
Depends on: DMADEVICES [=y] && X86_64 [=y] && PCI [=y]
Location:
-> Device Drivers
-> DMA Engine support (DMADEVICES [=y])
Selects: DMA_ENGINE [=y] && DMA_VIRTUAL_CHANNELS [=y]
---
Symbol: INTEL_IDXD_COMPAT [=n]
Type : bool
Defined at drivers/dma/Kconfig:299
Prompt: Legacy behavior for idxd driver
Depends on: DMADEVICES [=y] && PCI [=y] && X86_64 [=y]
Location:
-> Device Drivers
-> DMA Engine support (DMADEVICES [=y])
Selects: INTEL_IDXD_BUS [=m]
---
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1945179
Upstream Status: RHEL-only
These drivers have been deprecated with RHEL9, so with RHEL10 it is time
to remove them:
- CONFIG_BRIDGE_NF_EBTABLES
- CONFIG_IP6_NF_IPTABLES
- CONFIG_IP_NF_ARPTABLES
- CONFIG_IP_NF_IPTABLES
- CONFIG_IP_SET
- CONFIG_NFT_COMPAT
Enable previous selected symbols to reduce impact to deprecated symbols:
- CONFIG_NF_CONNTRACK_LABELS
Drop symbols not used anymore:
- CONFIG_NETFILTER_XTABLES
- CONFIG_BRIDGE_NETFILTER
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.
Symbol: DAMON [=n]
Type : bool
Defined at mm/damon/Kconfig:5
Prompt: DAMON: Data Access Monitoring Framework
Location:
-> Memory Management options
-> Data Access Monitoring
---
Cc: Rafael Aquini <aquini@redhat.com>
Cc: Aristeu Rozanski <arozansk@redhat.com>
Cc: Artem Savkov <asavkov@redhat.com>
Cc: Baoquan He <bhe@redhat.com>
Cc: Christoph von Recklinghausen <crecklin@redhat.com>
Cc: Don Dutile <ddutile@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Nico Pache <npache@redhat.com>
Cc: Waiman Long <longman@redhat.com>
Cc: mm-maint@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1945179
Upstream Status: RHEL-only
Allow marking drivers deprecated. The printed message is basically
identical to what mark_hardware_deprecated() prints but generalized a
bit to cover non-hardware drivers also. Semantically, the introduced
function aligns with mark_driver_unsupported().
Signed-off-by: Phil Sutter <psutter@redhat.com>
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.
Symbol: GPIO_VIRTIO [=n]
Type : tristate
Defined at drivers/gpio/Kconfig:1674
Prompt: VirtIO GPIO support
Depends on: GPIOLIB [=y] && VIRTIO [=y]
Location:
-> Device Drivers
-> GPIO Support (GPIOLIB [=y])
-> Virtual GPIO drivers
---
Cc: Brian Masney <bmasney@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: NVHE_EL2_DEBUG [=n]
Type : bool
Defined at arch/arm64/kvm/Kconfig:50
Prompt: Debug mode for non-VHE EL2 object
Depends on: VIRTUALIZATION [=y] && KVM [=y]
Location:
-> Virtualization (VIRTUALIZATION [=y])
-> Kernel-based Virtual Machine (KVM) support (KVM [=y])
---
Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: DMA_RESTRICTED_POOL [=n]
Type : bool
Defined at kernel/dma/Kconfig:83
Prompt: DMA Restricted Pool
Depends on: OF [=y] && OF_RESERVED_MEM [=y] && SWIOTLB [=y]
Location:
-> Library routines
---
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Donald Dutile <ddutile@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Joel Savitz <jsavitz@redhat.com>
Cc: Lucas Zampieri <lzampier@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: WERROR [=y]
Type : bool
Defined at init/Kconfig:140
Prompt: Compile the kernel with warnings as errors
Location:
-> General setup
---
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Aristeu Rozanski <arozansk@redhat.com>
Cc: Artem Savkov <asavkov@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Kairui Song <kasong@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: ZERO_CALL_USED_REGS [=n]
Type : bool
Defined at security/Kconfig.hardening:235
Prompt: Enable register zeroing on function exit
Depends on: CC_HAS_ZERO_CALL_USED_REGS [=y]
Location:
-> Security options
-> Kernel hardening options
-> Memory initialization
---
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Christoph von Recklinghausen <crecklin@redhat.com>
Cc: Richard Guy Briggs <rbriggs@redhat.com>
Cc: Vladis Dronov <vdronov@redhat.com>
Cc: Wander Costa <wcosta@redhat.com>
Cc: Yannick Cote <ycote@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: INTEL_SAR_INT1092 [=n]
Type : tristate
Defined at drivers/platform/x86/intel/int1092/Kconfig:1
Prompt: Intel Specific Absorption Rate Driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && X86_PLATFORM_DRIVERS_INTEL [=y] && ACPI [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
-> Intel x86 Platform Specific Device Drivers (X86_PLATFORM_DRIVERS_INTEL [=y])
---
Symbol: MERAKI_MX100 [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:284
Prompt: Cisco Meraki MX100 Platform Driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && GPIOLIB [=y] && GPIO_ICH [=m] && LEDS_CLASS [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
Selects: LEDS_GPIO [=n]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: SND_SOC_AMD_ACP5x [=n]
Type : tristate
Defined at sound/soc/amd/Kconfig:56
Prompt: AMD Audio Coprocessor-v5.x I2S support
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && X86 [=y] && PCI [=y]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
---
Symbol: SND_SOC_MT8195 [=n]
Type : tristate
Defined at sound/soc/mediatek/Kconfig:188
Prompt: ASoC support for Mediatek MT8195 chip
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
Selects: SND_SOC_MEDIATEK [=n]
---
Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: NVMEM_NINTENDO_OTP [=n]
Type : tristate
Defined at drivers/nvmem/Kconfig:110
Prompt: Nintendo Wii and Wii U OTP Support
Depends on: NVMEM [=y]
Location:
-> Device Drivers
-> NVMEM Support (NVMEM [=y])
---
Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: VIDEO_IMX335 [=n]
Type : tristate
Defined at drivers/media/i2c/Kconfig:845
Prompt: Sony IMX335 sensor support
Depends on: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m]
Visible if: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
Location:
-> Device Drivers
-> Multimedia support (MEDIA_SUPPORT [=m])
-> Media ancillary drivers
-> Camera sensor devices
Selects: VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y] && V4L2_FWNODE [=n]
---
Symbol: VIDEO_IMX412 [=n]
Type : tristate
Defined at drivers/media/i2c/Kconfig:871
Prompt: Sony IMX412 sensor support
Depends on: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m]
Visible if: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
Location:
-> Device Drivers
-> Multimedia support (MEDIA_SUPPORT [=m])
-> Media ancillary drivers
-> Camera sensor devices
Selects: VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y] && V4L2_FWNODE [=n]
---
Symbol: VIDEO_OV9282 [=n]
Type : tristate
Defined at drivers/media/i2c/Kconfig:1134
Prompt: OmniVision OV9282 sensor support
Depends on: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m]
Visible if: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
Location:
-> Device Drivers
-> Multimedia support (MEDIA_SUPPORT [=m])
-> Media ancillary drivers
-> Camera sensor devices
Selects: VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y] && V4L2_FWNODE [=n]
---
Cc: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: AD5110 [=n]
Type : tristate
Defined at drivers/iio/potentiometer/Kconfig:9
Prompt: Analog Devices AD5110 and similar Digital Potentiometer driver
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Digital potentiometers
---
Symbol: SENSIRION_SGP40 [=n]
Type : tristate
Defined at drivers/iio/chemical/Kconfig:134
Prompt: Sensirion SGP40 gas sensor
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Chemical Sensors
Selects: CRC8 [=m]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: DRM_PANEL_INNOLUX_EJ030NA [=n]
Type : tristate
Defined at drivers/gpu/drm/panel/Kconfig:149
Prompt: Innolux EJ030NA 320x480 LCD panel
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_PANEL [=y] && OF [=y] && SPI [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Panels
Selects: REGMAP_SPI [=m]
---
Symbol: DRM_PANEL_SAMSUNG_ATNA33XC20 [=n]
Type : tristate
Defined at drivers/gpu/drm/panel/Kconfig:368
Prompt: Samsung ATNA33XC20 eDP panel
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_PANEL [=y] && OF [=y] && BACKLIGHT_CLASS_DEVICE [=y] && PM [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Panels
Selects: DRM_DP_AUX_BUS [=n]
---
Symbol: DRM_PANEL_SAMSUNG_DB7430 [=n]
Type : tristate
Defined at drivers/gpu/drm/panel/Kconfig:379
Prompt: Samsung DB7430-based DPI panels
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_PANEL [=y] && OF [=y] && SPI [=y] && GPIOLIB [=y] && BACKLIGHT_CLASS_DEVICE [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Panels
Selects: DRM_MIPI_DBI [=n]
---
Symbol: DRM_PANEL_WIDECHIPS_WS2401 [=n]
Type : tristate
Defined at drivers/gpu/drm/panel/Kconfig:600
Prompt: Widechips WS2401 DPI panel driver
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_PANEL [=y] && SPI [=y] && GPIOLIB [=y] && BACKLIGHT_CLASS_DEVICE [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Panels
Selects: DRM_MIPI_DBI [=n]
---
Symbol: DRM_VMWGFX_MKSSTATS [=n]
Type : bool
Defined at drivers/gpu/drm/vmwgfx/Kconfig:25
Prompt: Enable mksGuestStats instrumentation of vmwgfx by default
Depends on: HAS_IOMEM [=y] && DRM_VMWGFX [=m] && X86 [=y]
Location:
-> Device Drivers
-> Graphics support
-> DRM driver for VMware Virtual GPU (DRM_VMWGFX [=m])
---
Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Cc: "Michel Dänzer" <mdaenzer@redhat.com>
Cc: "Jérôme Glisse" <jglisse@redhat.com>
Cc: Karol Herbst <kherbst@redhat.com>
Cc: Ben Skeggs <bskeggs@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: DMABUF_SYSFS_STATS [=n]
Type : bool
Defined at drivers/dma-buf/Kconfig:75
Prompt: DMA-BUF sysfs statistics
Location:
-> Device Drivers
-> DMABUF options
Selects: DMA_SHARED_BUFFER [=y]
---
Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Now that the CONFIG_INFINIBAND_IRDMA driver is supported, we can remove
the CONFIG_INFINIBAND_I40IW, because the IRDMA driver replaces the I40IW
driver.
Upstream: RHEL-only.
Signed-off-by: Kamal Heib <kheib@redhat.com>
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.
Symbol: MCTP [=n]
Type : tristate
Defined at net/mctp/Kconfig:2
Prompt: MCTP core protocol support
Depends on: NET [=y]
Location:
-> Networking support (NET [=y])
---
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Antoine Tenart <atenart@redhat.com>
Cc: Balazs Nemeth <bnemeth@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: IPV6_IOAM6_LWTUNNEL [=n]
Type : bool
Defined at net/ipv6/Kconfig:331
Prompt: IPv6: IOAM Pre-allocated Trace insertion support
Depends on: NET [=y] && INET [=y] && IPV6 [=y]
Location:
-> Networking support (NET [=y])
-> Networking options
-> TCP/IP networking (INET [=y])
-> The IPv6 protocol (IPV6 [=y])
Selects: LWTUNNEL [=y]
---
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Antoine Tenart <atenart@redhat.com>
Cc: Balazs Nemeth <bnemeth@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: MAXLINEAR_GPHY [=n]
Type : tristate
Defined at drivers/net/phy/Kconfig:210
Prompt: Maxlinear Ethernet PHYs
Depends on: NETDEVICES [=y] && PHYLIB [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> PHY Device support and infrastructure (PHYLIB [=y])
---
Cc: Petr Oros <poros@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: SENSORS_AQUACOMPUTER_D5NEXT [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:257
Prompt: Aquacomputer D5 Next watercooling pump
Depends on: HWMON [=y] && USB_HID [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
Symbol: SENSORS_SBRMI [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:1564
Prompt: Emulated SB-RMI sensor
Depends on: HWMON [=y] && I2C [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
The redhat/configs/pending-common/generic/CONFIG_CHELSIO_IPSEC_INLINE
file was left behind. It enables the config item as a module. However,
the common/generic/ directory includes this item as a built-in (=y).
Remove the pending-common CONFIG_CHELSIO_IPSEC_INLINE file AND change
the common/generic/ entry from =y to =m. The result is the generated
kernel config files do not change.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
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.
Symbol: KCSAN [=n]
Type : bool
Defined at lib/Kconfig.kcsan:23
Prompt: KCSAN: dynamic data race detector
Depends on: HAVE_ARCH_KCSAN [=y] && HAVE_KCSAN_COMPILER [=y] && DEBUG_KERNEL [=y] && !KASAN [=n] && !KCSAN_KCOV_BROKEN [=n]
Location:
-> Kernel hacking
-> Generic Kernel Debugging Instruments
Selects: STACKTRACE [=y]
---
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Aristeu Rozanski <arozansk@redhat.com>
Cc: Christoph von Recklinghausen <crecklin@redhat.com>
Cc: Eugene Syromiatnikov <esyromia@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Nico Pache <npache@redhat.com>
Cc: Oleg Nesterov <onestero@redhat.com>
Cc: Rafael Aquini <aquini@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: HW_RANDOM_ARM_SMCCC_TRNG [=y]
Type : tristate
Defined at drivers/char/hw_random/Kconfig:527
Prompt: Arm SMCCC TRNG firmware interface support
Depends on: HW_RANDOM [=y] && HAVE_ARM_SMCCC_DISCOVERY [=y]
Location:
-> Device Drivers
-> Character devices
-> Hardware Random Number Generator Core support (HW_RANDOM [=y])
---
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: CRYPTO_SM4_AESNI_AVX2_X86_64 [=n]
Type : tristate
Defined at crypto/Kconfig:1594
Prompt: SM4 cipher algorithm (x86_64/AES-NI/AVX2)
Depends on: CRYPTO [=y] && X86 [=y] && 64BIT [=y]
Location:
-> Cryptographic API (CRYPTO [=y])
Selects: CRYPTO_SKCIPHER [=y] && CRYPTO_SIMD [=y] && CRYPTO_ALGAPI [=y] && CRYPTO_LIB_SM4 [=n] && CRYPTO_SM4_AESNI_AVX_X86_64 [=n]
---
Symbol: CRYPTO_SM4_AESNI_AVX_X86_64 [=n]
Type : tristate
Defined at crypto/Kconfig:1573
Prompt: SM4 cipher algorithm (x86_64/AES-NI/AVX)
Depends on: CRYPTO [=y] && X86 [=y] && 64BIT [=y]
Location:
-> Cryptographic API (CRYPTO [=y])
Selects: CRYPTO_SKCIPHER [=y] && CRYPTO_SIMD [=y] && CRYPTO_ALGAPI [=y] && CRYPTO_LIB_SM4 [=n]
Selected by [n]:
- CRYPTO_SM4_AESNI_AVX2_X86_64 [=n] && CRYPTO [=y] && X86 [=y] && 64BIT [=y]
---
Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Phil Auld <pauld@redhat.com>
Cc: Vladis Dronov <vdronov@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
Symbol: PERF_EVENTS_AMD_UNCORE [=y]
Type : tristate
Defined at arch/x86/events/Kconfig:37
Prompt: AMD Uncore performance events
Depends on: PERF_EVENTS [=y] && CPU_SUP_AMD [=y]
Location:
-> Processor type and features
-> Performance monitoring
---
Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Now that RHEL9 is using 4K pagesize, MAX_ZONEORDER is defaulting
to 11. Fedora uses an out of tree patch to default to 13 when
building for server class machines. RHEL9 should also be using 13,
so make the MAX_ZONEORDER config and the out of tree patch common
between RHEL9 and Fedora.
Signed-off-by: Mark Salter <msalter@redhat.com>
The existing Makefiles and scripts are hard coded to expect that we are
building from the os-build branch with master being the upstream branch.
This does not work well for fedora-stable releases, and does not offer
flexibility to build different trees without knowing the Makefiles and
scripts well enough to know what to change. This change creates a
redhat/Makefile.variables which should be a self documented single file
to change when building with a different upstream or dist branch.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1967640
Even if we build perf dynamically against libtraceevent present on the system,
it still builds traceevent plugins. If we only exclude the files from
the perf package, to not conflict with libtraceevent package, its debug files
will still get included in the kernel-debuginfo package. We don't want that,
since libtraceevent already should ship plugins and its debuginfo. Thus
remove all traceevent files instead of partially excluding them through
rpm's package file list, any files there should already ship with
libtraceevent related packages.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
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_ZONEFS_FS:
zonefs is a simple file system which exposes zones of a zoned block
device (e.g. host-managed or host-aware SMR disk drives) as files.
If unsure, say N.
Symbol: ZONEFS_FS [=n]
Type : tristate
Defined at fs/zonefs/Kconfig:1
Prompt: zonefs filesystem support
Depends on: BLOCK [=y] && BLK_DEV_ZONED [=y]
Location:
-> File systems
Selects: FS_IOMAP [=y] && CRC32 [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_SIM_BLOCK:
vDPA block device simulator which terminates IO request in a
memory buffer.
Symbol: VDPA_SIM_BLOCK [=n]
Type : tristate
Defined at drivers/vdpa/Kconfig:29
Prompt: vDPA simulator for block device
Depends on: VDPA [=m] && VDPA_SIM [=m]
Location:
-> Device Drivers
-> vDPA drivers (VDPA [=m])
-> vDPA device simulator core (VDPA_SIM [=m])
---
CONFIG_VDPA_SIM_NET:
vDPA networking device simulator which loops TX traffic back to RX.
Symbol: VDPA_SIM_NET [=n]
Type : tristate
Defined at drivers/vdpa/Kconfig:22
Prompt: vDPA simulator for networking device
Depends on: VDPA [=m] && VDPA_SIM [=m]
Location:
-> Device Drivers
-> vDPA drivers (VDPA [=m])
-> vDPA device simulator core (VDPA_SIM [=m])
Selects: GENERIC_NET_UTILS [=y]
---
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v3:
- rebase
- CONFIG_VDPA_SIM_NET remove matching fedora config
v2:
- CONFIG_VDPA_SIM_BLOCK enabled as a module
- CONFIG_VDPA_SIM_NET enabled as a module
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
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_DWMAC_LOONGSON:
This selects the LOONGSON PCI bus support for the stmmac driver,
Support for ethernet controller on Loongson-2K1000 SoC and LS7A1000 bridge.
Symbol: DWMAC_LOONGSON [=n]
Type : tristate
Defined at drivers/net/ethernet/stmicro/stmmac/Kconfig:253
Prompt: Loongson PCI DWMAC support
Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_STMICRO [=y] && STMMAC_ETH [=m] && PCI [=y] && COMMON_CLK [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Ethernet driver support (ETHERNET [=y])
-> STMicroelectronics devices (NET_VENDOR_STMICRO [=y])
-> STMicroelectronics Multi-Gigabit Ethernet driver (STMMAC_ETH [=m])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_BATTERY_RT5033:
This adds support for battery fuel gauge in Richtek RT5033 PMIC.
The fuelgauge calculates and determines the battery state of charge
according to battery open circuit voltage.
Symbol: BATTERY_RT5033 [=n]
Type : tristate
Defined at drivers/power/supply/Kconfig:713
Prompt: RT5033 fuel gauge support
Depends on: POWER_SUPPLY [=y] && I2C [=y]
Location:
-> Device Drivers
-> Power supply class support (POWER_SUPPLY [=y])
Selects: REGMAP_I2C [=m]
---
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Bugzilla: 1995338
Upstream Status: RHEL only
Tested: Local xfstests on ext4 and xfs with and without dax
Make sure to taint the kernel with TAINT_TECH_PREVIEW when a file
system is mounted with "-o dax".
Signed-off-by: Bill O'Donnell <bodonnel@redhat.com>
We already enable a number of Realtek rtw88 pcie wifi
modules, these are widely used on a number of Edge GW
devices so also enable the 8723DE/8821CE modules too.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
The debug options shouldn't been enabled in the standard kernel. This
is already the case for ark so do the same in Fedora too.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
We already enable PTP support on Fedora, we would want the
VMware virtual PTP clock suppoort on ARK OSes too.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
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_BLK_CGROUP_IOPRIO:
Enable the .prio interface for assigning an I/O priority class to
requests. The I/O priority class affects the order in which an I/O
scheduler and block devices process requests. Only some I/O schedulers
and some block devices support I/O priorities.
Symbol: BLK_CGROUP_IOPRIO [=n]
Type : bool
Defined at block/Kconfig:165
Prompt: Cgroup I/O controller for assigning an I/O priority class
Depends on: BLOCK [=y] && BLK_CGROUP [=y]
Location:
-> Enable the block layer (BLOCK [=y])
---
Cc: Ming Lei <ming.lei@redhat.com>
Cc: Jeff Moyer <jmoyer@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
The CDN DP needs a PHY and a extcon to work correctly. But no extcon is
provided by the device-tree, which leads to an error:
cdn-dp fec00000.dp: [drm:cdn_dp_probe [rockchipdrm]] *ERROR* missing extcon or phy
cdn-dp: probe of fec00000.dp failed with error -22
Disable the CDN DP to make graphic work on the Pinebook Pro.
Reported-by: Guillaume Gardet <guillaume.gardet@arm.com>
Signed-off-by: Matthias Brugger <mbrugger@suse.com>
Some chargers try to put the charged device into device data
role. Before this commit this condition caused the tcpm state machine to
issue a hard reset due to a capability missmatch.
Signed-off-by: Dan Johansen <strit@manjaro.org>
A rhel8 commit - 89bf8dd3c57dda93555963e60a3077534062918c
Adding CI_DEVICE_ID_LSI_SAS0079GEN2, PCI_DEVICE_ID_LSI_SAS0073SKINNY
and PCI_DEVICE_ID_LSI_SAS0071SKINNY.
Signed-off-by: Tomas Henzl <thenzl@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1995321
Upstream Status: https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
commit f19ee6bb1a
Author: Darrick J. Wong <djwong@kernel.org>
Date: Fri Aug 6 11:05:44 2021 -0700
xfs: drop experimental warnings for bigtime and inobtcount
These two features were merged a year ago, userspace tooling have been
merged, and no serious errors have been reported by the developers.
Drop the experimental tag to encourage wider testing.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Chandan Babu R <chandanrlinux@gmail.com>
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
Reviewed-by: Bill O'Donnell <billodo@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Bill O'Donnell <bodonnel@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1993393
liquidio driver was already disabled on Fedora, but was still being
enabled on RHEL/ark. This was enabled back in rhel8 but we got a request
to revert that later in rhel8. So there is no reason to keep it enabled
anymore in RHEL/ark too.
Disabling the driver also allowed some simplification/removal of now
uneeded config files and unification of them. While at it, I also
moved CAVIUM_PTP to m in rhel/ark as is already the case in Fedora
(afaik there is no apparent reason to keep it builtin, and was just the
result of default choice of this option looking at the option history),
and I also disabled LIQUIDIO_VF following the liquidio disabling (this
affects Fedora too where it was still enabled).
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
To enable CentOS Stream double pipelines, the pipeline type check now
uses regexes. This means that both "trusted" (c9s) and "trusted-ark"
(ARK) pipelines would get picked and be executed for ARK MRs which is
not what we want. Rename the ARK pipeline type to avoid this.
Bugzilla: INTERNAL
Upstream Status: RHEL-only
Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
The configuration for c9s was, up till now, a commented out placeholder.
The plans are finished now so we can also update the config accordingly.
We want two pipelines:
- A full c9s pipeline (build and test), publicly available
- A build for RHEL9 (RH internal only), to ensure nothing breaks (this
should not happen, but better be safe)
Add a new anchor for RHEL build-only and the extra pipelines. As we now
have a lot of pipelines defined in this file, add comments to mark where
the actual definitions start for easier orientation.
Bugzilla: INTERNAL
Upstream Status: RHEL-only
Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
The RHEL container is now available so we can unify the architecture
list. We also need to specify which CKI power builder should be used,
as CKI has more of them and not all are supported for c9s/RHEL9.
Bugzilla: INTERNAL
Upstream Status: RHEL-only
Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
Since the initial implementation, we've added a few more common options
and anchors into the kernel templates. Relevant here is .rhel_common
which we can now use, so we don't forget to update any of the options.
Also split the lines of the "extends" lists to make a visual distinction
between the common (imported) anchors and the ones defined in this CI
file.
Bugzilla: INTERNAL
Upstream Status: RHEL-only
Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
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_MTD_MCHP48L640:
This enables access to Microchip 48L640 EERAM chips, using SPI.
Symbol: MTD_MCHP48L640 [=n]
Type : tristate
Defined at drivers/mtd/devices/Kconfig:92
Prompt: Microchip 48L640 EERAM
Depends on: MTD [=m] && HAS_IOMEM [=y] && SPI_MASTER [=y]
Location:
-> Device Drivers
-> Memory Technology Device (MTD) support (MTD [=m])
-> Self-contained MTD device drivers
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_RESET_MCHP_SPARX5:
This driver supports switch core reset for the Microchip Sparx5 SoC.
Symbol: RESET_MCHP_SPARX5 [=n]
Type : bool
Defined at drivers/reset/Kconfig:117
Prompt: Microchip Sparx5 reset driver
Depends on: RESET_CONTROLLER [=y] && (HAS_IOMEM [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Reset Controller Support (RESET_CONTROLLER [=y])
Selects: MFD_SYSCON [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1890304
Upstream status: RHEL-only
Ampere has requested that CONFIG_NODES_SHIFT be increased to allow for a larger
number of nodes on future platforms. Increase from 4 to 6 to allow for up to 32
nodes.
Signed-off-by: Chris von Recklinghausen <crecklin@redhat.com>
WIRELESS_HOTKEY is not new, it is a rename of the HP_WIRELESS
Kconfig symbol because the same firmware interface is now also used
on laptops from other vendors.
CONFIG_HP_WIRELESS has always been enabled in RHEL kernels and it
was in fact still enabled in 5.13.0-1.el9. So enabling
CONFIG_WIRELESS_HOTKEY basically restores the old status-quo.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1988254
Upstream Status: RHEL only.
Add redhat/configs for CONFIG_NVRAM on regular and debug powerpc kernels.
Signed-off-by: Desnes A. Nunes do Rosario <drosario@redhat.com>
This is the serial driver for Intel Elkhart Lake, plus a few others,
and it needs to be built in for serial console output on x86. This
is no change for ARK, but moves this to common/generic/x86.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Upstream: RHEL only
Bugzilla: 1984784
This patch overrides the drivers/char/random RNGs with the FIPS
RNG from Crypto API when FIPS mode is enabled.
Signed-off-by: Herbert Xu <herbert.xu@redhat.com>
Upstream: RHEL only
Bugzilla: 1984784
This patch introduces a hook mechanism to drivers/char/random
to allow the reads on /dev/*random as well as getrandom(2) to
be overridden by an external RNG.
This will be used to override drivers/char/random with a FIPS
RNG in a subsequent patch.
Signed-off-by: Herbert Xu <herbert.xu@redhat.com>
We decided to disable the Soft-RoCE driver due to the current unstable
status of the driver in the upstream kernel, also because the driver is
not fully maintained in the upstream community.
Upstream: RHEL-only.
Signed-off-by: Kamal Heib <kheib@redhat.com>
https://bugzilla.redhat.com/show_bug.cgi?id=1989983
MAX_LOCKDEP_CHAINS is controlled by LOCKDEP_CHAINS_BITS. We are running
into issues with the default of 16, so let's move it to 17 and double
the MAX_LOCKDEP_CHAINS from 64K to 128K.
CONFIG_LOCKDEP_CHAINS_BITS isn't used in generic kernel. It is only used
in debug kernels where CONFIG_PROVE_LOCKING is turned on.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
Commit 0ec8e4cdd8 ("Build Fedora x86s kernels with bytcr-wm5102"),
tried to enable support for audio on x86_64 device with a WM5102 codec.
But it enabled the CONFIG_MFD_ARIZONA symbol, which is not
user-selectable, so setting it in the fedora config is not necessary
and is in essence a no-op.
The CONFIG_MFD_ARIZONA gets automatically selected as necessary by the
CONFIG_MFD_ARIZONA_I2C/CONFIG_MFD_ARIZONA_SPI Kconfig options.
The x86_64 devices with a WM5102 codec, all use the SPI bus, so this
commit enables CONFIG_MFD_ARIZONA_SPI=m. This commit also a whole bunch
of other symbols which depend on CONFIG_MFD_ARIZONA and thus now
become available. Those necessary for supporting these x86_64 devices
are set to 'm' the rest is left disabled.
Starting with 5.14-rc1 all of the Arizona code can be built as a module
so enabling this will not grow the bzImage size.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1972795
Upstream Status: RHEL only
Tested: on ARM with qemu (Jean-Philippe Brucker's qemu branch as the
qemu integration is not yet upstream, with both protected virtio-blk-pci
and a virtio-net-pci devices)
Commit fe6d9534db ("redhat/configs: Set CONFIG_VIRTIO_IOMMU on aarch64")
enabled the compilation of the virtio-iommu driver on ARM but set the
config to 'm'. However if there are devices behind the vIOMMU that are
needed during the boot such as a virtio-blk-pci device, the guest fails
to boot as the driver is not loaded. Let's fix this bootstrap issue
by compiling the driver in-kernel as it is done for other iommu drivers.
Signed-off-by: Eric Auger <eric.auger@redhat.com>
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_CRYPTO_DEV_SL3516:
This option allows you to have support for SL3516 crypto offloader.
Symbol: CRYPTO_DEV_SL3516 [=n]
Type : tristate
Defined at drivers/crypto/Kconfig:269
Prompt: Stormlink SL3516 crypto offloader
Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && HAS_IOMEM [=y] && PM [=y]
Location:
-> Cryptographic API (CRYPTO [=y])
-> Hardware crypto devices (CRYPTO_HW [=y])
Selects: CRYPTO_SKCIPHER [=y] && CRYPTO_ENGINE [=n] && CRYPTO_ECB [=y] && CRYPTO_AES [=y] && HW_RANDOM [=y]
---
Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Ensure that the ARK configuration follows RHEL 8.5. Especially
the Intel SoundWire drivers were not included and many Intel SOF
driver configurations were not in sync.
Also use power save settings for HDA and AC97 drivers from Fedora.
Hopefully, the drivers are fixed now (the problematic hardware
is detected automatically and the power save is turned off unless
the user force this functionality).
The patchset contains also many cleanups (reshuffling) for common tree
for CONFIG_SND and CONFIG_SOUNDWIRE configuration options.
Signed-off-by: Jaroslav Kysela <jkysela@redhat.com>
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.
Symbol: SND_SOC_SSM2518 [=n]
Type : tristate
Defined at sound/soc/codecs/Kconfig:1327
Prompt: Analog Devices SSM2518 Class-D Amplifier
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && I2C [=y]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> CODEC drivers
Implied by [n]:
- SND_SOC_ALL_CODECS [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n]
---
Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
The Compute Express Link is based upon PCI and is a faster
interconnect that will be supported across most modern
architectures so have a single common config.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1990040
We can't build/ship these modules after export control compliance
review. This was raised in PELC review for RHEL 9.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Right now when we do the dist-git sync, it overrides/deletes everything
which is not on the src.rpm, which might delete any gating configuration
on dist-git. Make sure we always copy the gating configuration for
centos/rhel9. This might need some tweak later if Fedora or future RHEL
uses the same gating file but with different config.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Many modern cloud instance types have hardware with RDRAND, but the RHEL-9
still do not use it. Enable CONFIG_RANDOM_TRUST_CPU the same way as in the
RHEL-8 and Fedora and add ARM too.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976877
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1983298
Upstream: Config only
Testing: keyutils testsuite
The big-key key type is a bool as it's expected to be built into the core
kernel, however it requires ChaCha20Poly1305 crypto to function.
Currently, the crypto bits are built as modules, so BIG_KEYS doesn't even
get enabled. BIG_KEYS does a depends-on in Kconfig because using select is
non-transitive and all the dependencies would need selecting - but that's a
variable list, depending on arch.
Fix this by setting the arch-specific ChaCha20 and Poly1305 deps to =y as
well as the direct crypto library modules required by BIG_KEYS. BIG_KEYS
is already set to =y so that then becomes available automatically.
This was detected by the keyutils testsuite trying to create a big key.
Signed-off-by: David Howells <dhowells@redhat.com>
Due to some change of the kernel makefiles, "samples/bpf" does not work
anymore as a make target. Use M= instead.
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1956988
In the past, some of the kernel tools Makefiles didn't allow the override of
CFLAGS, which made them compiled without stack protector and without position
independent code. This triggers CI failures in RHEL with annocheck.
However, since upstream commits 4ccc98a489
(tools gpio: Allow overriding CFLAGS) and 5729746102
(tools iio: Override CFLAGS assignments), we can override the
compiler flags, so just convert the build of iio and gpio tools to
use tools_make macro as other tools, which passes the correct CFLAGS.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
The current config scripts logic expects the helpnewconfig output for
each item to begin with the full config item name followed by a colon.
But if a config item has no help text then the helpnewconfig output does
not follow this format.
Fix this by adjusting the process_configs.sh and gen_config_patches.sh
awk scripts so they get the config item name from the Symbol: line which
is always present in helpnewconfig output
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
The FSI interface is a POWER specific interface used for BMCs
so only enable it on POWER configs.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
The changes in common are just disables from pending/common. The
rest are updates for Fedora config updates.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
This is only used on x86 chromebooks for a PMIC for some camera
interfaces so we don't need to support it anywhere else. Let's
migrate from the deleted drivers to the new one. The
MFD_TPS68470 driver has been deleted so no functional change
elsewhere.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
The FB_XILINX driver isn't used on any of the Xilinx HW we support,
whereas the FB_ARMCLCD driver has long been replaced by DRM_PL111 and
it was only still enabled in Fedora by mistake.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1940075
Upstream: RHEL only
MAX_LOCKDEP_ENTRIES in lockdep is controlled by CONFIG_LOCKDEP_BITS. By
increasing it from a default of 15 to 16, we double MAX_LOCKDEP_ENTRIES
from 32k to 64k. That should be big enough for our internal use by our
QE.
CONFIG_LOCKDEP_BITS isn't used in generic kernel. It is only used
in debug kernel when CONFIG_LOCKDEP is turned on by the enabling of
CONFIG_PROVE_LOCKING.
Signed-off-by: Waiman Long <longman@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1981406
The current hardlink implementation that is available on latest
util-linux versions (at least >= 2.37) is verbose by default. Thus
lots of output is printed when hardlink runs at the kernel-devel
install with newer hardlink versions. Avoid that by redirecting
the output to /dev/null. I also could use the -q option, but that
may not be available with hardlink versions eg. on older stable Fedora
versions where current kernels might still be built for them, so the
redirection seems the safest approach.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1977056
This is a cherry pick from the following rhel-8 change into kernel-ark:
commit 88049ff66893839cb85731db809b1ba47a3a23f3
Author: Rafael Aquini <aquini@redhat.com>
Date: Tue Jun 25 19:25:09 2019 -0400
[rpmspec] correct the ghost initramfs attributes
Message-id: <0d44bbb391ffd1cee003581ffffb93ad315b4e27.1561490617.git.aquini@redhat.com>
Patchwork-id: 265851
O-Subject: [RHEL8 PATCH] redhat: spec: correct the ghost initramfs attributes
Bugzilla: 1678881
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1678881
Upstream Status: RHEL only
Build Info: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=22353984
This patch is a forward port of the following RHEL-7 commit:
commit f9e549645b10405f8b12f07649327ea293a5a78a
Author: Kyle Walker <kwalker@redhat.com>
Date: Mon Feb 4 19:11:11 2019 -0500
[redhat] spec: Correct the ghost initramfs attributes
Message-id: <20190204191110.4217-1-kwalker@redhat.com>
Patchwork-id: 239860
O-Subject: [RHEL7 BZ 1571909] spec: Correct the ghost initramfs attributes
Bugzilla: 1571909
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Patrick Talbert <ptalbert@redhat.com>
Bugzilla: 1571909
Message-id: <20190204191110.4217-1-kwalker@redhat.com>
Patchwork-id: 239860
O-Subject: [RHEL7 BZ 1571909] spec: Correct the ghost initramfs attributes
Bugzilla: 1571909
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Patrick Talbert <ptalbert@redhat.com>
Bugzilla: 1571909
Upstream Status: RHEL only
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=20067072
The initramfs ghost directive doesn't include the necessary attributes
macro. When generating the initramfs, dracut sets the umask to 0077, which
will result in 0600 as shown below.
# dracut -f 2>/dev/null 1>&2
# ls -l /boot/initramfs-3.10.0-957.1.3.el7.x86_64.img
-rw-------. 1 root root 21266044 Feb 4 12:09 /boot/initramfs-3.10.0-957.1.3.el7.x86_64.img
But this doesn't match the specfile which currently assumes 0644 and
results in RPM verification failures.
# rpm -V kernel
.M....... g /boot/initramfs-3.10.0-957.1.3.el7.x86_64.img
The issue was masked in previous releases as ghost directives were never
properly verified as indicated in BZ1395818. Resolved by applying a 0600
attribute set for ghost initramfs entries.
Signed-off-by: Kyle Walker <kwalker@redhat.com>
Signed-off-by: Jan Stancek <jstancek@redhat.com>
Signed-off-by: Rafael Aquini <aquini@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1977056
Right now we don't remove the file modules.builtin.alias.bin from the
list of depmod files we already remove at the kernel build time. This
makes it being included in the kernel-core package and being listed
with rpm -V output, eg.:
$ rpm -V kernel-core
(...)
.......T. /lib/modules/5.14.0-0.rc2.23.el9.x86_64/modules.builtin.alias.bin
I just redid the removal command to explicitly call each file created by depmod.
We could by mistake do a glob like modules.builtin.* which would wrongly include
modules.builtin.modinfo for example, so seems safest to do it this way. While at
it I removed the *map glob which may be was needed in the past (may
be very distant past?) but this file is not created anymore. I manually
verified the amended list to what is in kmod sources at tools/depmod.c,
at the depmod_output() function.
This also removes the duplicated removal calls, instead of having to
modify two places, just do a single function and call it in the two places
it's needed.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
CONFIG_DRM_HYPERV was set for x86 by !1259 and then for everyone by
!1213. It is only needed for x86 so remove the less specific one.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
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_DRM_HYPERV:
This is a KMS driver for Hyper-V synthetic video device. Choose this
option if you would like to enable drm driver for Hyper-V virtual
machine. Unselect Hyper-V framebuffer driver (CONFIG_FB_HYPERV) so
that DRM driver is used by default.
If M is selected the module will be called hyperv_drm.
Symbol: DRM_HYPERV [=n]
Type : tristate
Defined at drivers/gpu/drm/Kconfig:382
Prompt: DRM Support for Hyper-V synthetic video device
Depends on: HAS_IOMEM [=y] && DRM [=m] && PCI [=y] && MMU [=y] && HYPERV [=m]
Location:
-> Device Drivers
-> Graphics support
Selects: DRM_KMS_HELPER [=m] && DRM_GEM_SHMEM_HELPER [=y]
---
CONFIG_DRM_ITE_IT66121:
Support for ITE IT66121 HDMI bridge.
Symbol: DRM_ITE_IT66121 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:121
Prompt: ITE IT66121 HDMI bridge
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_KMS_HELPER [=m] && REGMAP_I2C [=m]
---
CONFIG_DRM_SIMPLEDRM:
DRM driver for simple platform-provided framebuffers.
This driver assumes that the display hardware has been initialized
by the firmware or bootloader before the kernel boots. Scanout
buffer, size, and display format must be provided via device tree,
UEFI, VESA, etc.
On x86 and compatible, you should also select CONFIG_X86_SYSFB to
use UEFI and VESA framebuffers.
Symbol: DRM_SIMPLEDRM [=n]
Type : tristate
Defined at drivers/gpu/drm/tiny/Kconfig:41
Prompt: Simple framebuffer driver
Depends on: HAS_IOMEM [=y] && DRM [=m]
Location:
-> Device Drivers
-> Graphics support
Selects: DRM_GEM_SHMEM_HELPER [=y] && DRM_KMS_HELPER [=m]
---
CONFIG_DRM_TI_SN65DSI83:
Texas Instruments SN65DSI83 and SN65DSI84 DSI to LVDS Bridge driver
Symbol: DRM_TI_SN65DSI83 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:288
Prompt: TI SN65DSI83 and SN65DSI84 DSI to LVDS bridge
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_KMS_HELPER [=m] && REGMAP_I2C [=m] && DRM_PANEL [=y] && DRM_MIPI_DSI [=n]
---
CONFIG_HSA_AMD_SVM:
Enable this to use unified memory and managed memory in HIP. This
memory manager supports two modes of operation. One based on
preemptions and one based on page faults. To enable page fault
based memory management on most GFXv9 GPUs, set the module
parameter amdgpu.noretry=0.
Symbol: HSA_AMD_SVM [=y]
Type : bool
Defined at drivers/gpu/drm/amd/amdkfd/Kconfig:16
Prompt: Enable HMM-based shared virtual memory manager
Depends on: HAS_IOMEM [=y] && HSA_AMD [=y] && DEVICE_PRIVATE [=y]
Location:
-> Device Drivers
-> Graphics support
-> AMD GPU (DRM_AMDGPU [=m])
-> HSA kernel driver for AMD GPU devices (HSA_AMD [=y])
Selects: HMM_MIRROR [=y] && MMU_NOTIFIER [=y]
---
Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Cc: Jeremy Cline <jcline@redhat.com>
Cc: "Michel Dänzer" <mdaenzer@redhat.com>
Cc: "Jérôme Glisse" <jglisse@redhat.com>
Cc: Karol Herbst <kherbst@redhat.com>
Cc: Ben Skeggs <bskeggs@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Small cleanup to simplify code by re-using duplicated sections through
extends.
Also remove legacy config branch push (now done through merge_upstream).
Signed-off-by: Don Zickus <dzickus@redhat.com>
https://fedoraproject.org//wiki/Changes/UnversionedDocdirs says:
Packages for which multiple versions are intended to be installed need to
be changed to install their docs into appropriately versioned subdirs.
kernel docs are currently installed to /usr/share/doc/kernel-doc-$VERSION
(for example: /usr/share/doc/kernel-doc-5.14.0), which prevents user
from having kernel docs installed for multiple releases if they happen
to share same $VERSION. This is more visible in downstream releases,
where $VERSION is same for entire lifetime of stream.
This patch adds $RELEASE to kernel doc directory name to allow installing
multiple versions in parallel.
Signed-off-by: Jan Stancek <jstancek@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1880486
Upstream Status: RHEL only.
Add redhat/configs for new CONFIG_INTEL_PMT_CRASHLOG.
Autogenerated & verified by editconfig.
Signed-off-by: David Arcari <darcari@redhat.com>
Signed-off-by: Michael Petlan <mpetlan@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1880486
Upstream Status: RHEL only.
Add redhat/configs for new CONFIG_INTEL_PMT_TELEMETRY.
Autogenerated & verified by editconfig.
Signed-off-by: David Arcari <darcari@redhat.com>
Signed-off-by: Michael Petlan <mpetlan@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1880486
Upstream Status: RHEL only.
Add redhat/configs for new CONFIG_MFD_INTEL_PMT.
Autogenerated & verified by editconfig.
Signed-off-by: David Arcari <darcari@redhat.com>
Signed-off-by: Michael Petlan <mpetlan@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1638087
This option has been enabled in Fedora already.
Also it is mentioned in this BZ that 'our current plan is to enable this
in RHEL 9 first', so enable this option in redhat/configs/common so that
people can use ZNS via userspace or play it via nvme-cli.
Signed-off-by: Ming Lei <ming.lei@redhat.com>
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_STACKTRACE_BUILD_ID:
Selecting this option adds build ID information for symbols in
stacktraces printed with the printk format '%p[SR]b'.
This option is intended for distros where debuginfo is not easily
accessible but can be downloaded given the build ID of the vmlinux or
kernel module where the function is located.
Symbol: STACKTRACE_BUILD_ID [=n]
Type : bool
Defined at lib/Kconfig.debug:38
Prompt: Show build ID information in stacktraces
Depends on: PRINTK [=y]
Location:
-> Kernel hacking
-> printk and dmesg options
---
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Aristeu Rozanski <arozansk@redhat.com>
Cc: Christoph von Recklinghausen <crecklin@redhat.com>
Cc: Eugene Syromiatnikov <esyromia@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Nico Pache <npache@redhat.com>
Cc: Oleg Nesterov <onestero@redhat.com>
Cc: Rafael Aquini <aquini@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
This also requires the --with toolchain_clang option in order to be
fully enabled. Currently only supported with x86_64 and aarch64.
As a part of this change, the process_configs.sh script has been updated
so that it can be passed additional make options via the -m flag. The
LTO related config options depend on CONFIG_CC_IS_CLANG, and so the make
invocations in this script need to be passed CC=clang in order for the LTO
options to be enabled.
Signed-off-by: Tom Stellard <tstellar@redhat.com>
Upstream is preparing to remove DVB_AV7110 as it only supports
MPEG2 and most DVB stream require newer codecs, and has other
issues. Upstream commits are 989cf18 and b998a59.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
After every scheduled upstream merge, a script is run to find new
configs, generate pending-* files for them and for ark, create
branches to push MRs.
However, there is a case where new Fedora configs are found but not
new ARK configs. This case had issues.
When the merge is done, make dist-configs-commit is called for Fedora
and RHEL. This results in a possible new commit if configs are found.
The command is run twice and creates the following matrix:
1. Both Fedora and RHEL have new configs.
2. Neither Fedora nor RHEL have new configs.
3. Fedora does not have new configs, but RHEL does.
4. Fedora has new configs, bug RHEL does not.
1 and 2 are common and 1-3 are handled correctly.
Scenario 4 is not.
When the configs are committed, the next script gen_config_patches.sh
looks for a special commit 'AUTOMATIC'. It doesn't care if that commit
comes from Fedora or RHEL.
The gen_config_patches.sh can not handle pending-fedora changes, so
those changes are filtered in the script.
In scenario 4 that leaves an empty file to process, which the script
aborts on. Further no print out was displayed which slowed down
debugging.
The are multiple ways to address this. This patch does multiple things.
* Adds a print statement on the failure for future debugging.
* Exits on success if there are no changes to process after filtering.
* Reduces the risk of calling gen_config_patches.sh by only calling
the script when RHEL adds new configs.
Tested scenario 4 with last week's os-build HEAD.
Signed-off-by: Don Zickus <dzickus@redhat.com>
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_OSNOISE_TRACER:
In the context of high-performance computing (HPC), the Operating
System Noise (osnoise) refers to the interference experienced by an
application due to activities inside the operating system. In the
context of Linux, NMIs, IRQs, SoftIRQs, and any other system thread
can cause noise to the system. Moreover, hardware-related jobs can
also cause noise, for example, via SMIs.
The osnoise tracer leverages the hwlat_detector by running a similar
loop with preemption, SoftIRQs and IRQs enabled, thus allowing all
the sources of osnoise during its execution. The osnoise tracer takes
note of the entry and exit point of any source of interferences,
increasing a per-cpu interference counter. It saves an interference
counter for each source of interference. The interference counter for
NMI, IRQs, SoftIRQs, and threads is increased anytime the tool
observes these interferences' entry events. When a noise happens
without any interference from the operating system level, the
hardware noise counter increases, pointing to a hardware-related
noise. In this way, osnoise can account for any source of
interference. At the end of the period, the osnoise tracer prints
the sum of all noise, the max single noise, the percentage of CPU
available for the thread, and the counters for the noise sources.
In addition to the tracer, a set of tracepoints were added to
facilitate the identification of the osnoise source.
The output will appear in the trace and trace_pipe files.
To enable this tracer, echo in "osnoise" into the current_tracer
file.
Symbol: OSNOISE_TRACER [=n]
Type : bool
Defined at kernel/trace/Kconfig:359
Prompt: OS Noise tracer
Depends on: TRACING_SUPPORT [=y] && FTRACE [=y]
Location:
-> Kernel hacking
-> Tracers (FTRACE [=y])
Selects: GENERIC_TRACER [=y]
Selected by [n]:
- TIMERLAT_TRACER [=n] && TRACING_SUPPORT [=y] && FTRACE [=y]
---
CONFIG_TIMERLAT_TRACER:
The timerlat tracer aims to help the preemptive kernel developers
to find sources of wakeup latencies of real-time threads.
The tracer creates a per-cpu kernel thread with real-time priority.
The tracer thread sets a periodic timer to wakeup itself, and goes
to sleep waiting for the timer to fire. At the wakeup, the thread
then computes a wakeup latency value as the difference between
the current time and the absolute time that the timer was set
to expire.
The tracer prints two lines at every activation. The first is the
timer latency observed at the hardirq context before the
activation of the thread. The second is the timer latency observed
by the thread, which is the same level that cyclictest reports. The
ACTIVATION ID field serves to relate the irq execution to its
respective thread execution.
The tracer is build on top of osnoise tracer, and the osnoise:
events can be used to trace the source of interference from NMI,
IRQs and other threads. It also enables the capture of the
stacktrace at the IRQ context, which helps to identify the code
path that can cause thread delay.
Symbol: TIMERLAT_TRACER [=n]
Type : bool
Defined at kernel/trace/Kconfig:393
Prompt: Timerlat tracer
Depends on: TRACING_SUPPORT [=y] && FTRACE [=y]
Location:
-> Kernel hacking
-> Tracers (FTRACE [=y])
Selects: OSNOISE_TRACER [=n] && GENERIC_TRACER [=y]
---
Cc: Jerome Marchand <jmarchan@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_FXLS8962AF_I2C:
Say yes here to build support for the NXP 3-axis automotive
accelerometer FXLS8962AF/FXLS8964AF with I2C support.
To compile this driver as a module, choose M here: the module
will be called fxls8962af_i2c.
Symbol: FXLS8962AF_I2C [=n]
Type : tristate
Defined at drivers/iio/accel/Kconfig:235
Prompt: NXP FXLS8962AF/FXLS8964AF Accelerometer I2C Driver
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Accelerometers
Selects: FXLS8962AF [=n] && REGMAP_I2C [=m]
---
CONFIG_FXLS8962AF_SPI:
Say yes here to build support for the NXP 3-axis automotive
accelerometer FXLS8962AF/FXLS8964AF with SPI support.
To compile this driver as a module, choose M here: the module
will be called fxls8962af_spi.
Symbol: FXLS8962AF_SPI [=n]
Type : tristate
Defined at drivers/iio/accel/Kconfig:247
Prompt: NXP FXLS8962AF/FXLS8964AF Accelerometer SPI Driver
Depends on: IIO [=m] && SPI [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Accelerometers
Selects: FXLS8962AF [=n] && REGMAP_SPI [=m]
---
CONFIG_IIO_ST_LSM9DS0:
Say yes here to build support for STMicroelectronics LSM9DS0 IMU
sensor. Supported devices: accelerometer/magnetometer of lsm9ds0.
To compile this driver as a module, choose M here: the module
will be called st_lsm9ds0.
Symbol: IIO_ST_LSM9DS0 [=n]
Type : tristate
Defined at drivers/iio/imu/st_lsm9ds0/Kconfig:3
Prompt: STMicroelectronics LSM9DS0 IMU driver
Depends on: IIO [=m] && (I2C [=y] || SPI_MASTER [=y]) && SYSFS [=y] && !SENSORS_LIS3_I2C [=m] && !SENSORS_LIS3_SPI [=n]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Inertial measurement units
Selects: IIO_ST_LSM9DS0_I2C [=n] && IIO_ST_LSM9DS0_SPI [=n] && IIO_ST_ACCEL_3AXIS [=n] && IIO_ST_MAGN_3AXIS [=n]
---
CONFIG_SCA3300:
Say yes here to build support for Murata SCA3300 3-Axis
accelerometer.
To compile this driver as a module, choose M here: the module will be
called sca3300.
Symbol: SCA3300 [=n]
Type : tristate
Defined at drivers/iio/accel/Kconfig:482
Prompt: Murata SCA3300 3-Axis Accelerometer Driver
Depends on: IIO [=m] && SPI [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Accelerometers
Selects: CRC8 [=m] && IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]
---
CONFIG_SPS30_I2C:
Say Y here to build support for the Sensirion SPS30 I2C interface
driver.
To compile this driver as a module, choose M here: the module will
be called sps30_i2c.
Symbol: SPS30_I2C [=n]
Type : tristate
Defined at drivers/iio/chemical/Kconfig:139
Prompt: SPS30 particulate matter sensor I2C driver
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Chemical Sensors
Selects: SPS30 [=n] && CRC8 [=m]
---
CONFIG_TI_TSC2046:
Say yes here to build support for ADC functionality of Texas
Instruments TSC2046 touch screen controller.
This driver can also be built as a module. If so, the module will be
called ti-tsc2046.
Symbol: TI_TSC2046 [=n]
Type : tristate
Defined at drivers/iio/adc/Kconfig:1193
Prompt: Texas Instruments TSC2046 ADC driver
Depends on: IIO [=m] && SPI [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Analog to digital converters
Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]
---
CONFIG_TMP117:
If you say yes here you get support for the Texas Instruments
TMP117 Digital temperature sensor with integrated NV memory.
This driver can also be built as a module. If so, the module will
be called tmp117.
Symbol: TMP117 [=n]
Type : tristate
Defined at drivers/iio/temperature/Kconfig:99
Prompt: TMP117 Digital temperature sensor with integrated NV memory
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Temperature sensors
---
CONFIG_TSL2591:
Select Y here for support of the AMS/TAOS TSL2591 ambient light sensor,
featuring channels for combined visible + IR intensity and lux illuminance.
Access data via iio and sysfs. Supports iio_events.
To compile this driver as a module, select M: the
module will be called tsl2591.
Symbol: TSL2591 [=n]
Type : tristate
Defined at drivers/iio/light/Kconfig:502
Prompt: TAOS TSL2591 ambient light sensor
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Light sensors
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_COMMON_CLK_HI3559A:
Build the clock driver for hi3559a.
Symbol: COMMON_CLK_HI3559A [=y]
Type : bool
Defined at drivers/clk/hisilicon/Kconfig:18
Prompt: Hi3559A Clock Driver
Depends on: COMMON_CLK [=y] && (ARCH_HISI [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Common Clock Framework (COMMON_CLK [=y])
---
CONFIG_LMK04832:
Say yes here to build support for Texas Instruments' LMK04832 Ultra
Low-Noise JESD204B Compliant Clock Jitter Cleaner With Dual Loop PLLs
Symbol: LMK04832 [=n]
Type : tristate
Defined at drivers/clk/Kconfig:54
Prompt: Ti LMK04832 JESD204B Compliant Clock Jitter Cleaner
Depends on: COMMON_CLK [=y] && SPI [=y]
Location:
-> Device Drivers
-> Common Clock Framework (COMMON_CLK [=y])
Selects: REGMAP_SPI [=m]
---
Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v3:
- CONFIG_COMMON_CLK_HI3559A enabled for fedora.
v2:
- CONFIG_COMMON_CLK_HI3559A moved to arm/aarch64 and disabled.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
The Linux framebuffer device stack is EOL so we should use the
HyperV drm driver rather than the FB driver.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
There's no functional change here for either ARK or Fedora as the
configs were the same, this just cleans them up and unifies them
for easier mangmement.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
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_FFA_TRANSPORT:
This Firmware Framework(FF) for Arm A-profile processors describes
interfaces that standardize communication between the various
software images which includes communication between images in
the Secure world and Normal world. It also leverages the
virtualization extension to isolate software images provided
by an ecosystem of vendors from each other.
This driver provides interface for all the client drivers making
use of the features offered by ARM FF-A.
Symbol: ARM_FFA_TRANSPORT [=n]
Type : tristate
Defined at drivers/firmware/arm_ffa/Kconfig:2
Prompt: Arm Firmware Framework for Armv8-A
Depends on: OF [=y] && ARM64 [=y]
Location:
-> Firmware Drivers
---
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Add CI for mirrored c9s and future RHEL9 repositories. Make use of the
new defaults and templates so we don't have to define everything all
over again.
The c9s/RHEL9 specific parts can be extracted into the repos when the
ARK mirror stops and be removed from here.
Upstream Status: RHEL-only
Bugzilla: INTERNAL
Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
Upstream commit 788691464c has changed SLUB_DEBUG to select
STACKDEPOT if STACKTRACE_SUPPORT. STACKDEPOT in turn selects STACKTRACE.
As s390x has stacktrace support, this leaves us with the option of
turning on STACKTRACE for s390x zfcpdump kernels or turning off
SLUB_DEBUG on those kernels.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
RHEL9 for Aarch64 will use 4K pages. Shuffle the related configs
around so that they are shared by both ark and fedora.
Signed-off-by: Mark Salter <msalter@redhat.com>
Enable the I2C based TPM2 modules on all Fedora arches except s390x.
They're needed on POWER64 for various security functions and we need
them on x86/aarch64 for IoT and other bits.
Also enable them on aarch64 for RHEL as we need them for RHEL for Edge.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1972795
Upstream Status: RHEL only
Tested: on ARM with qemu (Jean-Philippe Brucker's qemu branch as the
qemu integration is not yet upstream)
We want to support the virtio-iommu on ARM. So let's compile it.
Signed-off-by: Eric Auger <eric.auger@redhat.com>
---
v1 -> v2:
- do not set the config in ark/generic/arm/aarch64 but rather
in common/generic/arm/aarch64 and just cares about the setting
for ARM as the default already is set to false in common.
Fedora and rhel-rt config already have CONFIG_RT_GROUP_SCHED disabled.
RT_GROUP_SCHED does not play well with cgroups v2. Rather than keep
this enabled, disable it in rhel going forward.
Signed-off-by: Phil Auld <pauld@redhat.com>
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_FB_SSD1307:
This driver implements support for the Solomon SSD1307
OLED controller over I2C.
Symbol: FB_SSD1307 [=n]
Type : tristate
Defined at drivers/video/fbdev/Kconfig:2209
Prompt: Solomon SSD1307 framebuffer support
Depends on: HAS_IOMEM [=y] && FB [=y] && I2C [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Graphics support
-> Frame buffer Devices
-> Support for frame buffer devices (FB [=y])
Selects: FB_SYS_FOPS [=m] && FB_SYS_FILLRECT [=m] && FB_SYS_COPYAREA [=m] && FB_SYS_IMAGEBLIT [=m] && FB_DEFERRED_IO [=y] && PWM [=y] && FB_BACKLIGHT [=n]
---
Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Cc: Jeremy Cline <jcline@redhat.com>
Cc: "Michel Dänzer" <mdaenzer@redhat.com>
Cc: "Jérôme Glisse" <jglisse@redhat.com>
Cc: Karol Herbst <kherbst@redhat.com>
Cc: Ben Skeggs <bskeggs@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Enable KEXEC_SIG for s390x and x86_64 which is already enabled in RHEL8.
Note when building .src.rpm, process_configs.sh would error on unset config
options. So CONFIG_KEXEC_SIG_FORCE files are added as well.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976835
Signed-off-by: Coiby Xu <coxu@redhat.com>
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_WATCHDOG_HRTIMER_PRETIMEOUT:
Enable this if you want to use a hrtimer timer based pretimeout for
watchdogs that do not natively support pretimeout support. Be aware
that because this pretimeout functionality uses hrtimers, it may not
be able to fire before the actual watchdog fires in some situations.
Symbol: WATCHDOG_HRTIMER_PRETIMEOUT [=n]
Type : bool
Defined at drivers/watchdog/Kconfig:76
Prompt: Enable watchdog hrtimer-based pretimeouts
Depends on: WATCHDOG [=y]
Location:
-> Device Drivers
-> Watchdog Timer Support (WATCHDOG [=y])
---
Cc: Jonathan Toppins <jtoppins@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_INFINIBAND_IRDMA:
This is an Intel(R) Ethernet Protocol Driver for RDMA driver
that support E810 (iWARP/RoCE) and X722 (iWARP) network devices.
Symbol: INFINIBAND_IRDMA [=n]
Type : tristate
Defined at drivers/infiniband/hw/irdma/Kconfig:2
Prompt: Intel(R) Ethernet Protocol Driver for RDMA
Depends on: INFINIBAND [=m] && (INFINIBAND_USER_ACCESS [=m] || !INFINIBAND_USER_ACCESS [=m]) && INET [=y] && (IPV6 [=y] || !IPV6 [=y]) && PCI [=y] && ICE [=m] && I40E [=m]
Location:
-> Device Drivers
-> InfiniBand support (INFINIBAND [=m])
Selects: GENERIC_ALLOCATOR [=y] && CONFIG_AUXILIARY_BUS
---
Cc: Kamal Heib <kheib@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v2:
CONFIG_INFINIBAND_IRDMA enabled as a module.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
Turns out we also need to keep bpftool BuildRequires out of noarch as
well, at least on a recent centos koji build I bumped into it:
BuildError: error building package (arch noarch), mock exited with status (...)
Executing command: ['/usr/bin/dnf', 'builddep', '--installroot', (...)
(...)
DEBUG util.py:444: No matching package to install: 'bpftool'
(...)
DEBUG util.py:444: Not all dependencies satisfied
DEBUG util.py:444: Error: Some packages could not be found.
DEBUG util.py:598: Child return code was: 1
DEBUG util.py:169: kill orphans
noarch doesn't build any kernel of course so just keep it out too.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1977529
This option was enabled by mistake (from my own part): this is only used for
allowing the option {IMA,EVM}_X509_PATH to be set with a specific path in
the system pointing to a valid X509 certificate, specific built for the
integrity subsystem. It turns out that we don't have such certificate and am
not sure it's going to be used anytime soon. In RHEL-8 we've allowed trusted
certificates to the integrity subsystem using the secure boot CA and the
certs used for the kernel build.
With these options set we have the following two error lines in dmesg:
integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1953486
Upstream Status: RHEL only
As part of Red Hat’s commitment to remove problematic language from
our code, documentation, websites, and open source projects that we
are involved with, this patch renames kABI whitelist to stablelist.
Signed-off-by: Čestmír Kalina <ckalina@redhat.com>
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_MEDIATEK_GE_PHY:
Supports the MediaTek Gigabit Ethernet PHYs.
Symbol: MEDIATEK_GE_PHY [=n]
Type : tristate
Defined at drivers/net/phy/Kconfig:210
Prompt: MediaTek Gigabit Ethernet PHYs
Depends on: NETDEVICES [=y] && PHYLIB [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> PHY Device support and infrastructure (PHYLIB [=y])
---
CONFIG_MOTORCOMM_PHY:
Enables support for Motorcomm network PHYs.
Currently supports the YT8511 gigabit PHY.
Symbol: MOTORCOMM_PHY [=n]
Type : tristate
Defined at drivers/net/phy/Kconfig:237
Prompt: Motorcomm PHYs
Depends on: NETDEVICES [=y] && PHYLIB [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> PHY Device support and infrastructure (PHYLIB [=y])
---
Cc: Petr Oros <poros@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_HUGETLB_PAGE_FREE_VMEMMAP_DEFAULT_ON:
When using HUGETLB_PAGE_FREE_VMEMMAP, the freeing unused vmemmap
pages associated with each HugeTLB page is default off. Say Y here
to enable freeing vmemmap pages of HugeTLB by default. It can then
be disabled on the command line via hugetlb_free_vmemmap=off.
Symbol: HUGETLB_PAGE_FREE_VMEMMAP_DEFAULT_ON [=n]
Type : bool
Defined at fs/Kconfig:248
Prompt: Default freeing vmemmap pages of HugeTLB to on
Depends on: HUGETLB_PAGE_FREE_VMEMMAP [=y]
Location:
-> File systems
-> Pseudo filesystems
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
This patch is a forward-port from what we already have in RHEL-8 kernels and
should also be done in RHEL-9 to avoid unexpected failures on customers.
Add the secure boot key certificate to the trusted kernel keyring
(.builtin_trusted_keys) to allow the placement of the kernel signing key
(shipped with the distro) in other kernel trusted keyrings, i.e. .ima
trusted keyring.
The need for adding the secure boot CA cert in the trusted kernel keyring
exists only for arches without UEFI support which don't support adding certs
to .platform_keyring and, consequently, can't add our own kernel image
signing key to trusted keyrings.
The biggest usage of that is for loading signed kernel images during
kexec/kdump process in arches that depends on the IMA infrastructure to
check the signatures, which has the ability to verify appended signatures
instead of the UEFI PE format. Said arches are PowerPC and S390X.
Cc: Justin M. Forbes <jforbes@fedoraproject.org>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Patrick Talbert <ptalbert@redhat.com>
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
IMA_ARCH_POLICY was already enabled for x86_64 and ppc64le. Recently,
the IMA code handling EFI was unified under
security/integrity/ima/ima_efi.c and aarch64 with CONFIG_EFI can use it
for the IMA_ARCH_POLICY logic.
In somewhat the same way, s390x has all the bits in upstream to enable
IMA_ARCH_POLICY, which is tied with the IMA_SECURE_AND_OR_TRUSTED_BOOT
that s390x supports with its IPL mode and also make use during KEXEC'ing
a kernel image in their secure boot. With that, I'm proactivelly
enabling IMA_ARCH_POLICY for s390x as well.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1858599
Upstream: RHEL-only
Build the mlxbf_gige driver on aarch64 systems for BlueField-2 systems.
The second generation BlueField SoC supports an out-of-band Gigabit
Ethernet management port to the Arm subsystem. This driver supports
TCP/IP network connectivity for that port, and provides back-end routines
to handle basic ethtool requests.
Signed-off-by: Alaa Hleihel <ahleihel@redhat.com>
It has been a long-term demand for having a default crashkernel
value for each kernel build. This helps to manage kernel's
crashkernel usage by kernel version and provide users a reference
default value.
RHEL kernels support a `crashkernel=auto` cmdline param. And kernel
have a built-in default value used when `auto` is specified.
Many attempts are made to push this upstream. Recent attempt to
push this upstream raised a lot of discussions [1].
Upstream is not accepting this `crashkernel=auto` design. So after
more discussions, instead of adding a default value in kernel, just
add a config that packaged with kernel is more doable. Other packages,
like kexec-tools[2], can use this as a reference and update kernel
cmdline param.
[1]: https://lore.kernel.org/linux-mm/20210507010432.IN24PudKT%25akpm@linux-foundation.org/
[2]: https://lists.fedoraproject.org/archives/list/kexec@lists.fedoraproject.org/thread/RXOEJD6NLLELYAT3VAHS5S56SO5AT7WN/
Signed-off-by: Kairui Song <kasong@redhat.com>
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_DELL_WMI_PRIVACY:
This option adds integration with the "Dell Hardware Privacy"
feature of Dell laptops to the dell-wmi driver.
Symbol: DELL_WMI_PRIVACY [=n]
Type : bool
Defined at drivers/platform/x86/dell/Kconfig:167
Prompt: Dell WMI Hardware Privacy Support
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && X86_PLATFORM_DRIVERS_DELL [=y] && DELL_WMI [=m] && LEDS_TRIGGER_AUDIO [=m]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
-> Dell X86 Platform Specific Device Drivers (X86_PLATFORM_DRIVERS_DELL [=y])
-> Dell WMI notifications (DELL_WMI [=m])
---
CONFIG_THINKPAD_LMI:
This driver allows changing BIOS settings on Lenovo machines whose
BIOS support the WMI interface.
To compile this driver as a module, choose M here: the module will
be called think-lmi.
Symbol: THINKPAD_LMI [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:643
Prompt: Lenovo WMI-based systems management driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI_WMI [=m]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
Selects: FW_ATTR_CLASS [=m]
---
CONFIG_WIRELESS_HOTKEY:
This driver provides supports for the wireless buttons found on some AMD,
HP, & Xioami laptops.
On such systems the driver should load automatically (via ACPI alias).
To compile this driver as a module, choose M here: the module will
be called wireless-hotkey.
Symbol: WIRELESS_HOTKEY [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:418
Prompt: Wireless hotkey button
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y] && INPUT [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
---
CONFIG_X86_PLATFORM_DRIVERS_INTEL:
Say Y here to get to see options for device drivers for
various Intel x86 platforms, including vendor-specific
drivers. This option alone does not add any kernel code.
If you say N, all options in this submenu will be skipped
and disabled.
Symbol: X86_PLATFORM_DRIVERS_INTEL [=y]
Type : bool
Defined at drivers/platform/x86/intel/Kconfig:6
Prompt: Intel x86 Platform Specific Device Drivers
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_MFD_QCOM_PM8008:
Select this option to get support for the Qualcomm Technologies, Inc.
PM8008 PMIC chip. PM8008 is a dedicated camera PMIC that integrates
all the necessary power management, housekeeping, and interface
support functions into a single IC. This driver provides common
support for accessing the device by instantiating all the child nodes
under it in the device tree. Additional drivers must be enabled in
order to use the functionality of the device.
Symbol: MFD_QCOM_PM8008 [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:2103
Prompt: QCOM PM8008 Power Management IC
Depends on: HAS_IOMEM [=y] && I2C [=y] && OF [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: REGMAP_I2C [=m] && REGMAP_IRQ [=n]
---
CONFIG_MFD_RT4831:
This enables support for the Richtek RT4831 that includes 4 channel
WLED driving and Display Bias Voltage. It's commonly used to provide
power to the LCD display and LCD backlight.
Symbol: MFD_RT4831 [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:1081
Prompt: Richtek RT4831 four channel WLED and Display Bias Voltage
Depends on: HAS_IOMEM [=y] && I2C [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: MFD_CORE [=y] && REGMAP_I2C [=m]
---
Cc: Torez Smith <torez@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_IOSM:
This driver enables Intel M.2 WWAN Device communication.
If you have one of those Intel M.2 WWAN Modules and wish to use it in
Linux say Y/M here.
If unsure, say N.
Symbol: IOSM [=n]
Type : tristate
Defined at drivers/net/wwan/Kconfig:59
Prompt: IOSM Driver for Intel M.2 WWAN Device
Depends on: NETDEVICES [=y] && WWAN [=y] && INTEL_IOMMU [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Wireless WAN
-> WWAN Driver Core (WWAN [=y])
---
CONFIG_WWAN_HWSIM:
This driver is a developer testing tool that can be used to test WWAN
framework.
To compile this driver as a module, choose M here: the module will be
called wwan_hwsim. If unsure, say N.
Symbol: WWAN_HWSIM [=n]
Type : tristate
Defined at drivers/net/wwan/Kconfig:19
Prompt: Simulated WWAN device
Depends on: NETDEVICES [=y] && WWAN [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Wireless WAN
-> WWAN Driver Core (WWAN [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_PHY_CAN_TRANSCEIVER:
This option enables support for CAN transceivers as a PHY. This
driver provides function for putting the transceivers in various
functional modes using gpios and sets the attribute max link
rate, for CAN drivers.
Symbol: PHY_CAN_TRANSCEIVER [=n]
Type : tristate
Defined at drivers/phy/Kconfig:64
Prompt: CAN transceiver PHY
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=n]
---
CONFIG_PHY_HI3670_USB:
Enable this to support the HISILICON HI3670 USB PHY.
To compile this driver as a module, choose M here.
Symbol: PHY_HI3670_USB [=n]
Type : tristate
Defined at drivers/phy/hisilicon/Kconfig:26
Prompt: hi3670 USB PHY support
Depends on: ARCH_HISI [=y] && ARM64 [=y] || COMPILE_TEST [=n]
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=y] && MFD_SYSCON [=y]
---
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_XILLYUSB:
XillyUSB is the Xillybus variant which uses USB for communicating
with the FPGA.
Set to M if you want Xillybus to use USB for communicating with
the FPGA. The module will be called xillyusb.
Symbol: XILLYUSB [=n]
Type : tristate
Defined at drivers/char/xillybus/Kconfig:42
Prompt: XillyUSB: Xillybus generic FPGA interface for USB
Depends on: USB [=y]
Location:
-> Device Drivers
-> Character devices
Selects: CRC32 [=y] && XILLYBUS_CLASS [=n]
---
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_SCHED_CORE:
This option permits Core Scheduling, a means of coordinated task
selection across SMT siblings. When enabled -- see
prctl(PR_SCHED_CORE) -- task selection ensures that all SMT siblings
will execute a task from the same 'core group', forcing idle when no
matching task is found.
Use of this feature includes:
- mitigation of some (not all) SMT side channels;
- limiting SMT interference to improve determinism and/or performance.
SCHED_CORE is default enabled when SCHED_SMT is enabled -- when
unused there should be no impact on performance.
Symbol: SCHED_CORE [=y]
Type : bool
Defined at kernel/Kconfig.preempt:103
Prompt: Core Scheduling for SMT
Depends on: SCHED_SMT [=y]
Location:
-> General setup
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
This option sets module text and rodata memory will be made read-only,
and non-text memory will be made non-executable. This helps to protect
against against certain security exploits and doesn't affect
performance. We've also had it enabled on ARMv7 for some time without
issues.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
This introduce two empty packages which requires both
kernel{,-debug}-core & kernel{,-debug}-devel for a given package
version. This is usefull for installing version matching packages when
you already have the kernel{,-debug}-core package installed and want to
install the matching {,-debug}-devel package without specifying the
version nor updating the already installed package.
We can not have the kernel{,-debug}-devel packages require the version
matching kernel{,-debug}-core package has this breaks building modules
inside a container:
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1083
This is an enhancement for rpm-ostree based Fedora variants such as
Fedora Silverblue. See the full discussion in:
https://pagure.io/workstation-ostree-config/pull-request/214
Signed-off-by: Timothée Ravier <travier@redhat.com>
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_TEST_CLOCKSOURCE_WATCHDOG:
Enable this option to create a kernel module that will trigger
a test of the clocksource watchdog. This module may be loaded
via modprobe or insmod in which case it will run upon being
loaded, or it may be built in, in which case it will run
shortly after boot.
If unsure, say N.
Symbol: TEST_CLOCKSOURCE_WATCHDOG [=n]
Type : tristate
Defined at lib/Kconfig.debug:2591
Prompt: Test clocksource watchdog in kernel space
Depends on: RUNTIME_TESTING_MENU [=y] && CLOCKSOURCE_WATCHDOG [=y]
Location:
-> Kernel hacking
-> Kernel Testing and Coverage
-> Runtime Testing (RUNTIME_TESTING_MENU [=y])
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
As of MR 1155 building with_selftests turns on with_bpftool. In order
to properly turn off with_bpftool we must also turn off with_selftests.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
The MR 1153 change which generates the vmlinux.h as an artifact in
kernel-devel seems to have also removed the '%define with_bpftool 0'
from the Fedora section, resulting in a bpftool subpackage being created
in Fedora kernel builds. This is unnecessary for the vmlinux.h
generation and undesired from a Fedora packaging standpoint.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
The most recent pull of tip included changes to switch from using
syscalltbl.sh and syscallhdr.sh in arch/x86/entry/syscalls/ to the
generic versions in scripts/. As those were included in kernel-devel we
need to move the locations in the spec or the build will fail.
Upstream commits for reference:
6218d0f6b83cba325b35
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
Previous commit "rpmspec: build debug-* meta-packages if debug
builds are disabled" failed to consider the architectures or
cases where we disable debug packages, and made meta packages
being built for them even if real debug package build was
disabled in the normal case. So eg. for arches we don't build
kernels (eg. i686) debug meta packages could appear even if we
don't have kernel/kernel-debug being built.
This adds some logic to see if really with_debug was enabled,
and creating the meta-package only when it is enabled/set.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
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_IMA_DISABLE_HTABLE:
This option disables htable to allow measurement of duplicate records.
Symbol: IMA_DISABLE_HTABLE [=n]
Type : bool
Defined at security/integrity/ima/Kconfig:338
Prompt: Disable htable to allow measurement of duplicate records
Depends on: INTEGRITY [=y] && IMA [=y]
Location:
-> Security options
-> Integrity subsystem (INTEGRITY [=y])
---
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Kernel builds are failing on i686 due missing or not available bpftool.
It does not make sense to require it on arches that we only build
headers and don't need bpftool, so make it not required on this case.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976270
The CONFIG_HMC_DRV switch is specific to s390x, and uses the same
setting in Fedora and ARK, so we should consolidate this setting
in the redhat/configs/common/generic/s390x/ folder.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976270
The other CONFIG_EXPOLINE_* options already reside in the folder
redhat/configs/common/generic/s390x/, so we should move the
CONFIG_EXPOLINE_OFF switch here, too.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976270
We never enabled this for the RHEL/ARK kernel, so this setting in
Fedora looked suspicious... and after asking some people from IBM,
they confirmed that this is unused on s390x, so we can disable this
now.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976270
The CONFIG_NO_BOOTMEM switch has been removed upstream in commit
b4a991ec58 ("mm: remove CONFIG_NO_BOOTMEM"), so we can drop this
setting in the ARK kernel config now, too.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976270
Since upstream commit bb533ec8ba ("s390/config: do not select VIRTIO_CONSOLE
via Kconfig"), it's possible to build the virtio-console driver as a module
on s390x, too. We've switch the RHEL8 setting to "m" in BZ 1954119, so we
should adapt the Fedora / ARK / RHEL9 setting accordingly now, too (by
disabling the s390x-specific setting, so that we fall back to the generic
CONFIG_VIRTIO_CONSOLE=m setting).
Signed-off-by: Thomas Huth <thuth@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976270
These two options have been enabled for RHEL8 in BZ 1660917, so we should
enable those now in RHEL9/ARK, too.
Signed-off-by: Thomas Huth <thuth@redhat.com>
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_SENSORS_DPS920AB:
If you say yes here you get hardware monitoring support for Delta
DPS920AB Power Supplies.
This driver can also be built as a module. If so, the module will
be called dps920ab.
Symbol: SENSORS_DPS920AB [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:89
Prompt: Delta DPS920AB Power Supply
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
CONFIG_SENSORS_MP2888:
If you say yes here you get hardware monitoring support for MPS
MP2888 Digital, Multi-Phase, Pulse-Width Modulation Controller.
This driver can also be built as a module. If so, the module will
be called mp2888.
Symbol: SENSORS_MP2888 [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:261
Prompt: MPS MP2888
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
CONFIG_SENSORS_PIM4328:
If you say yes here you get hardware monitoring support for Flex
PIM4328, PIM4820 and PIM4006 Power Interface Modules.
This driver can also be built as a module. If so, the module will
be called pim4328.
Symbol: SENSORS_PIM4328 [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:279
Prompt: Flex PIM4328 and compatibles
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
CONFIG_SENSORS_SHT4x:
If you say yes here you get support for the Sensiron SHT40, SHT41 and
SHT45 humidity and temperature sensors.
This driver can also be built as a module. If so, the module
will be called sht4x.
Symbol: SENSORS_SHT4x [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:1586
Prompt: Sensiron humidity and temperature sensors. SHT4x and compat.
Depends on: HWMON [=y] && I2C [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
Selects: CRC8 [=m]
---
Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
We need to revert the merge request !1150 and make CONFIG_CRYPTO_ECDH
and CONFIG_CRYPTO_ECDSA back to =m. Current =y setting prevents a kernel
booting in FIPS mode. This blocks some processes, see bz1915290#c23. This
is an upstream issue and we need this revert until a proposed upstream
solution is fully tested.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1947240
Link: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1150
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
The module compress options are already in common and are the
same so just drop them. No functional change.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Enable the needed configs on aarch64 for enabling the following
on BlueField SoC:
- TmFifo driver to provide console and network access to the external host.
- bootctl platform driver to provide the ability to query secure state
and control the eMMC boot partition swapping by sending SMC calls to
ATF running at EL3.
- ipmb-dev-int driver and it's dependencies for supporting receiving IPMB
requests on a Satellite MC from the BMC. Once a response is ready, this
driver will send back a response to the BMC via the IPMB channel.
Bugzilla: http://bugzilla.redhat.com/1858592
Bugzilla: http://bugzilla.redhat.com/1858594
Bugzilla: http://bugzilla.redhat.com/1858596
Upstream: RHEL-only
Signed-off-by: Alaa Hleihel <ahleihel@redhat.com>
It's enabled on RHEL8 and it's going to be needed on RHEL9 as well.
Cc: Guillaume Nault <gnault@redhat.com>
Signed-off-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
The config checks pass on clang now that the CONFIG_INIT_STACK_ALL_PATTERN
and CONFIG_INIT_STACK_ALL_ZERO have been added to the config files.
Signed-off-by: Tom Stellard <tstellar@redhat.com>
Enabling CONFIG_DEBUG_KERNEL for zfcpdump otherwise
CONFIG_DEBUG_INFO_BTF won't be enabled.
The CONFIG_DEBUG_KERNEL rnabled several other generic
options. Disabling them so the zfcp config stays the
same (apart from CONFIG_DEBUG_INFO_BTF enablement).
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
For split environments where the kernel and userspace tools are not
built together, take the -devel packaged vmlinux.h file and use it
to build bpftools.
Use the VMLINUX_H= env variable to tell the tools which file to use.
Orginally done by Jiri Olsa <jolsa@redhat.com>
Updated to transition from artifacts to -devel package.
Signed-off-by: Don Zickus <dzickus@redhat.com>
Adding/generating vmlinux.h by bpftool to the kernel-devel
package:
$ rpm -ql -p kernel-devel-5.13.0-0.rc...x86_64.rpm | grep vmlinux.h
/usr/src/kernels/5.13.0-0.rc...x86_64/vmlinux.h
Some tools like bpftool or selftest need vmlinux.h to properly
compile. The vmlinux.h will be used by build system to compile
tools separately.
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
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_USB_RTL8153_ECM:
This option supports ECM mode for RTL8153 ethernet adapter, when
CONFIG_USB_RTL8152 is not set, or the RTL8153 device is not
supported by r8152 driver.
Symbol: USB_RTL8153_ECM [=m]
Type : tristate
Defined at drivers/net/usb/Kconfig:631
Prompt: RTL8153 ECM support
Depends on: NETDEVICES [=y] && USB_NET_DRIVERS [=y] && USB_NET_CDCETHER [=m] && (USB_RTL8152 [=m] || USB_RTL8152 [=m]=n)
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> USB Network Adapters (USB_NET_DRIVERS [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_CAN_ETAS_ES58X:
This driver supports the ES581.4, ES582.1 and ES584.1 interfaces
from ETAS GmbH (https://www.etas.com/en/products/es58x.php).
To compile this driver as a module, choose M here: the module
will be called etas_es58x.
Symbol: CAN_ETAS_ES58X [=n]
Type : tristate
Defined at drivers/net/can/usb/Kconfig:23
Prompt: ETAS ES58X CAN/USB interfaces
Depends on: NET [=y] && CAN [=m] && CAN_DEV [=m] && USB [=y]
Location:
-> Networking support (NET [=y])
-> CAN bus subsystem support (CAN [=m])
-> CAN Device Drivers
-> Platform CAN drivers with Netlink support (CAN_DEV [=m])
-> CAN USB interfaces
Selects: CRC16 [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_BMI088_ACCEL:
Say yes here to build support for the Bosch BMI088 accelerometer.
This is a combo module with both accelerometer and gyroscope. This
driver only implements the accelerometer part, which has its own
address and register map. BMG160 provides the gyroscope driver.
Symbol: BMI088_ACCEL [=n]
Type : tristate
Defined at drivers/iio/accel/Kconfig:160
Prompt: Bosch BMI088 Accelerometer Driver
Depends on: IIO [=m] && SPI [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Accelerometers
Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] && REGMAP [=y] && BMI088_ACCEL_SPI [=n]
---
CONFIG_TI_ADS131E08:
Say yes here to get support for Texas Instruments ADS131E04, ADS131E06
and ADS131E08 chips.
This driver can also be built as a module. If so, the module will be
called ti-ads131e08.
Symbol: TI_ADS131E08 [=n]
Type : tristate
Defined at drivers/iio/adc/Kconfig:1157
Prompt: Texas Instruments ADS131E08
Depends on: IIO [=m] && SPI [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Analog to digital converters
Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_EXTCON_USBC_TUSB320:
Say Y here to enable support for USB Type C cable detection extcon
support using a TUSB320.
Symbol: EXTCON_USBC_TUSB320 [=n]
Type : tristate
Defined at drivers/extcon/Kconfig:189
Prompt: TI TUSB320 USB-C extcon support
Depends on: EXTCON [=y] && I2C [=y]
Location:
-> Device Drivers
-> External Connector Class (extcon) support (EXTCON [=y])
Selects: REGMAP_I2C [=m]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_BATTERY_GOLDFISH:
Say Y to enable support for the Goldfish battery and AC power
driver. Originated in the Android Studio Emulator (goldfish) it is
going to be used in other emulators.
Symbol: BATTERY_GOLDFISH [=n]
Type : tristate
Defined at drivers/power/supply/Kconfig:705
Prompt: Goldfish battery driver
Depends on: POWER_SUPPLY [=y] && HAS_IOMEM [=y]
Location:
-> Device Drivers
-> Power supply class support (POWER_SUPPLY [=y])
---
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_PWM_ATMEL_TCB:
Generic PWM framework driver for Atmel Timer Counter Block.
A Timer Counter Block provides 6 PWM devices grouped by 2.
Devices in a given group must have the same period.
To compile this driver as a module, choose M here: the module
will be called pwm-atmel-tcb.
Symbol: PWM_ATMEL_TCB [=n]
Type : tristate
Defined at drivers/pwm/Kconfig:76
Prompt: Atmel TC Block PWM support
Depends on: PWM [=y] && OF [=y]
Location:
-> Device Drivers
-> Pulse-Width Modulation (PWM) Support (PWM [=y])
Selects: REGMAP_MMIO [=n]
---
CONFIG_PWM_DWC:
PWM driver for Synopsys DWC PWM Controller attached to a PCI bus.
To compile this driver as a module, choose M here: the module
will be called pwm-dwc.
Symbol: PWM_DWC [=n]
Type : tristate
Defined at drivers/pwm/Kconfig:167
Prompt: DesignWare PWM Controller
Depends on: PWM [=y] && PCI [=y]
Location:
-> Device Drivers
-> Pulse-Width Modulation (PWM) Support (PWM [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_MTD_NAND_ECC_SW_BCH:
This enables support for software BCH error correction. Binary BCH
codes are more powerful and cpu intensive than traditional Hamming
ECC codes. They are used with NAND devices requiring more than 1 bit
of error correction.
Symbol: MTD_NAND_ECC_SW_BCH [=n]
Type : bool
Defined at drivers/mtd/nand/Kconfig:38
Prompt: Software BCH ECC engine
Depends on: MTD [=m]
Location:
-> Device Drivers
-> Memory Technology Device (MTD) support (MTD [=m])
-> NAND
-> ECC engine support
Selects: BCH [=n] && MTD_NAND_ECC [=n]
---
CONFIG_MTD_NAND_ECC_SW_HAMMING:
This enables support for software Hamming error
correction. This correction can correct up to 1 bit error
per chunk and detect up to 2 bit errors. While it used to be
widely used with old parts, newer NAND chips usually require
more strength correction and in this case BCH or RS will be
preferred.
Symbol: MTD_NAND_ECC_SW_HAMMING [=n]
Type : bool
Defined at drivers/mtd/nand/Kconfig:18
Prompt: Software Hamming ECC engine
Depends on: MTD [=m]
Location:
-> Device Drivers
-> Memory Technology Device (MTD) support (MTD [=m])
-> NAND
-> ECC engine support
Selects: MTD_NAND_ECC [=n]
Selected by [n]:
- SM_FTL [=n] && MTD [=m] && BLOCK [=y]
- MTD_NAND_NDFC [=n] && MTD [=m] && MTD_RAW_NAND [=n] && 4xx
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_ADXRS290:
Say yes here to build support for Analog Devices ADXRS290 programmable
digital output gyroscope.
This driver can also be built as a module. If so, the module will be
called adxrs290.
Symbol: ADXRS290 [=n]
Type : tristate
Defined at drivers/iio/gyro/Kconfig:44
Prompt: Analog Devices ADXRS290 Dual-Axis MEMS Gyroscope SPI driver
Depends on: IIO [=m] && SPI [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Digital gyroscope sensors
Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]
---
CONFIG_AS73211:
If you say yes here you get support for the AMS AS73211
JENCOLOR(R) Digital XYZ Sensor.
For triggered measurements, you will need an additional trigger driver
like IIO_HRTIMER_TRIGGER or IIO_SYSFS_TRIGGER.
This driver can also be built as a module. If so, the module
will be called as73211.
Symbol: AS73211 [=n]
Type : tristate
Defined at drivers/iio/light/Kconfig:89
Prompt: AMS AS73211 XYZ color sensor
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Light sensors
Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]
---
CONFIG_HDC2010:
Say yes here to build support for the Texas Instruments
HDC2010 and HDC2080 relative humidity and temperature sensors.
To compile this driver as a module, choose M here: the module
will be called hdc2010.
Symbol: HDC2010 [=n]
Type : tristate
Defined at drivers/iio/humidity/Kconfig:41
Prompt: TI HDC2010 relative humidity and temperature sensor
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Humidity sensors
---
CONFIG_IIO_BUFFER_DMA:
Provides the generic IIO DMA buffer infrastructure that can be used by
drivers for devices with DMA support to implement the IIO buffer.
Should be selected by drivers that want to use the generic DMA buffer
infrastructure.
Symbol: IIO_BUFFER_DMA [=n]
Type : tristate
Defined at drivers/iio/buffer/Kconfig:13
Prompt: Industrial I/O DMA buffer infrastructure
Depends on: IIO [=m] && IIO_BUFFER [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Enable buffer support within IIO (IIO_BUFFER [=y])
Selected by [n]:
- IIO_BUFFER_DMAENGINE [=n] && IIO [=m] && IIO_BUFFER [=y]
---
CONFIG_IIO_BUFFER_DMAENGINE:
Provides a bonding of the generic IIO DMA buffer infrastructure with the
DMAEngine framework. This can be used by converter drivers with a DMA port
connected to an external DMA controller which is supported by the
DMAEngine framework.
Should be selected by drivers that want to use this functionality.
Symbol: IIO_BUFFER_DMAENGINE [=n]
Type : tristate
Defined at drivers/iio/buffer/Kconfig:22
Prompt: Industrial I/O DMA buffer integration with DMAEngine
Depends on: IIO [=m] && IIO_BUFFER [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Enable buffer support within IIO (IIO_BUFFER [=y])
Selects: IIO_BUFFER_DMA [=n]
Selected by [n]:
- ADI_AXI_ADC [=n] && IIO [=m]
---
CONFIG_IIO_TRIGGERED_EVENT:
Provides helper functions for setting up triggered events.
Symbol: IIO_TRIGGERED_EVENT [=n]
Type : tristate
Defined at drivers/iio/Kconfig:65
Prompt: Enable triggered events support
Depends on: IIO [=m]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
Selects: IIO_TRIGGER [=y]
Selected by [n]:
- HI8435 [=n] && IIO [=m] && SPI [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_USB_CDNS_SUPPORT:
Say Y here if your system has a Cadence USBSS or USBSSP
dual-role controller.
It supports: dual-role switch, Host-only, and Peripheral-only.
Symbol: USB_CDNS_SUPPORT [=n]
Type : tristate
Defined at drivers/usb/cdns3/Kconfig:1
Prompt: Cadence USB Support
Depends on: USB_SUPPORT [=y] && (USB [=y] || USB_GADGET [=n]) && HAS_DMA [=y]
Location:
-> Device Drivers
-> USB support (USB_SUPPORT [=y])
Selects: USB_XHCI_PLATFORM [=n] && USB_ROLE_SWITCH [=m]
---
CONFIG_USB_SERIAL_XR:
Say Y here if you want to use MaxLinear/Exar USB to Serial converter
devices.
To compile this driver as a module, choose M here: the
module will be called xr_serial.
Symbol: USB_SERIAL_XR [=n]
Type : tristate
Defined at drivers/usb/serial/Kconfig:636
Prompt: USB MaxLinear/Exar USB to Serial driver
Depends on: USB_SUPPORT [=y] && USB [=y] && USB_SERIAL [=y]
Location:
-> Device Drivers
-> USB support (USB_SUPPORT [=y])
-> USB Serial Converter support (USB_SERIAL [=y])
---
Cc: Torez Smith <torez@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Enable the QCom ath11k wireless module that ships with a number of
modern devices/laptpos. We enable the PCI module, and MHI/QRTR deps,
plus the AHB module for Fedora Arm but disable all for POWER/s390x.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
The Modem Host Interface (MHI) is used for most newer 4G/LTE and 5G
modems. It's basically virtual ethernet over a PCI <-> PCIE-endpoint
with a control over a TTY interface. These modems are already in the
latest Lenovo laptops and likely others, as well as Edge gateways.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
The bpf selftest and samples suites are quite unstable and might
fail to compile. Make sure that won't break the rpm build and
enable their build.
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
ARK kernel specific change.
Disabling test that won't compile under clang-12.
Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
Backport of RHEL8 commit.
- skipping redhat/git/files hunk
commit 9e682a5da6015f4357aca94592d0a6a9444322bf
Author: Thomas Huth <thuth@redhat.com>
Date: Mon Feb 22 12:20:36 2021 +0100
kvm: Add kvm_stat.service file and kvm_stat logrotate config to the tools
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1919930
Upstream Status: RHEL only
Install the kvm_stat.service systemd file and add a logrotate config
to avoid that the logs fill up the disk space.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Backport of RHEL8 commit.
commit 89f64e99dc9cc67f072621d1016f771302d02c14
Author: Hangbin Liu <haliu@redhat.com>
Date: Wed Dec 16 13:23:29 2020 -0500
[redhat] kernel.spec: add net/forwarding to TARGETS list
Message-id: <20201216132329.2294096-1-haliu@redhat.com>
Patchwork-id: 345158
Patchwork-instance: patchwork
O-Subject: [RHEL8.4 net PATCH] kernel.spec: add net/forwarding to TARGETS list
Bugzilla: 1908340
RH-Acked-by: Andrea Claudi <aclaudi@redhat.com>
RH-Acked-by: Antoine Tenart <atenart@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Ivan Vecera <ivecera@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1908340
Upstream Status: RHEL Only
Since RHEL8 commit 771c0c0fcd28 ("[tools] selftests: Extract
run_kselftest.sh and generate stand-alone test list") the selftest
list will be generated to a separate file kselftest-list.txt based on
TARGETS.
But net/forwarding is not in TARGETS. So the final list will not
contain any forwarding test. This will block the kselftest
in beaker as we can't find forwarding tests in list file.
Signed-off-by: Hangbin Liu <haliu@redhat.com>
Signed-off-by: Timothy Redaelli <tredaelli@redhat.com>
Signed-off-by: Jan Stancek <jstancek@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Backport of RHEL8 commit.
commit 0fd69ec14a91d1bc889e2f9abf1ceb9233334eeb
Author: Davide Caratti <dcaratti@redhat.com>
Date: Tue Nov 24 17:03:55 2020 -0500
[redhat] redhat: kernel.spec: selftests: add action.o to kernel-selftests-internal
Message-id: <fcda1fa45c5388e2eda623530832fc497124837d.1606234520.git.dcaratti@redhat.com>
Patchwork-id: 341690
Patchwork-instance: patchwork
O-Subject: [RHEL8.4 PATCH] redhat: kernel.spec: selftests: add action.o to kernel-selftests-internal
Bugzilla: 1900944
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Hangbin Liu <haliu@redhat.com>
RH-Acked-by: Ivan Vecera <ivecera@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1900944
Upstream Status: RHEL Only
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=33255259
Tested:
# rpm -qlp kernel-selftests-internal-4.18.0-250.el8.bz1900944.x86_64.rpm | grep tc-testing
verified that:
- action.o is included
- all other items are still there
# rpm -ivh kernel-selftests-internal-4.18.0-250.el8.bz1900944.x86_64.rpm
# pushd /usr/libexec/tc-testing
# ./tdc.py -c bpf --nobuildebpf
# popd
(verified that all tests are passing)
Shuang reports that clang/llvm are needed to build action.o, the eBPF
program used by tdc.py, and the eBPF test program is not shipped
in kernel-selftests-internal RPM. Now that tdc execution has been made
compliant to kselftests, it's sufficient to add 'tc-testing' to
TARGETS, as follows:
$ make TARGETS="<list of targets>" <kselftests-target>
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
Signed-off-by: Jan Stancek <jstancek@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Backport of RHEL8 commit.
commit 334cd6472196835d71a4eb0479822e73fa364498
Author: Jiri Benc <jbenc@redhat.com>
Date: Tue Aug 18 13:38:55 2020 -0400
[redhat] redhat: avoid building bpftool repeatedly
Message-id: <5d080c5b61399ad635a271a7ff28a3c63f67d6ff.1597757857.git.jbenc@redhat.com>
Patchwork-id: 324292
Patchwork-instance: patchwork
O-Subject: [RHEL8.3 64/63] redhat: avoid building bpftool repeatedly
Bugzilla: 1866908
RH-Acked-by: Bruno Meneguele <bmeneg@redhat.com>
RH-Acked-by: Frantisek Hrbata <fhrbata@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1866908
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=30777253
Currently, tools/testing/selftests/bpf/Makefile builds bpftool twice, even
though it has already been built.
It is first built as tools/testing/selftests/bpf/tools/build/bpftool/bpftool
and then a build of runqslower is invoked, which builds bpftool again as
tools/testing/selftests/bpf/tools/bpftool. This is not only waste of time
and resources, it's also prone to build errors: the two additional bpftool
builds are run in parallel from the same base directory. As the result, they
both try to create profiler.skel.h, which, depending on timing, may lead to
gcc seeing a truncated include file and failing with weird errors.
There's a mechanism in the makefile to use an already built bpftool. Let's
just use it.
Tested: built and run selftests, everything seems working as it should.
According to brew logs, bpftool is not built anymore from selftests.
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
In ARK, the rpm build continues even if some of the selftests cannot be
built. It's not always possible to build selftests, as upstream sometimes
dependens on too new llvm version or has other issues. If something did not
get built, just skip it.
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
The mentioned commit that blindly copied everything is not included, it
would not make much sense, this patch is completely replacing it.
commit 27bee04408ff1f9dc9257148cdc1a178d847d815
Author: Jiri Benc <jbenc@redhat.com>
Date: Fri Aug 7 13:13:37 2020 -0400
[redhat] redhat: kernel.spec: fix installation of bpf selftests
Message-id: <e86f03cfa84e50ee1cad57c0d102d85321fc1034.1596793349.git.jbenc@redhat.com>
Patchwork-id: 323567
Patchwork-instance: patchwork
O-Subject: [RHEL8.3 58/63] redhat: kernel.spec: fix installation of bpf selftests
Bugzilla: 1866908
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1866908
Upstream status: RHEL only
RHEL 8 commit 7207d2907bd8 ("[redhat] redhat/kernel.spec: install
selftests/bpf separately") attempted to fix installation of bpf selftests.
However, it was blindly copying everything, including source files and build
artifacts.
Install only the files that are actually required, that is executable files,
Python files and BPF object files. There will be also 'settings' file added
later.
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Backport of RHEL8 commit.
- small conflict with already added _smp_mflags
commit a4c21259df563abcb973f969ba4d7ff1868475e1
Author: Jiri Benc <jbenc@redhat.com>
Date: Fri Aug 7 13:13:36 2020 -0400
[redhat] redhat: fix samples and selftests make options
Message-id: <df632ec3de2f11a0fb12a2123eb180cb12e0fd64.1596793349.git.jbenc@redhat.com>
Patchwork-id: 323566
Patchwork-instance: patchwork
O-Subject: [RHEL8.3 57/63] redhat: fix samples and selftests make options
Bugzilla: 1866908
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1866908
The make should not be invoked with -s, it causes all information useful for
build debugging to be missing from the build log. The V=1 is ignored by some
selftests dirs but honored by others, let's keep it there, it does no harm
for the dirs where it is not used.
While touching those make invocations, let's also speed up the build by
using parallel build.
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Backport of RHEL8 commit.
commit de79ce798e1a04173f6d963379f8e48a92e14b67
Author: Michael Petlan <mpetlan@redhat.com>
Date: Tue Jun 23 10:15:03 2020 -0400
[redhat] spec: Do not export shared objects from libexecdir to RPM Provides
Message-id: <20200623101503.11173-1-mpetlan@redhat.com>
Patchwork-id: 321392
Patchwork-instance: patchwork
O-Subject: [RHEL8.3 PATCH v2] spec: Do not export shared objects from libexecdir to RPM Provides
Bugzilla: 1846014
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Rafael Aquini <aquini@redhat.com>
RH-Acked-by: Jiri Olsa <jolsa@redhat.com>
Bugzilla: 1846014https://bugzilla.redhat.com/show_bug.cgi?id=1846014
RHEL-only
The package kernel-selftests-internal incorrectly exported libbpf.so
as Provides, thus libbpf as perf dependency could have been satisfied
by kernel-selftests-internal at the RPM level, although the libbpf.so
file in /usr/libexec could not be used by perf. Don't export the library
if it's invisible to linker.
v1 --> v2
=========
Narrow the exclusion down to files under kselftests in order not to
exclude perl modules in libexec.
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Backport of RHEL8 commit.
commit 324e8df74b709bc19533a6ed0259378a290b4a22
Author: Brian Masney <bmasney@redhat.com>
Date: Fri Apr 24 12:32:20 2020 -0400
[redhat] kernel.spec: add missing dependency for the which package
Message-id: <20200424123220.523325-1-bmasney@redhat.com>
Patchwork-id: 304784
Patchwork-instance: patchwork
O-Subject: [RHEL8.3 BZ 1825838 PATCH v2] [redhat] kernel.spec: add missing dependency for the which package
Bugzilla: 1825838
RH-Acked-by: Luis Goncalves <lgoncalv@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Herton R. Krzesinski <herton@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1825838
Upstream status: RHEL only
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=28065951
Tested: build tested on my workstation and on brew
A RHEL 8.3 build inside a minimal container can fail with the following
error:
*** ERROR: Cannot find LLVM tool clang
make[2]: *** [/usr/src/kernel-rhel/samples/bpf/Makefile:256: verify_cmds] Error 1
make[1]: *** [Makefile:1718: /usr/src/kernel-rhel/samples/bpf/] Error 2
make[1]: Leaving directory '/usr/src/kernel-rhel'
make: *** [Makefile:231: all] Error 2
clang was installed and the real issue is the missing 'which' binary.
Let's go ahead and add that to the BuildRequires to avoid other people
running into this same issue.
Signed-off-by: Brian Masney <bmasney@redhat.com>
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Backport of RHEL8 commit.
commit e3b2d7aef8ad82c55b6f526b1e1318aec3b94d8f
Author: Frantisek Hrbata <fhrbata@redhat.com>
Date: Mon Apr 27 08:53:40 2020 -0400
[redhat] redhat: move slabinfo and page_owner_sort debuginfo to tools-debuginfo
Message-id: <20200427085340.GA5962@localhost.localdomain>
Patchwork-id: 305261
Patchwork-instance: patchwork
O-Subject: [RHEL8.3] redhat: move slabinfo and page_owner_sort debuginfo to tools-debuginfo
Bugzilla: 1828178
RH-Acked-by: Rafael Aquini <aquini@redhat.com>
RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1828178
Upstream Status: RHEL only
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=28196548
Tested: Verified that debuginfo files for slabinfo and page_owner_sort
are included in tools-debuginfo instead of debuginfo-common
Commit d06b1385849f3f5c1ff515888865ccb531ba90e9 ("redhat: spec: package and
ship VM tools"), included in kernel-4.18.0-193.13.el8, added slabinfo and
page_owner_sort tools. Unfortunatelly it missed to add the debuginfo for
these tools to tools-debuginfo package. As a result of this there are two
problems:
1) The debug info, along with build-id links, is presented in debuginfo-common
package, which is obviously wrong.
2) Since debuginfo-common is installonlypkgs the osci installability test fails,
because of conflicts on these files.
Error: Transaction test error:
file /usr/lib/debug/usr/bin/page_owner_sort.debug from install of
kernel-debuginfo-common-x86_64-4.18.0-193.14.el8.x86_64 conflicts
with file from package
kernel-debuginfo-common-x86_64-4.18.0-193.13.el8.x86_64
file /usr/lib/debug/usr/bin/slabinfo.debug from install of
kernel-debuginfo-common-x86_64-4.18.0-193.14.el8.x86_64 conflicts
with file from package
kernel-debuginfo-common-x86_64-4.18.0-193.13.el8.x86_64
Fixes: d06b1385849f ("redhat: spec: package and ship VM tools")
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Backport of RHEL8 commit.
commit d06b1385849f3f5c1ff515888865ccb531ba90e9
Author: Rafael Aquini <aquini@redhat.com>
Date: Mon Apr 20 15:08:53 2020 -0400
[redhat] redhat: spec: package and ship VM tools
Message-id: <1621bdede1391140ca7d51c1afd68bd0d9d89e85.1587394443.git.aquini@redhat.com>
Patchwork-id: 303890
Patchwork-instance: patchwork
O-Subject: [RHEL8 PATCH 2/2] redhat: spec: package and ship VM tools
Bugzilla: 1825432
RH-Acked-by: Don Dutile <ddutile@redhat.com>
RH-Acked-by: Aristeu Rozanski <aris@redhat.com>
RH-Acked-by: Waiman Long <longman@redhat.com>
Upstream status: RHEL only
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1825432
We've been missing these troubleshooting tools in kernel-tools for
too long already. This patch fixes that by building and packaging
both page_owner_sort and slabinfo VM kernel tools.
Signed-off-by: Rafael Aquini <aquini@redhat.com>
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
This seems to be generally useful, enabling it also for Fedora. Note that
the feature is inactive and needs to be enabled by a kernel boot parameter.
Skipping the KABI hunk.
commit 9c1a6617fb272f09474a94a3257ee4458eab7c15
Author: Rafael Aquini <aquini@redhat.com>
Date: Mon Apr 20 15:08:52 2020 -0400
[redhat] redhat: configs: enable CONFIG_PAGE_OWNER
Message-id: <a4b1babd75098b8e69cbb00426c27489d6c21915.1587394443.git.aquini@redhat.com>
Patchwork-id: 303888
Patchwork-instance: patchwork
O-Subject: [RHEL8 PATCH 1/2] redhat: configs: enable CONFIG_PAGE_OWNER
Bugzilla: 1825414
RH-Acked-by: Don Dutile <ddutile@redhat.com>
RH-Acked-by: Aristeu Rozanski <aris@redhat.com>
RH-Acked-by: Waiman Long <longman@redhat.com>
Upstream status: RHEL only
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1825414
Get CONFIG_PAGE_OWNER enabled on the RHEL kernel builds so we
provide this debug feature to help on extending our ability to
bug-chase kernel memory usage by 3rd party drivers.
This will also enable CONFIG_PAGE_EXTENSION, which will cause
struct mem_section to be extended, as well.
[jbenc: stripped irrelevant kABI preserving discussion]
Signed-off-by: Rafael Aquini <aquini@redhat.com>
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
The sh-utils build dependency was removed from ARK. However, those tools are
still needed for the kernel build. Although coreutils are present in the
build environment by default, it still seems to be a good practice to
require them explicitly.
commit 8aa18d3c37c5d057ef2398210dd70915ed26915e
Author: Brian Masney <bmasney@redhat.com>
Date: Mon Apr 6 15:41:26 2020 -0400
[redhat] kernel.spec: replace sh-utils dependency with coreutils
Message-id: <20200406154127.357506-2-bmasney@redhat.com>
Patchwork-id: 299250
Patchwork-instance: patchwork
O-Subject: [RHEL8.3 BZ 1821336 PATCH v4 1/2] kernel.spec: replace sh-utils dependency with coreutils
Bugzilla: 1821336
RH-Acked-by: Rafael Aquini <aquini@redhat.com>
RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1821336
Upstream Status: RHEL only
Build Info: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=27632566
Tested: via local RPM build and via brew build.
As of RHEL 8.0, the sh-utils package is now provided by the coreutils
package. Newer versions of Fedora don't include the sh-utils provides
so let's go ahead and update the BuildRequires to depend on coreutils.
Signed-off-by: Brian Masney <bmasney@redhat.com>
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Backport of RHEL8 commit.
commit 188976e5b7d5d5d23e5c640a8da412e0b1216864
Author: Petr Oros <poros@redhat.com>
Date: Mon Mar 23 14:42:59 2020 -0400
[redhat] add netdevsim driver selftests to kernel-selftests-internal
Message-id: <9e902c0a0d2e96360088b691075baee0ac525fee.1584973596.git.poros@redhat.com>
Patchwork-id: 297250
Patchwork-instance: patchwork
O-Subject: [RHEL8.3 net PATCH 21/21] redhat: add netdevsim driver selftests to kernel-selftests-internal
Bugzilla: 1805882
RH-Acked-by: Hangbin Liu <haliu@redhat.com>
RH-Acked-by: Ivan Vecera <ivecera@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1805882
Upstream status: RHEL only
These selftests will be used to verify various functionality implemented
in netdevsim driver. This is useful for functional as well as regression
testing. Netdevsim directory curently contain devlink and devlink_trap
selftests
Signed-off-by: Petr Oros <poros@redhat.com>
Signed-off-by: Timothy Redaelli <tredaelli@redhat.com>
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Backport of RHEL8 commit.
commit 8ecd7aeaa1a53b0e22da4e97aef7d89df292a112
Author: Steve Dickson <SteveD@redhat.com>
Date: Sun Feb 9 20:37:17 2020 -0500
[redhat] Makefile: Clean out the --without flags from the baseonly rule
Message-id: <20200209203717.299715-2-steved@redhat.com>
Patchwork-id: 294575
Patchwork-instance: patchwork
O-Subject: [PATCH 2/2] [PATCH 8.2] [redhat] Makefile: Clean out the --without flags from the baseonly rule.
Bugzilla: 1797242
RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
With the previous patch, the baseonly define undefines unnecessary
rpms that don't need to be build. So clean out the rh-kernel make
rule of the not needed --without flags.
Bugzilla: 1797242
Upstream: RHEL-only
Signed-off-by: Steve Dickson <steved@redhat.com>
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Backport of RHEL8 commit.
commit 010b2e366255fc0f30c68f404679f85937d2549c
Author: Steve Dickson <SteveD@redhat.com>
Date: Sun Feb 9 20:37:16 2020 -0500
[redhat] kernel.spec.template: Stop building unnecessary rpms for baseonly builds
Message-id: <20200209203717.299715-1-steved@redhat.com>
Patchwork-id: 294574
Patchwork-instance: patchwork
O-Subject: [PATCH 1/2] [PATCH 8.2 V2] [redhat] kernel.spec.template: Stop building unnecessary rpms for baseonly builds
Bugzilla: 1797242
RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
With baseonly builds, undefined a number unnecessary build
defines so the minimal number of rpms are built
Bugzilla: 1797242
Upstream: RHEL-only
Signed-off-by: Steve Dickson <steved@redhat.com>
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Backport of RHEL8 commit.
commit 128ccd9b6c19f5cce20fac1479d9677623fbfc26
Author: Jan Stancek <jstancek@redhat.com>
Date: Tue Dec 10 14:53:25 2019 -0500
[redhat] disable more kabi switches for gcov build
Message-id: <2e9b8ebc97c9eb430116a118dc8003f44870abf9.1575989369.git.jstancek@redhat.com>
Patchwork-id: 291825
O-Subject: [RHEL8.2 PATCH] redhat: disable more kabi switches for gcov build
Bugzilla: 1781513
RH-Acked-by: Bruno Eduardo de Oliveira Meneguele <bmeneg@redhat.com>
RH-Acked-by: Čestmír Kalina <ckalina@redhat.com>
RH-Acked-by: Herton R. Krzesinski <herton@redhat.com>
Bugzilla: 1781513
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=25255969
Upstream: RHEL only
Tested: make rh-srpm-gcov + compile only in brew
gcov build disables with_kabichk, which makes Source300 undefined.
But there are still couple kabi switches which use SOURCE300,
which can cause brew build to fail:
+ tar xjvf '%{SOURCE300}' -C /builddir/build/BUILDROOT/kernel-4.18.0-161.el8.gcov.noarch/lib/modules/
tar (child): %{SOURCE300}: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.lcnD1l (%install)
Bad exit status from /var/tmp/rpm-tmp.lcnD1l (%install)
Child return code was: 1
Signed-off-by: Jan Stancek <jstancek@redhat.com>
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Backport of RHEL8 commit.
- small conflict Flavour/Variant variable names.
commit 1b5714ef1f57ebc640fff6b6498a92f8e60a3699
Author: Philipp Rudo <prudo@redhat.com>
Date: Tue Aug 27 10:51:21 2019 -0400
[rpmspec] redhat: Fix error messages during build of zfcpdump kernel
Message-id: <20190827105121.28041-1-prudo@redhat.com>
Patchwork-id: 269801
O-Subject: [RHEL8.2 PATCH] [rpmspec] redhat: Fix error messages during build of zfcpdump kernel
Bugzilla: 1745652
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Steve Best <sbest@redhat.com>
Bugzilla: 1745652
Upstream Status: RHEL-only
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=23194083
Tested: Ran brew build and checked build.log for s390x
The zfcpdump kernel variant was renamed from 'kdump' to 'zfcpdump' to
prevent misconception in the transition from RHEL7 to RHEL8. When
forwardporting the kabi-dw tool it was missed to adjust to the rename
causing error messages during build like
+ '[' zfcpdump '!=' kdump ']'
+ mkdir -p
/builddir/build/BUILDROOT/kernel-4.18.0-137.el8.rhel.8.1.0.1743504.bz.s390x/kabi-dwarf
+ tar xjvf /builddir/build/SOURCES/kernel-kabi-dw-4.18.0-137.tar.bz2 -C
/builddir/build/BUILDROOT/kernel-4.18.0-137.el8.rhel.8.1.0.1743504.bz.s390x/kabi-dwarf
base/
run_kabi-dw.sh
**** Baseline dataset for kABI DWARF-BASED comparison report not found ****
Fix them by adjusting to the rename. Other than the error messages no
negative impact is expected. The zfcpdump kernel is not kABI protected.
Fixes: cbcbf154b64a ("[redhat] kabi: integrate kabi-dw")
Signed-off-by: Philipp Rudo <prudo@redhat.com>
Signed-off-by: Phillip Lougher <plougher@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Instead of specifying the files one by one, remove the whole
/usr/lib/perf/include directory the same way it is done in RHEL 8.
commit 9da4d617c730e81cf01e5685de5c5a23d6cd3003
Author: Michael Petlan <mpetlan@redhat.com>
Date: Thu May 23 10:14:56 2019 -0400
[rpmspec] perf: remove bpf examples
Message-id: <f2e1d39854d7d06cf9937de75a127d0e9b4ded99.1558604935.git.mpetlan@redhat.com>
Patchwork-id: 259900
O-Subject: [RHEL8.1 BZ1709242 189/190] [rpmspec] perf: remove bpf examples
Bugzilla: 1709242
RH-Acked-by: Jiri Olsa <jolsa@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
Bugzilla: 1709242
https://bugzilla.redhat.com/show_bug.cgi?id=1709242
Upstream Status: RHEL only
description
===========
The following files should not be packaged, since they are packaged
in fedora neither:
/usr/lib/perf/examples/bpf/5sec.c
/usr/lib/perf/examples/bpf/augmented_syscalls.c
/usr/lib/perf/examples/bpf/empty.c
/usr/lib/perf/examples/bpf/hello.c
/usr/lib/perf/examples/bpf/sys_enter_openat.c
/usr/lib/perf/include/bpf/bpf.h
/usr/lib/perf/include/bpf/stdio.h
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
This dependency doesn't make much sense. It says nothing about the running
kernel, it's possible to have mutliple kernel rpms of different versions
installed.
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Bring back the code to install kernel headers that was removed by ARK commit
3a65b42715 ("Sync up the ARK build scripts") without any explanation. The
headers are needed. Add SMP flags to speed up the build.
Turn on building of samples, reverting ARK commit 9d270db9fd ("Skip
ksamples for bpf, they are broken"). The reason they were broken was the
incorrect drop of the kernel headers installation.
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
When the tools_make macro was ported to ARK, one change made in the
original RHEL 8 commit were forgotten: the cpupower tools should be
built without debug (the default is DEBUG=true, which builds without
optimizations).
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
There is flowtable support for (the combined IPv4/IPv6) inet family
already, so having the IP-family specific ones disabled seems
artificial.
Signed-off-by: Phil Sutter <psutter@redhat.com>
These three config symbols were missing although enabled in RHEL8. They
are enabled in Fedora, so move the respective files (and drop the
explicit IP_VS_MH disabler from ark).
Signed-off-by: Phil Sutter <psutter@redhat.com>
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_CXL_MEM:
The CXL.mem protocol allows a device to act as a provider of
"System RAM" and/or "Persistent Memory" that is fully coherent
as if the memory was attached to the typical CPU memory
controller.
Say 'y/m' to enable a driver (named "cxl_mem.ko" when built as
a module) that will attach to CXL.mem devices for
configuration, provisioning, and health monitoring. This
driver is required for dynamic provisioning of CXL.mem
attached memory which is a prerequisite for persistent memory
support. Typically volatile memory is mapped by platform
firmware and included in the platform memory map, but in some
cases the OS is responsible for mapping that memory. See
Chapter 2.3 Type 3 CXL Device in the CXL 2.0 specification.
If unsure say 'm'.
Symbol: CXL_MEM [=n]
Type : tristate
Defined at drivers/cxl/Kconfig:16
Prompt: CXL.mem: Memory Devices
Depends on: CXL_BUS [=y]
Location:
-> Device Drivers
-> PCI support (PCI [=y])
-> CXL (Compute Express Link) Devices Support (CXL_BUS [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v2:
- CONFIG_CXL_MEM set to module
v3:
- CONFIG_CXL_MEM_RAW_COMMANDS disabled
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
Now that we have upstream fixes for the issues with these
drivers when DEBUG_SHIRQ is enabled we can enable pcie for
the rk3399 devices that support this PCIE IP block.
Fixes: RHBZ #1704945
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
MR 1167 added a buildreq for 'opencsd-devel >= 1.0.0-2' on aarch64.
Unfortunately, this version does not exist. The latest build of
opencsd for eln is opencsd-1.0.0-1.eln110. As of 5.12 kernels, perf
does require opencsd 1.0.0, so let's limit it there.
Cc: Michael Petlan mpetlan@redhat.com
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
Most of the configs are identical for fedora and ark so move them to
common/generic/s390x.
While at it move the remaining configs in fedora/generic to
fedora/generic/s390x.
Signed-off-by: Philipp Rudo <prudo@redhat.com>
Using cc-option adds a dependency on the compiler in the configuration
environment. This usually breaks the config creation when the target
architecture is not the host architecture. As a remedy f88717cf44
("Temporarily switch TUNE_DEFAULT to y") unset failing configs to their
defaults. In the meantime upstream introduced the scripts/dummy-tools,
which are meant to disable cc-option checks by always returning 'y'.
Make use of the dummy-tools and revert the workaround.
Signed-off-by: Philipp Rudo <prudo@redhat.com>
These configs add option -ftrivial-auto-var-init={pattern,zero} to the
CFLAGS. This option are specific to CLANG and thus are not present on
typical developer systems using GCC. By using the dummy-tools the
cc-option check that tests if these options are present in the current
environment is disabled (i.e. always returns 'y') making the priviously
hidden configs visible. Thus explicitely disable these configs to satisfy
process_configs.sh.
Furthermore these configs are part of a 'choice' from which
CONFIG_INIT_STACK_NONE is selected.
Signed-off-by: Philipp Rudo <prudo@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
This config adds option --pack-dyn-relocs=relr to the LDFLAGS. This
option is specific to LLD and thus is not present on typical developer
systems using LD. By using the dummy-tools the cc-option check that
tests if the option is present in the current environment is disabled
(i.e. always returns 'y') making the priviously hidden config visible.
Thus explicitely disable the config to satisfy process_configs.sh.
Signed-off-by: Philipp Rudo <prudo@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
The STMICRO nic is enabled in RHEL8.4 (aarch64-only) and should be enabled
in ark as well.
Looking at PCS_XPCS, I noticed dead configs for MDIO_XPCS which is the
previous name for PCS_XPCS. So I removed those as well.
Signed-off-by: Mark Salter <msalter@redhat.com>
ARCH_TEGRA and SERIAL_8250_TEGRA are enabled in RHEL8.4 and should
be enabled in ark as well.
Fedora currently enables these so I moved those into common/generic/arm.
Enabling ARCH_TEGRA uncovered a number of other Tegra options which needed
to be added for ark (none of which enabled at this point).
Signed-off-by: Mark Salter <msalter@redhat.com>
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_MST_IRQ:
Support MStar Interrupt Controller.
Symbol: MST_IRQ [=n]
Type : bool
Defined at drivers/irqchip/Kconfig:584
Prompt: MStar Interrupt Controller
Location:
-> Device Drivers
-> IRQ chip support
Selects: IRQ_DOMAIN [=y] && IRQ_DOMAIN_HIERARCHY [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
In RHEL-8, powerpc has support for IMA_KEXEC, and today, only ppc and
aarch64 supports IMA_KEXEC, which are backed by the HAVE_IMA_KEXEC option.
With that, lets enable it in ARK and also, since the HAVE_* option it's safe
to enable the CONFIG_IMA_KEXEC option as a common/generic option too.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
CONFIG_INTEGRITY_SIGNATURE has been enabled for all supported arches in
RHEL-8 and also in Fedora, but I missed it in ARK and, consequently, s390x
missed the CONFIG_IMA_APPRAISE_MODSIG option, which should be set.
However, enabling as generic option also force we to generically disable
CONFIG_IMA_APPRAISE_BUILD_POLICY, which is fine for now.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
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_PCS_XPCS:
This module provides helper functions for Synopsys DesignWare XPCS
controllers.
Symbol: PCS_XPCS [=n]
Type : tristate
Defined at drivers/net/pcs/Kconfig:8
Prompt: Synopsys DesignWare XPCS controller
Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> PCS device drivers
Selects: MDIO_BUS [=y]
Selected by [n]:
- STMMAC_ETH [=n] && NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_STMICRO [=n] && HAS_IOMEM [=y] && HAS_DMA [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_VP_VDPA:
This kernel module bridges virtio PCI device to vDPA bus.
Symbol: VP_VDPA [=n]
Type : tristate
Defined at drivers/vdpa/Kconfig:63
Prompt: Virtio PCI bridge vDPA driver
Depends on: VDPA [=m] && PCI_MSI [=y]
Location:
-> Device Drivers
-> vDPA drivers (VDPA [=m])
Selects: VIRTIO_PCI_LIB [=y]
---
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v2:
- CONFIG_VP_VDPA enabled as a module.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
Bugzilla: https://bugzilla.redhat.com/1877192
Decoding CoreSight needs opencsd-devel package at build-time and
opencsd package as runtime dependency. This feature is aarch64-only.
Signed-off-by: Michael Petlan <mpetlan@redhat.com>
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_CMA_SYSFS:
This option exposes some sysfs attributes to get information
from CMA.
Symbol: CMA_SYSFS [=n]
Type : bool
Defined at mm/Kconfig:532
Prompt: CMA information through sysfs interface
Depends on: CMA [=y] && SYSFS [=y]
Location:
-> Memory Management options
-> Contiguous Memory Allocator (CMA [=y])
---
Cc: Rafael Aquini <aquini@redhat.com>
Cc: Aristeu Rozanski <arozansk@redhat.com>
Cc: Don Dutile <ddutile@redhat.com>
Cc: Nico Pache <npache@redhat.com>
Cc: Waiman Long <longman@redhat.com>
Cc: mm-maint@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v2:
- CONFIG_CMA_SYSFS enabled.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
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_CIFS_SWN_UPCALL:
The Service Witness Protocol (SWN) is used to get notifications
from a highly available server of resource state changes. This
feature enables an upcall mechanism for CIFS which contacts a
userspace daemon to establish the DCE/RPC connection to retrieve
the cluster available interfaces and resource change notifications.
If unsure, say Y.
Symbol: CIFS_SWN_UPCALL [=n]
Type : bool
Defined at fs/cifs/Kconfig:193
Prompt: SWN feature support
Depends on: NETWORK_FILESYSTEMS [=y] && CIFS [=m]
Location:
-> File systems
-> Network File Systems (NETWORK_FILESYSTEMS [=y])
-> SMB3 and CIFS support (advanced network filesystem) (CIFS [=m])
---
Cc: kernel-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Bugzilla: 1964537
Upstream Status: RHEL only
io_uring is still under very active development. Disable support
for now. We will reassess this decision each minor release.
Note: this is a temporary patch which can be reverted after RHEL 9
branches from ark.
Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
module.
There is no advantage to this being a built-in; and the vendor prefers
it being a loadable module.
signed-off-by: Frank Ramsay <framsay@redhat.com>
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_AD5766:
Say yes here to build support for Analog Devices AD5766, AD5767
Digital to Analog Converter.
To compile this driver as a module, choose M here: the
module will be called ad5766.
Symbol: AD5766 [=n]
Type : tristate
Defined at drivers/iio/dac/Kconfig:192
Prompt: Analog Devices AD5766/AD5767 DAC driver
Depends on: IIO [=m] && SPI_MASTER [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Digital to analog converters
---
CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE:
This sensor present three angles, hinge angel, screen angles
and keyboard angle respect to horizon (ground).
Say yes here to build support for the HID custom
intel hinge sensor.
To compile this driver as a module, choose M here: the
module will be called hid-sensor-custom-hinge.
Symbol: HID_SENSOR_CUSTOM_INTEL_HINGE [=n]
Type : tristate
Defined at drivers/iio/position/Kconfig:19
Prompt: HID Hinge
Depends on: IIO [=m] && HID_SENSOR_HUB [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Linear and angular position sensors
Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] && HID_SENSOR_IIO_COMMON [=m] && HID_SENSOR_IIO_TRIGGER [=m]
---
CONFIG_YAMAHA_YAS530:
Say Y here to add support for the Yamaha YAS530 series of
3-Axis Magnetometers. Right now YAS530, YAS532 and YAS533 are
fully supported.
This driver can also be compiled as a module.
To compile this driver as a module, choose M here: the module
will be called yamaha-yas.
Symbol: YAMAHA_YAS530 [=n]
Type : tristate
Defined at drivers/iio/magnetometer/Kconfig:208
Prompt: Yamaha YAS530 family of 3-Axis Magnetometers (I2C)
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Magnetometer sensors
Selects: REGMAP_I2C [=m] && IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Nitro Enclaves driver is enabled in RHEL8 and should remain enabled. Move
the config setting from fedora/ to common/.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Explicitly use shell formatting for code blocks. Move instructions for pull
mirroring outside of a code block.
Provide a link that takes users to their own fork of the repository. Add a
link for users to register their SSH key in GitLab.
Remove a comment about creating a symlink at /usr/libexec/python-platform,
which is not necessary since commit a069f47f6141. Remove unneeded commands
for checking out the 'os-build' branch or pulling updates immediately after
cloning the repository.
Differentiate between building source and binary RPM packages, which happen
in separate steps. Since the examples use Koji or Mock, the kernel's build
dependencies do not need to be installed locally.
Signed-off-by: David Ward <david.ward@ll.mit.edu>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1961178
Upstream Status: RHEL only
Tested: on x86 with libvirt, on ARM with qemu as pvpanic-pci is not
yet integrated in libvirt
With the introduction of pvpanic-pci new configs were introduced
for the MMIO and PCI flavour. On x86, currently none is set so
the ISA device is not available (this is a regression). The MMIO
flavour must be used on x86_64.
On ARM, the PCI one must be set.
Signed-off-by: Eric Auger <eric.auger@redhat.com>
---
v1 -> v2:
- s/y/m for PCI and MMIO configs
There's recent change [1] that adds new config option and sets
unprivileged_bpf_disabled to 2 if the option is enabled
(CONFIG_BPF_UNPRIV_DEFAULT_OFF).
The current RHEL specific behaviour is to set unprivileged_bpf_disabled
to 1 by default and add boot command line argument to enable
unpriv bpf.
The config option is enabled in previous patch, adding the taint
for proc/sysctl unprivileged_bpf_disabled setup.
# sysctl kernel.unprivileged_bpf_disabled
kernel.unprivileged_bpf_disabled = 2
# cat /proc/sys/kernel/tainted
0
# sysctl kernel.unprivileged_bpf_disabled=0
[ 45.751085] Unprivileged BPF has been enabled, tainting the kernel
kernel.unprivileged_bpf_disabled = 0
# sysctl kernel.unprivileged_bpf_disabled=1
kernel.unprivileged_bpf_disabled = 1
# sysctl kernel.unprivileged_bpf_disabled=0
sysctl: setting key "kernel.unprivileged_bpf_disabled": Operation not permitted
# sysctl kernel.unprivileged_bpf_disabled=2
sysctl: setting key "kernel.unprivileged_bpf_disabled": Operation not permitted
# cat /proc/sys/kernel/tainted
2147483648
[1] 08389d8882 ("bpf: Add kconfig knob for disabling unpriv bpf by default")
[2] 607f0e89af7e ("bpf: set unprivileged_bpf_disabled to 1 by default, add a boot parameter")
Fixes: 607f0e89af7e ("bpf: set unprivileged_bpf_disabled to 1 by default, add a boot parameter")
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
With the recent kernel versions, it is possible now to use virtio-fs
on s390x machines, too. Remove the s390x-specific CONFIG_VIRTIO_FS
file, so that this feature now also gets enabled via the generic
CONFIG_VIRTIO_FS=m setting on s390x, too.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1871130
Signed-off-by: Thomas Huth <thuth@redhat.com>
Shipment of the devices required for these options were ceased with z13.
With the ALS set to z14 for ark there is no need to keep the options
enabled.
v2: disable the configs for fedora as well
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1903201
Signed-off-by: Philipp Rudo <prudo@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1948340
Upstream Status: RHEL only
Tested: Instructions in the first comment in bz1948340.
Diag modules are required when investigating sockets with the `ss` tool,
and are loaded on-demand. This is also what happens when using the
`sosreport` tool. Recent discussions pointed out it was not always
possible to load extra modules on a production system, for various
reasons, and the `sosreport` tool was updated to avoid modules to be
loaded by default. Links to the discussions are available in the bz.
The issue is with this policy the `ss` command is now skipped, except if
the administrator explicitly allows it to do so or if diag modules are
already loaded. This results in a loss of valuable information when
generating an `sosreport`, impacting the following investigation.
This patch enables a set of selected DIAG modules to be built-in, so
that `ss` and `sosreport` can be used without loading additional
modules (only diag modules not depending on another loadable module were
considered):
- CONFIG_INET_DIAG
- CONFIG_INET_RAW_DIAG
- CONFIG_INET_TCP_DIAG
- CONFIG_INET_UDP_DIAG
- CONFIG_INET_MPTCP_DIAG
- CONFIG_NETLINK_DIAG
- CONFIG_PACKET_DIAG
- CONFIG_UNIX_DIAG
The generated configuration do not enable any additional non-listed
options with this change. The kernel image increase in size is very
minimal.
Signed-off-by: Antoine Tenart <atenart@redhat.com>
BZ: 1948690
Upstream Status: RHEL-only
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
rhel-8.git commit f027c2e4045d02d103c7a545181b6df0b6162ee7
Author: David Milburn <dmilburn@redhat.com>
Date: Wed Jan 29 15:29:37 2020 -0500
[nvme] nvme: nvme_mpath_init remove multipath check
Message-id: <1580311777-9193-1-git-send-email-dmilburn@redhat.com>
Patchwork-id: 294254
Patchwork-instance: patchwork
O-Subject: [RHEL8.2 PATCH] nvme: nvme_mpath_init remove multipath check
Bugzilla: 1790958
RH-Acked-by: Gopal Tiwari <gtiwari@redhat.com>
RH-Acked-by: Ewan Milne <emilne@redhat.com>
Marco Patalano found missing NVMe optimized/inaccessible paths when
executing "nvme list-subsys" command with native multipathing disabled.
He was able to git bisect this back to 6d0f426e ("nvme: fix multipath
crash when ANA is deactivated"). The problem is the check for multipath,
removing this is similar to RHEL commit 158eef2e ("nvme: allow ANA support
to be independent of native multipathing"), I did leave the existing
comment in place for future back ports and as a reminder to watch for
these changes in the future.
Bugzilla: 1790958
Build info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=26061480
Upstream: RHEL only
Test: QE verified "nvme list-subsys" command and did sanity check with native
multipathing disabled.
Fixes: 6d0f426e ("nvme: fix multipath crash when ANA is deactivated")
Signed-off-by: David Milburn <dmilburn@redhat.com>
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1952426
Due to independent usage of libtraceevent by various users (perf, trace-cmd),
it now exists as a separate package, which provides the library+plugins. Now
perf has to link against it and not install its own libtraceevent, since that
would conflict.
v1 --> v2
=========
Rebased to latest os-build branch.
Signed-off-by: Michael Petlan <mpetlan@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1945477
Upstream: RHEL only
We are planning to deprecate Teaming in RHEL 9 and remove it in RHEL 10.
Teaming and Bonding offer similar functionalities and are causing confusion
for our customers. In the past, Bonding was not keeping up-to-date and
hence Teaming was an option being pursued. Bonding now is keeping current
and also widely adopted by our customers. Hence, it makes sense to keep
Bonding as our preferred option going forward and avoid causing un-necessary
confusion.
Signed-off-by: Hangbin Liu <haliu@redhat.com>
Our current plan is to build crypto modules that we may want to certify
with FIPS-140-3 statically in the kernel.
So add ECDH and ECDSA as well. We currently already claim ECDSA in RHEL-8
kernels. Adding ECDH for completeness.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1947240
Signed-off-by: Simo Sorce <simo@redhat.com>
DIST defaults to '.fc33' if it is not set (which no longer corresponds to
Fedora Rahwide). Obtain the default value from the RPM macros instead.
Signed-off-by: David Ward <david.ward@ll.mit.edu>
This option had no effect. Test for it so that %{debugbuildsenabled}
can be overridden at build time without modifying the SPEC file.
Signed-off-by: David Ward <david.ward@ll.mit.edu>
Fix the descriptions of the %{released_kernel} and %{debugbuildsenabled}
macros to match their current usage. Also improve a comment that appears
above the build option tests.
Move the tests for --without-zfcpdump and --without-vdso-install so they
are located next to related build options. Also move the definitions of
%{debugbuildsenabled} and %{kversion} to be next to related definitions.
This commit does not make any functional changes to the SPEC file.
Signed-off-by: David Ward <david.ward@ll.mit.edu>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1943423
Upstream: RHEL only
Enable CONFIG_EXFAT_FS as requested in the bugzilla. Config
CONFIG_EXFAT_DEFAULT_IOCHARSET is needed by exFAT.
Remove the fedora specific configs and enable them in common folder.
Do not enable the option on s390x-zfcpdump kernel to avoid
configuration 'mismatch warning'.
Signed-off-by: Pavel Reichl <preichl@redhat.com>
Currently a number of FIPS-allowed algorithms are built as modules or are
not enabled in Fedora and ARK. This can result in a panic while booting
in the FIPS mode. Fix this by embedding the FIPS-allowed algorithms, modes
and templates into a kernel, the same way as CTC, CBC and other algorithms
already do.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1947240
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
CONFIG_HYPERV_TESTING=y is needed for some testing tools in the
hyperv-daemons package. Enable it for debug kernels
Signed-off-by: Mohammed Gamal <mgamal@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1945002
Upstream: RHEL only
CMA is Tech Preview in RHEL 9 for x86_64; to detect the use of CMA easily,
taint the kernel via mark_tech_preview(). Further print an info when
cma_alloc() is getting called for the first time.
Keep s390x (for vmcp) and ppc64 (for KVM) unmodified, as they have been
automatically creating CMA regions already in RHEL 8.
Signed-off-by: David Hildenbrand <david@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1945002
Upstream: RHEL only
Enable CONFIG_CMA on x86_64 in ARK as we already have in fedora; move the
relevant configs from redhat/configs/fedora to redhat/configs/common.
As one example CMA will be required to eventually support RDMA<->GPU
p2pdma via dma-buf. As another example, CMA will be useful useful for more
reliable runtime allocation of gigantic pages.
Let's keep CONFIG_DMABUF_HEAPS_CMA disabled for now -- we'll enable it
separately, via a different BZ in the future.
Note that:
* CONFIG_DMA_CMA=Y has to be set due to FB_HYPERV, which force-enables it
via "select DMA_CMA if HAVE_DMA_CONTIGUOUS && CMA"
* CONFIG_CMA_AREAS has to be configured due to CONFIG_CMA; use the fedora
value (7). We can bump it up once we actually need more areas.
* CONFIG_CMA_DEBUG and CONFIG_CMA_DEBUGFS have to be configured due to
CONFIG_CMA; use the fedora values, which disables both.
* CONFIG_DMA_PERNUMA_CMA has to be configured due to CONFIG_DMA_CMA; use
the fedora value, which disables it. We can enable once we actually
need it.
* CONFIG_CMA_ALIGNMENT, CONFIG_CMA_SIZE_MBYTES, CONFIG_CMA_SIZE_SEL_MAX,
CONFIG_CMA_SIZE_SEL_MBYTES, CONFIG_CMA_SIZE_SEL_MIN,
CONFIG_CMA_SIZE_SEL_PERCENTAGE have to be configured due to
CONFIG_DMA_CMA; use the fedora values, which correspond to the defaults
* 1MiB alignment of buffers
* CMA being disabled, requiring explicit "cma=size[MG]" on the cmdline
Signed-off-by: David Hildenbrand <david@redhat.com>
During upstream git snapshot builds, Fedora uses the debug configs to
build the main kernels, and drops the *-debug package variants. However
if someone installs a kernel-debug package for example it'll not update
until the next non-snapshot build. So add support to keep the debug
packages around even for snapshot builds, however in this case, they
will be just meta-packages requiring the main kernel-* packages built
with debug configs.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
The GPIOs provided by the AMD pinctrl module may be used by various
ACPI methods (e.g. _PS0, _PS3) and resources (GpioInt). These ACPI
uses may happen before the module has a chance to load when amd_pinctrl
is build as a module.
Change the CONFIG_PINCTRL_AMD option to y, so that the amd_pinctrl
code gets built into the kernel to fix this. This specifically fixes
I2C-HID touchpads on AMD based laptops sometimes not working at boot.
BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1634832
BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1957203
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
This was a change done in the RHEL 8 kernel package, with the purpose
of providing means to other tools to determine if the kernel-headers
changed between package updates. For example, linux containers that
only install kernel-headers would not be flagged for the need of CVE
updates if kernel-headers didn't change, in case of kernel CVEs that
didn't affect the headers.
But this content hash ended up never being used and AFAIK there
were no users. The need to avoid kernel CVEs flagging containers needing
updates only because of kernel-headers installed but not affected,
was handled through changes made in Red Hat's errata tool, and the
content hash here has no use anymore.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
InitBuildVars is only called in case BuildKernel is not called (because
it already calls InitBuildVars), and that is done eg. when all kernel
builds are disabled but still building of tools is wanted which needs
the definitions/variables it declares. However, the check is missing the
case when armv7hl with_pae is enabled which already called
BuildKernel->InitBuildVars, this just adds the missing check.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Fedora generic kernel config enables support for zoned block devices
with CONFIG_BLK_DEV_ZONED=y. The dm-zoned device mapper target is also
already enabled with CONFIG_DM_ZONED=m. When kernel 5.12 is introduced,
this default configuration will also enable btrfs native zoned block
device support.
Complete Fedora zoned block device ecosystem by enabling als zonefs as a
module. zonefs was introduced in kernel 5.6 and is already supported by
util-linux libblkid. A request for the zonefs-tools package will be sent
too for completes.
Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
In the current upstream kernel state all RHEL supported arches (aarch64,
x86_64, s390x and powerpc) supports loading platform keys (coming from the
boot process) to a trusted keyring in the system.
This patch enables CONFIG_INTEGRITY_PLATFORM_KEYRING to all ARK arches and
each CONFIG_LOAD_<arch>_KEYS to their respective architecture folder.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
This CONFIG option deprecates CONFIG_IMA_TRUSTED_KEYRING, however the old
one is still being required by some other options in upstream, that's why we
don't remove it yet.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
INTEGRITY_ASYMMETRIC_KEYS was already enabled in Fedora/generic/. This patch
adds it to common/generic because all supported ARK arches supports it.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
This change passes %{make_opts} to make when using the perf_make,
tools_make, and bpftool_make macros. The main effect of this change
is that these macros will correctly set CC=clang when the --with
toolchain_clang option is passed to rpmbuild.
Additionally, this change also affects the verbosity of the make output
when these macros are used:
perf_make:
* Before was always passing the -s (silent) flag.
* Now will pass -s flag by default and V=1 (verbose) arg when
--with verbose option is passed to rpmbuild.
tools_make and bfptool_make:
* Before was always passing V=1 arg.
* Now will pass -s flag by default and V=1 arg when
--with verbose option is passed to rpmbuild.
Signed-off-by: Tom Stellard <tstellar@redhat.com>
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_MICROSOFT_MANA:
This driver supports Microsoft Azure Network Adapter (MANA).
So far, the driver is only supported on X86_64.
To compile this driver as a module, choose M here.
The module will be called mana.
Symbol: MICROSOFT_MANA [=n]
Type : tristate
Defined at drivers/net/ethernet/microsoft/Kconfig:18
Prompt: Microsoft Azure Network Adapter (MANA) support
Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MICROSOFT [=y] && PCI_MSI [=y] && X86_64 [=y] && PCI_HYPERV [=m]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Ethernet driver support (ETHERNET [=y])
-> Microsoft Network Devices (NET_VENDOR_MICROSOFT [=y])
---
CONFIG_NET_VENDOR_MICROSOFT:
If you have a network (Ethernet) device belonging to this class, say Y.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip the
question about Microsoft network devices. If you say Y, you will be
asked for your specific device in the following question.
Symbol: NET_VENDOR_MICROSOFT [=y]
Type : bool
Defined at drivers/net/ethernet/microsoft/Kconfig:5
Prompt: Microsoft Network Devices
Depends on: NETDEVICES [=y] && ETHERNET [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Ethernet driver support (ETHERNET [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v2:
- CONFIG_MICROSOFT_MANA enabled as module
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
This setting seems to have slipped through review process: Before this
symbol was introduced, the relevant feature was always enabled. Since it
is there now, we should use the opportunity to disable it and avoid any
further security holes it may contain in addition to the already fixed
ones.
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_NET_VENDOR_BROADCOM:
If you have a network (Ethernet) chipset belonging to this class,
say Y.
Note that the answer to this question does not directly affect
the kernel: saying N will just cause the configurator to skip all
the questions regarding Broadcom chipsets. If you say Y, you will
be asked for your specific chipset/driver in the following questions.
Symbol: NET_VENDOR_BROADCOM [=y]
Type : bool
Defined at drivers/net/ethernet/broadcom/Kconfig:6
Prompt: Broadcom devices
Depends on: NETDEVICES [=y] && ETHERNET [=y] && (SSB_POSSIBLE [=y] && HAS_DMA [=y] || PCI [=y] || BCM63XX || SIBYTE_SB1xxx_SOC)
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Ethernet driver support (ETHERNET [=y])
Selected by [n]:
- SCSI_BNX2_ISCSI [=n] && SCSI_LOWLEVEL [=y] && SCSI [=y] && NET [=y] && PCI [=y] && (IPV6 [=y] || IPV6 [=y]=n) && MMU [=y]
- SCSI_BNX2X_FCOE [=n] && SCSI_LOWLEVEL [=y] && SCSI [=y] && PCI [=y] && (IPV6 [=y] || IPV6 [=y]=n) && LIBFC [=m] && LIBFCOE [=m] && MMU [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_IFCVF:
This kernel module can drive Intel IFC VF NIC to offload
virtio dataplane traffic to hardware.
To compile this driver as a module, choose M here: the module will
be called ifcvf.
Symbol: IFCVF [=n]
Type : tristate
Defined at drivers/vdpa/Kconfig:28
Prompt: Intel IFC VF vDPA driver
Depends on: VDPA [=m] && PCI_MSI [=y]
Location:
-> Device Drivers
-> vDPA drivers (VDPA [=m])
---
CONFIG_MLX5_VDPA_NET:
VDPA network driver for ConnectX6 and newer. Provides offloading
of virtio net datapath such that descriptors put on the ring will
be executed by the hardware. It also supports a variety of stateless
offloads depending on the actual device used and firmware version.
Symbol: MLX5_VDPA_NET [=n]
Type : tristate
Defined at drivers/vdpa/Kconfig:45
Prompt: vDPA driver for ConnectX devices
Depends on: VDPA [=m] && MLX5_CORE [=m]
Location:
-> Device Drivers
-> vDPA drivers (VDPA [=m])
Selects: MLX5_VDPA [=n]
---
CONFIG_VDPA_SIM:
Enable this module to support vDPA device simulators. These devices
are used for testing, prototyping and development of vDPA.
Symbol: VDPA_SIM [=n]
Type : tristate
Defined at drivers/vdpa/Kconfig:12
Prompt: vDPA device simulator core
Depends on: VDPA [=m] && RUNTIME_TESTING_MENU [=y] && HAS_DMA [=y]
Location:
-> Device Drivers
-> vDPA drivers (VDPA [=m])
Selects: DMA_OPS [=y] && VHOST_RING [=n]
---
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v2:
- CONFIG_IFCVF enable as a module.
- CONFIG_MLX5_VDPA_NET enable as a module.
- CONFIG_VDPA_SIM enable as a module.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
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_INTEL_IDXD_PERFMON:
Enable performance monitor (pmu) support for the Intel(R)
data accelerators present in Intel Xeon CPU. With this
enabled, perf can be used to monitor the DSA (Intel Data
Streaming Accelerator) events described in the Intel DSA
spec.
If unsure, say N.
Symbol: INTEL_IDXD_PERFMON [=n]
Type : bool
Defined at drivers/dma/Kconfig:303
Prompt: Intel Data Accelerators performance monitor support
Depends on: DMADEVICES [=y] && INTEL_IDXD [=m]
Location:
-> Device Drivers
-> DMA Engine support (DMADEVICES [=y])
-> Intel Data Accelerators support (INTEL_IDXD [=m])
---
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v2:
- CONFIG_INTEL_IDXD_PERFMON enabled for x86.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
ATM the Apple Silicon isn't useful for the average user, those that
want to experiment will be building their own kernel (and HW adapters).
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
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_MARVELL_88X2222_PHY:
Support for the Marvell 88X2222 Dual-port Multi-speed Ethernet
Transceiver.
Symbol: MARVELL_88X2222_PHY [=n]
Type : tristate
Defined at drivers/net/phy/Kconfig:204
Prompt: Marvell 88X2222 PHY
Depends on: NETDEVICES [=y] && PHYLIB [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> PHY Device support and infrastructure (PHYLIB [=y])
---
CONFIG_NXP_C45_TJA11XX_PHY:
Enable support for NXP C45 TJA11XX PHYs.
Currently supports only the TJA1103 PHY.
Symbol: NXP_C45_TJA11XX_PHY [=n]
Type : tristate
Defined at drivers/net/phy/Kconfig:237
Prompt: NXP C45 TJA11XX PHYs
Depends on: NETDEVICES [=y] && PHYLIB [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> PHY Device support and infrastructure (PHYLIB [=y])
---
Cc: Petr Oros <poros@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Bugzilla: https://bugzilla.redhat.com/1957210
Upstream: RHEL-only
description
===========
Enable dynamic linking of perf against libbpf. Also, libbpf-devel
becomes a build-dependency for kernel.src.rpm and libbpf becomes
a runtime dependency for perf.rpm.
Signed-off-by: Michael Petlan <mpetlan@redhat.com>
Intel consolidated the architecture definitions around it's Arm based
FPGA SoCs into a single architecture definition, so clean this up (NFC).
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
The PTP_1588_CLOCK_KVM support is now avaialble to arm,
it was already built everywhere for ARK so let's move
it to common to do so for Fedora too.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
In the 5.12 kernel cycle, CONFIG_HSA_AMD was changed to select
DRM_AMDGPU_USERPTR. This creates a config mismatch for ppc64le as
HSA_AMD was enabled there, but DRM_AMDGPU_USERPTR was not. This change
enables DRM_AMDGPU_USERPTR for everything, it is dependent on
DRM_AMDGPU, so this will not change the current s390X configs.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
CI has been doing rpminspect runs against built rpm packages.
We have to add specific configuration for rpminspect, that can vary
depending on the kernel branch. For example, older releases didn't
have the kernel meta-package, but today kernel have it and requires
kernel-core/kernel-modules which are the ones which contains files.
This configuration is supposed as a tweak only for the cases where
it makes sense having it here, to ship with dist-git, instead of
changing rpminspect-data-* packages.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
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_NETFILTER_XTABLES_COMPAT:
This option provides a translation layer to run 32bit arp,ip(6),ebtables
binaries on 64bit kernels.
If unsure, say N.
Symbol: NETFILTER_XTABLES_COMPAT [=y]
Type : bool
Defined at net/netfilter/Kconfig:731
Prompt: Netfilter Xtables 32bit support
Depends on: NET [=y] && INET [=y] && NETFILTER [=y] && NETFILTER_XTABLES [=y] && COMPAT [=y]
Location:
-> Networking support (NET [=y])
-> Networking options
-> Network packet filtering framework (Netfilter) (NETFILTER [=y])
-> Core Netfilter Configuration
-> Netfilter Xtables support (required for ip_tables) (NETFILTER_XTABLES [=y])
---
CONFIG_NF_LOG_SYSLOG:
This option enable support for packet logging via syslog.
It supports IPv4, IPV6, ARP and common transport protocols such
as TCP and UDP.
This is a simpler but less flexible logging method compared to
CONFIG_NETFILTER_NETLINK_LOG.
If both are enabled the backend to use can be configured at run-time
by means of per-address-family sysctl tunables.
Symbol: NF_LOG_SYSLOG [=m]
Type : tristate
Defined at net/netfilter/Kconfig:74
Prompt: Syslog packet logging
Depends on: NET [=y] && INET [=y] && NETFILTER [=y]
Location:
-> Networking support (NET [=y])
-> Networking options
-> Network packet filtering framework (Netfilter) (NETFILTER [=y])
-> Core Netfilter Configuration
Selected by [m]:
- NETFILTER_XT_TARGET_LOG [=m] && NET [=y] && INET [=y] && NETFILTER [=y] && NETFILTER_XTABLES [=y]
- NF_LOG_ARP [=m] && NET [=y] && INET [=y] && NETFILTER [=y]
- NF_LOG_IPV4 [=m] && NET [=y] && INET [=y] && NETFILTER [=y]
- NF_LOG_IPV6 [=m] && NET [=y] && INET [=y] && IPV6 [=y] && NETFILTER [=y]
---
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Antoine Tenart <atenart@redhat.com>
Cc: Balazs Nemeth <bnemeth@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_PCPU_DEV_REFCNT:
network device refcount are using per cpu variables if this option is set.
This can be forced to N to detect underflows (with a performance drop).
Symbol: PCPU_DEV_REFCNT [=y]
Type : bool
Defined at net/Kconfig:248
Prompt: Use percpu variables to maintain network device refcount
Depends on: NET [=y] && SMP [=y]
Location:
-> Networking support (NET [=y])
-> Networking options
---
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Antoine Tenart <atenart@redhat.com>
Cc: Balazs Nemeth <bnemeth@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_I2C_CP2615:
If you say yes to this option, support will be included for Silicon
Labs CP2615's I2C interface.
This driver can also be built as a module. If so, the module
will be called i2c-cp2615.
Symbol: I2C_CP2615 [=n]
Type : tristate
Defined at drivers/i2c/busses/Kconfig:1212
Prompt: Silicon Labs CP2615 USB sound card and I2C adapter
Depends on: I2C [=y] && HAS_IOMEM [=y] && USB [=y]
Location:
-> Device Drivers
-> I2C support
-> I2C support (I2C [=y])
-> I2C Hardware Bus support
---
CONFIG_I2C_HISI:
Say Y here if you want to have Hisilicon I2C controller support
available on the Kunpeng Server.
This driver can also be built as a module. If so, the module
will be called i2c-hisi.
Symbol: I2C_HISI [=n]
Type : tristate
Defined at drivers/i2c/busses/Kconfig:648
Prompt: HiSilicon I2C controller
Depends on: I2C [=y] && HAS_IOMEM [=y] && (ARM64 [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> I2C support
-> I2C support (I2C [=y])
-> I2C Hardware Bus support
---
Cc: Gopal Tiwari <gtiwari@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_INTEL_TCC_COOLING:
Enable this to support system cooling by adjusting the effective TCC
activation temperature via the TCC Offset register, which is widely
supported on modern Intel platforms.
Note that, on different platforms, the behavior might be different
on how fast the setting takes effect, and how much the CPU frequency
is reduced.
Symbol: INTEL_TCC_COOLING [=n]
Type : tristate
Defined at drivers/thermal/intel/Kconfig:83
Prompt: Intel TCC offset cooling Driver
Depends on: THERMAL [=y] && (X86 [=y] || X86_INTEL_QUARK [=n] || COMPILE_TEST [=n]) && X86 [=y]
Location:
-> Device Drivers
-> Thermal drivers (THERMAL [=y])
-> Intel thermal drivers
---
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_BT_AOSPEXT:
This options enables support for the Android Open Source
Project defined HCI vendor extensions.
Symbol: BT_AOSPEXT [=n]
Type : bool
Defined at net/bluetooth/Kconfig:102
Prompt: Enable Android Open Source Project extensions
Depends on: NET [=y] && BT [=m]
Location:
-> Networking support (NET [=y])
-> Bluetooth subsystem support (BT [=m])
---
Cc: Gopal Tiwari <gtiwari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_BT_VIRTIO:
Virtio Bluetooth support driver.
This driver supports Virtio Bluetooth devices.
Say Y here to compile support for HCI over Virtio into the
kernel or say M to compile as a module.
Symbol: BT_VIRTIO [=n]
Type : tristate
Defined at drivers/bluetooth/Kconfig:428
Prompt: Virtio Bluetooth driver
Depends on: NET [=y] && BT [=m] && VIRTIO [=y]
Location:
-> Networking support (NET [=y])
-> Bluetooth subsystem support (BT [=m])
-> Bluetooth device drivers
---
Cc: Gopal Tiwari <gtiwari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
The Modem Host Interface (MHI) is used for most newer 4G/LTE and 5G
modems. It's basically virtual ethernet over a PCI <-> PCIE-endpoint
with a control over a TTY interface. These modems are already in the
latest Lenovo laptops and likely others.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
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_MODPROBE_PATH:
When kernel code requests a module, it does so by calling
the "modprobe" userspace utility. This option allows you to
set the path where that binary is found. This can be changed
at runtime via the sysctl file
/proc/sys/kernel/modprobe. Setting this to the empty string
removes the kernel's ability to request modules (but
userspace can still load modules explicitly).
Symbol: MODPROBE_PATH [=/sbin/modprobe]
Type : string
Defined at init/Kconfig:2302
Prompt: Path to modprobe binary
Depends on: MODULES [=y]
Location:
-> Enable loadable module support (MODULES [=y])
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_INPUT_IQS626A:
Say Y to enable support for the Azoteq IQS626A capacitive
touch controller.
To compile this driver as a module, choose M here: the
module will be called iqs626a.
Symbol: INPUT_IQS626A [=n]
Type : tristate
Defined at drivers/input/misc/Kconfig:766
Prompt: Azoteq IQS626A capacitive touch controller
Depends on: !UML && INPUT [=y] && INPUT_MISC [=y] && I2C [=y]
Location:
-> Device Drivers
-> Input device support
-> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-> Miscellaneous devices (INPUT_MISC [=y])
Selects: REGMAP_I2C [=m]
---
CONFIG_TOUCHSCREEN_HYCON_HY46XX:
Say Y here if you have a touchscreen using Hycon hy46xx
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called hycon-hy46xx.
Symbol: TOUCHSCREEN_HYCON_HY46XX [=n]
Type : tristate
Defined at drivers/input/touchscreen/Kconfig:414
Prompt: Hycon hy46xx touchscreen support
Depends on: !UML && INPUT [=y] && INPUT_TOUCHSCREEN [=y] && I2C [=y]
Location:
-> Device Drivers
-> Input device support
-> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-> Touchscreens (INPUT_TOUCHSCREEN [=y])
---
CONFIG_TOUCHSCREEN_ILITEK:
Say Y here if you have touchscreen with ILITEK touch IC,
it supports 213X/23XX/25XX and other Lego series.
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called ilitek_ts_i2c.
Symbol: TOUCHSCREEN_ILITEK [=n]
Type : tristate
Defined at drivers/input/touchscreen/Kconfig:440
Prompt: Ilitek I2C 213X/23XX/25XX/Lego Series Touch ICs
Depends on: !UML && INPUT [=y] && INPUT_TOUCHSCREEN [=y] && I2C [=y]
Location:
-> Device Drivers
-> Input device support
-> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-> Touchscreens (INPUT_TOUCHSCREEN [=y])
---
CONFIG_TOUCHSCREEN_MSG2638:
Say Y here if you have an I2C touchscreen using MStar msg2638.
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called msg2638.
Symbol: TOUCHSCREEN_MSG2638 [=n]
Type : tristate
Defined at drivers/input/touchscreen/Kconfig:616
Prompt: MStar msg2638 touchscreen support
Depends on: !UML && INPUT [=y] && INPUT_TOUCHSCREEN [=y] && I2C [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Input device support
-> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-> Touchscreens (INPUT_TOUCHSCREEN [=y])
---
Cc: Tony Camuso <tcamuso@redhat.com>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
There are two modules: sctp_diag and l2tp_ip6 that are in kernel-modules
that accidentally dragged the rest of the sctp and l2tp mdoules in
there. Instead all those modules should stay in modules-extra.
Move the offending modules into modules-extra.
Cc: mleitner@redhat.com
Cc: lxin@redhat.com
Cc: jbenc@redhat.com
Signed-off-by: Don Zickus <dzickus@redhat.com>
CKI has been failing to cross build a ppc64le rpm for a while now. The
reason why is the ppc64le-gnu-strip command could not recognize the
scripts/dtc/libfdt/fdt_strerror.o file because it was an x86_64 file
type. That is a result of the cross env.
What should have happened is, none of the *.o files in the script
directory should be there and thus the strip command would have nothing
to strip.
Having x86_64 files lying around to be packaged in kernel-devel is
another problem. But for this build problem, just remove all the *.o
files in the script/ area.
The spec file tries to do this, but fails to remove *.o's at another
directory layer (libfdt). Let's just replace the 'rm' commands with a
'find and rm' command instead.
Tested in a CKI container. After this change, the rpm builds.
Signed-off-by: Don Zickus <dzickus@redhat.com>
The GPIOs provided by the AMD pinctrl module may be used by various
ACPI methods (e.g. _PS0, _PS3) and resources (GpioInt). These ACPI
uses may happen before the module has a chance to load when amd_pinctrl
is build as a module.
Change the CONFIG_PINCTRL_AMD option to y, so that the amd_pinctrl
code gets built into the kernel to fix this. This specifically fixes
I2C-HID touchpads on AMD based laptops sometimes not working at boot.
BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1634832
BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1957203
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
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_MFD_ATC260X_I2C:
Support for the Actions Semi ATC260x PMICs controlled via I2C.
This driver provides common support for accessing the ATC2603C
and ATC2609A chip variants, additional drivers must be enabled
in order to use the functionality of the device.
Symbol: MFD_ATC260X_I2C [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:2064
Prompt: Actions Semi ATC260x PMICs with I2C
Depends on: HAS_IOMEM [=y] && I2C [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: MFD_ATC260X [=n] && REGMAP_I2C [=m]
---
CONFIG_MFD_NTXEC:
Say yes here if you want to support the embedded controller found in
certain e-book readers designed by the original design manufacturer
Netronix.
Symbol: MFD_NTXEC [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:970
Prompt: Netronix embedded controller (EC)
Depends on: HAS_IOMEM [=y] && (OF [=y] || COMPILE_TEST [=n]) && I2C [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: REGMAP_I2C [=m] && MFD_CORE [=m]
---
CONFIG_MFD_ROHM_BD957XMUF:
Select this option to get support for the ROHM BD9576MUF and
BD9573MUF Power Management ICs. BD9576 and BD9573 are primarily
designed to be used to power R-Car series processors.
Symbol: MFD_ROHM_BD957XMUF [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:1981
Prompt: ROHM BD9576MUF and BD9573MUF Power Management ICs
Depends on: HAS_IOMEM [=y] && I2C [=y]=y && OF [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: REGMAP_I2C [=m] && MFD_CORE [=m]
---
Cc: Torez Smith <torez@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_LEDS_RT4505:
This option enables support for the RT4505 flash LED controller.
RT4505 includes torch and flash functions with programmable current.
And it's commonly used to compensate the illuminance for the camera
inside the mobile product like as phones or tablets.
Symbol: LEDS_RT4505 [=n]
Type : tristate
Defined at drivers/leds/flash/Kconfig:5
Prompt: LED support for RT4505 flashlight controller
Depends on: NEW_LEDS [=y] && LEDS_CLASS_FLASH [=m] && I2C [=y] && OF [=y] && (V4L2_FLASH_LED_CLASS [=n] || !V4L2_FLASH_LED_CLASS [=n])
Location:
-> Device Drivers
-> LED Support (NEW_LEDS [=y])
Selects: REGMAP_I2C [=m]
---
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Some time ago this config option came in, and the scripts missed it. I
added the file to pending turning it off, but that doesn't get it
reviewed. This MR would move the config from pending to common, but it
does keep CONFIG_KASAN_HW_TAGS off. Let me know if you would rather
turn it on.
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Justin M. Forbes <jforbes@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_VEXPRESS_CONFIG:
Platform configuration infrastructure for the ARM Ltd.
Versatile Express.
Symbol: VEXPRESS_CONFIG [=y]
Type : tristate
Defined at drivers/bus/Kconfig:224
Prompt: Versatile Express configuration bus
Depends on: (ARM || ARM64 [=y]) && OF [=y]
Location:
-> Device Drivers
-> Bus devices
Selects: REGMAP [=y]
Cc: Myron Stowe <myron.stowe@redhat.com>
We're removing support for KVM on POWER in RHEL9. However, we're leaving
the KVM module enabled to allow for certain internal test scenarious. This
will also make life easier for possible IBM and/or community supported
efforts.
However, we only want to enable the KVM HV implementation, not the KVM PR
implementation. The latter is very slow, quite buggy on POWER9 and later
CPUs and generally just causes confusion. It's been disabled for a long
time in RHEL8 already (by 4e54d8b3cd8 "[redhat]powerpc64: disable kvm-pr").
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1930649
Upstream Status: RHEL only
Signed-off-by: David Gibson <dgibson@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1957219
RHEL-only
description
===========
Adding explicit bzip2 dependency for perf tool. The bzip2
is used in perf archive script command, and without bzip2
command it fails, like:
$ perf archive
tar (child): bzip2: Cannot exec: No such file or directory
tar (child): Error is not recoverable: exiting now
With explicit bzip2 dependency we're ok:
$ rpm -qp --requires perf-...rpm | grep bzip2
bzip2
Signed-off-by: Michael Petlan <mpetlan@redhat.com>
As CONFIG_TYPEC_UCSI and CONFIG_UCSI_ACPI now depend on
CONFIG_USB_ROLE_SWITCH, we end up with a config mismatch. We can either
change USB_ROLE_SWITCH to inline as I have done here, or change
TYPEC_UCSI and UCSI_ACPI to modules. I chose flipping USB_ROLE_SWITCH
inline as it seems the safer solution.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
While FW_LOADER_USER_HELPER is largerly deprecated, there are 2 drivers
which still require it, CONFIG_LEDS_LP55XX_COMMON is turned off, but
CONFIG_DELL_RBU is enabled for x86_64. This turns off
FW_LOADER_USER_HELPER for everything except for x86_64 to support the
DELL_RBU driver. As the DELL_RBU driver does a select on
FW_LOADER_USER_HELPER, the options were turning it on, or turning off
the DELL_RBU driver.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
Some time ago, a config mismatch required turning on
CONFIG_FB_MODE_HELPERS for ppc. As I went through to create a proper MR
to get that reviewed, I found that our existing configs were a mess on
this one. This cleans everything up. As only a few drivers rely on this
feature, and they select it, this should be correct. For RHEL configs,
it is only ppc64le that leaves it enabled.
Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Justin M. Forbes <jforbes@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_CGROUP_MISC:
Provides a controller for miscellaneous resources on a host.
Miscellaneous scalar resources are the resources on the host system
which cannot be abstracted like the other cgroups. This controller
tracks and limits the miscellaneous resources used by a process
attached to a cgroup hierarchy.
For more information, please check misc cgroup section in
/Documentation/admin-guide/cgroup-v2.rst.
Symbol: CGROUP_MISC [=n]
Type : bool
Defined at init/Kconfig:1113
Prompt: Misc resource controller
Depends on: CGROUPS [=y]
Location:
-> General setup
-> Control Group support (CGROUPS [=y])
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v2:
- CONFIG_CGROUP_MISC: enable it.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
CONFIG_VFIO now selects IOMMU_API instead of depending on it, causing
several config mismatches for the zfcpdump kernel. Best to just turn it
off in this instance.
Cc: Alex Williamson <alex.williamson@redhat.com>
Cc: Eric Auger <eric.auger@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
This file was added due to a config mismatch 9 months ago. That
mismatch no longer exists with the current ARK configs, so I am deleting
the file. If it becomes valid again, the scripts will create a new one
and send it through the regular config process.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
MR 1049 enabled CONFIG_CRYPTO_ECDSA and made it modular for everyone. As
the s390x zfcpdump kernels do not support modules, this needs to be
brought inline (or turned off all together) for that kernel.
Signed-off-by: Justin M. Forbes <jforbes@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_NET_DSA_MV88E6XXX_PTP:
Say Y to enable PTP hardware timestamping on Marvell 88E6xxx switch
chips that support it.
Symbol: NET_DSA_MV88E6XXX_PTP [=n]
Type : bool
Defined at drivers/net/dsa/mv88e6xxx/Kconfig:12
Prompt: PTP support for Marvell 88E6xxx
Depends on: NETDEVICES [=y] && HAVE_NET_DSA [=y] && PTP_1588_CLOCK [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Distributed Switch Architecture drivers
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
In the SPEC file, "flavour" is used when referring to the kernel "variant"
instead (such as debug, lpae, or zfcpdump). In the Fedora/ARK documentation
and scripts, "flavor" refers to a configuration directory (fedora or ark)
underneath redhat/configs/ in the os-build branch.
Signed-off-by: David Ward <david.ward@ll.mit.edu>
The %{upstream_branch} macro and others were dropped from the SPEC file (in
Fedora kernel dist-git commit cff59d310104) seven years ago. It left behind
the %{variant} macro, which is only used for --with-vanilla.
The --with-vanilla option does not work with the current SPEC file, because
defining %{variant} causes errors: it results in dependencies with invalid
NVRs (where the package release contains a dash). Defining %{vanilla} would
also cause the source RPM to be built using a different name, although it
would have exactly the same contents as the "kernel" source RPM.
Even the name %{variant} is misleading. In Fedora/RHEL, kernel "variants"
are built with different options than the generic kernel configuration, and
are provided in subpackages. The %{variant} macro was meant to be used when
the kernel is built from different sources instead. (The sources in vanilla
builds do not have any downstream patches applied.)
Instead of using %{variant}, rely on package builders to define %{buildid}
when they change the package sources, whether it is by using --with-vanilla
or by introducing additional patches. This allows %{variant} to be dropped.
Signed-off-by: David Ward <david.ward@ll.mit.edu>
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_MLX5_TC_SAMPLE:
Say Y here if you want to support offloading sample rules via tc
sample action.
If set to N, will not be able to configure tc rules with sample
action.
If unsure, set to Y
Symbol: MLX5_TC_SAMPLE [=y]
Type : bool
Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:107
Prompt: MLX5 TC sample offload support
Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_CLS_ACT [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Ethernet driver support (ETHERNET [=y])
-> Mellanox devices (NET_VENDOR_MELLANOX [=y])
-> Mellanox 5th generation network adapters (ConnectX series) Ethernet support (MLX5_CORE_EN [=y])
-> Mellanox Technologies MLX5 SRIOV E-Switch support (MLX5_ESWITCH [=y])
-> MLX5 TC classifier action support (MLX5_CLS_ACT [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1940794
Upstream: RHEL Only
The cryptos(BLAKE2S, Curve25519, CHACHA20POLY1305) in WireGuard are not
FIPS approved. Disable loading the cryptos is a better solution, but the
cryptos called by WireGuard are in lib/crypto/ instead of crypto/, which
is a little complex to disable. While disabling the WireGuard module is
more clear and easier.
So let's disable the WireGuard in FIPS mode first. When the issue that
loading the lib/crypto/ code in FIPS mode is fixed. We can revert this
internal patch.
Signed-off-by: Hangbin Liu <haliu@redhat.com>
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_NFS_V4_2_READ_PLUS:
This is intended for developers only. The READ_PLUS operation has
been shown to have issues under specific conditions and should not
be used in production.
Symbol: NFS_V4_2_READ_PLUS [=n]
Type : bool
Defined at fs/nfs/Kconfig:209
Prompt: NFS: Enable support for the NFSv4.2 READ_PLUS operation
Depends on: NETWORK_FILESYSTEMS [=y] && NFS_V4_2 [=y]
Location:
-> File systems
-> Network File Systems (NETWORK_FILESYSTEMS [=y])
---
Cc: kernel-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@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_MODULE_COMPRESS_GZIP:
Compress modules with GZIP. The installed modules are suffixed
with .ko.gz.
Symbol: MODULE_COMPRESS_GZIP [=n]
Type : bool
Defined at init/Kconfig:2264
Prompt: GZIP
Depends on: <choice>
Location:
-> Enable loadable module support (MODULES [=y])
-> Module compression mode (<choice> [=y])
---
CONFIG_MODULE_COMPRESS_NONE:
Do not compress modules. The installed modules are suffixed
with .ko.
Symbol: MODULE_COMPRESS_NONE [=y]
Type : bool
Defined at init/Kconfig:2258
Prompt: None
Depends on: <choice>
Location:
-> Enable loadable module support (MODULES [=y])
-> Module compression mode (<choice> [=y])
---
CONFIG_MODULE_COMPRESS_XZ:
Compress modules with XZ. The installed modules are suffixed
with .ko.xz.
Symbol: MODULE_COMPRESS_XZ [=n]
Type : bool
Defined at init/Kconfig:2270
Prompt: XZ
Depends on: <choice>
Location:
-> Enable loadable module support (MODULES [=y])
-> Module compression mode (<choice> [=y])
---
CONFIG_MODULE_COMPRESS_ZSTD:
Compress modules with ZSTD. The installed modules are suffixed
with .ko.zst.
Symbol: MODULE_COMPRESS_ZSTD [=n]
Type : bool
Defined at init/Kconfig:2276
Prompt: ZSTD
Depends on: <choice>
Location:
-> Enable loadable module support (MODULES [=y])
-> Module compression mode (<choice> [=y])
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_TEST_DIV64:
Enable this to turn on 'do_div()' function test. This test is
executed only once during system boot (so affects only boot time),
or at module load time.
If unsure, say N.
Symbol: TEST_DIV64 [=n]
Type : tristate
Defined at lib/Kconfig.debug:2078
Prompt: 64bit/32bit division and modulo test
Depends on: RUNTIME_TESTING_MENU [=y] && (DEBUG_KERNEL [=y] || m && MODULES [=y])
Location:
-> Kernel hacking
-> Kernel Testing and Coverage
-> Runtime Testing (RUNTIME_TESTING_MENU [=y])
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Currently the CFB algo is built as a module in Fedora and is not build in
ARK. This results in a panic while booting in a FIPS mode:
[ 3.347092] alg: skcipher: failed to allocate transform for cfb(aes): -2
[ 3.347918] Kernel panic - not syncing: alg: self-tests for cfb(aes) (cfb(aes)) failed in fips mode!
Fix this by embedding the CFB code into a kernel, the same way as CTS and
CBC algos already do. The reason why the CFB code is embedded and is not
built as a module is that dracut must add the module to an initramfs image.
This is not always the case.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1915290
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
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_CIO_INJECT:
This option provides a debugging facility to inject certain artificial events
and instruction responses to the CIO layer of Linux kernel. The newly created
debugfs user-interfaces will be at /sys/kernel/debug/s390/cio/*
Symbol: CIO_INJECT [=n]
Type : bool
Defined at arch/s390/Kconfig.debug:19
Prompt: CIO Inject interfaces
Depends on: DEBUG_KERNEL [=y] && DEBUG_FS [=y]
Location:
-> Kernel hacking
-> s390 Debugging
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v2:
- CONFIG_CIO_INJECT: s390 only
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
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_SECURITY_LANDLOCK:
Landlock is a sandboxing mechanism that enables processes to restrict
themselves (and their future children) by gradually enforcing
tailored access control policies. A Landlock security policy is a
set of access rights (e.g. open a file in read-only, make a
directory, etc.) tied to a file hierarchy. Such policy can be
configured and enforced by any processes for themselves using the
dedicated system calls: landlock_create_ruleset(),
landlock_add_rule(), and landlock_restrict_self().
See Documentation/userspace-api/landlock.rst for further information.
If you are unsure how to answer this question, answer N. Otherwise,
you should also prepend "landlock," to the content of CONFIG_LSM to
enable Landlock at boot time.
Symbol: SECURITY_LANDLOCK [=n]
Type : bool
Defined at security/landlock/Kconfig:3
Prompt: Landlock support
Depends on: SECURITY [=y] && !ARCH_EPHEMERAL_INODES [=n]
Location:
-> Security options
Selects: SECURITY_PATH [=n]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_SND_VIRTIO:
This is the virtual sound driver for virtio. Say Y or M.
Symbol: SND_VIRTIO [=n]
Type : tristate
Defined at sound/virtio/Kconfig:4
Prompt: Virtio sound driver
Depends on: SOUND [=m] && !UML && SND [=m] && VIRTIO [=y]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
Selects: SND_PCM [=m] && SND_JACK [=y]
---
Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v2:
- CONFIG_SND_VIRTIO enable as a module.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
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_CRYPTO_ECDSA:
Elliptic Curve Digital Signature Algorithm (NIST P192, P256 etc.)
is A NIST cryptographic standard algorithm. Only signature verification
is implemented.
Symbol: CRYPTO_ECDSA [=n]
Type : tristate
Defined at crypto/Kconfig:245
Prompt: ECDSA (NIST P192, P256 etc.) algorithm
Depends on: CRYPTO [=y]
Location:
-> Cryptographic API (CRYPTO [=y])
Selects: CRYPTO_ECC [=m] && CRYPTO_AKCIPHER [=y] && ASN1 [=y]
---
Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v2:
- CONFIG_CRYPTO_ECDSA enable as a module.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
Upstream commit a01d935b2e removed the
bpf-helpers man page from bpftool docs. Trying to rm the built man page
will fail the kernel build because it isn't there.
Signed-off-by: Justin M. Forbes <jforbes@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_KVM_XEN:
Provides KVM support for the hosting Xen HVM guests and
passing Xen hypercalls to userspace.
If in doubt, say "N".
Symbol: KVM_XEN [=n]
Type : bool
Defined at arch/x86/kvm/Kconfig:106
Prompt: Support for Xen hypercall interface
Depends on: VIRTUALIZATION [=y] && KVM [=m]
Location:
-> Virtualization (VIRTUALIZATION [=y])
-> Kernel-based Virtual Machine (KVM) support (KVM [=m])
---
Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_HID_FT260:
Provides I2C host adapter functionality over USB-HID through FT260
device. The customizable USB descriptor fields are exposed as sysfs
attributes.
To compile this driver as a module, choose M here: the module
will be called hid-ft260.
Symbol: HID_FT260 [=n]
Type : tristate
Defined at drivers/hid/Kconfig:354
Prompt: FTDI FT260 USB HID to I2C host support
Depends on: INPUT [=y] && HID [=y] && USB_HID [=y] && HIDRAW [=y] && I2C [=y]
Location:
-> Device Drivers
-> HID support
-> HID bus support (HID [=y])
-> Special HID drivers
---
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_SENSORS_BPA_RS600:
If you say yes here you get hardware monitoring support for BluTek
BPA-RS600 Power Supplies.
This driver can also be built as a module. If so, the module will
be called bpa-rs600.
Symbol: SENSORS_BPA_RS600 [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:59
Prompt: BluTek BPA-RS600 Power Supplies
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
CONFIG_SENSORS_FSP_3Y:
If you say yes here you get hardware monitoring support for
FSP/3Y-Power hot-swap power supplies.
Supported models: YH-5151E, YM-2151E
This driver can also be built as a module. If so, the module will
be called fsp-3y.
Symbol: SENSORS_FSP_3Y [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:68
Prompt: FSP/3Y-Power power supplies
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
CONFIG_SENSORS_IR36021:
If you say yes here you get hardware monitoring support for Infineon
IR36021.
This driver can also be built as a module. If so, the module will
be called ir36021.
Symbol: SENSORS_IR36021 [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:106
Prompt: Infineon IR36021
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
CONFIG_SENSORS_MAX15301:
If you say yes here you get hardware monitoring support for Maxim
MAX15301, as well as for Flex BMR461.
This driver can also be built as a module. If so, the module will
be called max15301.
Symbol: SENSORS_MAX15301 [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:179
Prompt: Maxim MAX15301
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
CONFIG_SENSORS_NZXT_KRAKEN2:
If you say yes here you get support for hardware monitoring for the
NZXT Kraken X42/X52/X62/X72 all-in-one CPU liquid coolers.
This driver can also be built as a module. If so, the module
will be called nzxt-kraken2.
Symbol: SENSORS_NZXT_KRAKEN2 [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:1485
Prompt: NZXT Kraken X42/X51/X62/X72 liquid coolers
Depends on: HWMON [=y] && USB_HID [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
CONFIG_SENSORS_STPDDC60:
If you say yes here you get hardware monitoring support for ST
STPDDC60 Universal Digital Multicell Controller, as well as for
Flex BMR481.
This driver can also be built as a module. If so, the module will
be called stpddc60.
Symbol: SENSORS_STPDDC60 [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:287
Prompt: ST STPDDC60
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
In 2019, hardlink was brought into util-linux upstream with v2.34. As
part of the util-linux package, it is now in /usr/bin instead of
/usr/sbin. No one noticed because we just skipped the hardlink and took
up a bit of extra space. Let's point to the correct location now.
Fixes rhbz 1889043
Signed-off-by: Justin M. Forbes <jforbes@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_SPI_ALTERA_CORE:
"The core code for the Altera SPI Controller"
Symbol: SPI_ALTERA_CORE [=n]
Type : tristate
Defined at drivers/spi/Kconfig:67
Prompt: Altera SPI Controller core code
Depends on: SPI [=y] && SPI_MASTER [=y]
Location:
-> Device Drivers
-> SPI support (SPI [=y])
Selects: REGMAP [=y]
Selected by [n]:
- SPI_ALTERA [=n] && SPI [=y] && SPI_MASTER [=y]
- SPI_ALTERA_DFL [=n] && SPI [=y] && SPI_MASTER [=y] && FPGA_DFL [=n]
---
CONFIG_SPI_HISI_KUNPENG:
This enables support for HiSilicon SPI controller found on
Kunpeng SoCs.
This driver can also be built as a module. If so, the module
will be called hisi-kunpeng-spi.
Symbol: SPI_HISI_KUNPENG [=n]
Type : tristate
Defined at drivers/spi/Kconfig:351
Prompt: HiSilicon SPI Controller for Kunpeng SoCs
Depends on: SPI [=y] && SPI_MASTER [=y] && (ARM64 [=y] && ACPI [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> SPI support (SPI [=y])
---
Cc: Al Stone <ahs3@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_RANDOMIZE_KSTACK_OFFSET_DEFAULT:
The kernel stack offset can be randomized (after pt_regs) by
roughly 5 bits of entropy, frustrating memory corruption
attacks that depend on stack address determinism or
cross-syscall address exposures. This feature is controlled
by kernel boot param "randomize_kstack_offset=on/off", and this
config chooses the default boot state.
Symbol: RANDOMIZE_KSTACK_OFFSET_DEFAULT [=n]
Type : bool
Defined at arch/Kconfig:1114
Prompt: Randomize kernel stack offset on syscall entry
Depends on: HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET [=y]
Location:
-> General architecture-dependent options
---
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_LOCKDEP_BITS:
Try increasing this value if you hit "BUG: MAX_LOCKDEP_ENTRIES too low!" message.
Symbol: LOCKDEP_BITS [=15]
Type : integer
Range : [10 30]
Defined at lib/Kconfig.debug:1373
Prompt: Bitsize for MAX_LOCKDEP_ENTRIES
Depends on: LOCKDEP [=y] && !LOCKDEP_SMALL [=n]
Location:
-> Kernel hacking
-> Lock Debugging (spinlocks, mutexes, etc...)
---
CONFIG_LOCKDEP_CHAINS_BITS:
Try increasing this value if you hit "BUG: MAX_LOCKDEP_CHAINS too low!" message.
Symbol: LOCKDEP_CHAINS_BITS [=16]
Type : integer
Range : [10 30]
Defined at lib/Kconfig.debug:1381
Prompt: Bitsize for MAX_LOCKDEP_CHAINS
Depends on: LOCKDEP [=y] && !LOCKDEP_SMALL [=n]
Location:
-> Kernel hacking
-> Lock Debugging (spinlocks, mutexes, etc...)
---
CONFIG_LOCKDEP_CIRCULAR_QUEUE_BITS:
Try increasing this value if you hit "lockdep bfs error:-1" warning due to __cq_enqueue() failure.
Symbol: LOCKDEP_CIRCULAR_QUEUE_BITS [=12]
Type : integer
Range : [10 30]
Defined at lib/Kconfig.debug:1405
Prompt: Bitsize for elements in circular_queue struct
Depends on: LOCKDEP [=y]
Location:
-> Kernel hacking
-> Lock Debugging (spinlocks, mutexes, etc...)
---
CONFIG_LOCKDEP_STACK_TRACE_BITS:
Try increasing this value if you hit "BUG: MAX_STACK_TRACE_ENTRIES too low!" message.
Symbol: LOCKDEP_STACK_TRACE_BITS [=19]
Type : integer
Range : [10 30]
Defined at lib/Kconfig.debug:1389
Prompt: Bitsize for MAX_STACK_TRACE_ENTRIES
Depends on: LOCKDEP [=y] && !LOCKDEP_SMALL [=n]
Location:
-> Kernel hacking
-> Lock Debugging (spinlocks, mutexes, etc...)
---
CONFIG_LOCKDEP_STACK_TRACE_HASH_BITS:
Try increasing this value if you need large MAX_STACK_TRACE_ENTRIES.
Symbol: LOCKDEP_STACK_TRACE_HASH_BITS [=14]
Type : integer
Range : [10 30]
Defined at lib/Kconfig.debug:1397
Prompt: Bitsize for STACK_TRACE_HASH_SIZE
Depends on: LOCKDEP [=y] && !LOCKDEP_SMALL [=n]
Location:
-> Kernel hacking
-> Lock Debugging (spinlocks, mutexes, etc...)
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_ACPI_CPPC_CPUFREQ_FIE:
This extends frequency invariance support in the CPPC cpufreq driver,
by using CPPC delivered and reference performance counters.
If in doubt, say N.
Symbol: ACPI_CPPC_CPUFREQ_FIE [=y]
Type : bool
Defined at drivers/cpufreq/Kconfig.arm:22
Prompt: Frequency Invariance support for CPPC cpufreq driver
Depends on: CPU_FREQ [=y] && (ARM || ARM64 [=y]) && ACPI_CPPC_CPUFREQ [=m] && GENERIC_ARCH_TOPOLOGY [=y]
Location:
-> CPU Power Management
-> CPU Frequency scaling
-> CPU Frequency scaling (CPU_FREQ [=y])
-> CPUFreq driver based on the ACPI CPPC spec (ACPI_CPPC_CPUFREQ [=m])
---
Cc: Al Stone <ahs3@redhat.com>
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Packages can be rebuilt from tagged commits in the kernel-ark repository by
cloning it and running the packaging scripts. This should be reproducible:
packages built from identical sources should have the same NVR.
For builds based on upstream snapshots, the package release contains a date
that is meant to correspond to changes in the fedora-ark repository. (It is
not the date of the upstream snapshot.) Instead, the packaging scripts set
this date from the system clock. Change this so that the commit date in the
kernel-ark repository is used.
Signed-off-by: David Ward <david.ward@ll.mit.edu>
For snapshot builds, the upstream tarball filename includes the date that
"make dist-sources" was run. This date has no relationship to the upstream
sources and should not be part of the filename.
The only other information in the filename is the abbreviated commit hash.
The filename does not directly show which upstream release preceded it.
Change the filename for upstream snapshots so it is based on the output of
"git describe". An example filename is:
linux-5.12-rc8-53-g2a1d7946f.tar.xz
This is a snapshot of commit 2a1d7946f, which is 53 commits ahead of the
tag v5.12-rc8. Note that the object name v5.12-rc8-53-g2a1d7946f can be
used in Git commands, just like the tags v5.12-rc8, v5.12, or v5.12.1.
Signed-off-by: David Ward <david.ward@ll.mit.edu>
There is a bug in gen_config_patches.sh which will assumes all new
configs are in redhat/configs/pending-common. This is not true
for pending-fedora configs. As a result the script reads the
pending-feodra config and tries to copy a pending-common config
into the final location.
The pending-common file does not exist thus creating an empty final
config file.
Fix this by filtering out any pending-fedora configs from the list of
configs to process.
Tested manually.
Signed-off-by: Don Zickus <dzickus@redhat.com>
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_USB4_DMA_TEST:
This allows sending and receiving DMA traffic through loopback
connection. Loopback connection can be done by either special
dongle that has TX/RX lines crossed, or by simply connecting a
cable back to the host. Only enable this if you know what you
are doing. Normal users and distro kernels should say N here.
To compile this driver a module, choose M here. The module will be
called thunderbolt_dma_test.
Symbol: USB4_DMA_TEST [=n]
Type : tristate
Defined at drivers/thunderbolt/Kconfig:34
Prompt: DMA traffic test driver
Depends on: USB4 [=y] && DEBUG_FS [=y]
Location:
-> Device Drivers
-> Unified support for USB4 and Thunderbolt (USB4 [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_NTB_EPF:
This driver supports EPF NTB on configurable endpoint.
If unsure, say N.
Symbol: NTB_EPF [=n]
Type : tristate
Defined at drivers/ntb/hw/epf/Kconfig:1
Prompt: Generic EPF Non-Transparent Bridge support
Depends on: NTB [=m] && m && MODULES [=y]
Location:
-> Device Drivers
-> Non-Transparent Bridge support (NTB [=m])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_APPLE:
This enables support for Apple's in-house ARM SoC family, starting
with the Apple M1.
Symbol: ARCH_APPLE [=n]
Type : bool
Defined at arch/arm64/Kconfig.platforms:29
Prompt: Apple Silicon SoC family
Location:
-> Platform selection
Selects: APPLE_AIC [=n]
---
CONFIG_ARCH_INTEL_SOCFPGA:
This enables support for Intel's SoCFPGA ARMv8 families:
Stratix 10 (ex. Altera), Agilex and eASIC N5X.
Symbol: ARCH_INTEL_SOCFPGA [=n]
Type : bool
Defined at arch/arm64/Kconfig.platforms:254
Prompt: Intel's SoCFPGA ARMv8 Families
Location:
-> Platform selection
---
CONFIG_ARM64_EPAN:
Enhanced Privileged Access Never (EPAN) allows Privileged
Access Never to be used with Execute-only mappings.
The feature is detected at runtime, and will remain disabled
if the cpu does not implement the feature.
Symbol: ARM64_EPAN [=y]
Type : bool
Defined at arch/arm64/Kconfig:1695
Prompt: Enable support for Enhanced Privileged Access Never (EPAN)
Depends on: ARM64_PAN [=y]
Location:
-> Kernel Features
-> ARMv8.7 architectural features
---
Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_ADV_SWBUTTON:
Say Y here to enable support for Advantech software defined
button feature. More information can be found at
<http://www.advantech.com.tw/products/>
To compile this driver as a module, choose M here. The module will
be called adv_swbutton.
Symbol: ADV_SWBUTTON [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:207
Prompt: Advantech ACPI Software Button Driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y] && INPUT [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
---
CONFIG_GIGABYTE_WMI:
Say Y here if you want to support WMI-based temperature reporting on
Gigabyte mainboards.
To compile this driver as a module, choose M here: the module will
be called gigabyte-wmi.
Symbol: GIGABYTE_WMI [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:126
Prompt: Gigabyte WMI temperature driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI_WMI [=m] && HWMON [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
---
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_DW_XDATA_PCIE:
This driver allows controlling Synopsys DesignWare PCIe traffic
generator IP also known as xData, present in Synopsys DesignWare
PCIe Endpoint prototype.
If unsure, say N.
Symbol: DW_XDATA_PCIE [=n]
Type : tristate
Defined at drivers/misc/Kconfig:405
Prompt: Synopsys DesignWare xData PCIe driver
Depends on: PCI [=y]
Location:
-> Device Drivers
-> Misc devices
---
CONFIG_PVPANIC_MMIO:
This driver provides support for the MMIO pvpanic device.
Symbol: PVPANIC_MMIO [=n]
Type : tristate
Defined at drivers/misc/pvpanic/Kconfig:15
Prompt: pvpanic MMIO device support
Depends on: HAS_IOMEM [=y] && (ACPI [=y] || OF [=n]) && PVPANIC [=y]
Location:
-> Device Drivers
-> Misc devices
-> pvpanic device support (PVPANIC [=y])
---
CONFIG_PVPANIC_PCI:
This driver provides support for the PCI pvpanic device.
pvpanic is a paravirtualized device provided by QEMU which
forwards the panic events from the guest to the host.
Symbol: PVPANIC_PCI [=n]
Type : tristate
Defined at drivers/misc/pvpanic/Kconfig:21
Prompt: pvpanic PCI device support
Depends on: PCI [=y] && PVPANIC [=y]
Location:
-> Device Drivers
-> Misc devices
-> pvpanic device support (PVPANIC [=y])
---
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
BZ: 1948690
Upstream Status: RHEL-only
This commit offers a more refined version of this rhel-8.git commit:
b904f4b8e0f90 [nvme] nvme: decouple basic ANA log page re-read support from native multipathing
Whether or not ANA is present is a choice of the target implementation;
the host (and whether it supports multipathing) has _zero_ influence on
this. If the target declares a path as 'inaccessible' the path _is_
inaccessible to the host. As such, ANA support should be functional
even if native multipathing is not.
Introduce ability to always re-read ANA log page as required due to ANA
error and make current ANA state available via sysfs -- even if native
multipathing is disabled on the host (e.g. nvme_core.multipath=N).
This is achieved by factoring out nvme_update_ana() and calling it in
nvme_complete_rq() for all FAILOVER requests.
This affords userspace access to the current ANA state independent of
which layer might be doing multipathing. This makes 'nvme list-subsys'
show ANA state for all NVMe subsystems with multiple controllers. It
also allows userspace multipath-tools to rely on the NVMe driver for
ANA support while dm-multipath takes care of multipathing.
And as always, if embedded NVMe users do not want any performance
overhead associated with ANA or native NVMe multipathing they can
disable CONFIG_NVME_MULTIPATH.
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
BZ: 1948690
Upstream Status: RHEL-only
This commit offers a more minimalist version of these 2 rhel-8.git commits:
f8fb6ea1226e2 [nvme] nvme: update failover handling to work with REQ_FAILFAST_TRANSPORT
7dadadb072515 [nvme] nvme: allow retry for requests with REQ_FAILFAST_TRANSPORT set
REQ_FAILFAST_TRANSPORT is set by upper layer software that handles
multipathing. Unlike SCSI, NVMe's error handling was specifically
designed to handle local retry for non-path errors. As such, allow
NVMe's local retry mechanism to be used for requests marked with
REQ_FAILFAST_TRANSPORT.
In this way, the mechanism of NVMe multipath or other multipath are
now equivalent. The mechanism is: non path related error will be
retried locally, path related error is handled by multipath.
Also, introduce FAILUP handling for REQ_FAILFAST_TRANSPORT. Update
NVMe to allow failover of requests marked with either REQ_NVME_MPATH
or REQ_FAILFAST_TRANSPORT. This allows such requests to be given a
disposition of either FAILOVER or FAILUP respectively.
nvme_complete_rq() is updated to call nvme_failup_req() if
nvme_decide_disposition() returns FAILUP. nvme_failup_req() ensures
the request is completed with a retryable path error.
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
The default for CONFIG_NETFS_SUPPORT is m and creates a config mismatch
on s390x zfcpdump as modules are disabled there. This turns it off for
that config.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
It was noticed with the change to use ark-infra, the CI scripts were
failing at 'git push gitlab $(git describe).
That command was supposed to push a newly created tag from 'make
dist-release-tag' which is pointed to by ark-latest.
A 'git describe' of ark-latest translates to that tag and is easily
pushed. With the addition of 'ark-infra', the last branch checked out
is ark-infra. A 'git describe' of that branch translates into an
un-tagged reference forcing the 'git push' script to fail.
Fix this by forcing the ark-latest branch to be checked last so that
'git describe' works correctly.
Signed-off-by: Don Zickus <dzickus@redhat.com>
The platform-python package was abandoned:
https://fedoraproject.org/wiki/Changes/Platform_Python_Stack
It does not exist in any supported version of Fedora or RHEL. All of them
provide a native Python 3 package where the interpreter is installed at
/usr/bin/python3. In an unprivileged environment, it may not be possible
to create a /usr/libexec/platform-python symlink to build these sources.
Signed-off-by: David Ward <david.ward@ll.mit.edu>
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_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK:
This adds support for SoundWire with Sound Open Firmware
for Intel(R) platforms.
Say Y if you want to enable SoundWire links with SOF.
If unsure select "N".
Symbol: SND_SOC_SOF_INTEL_SOUNDWIRE_LINK [=n]
Type : bool
Defined at sound/soc/sof/intel/Kconfig:356
Prompt: SOF support for SoundWire
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_SOF_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_PCI [=m] && ACPI [=y]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> Sound Open Firmware Support (SND_SOC_SOF_TOPLEVEL [=y])
-> SOF support for Intel audio DSPs (SND_SOC_SOF_INTEL_TOPLEVEL [=y])
---
Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v2:
- CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK set to y for x86 only.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
ARK and Fedora now have the same settings, so consolidate them in the
common config directory.
Cc: Lyude Paul <lyude@redhat.com>
Cc: Jeremy Cline <jcline@redhat.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
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_DEBUG_ENTRY:
This option enables sanity checks in s390 low-level entry code.
Some of these sanity checks may slow down kernel entries and
exits or otherwise impact performance.
If unsure, say N.
Symbol: DEBUG_ENTRY [=n]
Type : bool
Defined at arch/s390/Kconfig.debug:9
Prompt: Debug low-level entry code
Depends on: DEBUG_KERNEL [=y]
Location:
-> Kernel hacking
-> s390 Debugging
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v2:
- Set CONFIG_DEBUG_ENTRY for s390x debug variant.
- Removed redundant ark/generic CONFIG_DEBUG_ENTRY file.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
This is enabled as a module now for the generic case so we either need
to bake it in to the zfcpdump kernel or disable it. I chose the latter.
Cc: Philipp Rudo <prudo@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
Allow developers to use the ark infrastructure work on upstream
git trees. This change saves the redhat/ plus supporting files
on top of the 'master' branch.
A developer can then 'git merge ark-infra' to apply this
infrastructure.
"NO_CONFIGCHECKS make dist-configs" to create the configs. And
away they go.
Utilize the daily rawhide_release builds to create this branch. It
fits with the theme and is quick and easy to do in this job. Note
I use the 'ark-latest' as the source of the export. This should
include any environment fixes for the developer.
Tested by copy-n-pasting manual each step in the script to generate
the original ark-infra branch. The gitlab-ci.yml change should be
intuitive enough to skip testing.
V2: Use git-archive and better sed regexp
V3: remove git reset and sed
V4: added comment about kabi-module (no new changes)
The workflow has recently changed such that all development is done
on the 'os-build' branch. Update the docs to show how easy it is
to make a change, commit it, generate the srpm and upload it to koji.
Also add it a build dep for making a srpm: patchutils (for filterdiff).
V2: Fix checkout command and setup master branch
V3: Use default upstream/master and git pull mechanism
V4: Use default origin/master. Add text to setup mirroring
Cc: Bastien Nocera <bnocera@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Justin Forbes <jforbes@redhat.com>
Signed-off-by: Don Zickus <dzickus@redhat.com>
In Makefile.common there is logic that determines what the
merge-base is and is used to generate changelogs correctly.
The logic assumes a 'master' branch exists and is up to date.
However, the documentation recommends using 'upstream/master' to
keep everything up to date.
Let's sync the documentation and code and use upstream/master if
it exists otherwise, use 'master' as the fallback. If neither
exists error out.
Update redhat/genspec.sh to handle a different master too.
The 'error' out solves another problem when a master branch is not
defined not is 'upstream' used as recommended.
V2: change 'upstream' to 'origin' (Justin F.)
Signed-off-by: Don Zickus <dzickus@redhat.com>
Fedora's kernel build doesn't include the dccp net protocol modules.
(CONFIG_IP_DCCP is not set.) So remove dccp from "netprots".
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Fedora's kernel build doesn't include the aic94xx scsi module.
(CONFIG_SCSI_AIC94XX is not set.) So remove aic94xx from "scsidrvs".
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Fedora's kernel build doesn't include renesas ethernet modules. (Neither
CONFIG_ARCH_RENESAS nor CONFIG_COMPILE_TEST are set.) So remove renesas
from "ethdrvs".
The oki-semi ethernet module is only built as a builtin.
(CONFIG_NET_VENDOR_OKI=y.) So remove oki-semi from "ethdrvs" too.
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Fedora's kernel build doesn't include isdn modules anymore. (CONFIG_ISDN
is not set.) So remove isdn from "driverdirs".
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
There are a number of incorrect entries in the various lists used to
filter modules into modules-extra:
8 directories that have been removed upstream, because their
drivers have been dropped:
drivers/fmc
drivers/net/ethernet/icplus
drivers/net/irda
drivers/scsi/mpt2sas
drivers/usb/wusbcore
drivers/uwb
fs/ncpfs
net/irda
1 directory that has been renamed upstream (to .../tiny):
drivers/gpu/drm/tinydrm
3 directories that are actually modules:
drivers/gpu/drm/sun4i-drm-hdmi
drivers/scsi/advansys
drivers/scsi/wd719x
Update the filter lists accordingly.
(Note that sun4i-drm-hdmi is already filtered through
"drivers/gpu/drm/sun4i/" and that advansys and wd719x could be added to
the singlemods list, if that is still desirable.)
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
There are some pointless modules in the singlemods lists:
hwa-hc, iw_cxgb3, and cxgb3i_ddp have been removed from the kernel
iw_cxgb4 is already filtered out (by drivers/infiniband)
cxgb3i and cxgb4i are also filtered out (by drivers/scsi/cxgbi)
chtls is also filtered out (by drivers/net/ethernet/chelsio)
Remove these modules from these lists.
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Currently rhel builds are failing due to a depmod on scftorture which
expects torture.o which is being filtered into the internals package.
Signed-off-by: Nico Pache <npache@redhat.com>
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_CRYPTO_SM2:
Generic implementation of the SM2 public key algorithm. It was
published by State Encryption Management Bureau, China.
as specified by OSCCA GM/T 0003.1-2012 -- 0003.5-2012.
References:
https://tools.ietf.org/html/draft-shen-sm2-ecdsa-02http://www.oscca.gov.cn/sca/xxgk/2010-12/17/content_1002386.shtmlhttp://www.gmbz.org.cn/main/bzlb.html
Symbol: CRYPTO_SM2 [=n]
Type : tristate
Defined at crypto/Kconfig:263
Prompt: SM2 algorithm
Depends on: CRYPTO [=y]
Location:
-> Cryptographic API (CRYPTO [=y])
Selects: CRYPTO_SM3 [=n] && CRYPTO_AKCIPHER [=y] && CRYPTO_MANAGER [=y] && MPILIB [=y] && ASN1 [=y]
---
CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE:
Allow obsolete cryptographic algorithms to be selected that have
already been phased out from internal use by the kernel, and are
only useful for userspace clients that still rely on them.
Symbol: CRYPTO_USER_API_ENABLE_OBSOLETE [=y]
Type : bool
Defined at crypto/Kconfig:1915
Prompt: Enable obsolete cryptographic algorithms for userspace
Depends on: CRYPTO [=y] && CRYPTO_USER_API [=y]
Location:
-> Cryptographic API (CRYPTO [=y])
---
CONFIG_CRYPTO_USER_API_RNG_CAVP:
This option enables extra API for CAVP testing via the user-space
interface: resetting of DRBG entropy, and providing Additional Data.
This should only be enabled for CAVP testing. You should say
no unless you know what this is.
Symbol: CRYPTO_USER_API_RNG_CAVP [=n]
Type : bool
Defined at crypto/Kconfig:1895
Prompt: Enable CAVP testing of DRBG
Depends on: CRYPTO [=y] && CRYPTO_USER_API_RNG [=y] && CRYPTO_DRBG [=y]
Location:
-> Cryptographic API (CRYPTO [=y])
-> User-space interface for random number generator algorithms (CRYPTO_USER_API_RNG [=y])
---
Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v4:
- CONFIG_CRYPTO_SM4_ARM64_CE removed from fedora configs.
v3:
- CONFIG_CRYPTO_SM4 is set m.
- CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE not defined for s390x/zfsdump.
- CONFIG_CRYPTO_SM2,3,4 set to y for s390x/zfsdump.
v2:
- CONFIG_CRYPTO_SM3=m is set.
- CONFIG_CRYPTO_SM4 and CONFIG_CRYPTO_SM4_ARM64_CE are NOT set; they are left
enabled as modules in fedora.
- CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE and
CONFIG_CRYPTO_{ANUBIS,ARC4,KHAZAD,SEED,TEA} are disabled everywhere EXCEPT
they are all still enabled for s390x/zfcpdump.
- CONFIG_CRYPTO_USER_API_RNG_CAVP is disabled everywhere.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
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_VDPA:
This driver provides support for virtio based paravirtual
device driver over vDPA bus. For this to be useful, you need
an appropriate vDPA device implementation that operates on a
physical device to allow the datapath of virtio to be
offloaded to hardware.
If unsure, say M.
Symbol: VIRTIO_VDPA [=n]
Type : tristate
Defined at drivers/virtio/Kconfig:46
Prompt: vDPA driver for virtio devices
Depends on: VIRTIO_MENU [=y]
Location:
-> Device Drivers
-> Virtio drivers (VIRTIO_MENU [=y])
Selects: VDPA [=n] && VIRTIO [=y]
Enabled at the request of Michael S. Tsirkin. Disabled on zfcpdump as it
seems unnecessary and introduces a number of dependencies.
---
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
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_VHOST_VDPA:
This kernel module can be loaded in host kernel to accelerate
guest virtio devices with the vDPA-based backends.
To compile this driver as a module, choose M here: the module
will be called vhost_vdpa.
Symbol: VHOST_VDPA [=n]
Type : tristate
Defined at drivers/vhost/Kconfig:62
Prompt: Vhost driver for vDPA-based backend
Depends on: VHOST_MENU [=y] && EVENTFD [=y]
Location:
-> Device Drivers
-> VHOST drivers (VHOST_MENU [=y])
Selects: VHOST [=m] && VDPA [=n]
Enabled at the request of Michael S. Tsirkin. Disabled on zfcpdump as it
seems unnecessary.
---
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
ARM SMC configs in generic/aarch64/ are not in a proper location.
Move them to a proper one, namely, ark/generic/arm/aarch64/.
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
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_CHARGER_BQ25980:
Say Y to enable support for the TI BQ25980, BQ25975 and BQ25960
series of fast battery chargers.
Symbol: CHARGER_BQ25980 [=n]
Type : tristate
Defined at drivers/power/supply/Kconfig:639
Prompt: TI BQ25980 battery charger driver
Depends on: POWER_SUPPLY [=y] && I2C [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Power supply class support (POWER_SUPPLY [=y])
Selects: REGMAP_I2C [=m]
---
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_VIDEO_IMX334:
This is a Video4Linux2 sensor driver for the Sony
IMX334 camera.
To compile this driver as a module, choose M here: the
module will be called imx334.
Symbol: VIDEO_IMX334 [=n]
Type : tristate
Defined at drivers/media/i2c/Kconfig:816
Prompt: Sony IMX334 sensor support
Depends on: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m]
Visible if: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
Location:
-> Device Drivers
-> Multimedia support (MEDIA_SUPPORT [=m])
-> Media ancillary drivers
-> Camera sensor devices
Selects: VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y] && V4L2_FWNODE [=n]
---
CONFIG_VIDEO_OV5648:
This is a Video4Linux2 sensor driver for the OmniVision
OV5648 camera.
To compile this driver as a module, choose M here: the
module will be called ov5648.
Symbol: VIDEO_OV5648 [=n]
Type : tristate
Defined at drivers/media/i2c/Kconfig:953
Prompt: OmniVision OV5648 sensor support
Depends on: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m]
Visible if: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
Location:
-> Device Drivers
-> Multimedia support (MEDIA_SUPPORT [=m])
-> Media ancillary drivers
-> Camera sensor devices
Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && V4L2_FWNODE [=n]
---
CONFIG_VIDEO_OV8865:
This is a Video4Linux2 sensor driver for OmniVision
OV8865 camera sensor.
To compile this driver as a module, choose M here: the
module will be called ov8865.
Symbol: VIDEO_OV8865 [=n]
Type : tristate
Defined at drivers/media/i2c/Kconfig:1078
Prompt: OmniVision OV8865 sensor support
Depends on: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m]
Visible if: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
Location:
-> Device Drivers
-> Multimedia support (MEDIA_SUPPORT [=m])
-> Media ancillary drivers
-> Camera sensor devices
Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && V4L2_FWNODE [=n]
---
CONFIG_VIDEO_RDACM21:
This driver supports the IMI RDACM21 GMSL camera, used in
ADAS systems.
This camera should be used in conjunction with a GMSL
deserialiser such as the MAX9286.
Symbol: VIDEO_RDACM21 [=n]
Type : tristate
Defined at drivers/media/i2c/Kconfig:1260
Prompt: IMI RDACM21 camera support
Depends on: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y]
Visible if: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y] && MEDIA_CAMERA_SUPPORT [=y]
Location:
-> Device Drivers
-> Multimedia support (MEDIA_SUPPORT [=m])
-> Media ancillary drivers
-> Camera sensor devices
Selects: V4L2_FWNODE [=n] && VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y] && VIDEO_MAX9271_LIB [=n]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_CHARGER_BQ256XX:
Say Y to enable support for the TI BQ256XX battery chargers. The
BQ256XX family of devices are highly-integrated, switch-mode battery
charge management and system power path management devices for single
cell Li-ion and Li-polymer batteries.
Symbol: CHARGER_BQ256XX [=n]
Type : tristate
Defined at drivers/power/supply/Kconfig:658
Prompt: TI BQ256XX battery charger driver
Depends on: POWER_SUPPLY [=y] && I2C [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Power supply class support (POWER_SUPPLY [=y])
Selects: REGMAP_I2C [=m]
---
CONFIG_CHARGER_LTC4162L:
Say Y to include support for the Analog Devices (Linear Technology)
LTC4162-L battery charger connected to I2C.
Symbol: CHARGER_LTC4162L [=n]
Type : tristate
Defined at drivers/power/supply/Kconfig:517
Prompt: LTC4162-L charger
Depends on: POWER_SUPPLY [=y] && I2C [=y]
Location:
-> Device Drivers
-> Power supply class support (POWER_SUPPLY [=y])
Selects: REGMAP_I2C [=m]
---
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_POWER_RESET_VEXPRESS:
Power off and reset support for the ARM Ltd. Versatile
Express boards.
Symbol: POWER_RESET_VEXPRESS [=n]
Type : bool
Defined at drivers/power/reset/Kconfig:184
Prompt: ARM Versatile Express power-off and reset driver
Depends on: POWER_RESET [=y] && (ARM || ARM64 [=y]) && VEXPRESS_CONFIG [=y]=y
Location:
-> Device Drivers
-> Board level reset or power off (POWER_RESET [=y])
Cc: Lenny Szubowicz <lszubowi@redhat.com>
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_NVMEM_RMEM:
This driver maps reserved memory into an nvmem device. It might be
useful to expose information left by firmware in memory.
This driver can also be built as a module. If so, the module
will be called nvmem-rmem.
Symbol: NVMEM_RMEM [=n]
Type : tristate
Defined at drivers/nvmem/Kconfig:273
Prompt: Reserved Memory Based Driver Support
Depends on: NVMEM [=y]
Location:
-> Device Drivers
-> NVMEM Support (NVMEM [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_FUSE_DAX:
This allows bypassing guest page cache and allows mapping host page
cache directly in guest address space.
If you want to allow mounting a Virtio Filesystem with the "dax"
option, answer Y.
Symbol: FUSE_DAX [=y]
Type : bool
Defined at fs/fuse/Kconfig:42
Prompt: Virtio Filesystem Direct Host Memory Access support
Depends on: VIRTIO_FS [=m] && FS_DAX [=y] && DAX_DRIVER [=y]
Location:
-> File systems
-> FUSE (Filesystem in Userspace) support (FUSE_FS [=m])
-> Virtio Filesystem (VIRTIO_FS [=m])
Selects: INTERVAL_TREE [=y]
---
Cc: Miklos Szeredi <mszeredi@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_USB4_DEBUGFS_WRITE:
Enables writing to device configuration registers through
debugfs interface.
Only enable this if you know what you are doing! Never enable
this for production systems or distro kernels.
Symbol: USB4_DEBUGFS_WRITE [=n]
Type : bool
Defined at drivers/thunderbolt/Kconfig:21
Prompt: Enable write by debugfs to configuration spaces (DANGEROUS)
Depends on: USB4 [=y]
Location:
-> Device Drivers
-> Unified support for USB4 and Thunderbolt (USB4 [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_QCOM_OCMEM:
The On Chip Memory (OCMEM) allocator allows various clients to
allocate memory from OCMEM based on performance, latency and power
requirements. This is typically used by the GPU, camera/video, and
audio components on some Snapdragon SoCs.
Symbol: QCOM_OCMEM [=n]
Type : tristate
Prompt: Qualcomm On Chip Memory (OCMEM) driver
Location:
-> Device Drivers
-> SOC (System On Chip) specific Drivers
-> Qualcomm SoC drivers
Defined at drivers/soc/qcom/Kconfig:69
Depends on: ARCH_QCOM [=y]
Selects: QCOM_SCM [=n]
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_HID_PLAYSTATION:
Provides support for Sony PS5 controllers including support for
its special functionalities e.g. touchpad, lights and motion
sensors.
Symbol: HID_PLAYSTATION [=n]
Type : tristate
Defined at drivers/hid/Kconfig:856
Prompt: PlayStation HID Driver
Depends on: INPUT [=y] && HID [=y]
Location:
-> Device Drivers
-> HID support
-> HID bus support (HID [=y])
-> Special HID drivers
Selects: CRC32 [=y] && POWER_SUPPLY [=y]
---
CONFIG_I2C_HID_ACPI:
Say Y here if you use a keyboard, a touchpad, a touchscreen, or any
other HID based devices which is connected to your computer via I2C.
This driver supports ACPI-based systems.
If unsure, say N.
This support is also available as a module. If so, the module
will be called i2c-hid-acpi. It will also build/depend on the
module i2c-hid.
Symbol: I2C_HID_ACPI [=n]
Type : tristate
Defined at drivers/hid/i2c-hid/Kconfig:5
Prompt: HID over I2C transport layer ACPI driver
Depends on: I2C [=y] && INPUT [=y] && ACPI [=y]
Location:
-> Device Drivers
-> HID support
-> I2C HID support
---
CONFIG_I2C_HID_OF:
Say Y here if you use a keyboard, a touchpad, a touchscreen, or any
other HID based devices which is connected to your computer via I2C.
This driver supports Open Firmware (Device Tree)-based systems.
If unsure, say N.
This support is also available as a module. If so, the module
will be called i2c-hid-of. It will also build/depend on the
module i2c-hid.
Symbol: I2C_HID_OF [=n]
Type : tristate
Defined at drivers/hid/i2c-hid/Kconfig:20
Prompt: HID over I2C transport layer Open Firmware driver
Depends on: I2C [=y] && INPUT [=y] && OF [=y]
Location:
-> Device Drivers
-> HID support
-> I2C HID support
---
CONFIG_I2C_HID_OF_GOODIX:
Say Y here if you want support for Goodix i2c devices that use
the i2c-hid protocol on Open Firmware (Device Tree)-based
systems.
If unsure, say N.
This support is also available as a module. If so, the module
will be called i2c-hid-of-goodix. It will also build/depend on
the module i2c-hid.
Symbol: I2C_HID_OF_GOODIX [=n]
Type : tristate
Defined at drivers/hid/i2c-hid/Kconfig:35
Prompt: Driver for Goodix hid-i2c based devices on OF systems
Depends on: I2C [=y] && INPUT [=y] && OF [=y]
Location:
-> Device Drivers
-> HID support
-> I2C HID support
---
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
v2:
- CONFIG_HID_PLAYSTATION changed to m.
- CONFIG_PLAYSTATION_FF set to y.
- CONFIG_I2C_HID_ACPI changed to m.
- CONFIG_I2C_HID_OF set to m for aarch64.
- CONFIG_I2C_HID_OF_GOODIX set to m for aarch64.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
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_CSD_LOCK_WAIT_DEBUG:
This option enables debug prints when CPUs are slow to respond
to the smp_call_function*() IPI wrappers. These debug prints
include the IPI handler function currently executing (if any)
and relevant stack traces.
Symbol: CSD_LOCK_WAIT_DEBUG [=n]
Type : bool
Defined at lib/Kconfig.debug:1380
Prompt: Debugging for csd_lock_wait(), called from smp_call_function*()
Depends on: DEBUG_KERNEL [=y] && 64BIT [=y]
Location:
-> Kernel hacking
-> Lock Debugging (spinlocks, mutexes, etc...)
---
CONFIG_SCF_TORTURE_TEST:
This option provides a kernel module that runs torture tests
on the smp_call_function() family of primitives. The kernel
module may be built after the fact on the running kernel to
be tested, if desired.
Symbol: SCF_TORTURE_TEST [=n]
Type : tristate
Defined at lib/Kconfig.debug:1370
Prompt: torture tests for smp_call_function*()
Depends on: DEBUG_KERNEL [=y]
Location:
-> Kernel hacking
-> Lock Debugging (spinlocks, mutexes, etc...)
Selects: TORTURE_TEST [=n]
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Fix a copy/paste error of 'input' and use the obviously intended 'char'.
The effect of this fix is that the cm4000_cs, cm4040_cs and mwave
modules will now be shipped in Fedora's kernel-modules package, as was
apparently intended. Nothing should change for RHEL, which actually
doesn't build these modules.
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
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_SMC_WATCHDOG:
Say Y here to include support for a watchdog timer
implemented by the EL3 Secure Monitor on ARM platforms.
Requires firmware support.
To compile this driver as a module, choose M here: the
module will be called arm_smc_wdt.
Symbol: ARM_SMC_WATCHDOG [=n]
Type : tristate
Defined at drivers/watchdog/Kconfig:871
Prompt: ARM Secure Monitor Call based watchdog support
Depends on: WATCHDOG [=y] && (ARM || ARM64 [=y]) && OF [=y] && HAVE_ARM_SMCCC [=y]
Location:
-> Device Drivers
-> Watchdog Timer Support (WATCHDOG [=y])
Selects: WATCHDOG_CORE [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_VIDEO_IMX214:
This is a Video4Linux2 sensor driver for the Sony
IMX214 camera.
To compile this driver as a module, choose M here: the
module will be called imx214.
Symbol: VIDEO_IMX214 [=n]
Type : tristate
Defined at drivers/media/i2c/Kconfig:741
Prompt: Sony IMX214 sensor support
Depends on: MEDIA_SUPPORT [=m] && GPIOLIB [=y] && I2C [=y] && VIDEO_V4L2 [=m]
Visible if: MEDIA_SUPPORT [=m] && GPIOLIB [=y] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
Location:
-> Device Drivers
-> Multimedia support (MEDIA_SUPPORT [=m])
-> Media ancillary drivers
-> Camera sensor devices
Selects: V4L2_FWNODE [=n] && MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && REGMAP_I2C [=m]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_INPUT_DA7280_HAPTICS:
Say Y to enable support for the Dialog DA7280 haptics driver.
The haptics can be controlled by PWM or GPIO
with I2C communication.
To compile this driver as a module, choose M here: the
module will be called da7280.
Symbol: INPUT_DA7280_HAPTICS [=n]
Type : tristate
Defined at drivers/input/misc/Kconfig:623
Prompt: Dialog Semiconductor DA7280 haptics support
Depends on: !UML && INPUT_MISC [=y] && INPUT [=y] && I2C [=y]
Location:
-> Device Drivers
-> Input device support
-> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-> Miscellaneous devices (INPUT_MISC [=y])
Selects: REGMAP_I2C [=m]
---
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_LEDS_TRIGGER_TTY:
This allows LEDs to be controlled by activity on ttys which includes
serial devices like /dev/ttyS0.
When build as a module this driver will be called ledtrig-tty.
Symbol: LEDS_TRIGGER_TTY [=n]
Type : tristate
Defined at drivers/leds/trigger/Kconfig:147
Prompt: LED Trigger for TTY devices
Depends on: NEW_LEDS [=y] && LEDS_TRIGGERS [=y] && TTY [=y]
Location:
-> Device Drivers
-> LED Support (NEW_LEDS [=y])
-> LED Trigger support (LEDS_TRIGGERS [=y])
---
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_LITEX_SOC_CONTROLLER:
This option enables the SoC Controller Driver which verifies
LiteX CSR access and provides common litex_get_reg/litex_set_reg
accessors.
All drivers that use functions from litex.h must depend on
LITEX.
Symbol: LITEX_SOC_CONTROLLER [=n]
Type : tristate
Defined at drivers/soc/litex/Kconfig:8
Prompt: Enable LiteX SoC Controller driver
Depends on: OF [=y] || COMPILE_TEST [=n]
Location:
-> Device Drivers
-> SOC (System On Chip) specific Drivers
-> Enable LiteX SoC Builder specific drivers
Selects: LITEX [=n]
---
Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_CLK_GFM_LPASS_SM8250:
Support for the Glitch Free Mux (GFM) Low power audio
subsystem (LPASS) clocks found on SM8250 SoCs.
Symbol: CLK_GFM_LPASS_SM8250 [=n]
Type : tristate
Defined at drivers/clk/qcom/Kconfig:522
Prompt: SM8250 GFM LPASS Clocks
Depends on: COMMON_CLK [=y] && COMMON_CLK_QCOM [=y]
Location:
-> Device Drivers
-> Common Clock Framework (COMMON_CLK [=y])
-> Support for Qualcomm's clock controllers (COMMON_CLK_QCOM [=y])
---
CONFIG_COMMON_CLK_FSL_FLEXSPI:
On Layerscape SoCs there is a special clock for the FlexSPI
interface.
Symbol: COMMON_CLK_FSL_FLEXSPI [=n]
Type : tristate
Defined at drivers/clk/Kconfig:191
Prompt: Clock driver for FlexSPI on Layerscape SoCs
Depends on: COMMON_CLK [=y] && (ARCH_LAYERSCAPE [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Common Clock Framework (COMMON_CLK [=y])
---
CONFIG_SC_CAMCC_7180:
Support for the camera clock controller on Qualcomm Technologies, Inc
SC7180 devices.
Say Y if you want to support camera devices and functionality such as
capturing pictures.
Symbol: SC_CAMCC_7180 [=n]
Type : tristate
Defined at drivers/clk/qcom/Kconfig:293
Prompt: SC7180 Camera Clock Controller
Depends on: COMMON_CLK [=y] && COMMON_CLK_QCOM [=y]
Location:
-> Device Drivers
-> Common Clock Framework (COMMON_CLK [=y])
-> Support for Qualcomm's clock controllers (COMMON_CLK_QCOM [=y])
Selects: SC_GCC_7180 [=m]
---
CONFIG_SDX_GCC_55:
Support for the global clock controller on SDX55 devices.
Say Y if you want to use peripheral devices such as UART,
SPI, I2C, USB, SD/UFS, PCIe etc.
Symbol: SDX_GCC_55 [=n]
Type : tristate
Defined at drivers/clk/qcom/Kconfig:425
Prompt: SDX55 Global Clock Controller
Depends on: COMMON_CLK [=y] && COMMON_CLK_QCOM [=y]
Location:
-> Device Drivers
-> Common Clock Framework (COMMON_CLK [=y])
-> Support for Qualcomm's clock controllers (COMMON_CLK_QCOM [=y])
Selects: QCOM_GDSC [=y]
---
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
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_LEDS_LP50XX:
If you say yes here you get support for the Texas Instruments
LP5036, LP5030, LP5024, LP5018, LP5012 and LP5009 LED driver.
To compile this driver as a module, choose M here: the
module will be called leds-lp50xx.
Symbol: LEDS_LP50XX [=n]
Type : tristate
Defined at drivers/leds/Kconfig:398
Prompt: LED Support for TI LP5036/30/24/18/12/9 LED driver chip
Depends on: NEW_LEDS [=y] && LEDS_CLASS [=y] && REGMAP_I2C [=m] && (LEDS_CLASS_MULTICOLOR [=n] || !LEDS_CLASS_MULTICOLOR [=n])
Location:
-> Device Drivers
-> LED Support (NEW_LEDS [=y])
---
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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.
---
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_LEDS_AW2013:
This option enables support for the AW2013 3-channel
LED driver.
To compile this driver as a module, choose M here: the module
will be called leds-aw2013.
Symbol: LEDS_AW2013 [=n]
Type : tristate
Defined at drivers/leds/Kconfig:106
Prompt: LED support for Awinic AW2013
Depends on: NEW_LEDS [=y] && LEDS_CLASS [=y] && I2C [=y] && OF [=y]
Location:
-> Device Drivers
-> LED Support (NEW_LEDS [=y])
Cc: Tony Camuso <tcamuso@redhat.com>
This option was enabled in commit 1ec8c0f7827c, but it depends on
CONFIG_USB_XHCI_PLATFORM, which is only enabled on x86_64 and arm.
Signed-off-by: David Ward <david.ward@ll.mit.edu>
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_RMI4_F3A:
Say Y here if you want to add support for RMI4 function 3A.
Function 3A provides GPIO support for RMI4 devices. This includes
support for buttons on TouchPads and ClickPads.
Symbol: RMI4_F3A [=n]
Type : bool
Defined at drivers/input/rmi4/Kconfig:103
Prompt: RMI4 Function 3A (GPIO)
Depends on: !UML && INPUT [=y] && RMI4_CORE [=m]
Location:
-> Device Drivers
-> Input device support
-> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-> Synaptics RMI4 bus support (RMI4_CORE [=m])
---
CONFIG_TOUCHSCREEN_ZINITIX:
Say Y here if you have a touchscreen using Zinitix bt541,
or something similar enough.
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called zinitix.
Symbol: TOUCHSCREEN_ZINITIX [=n]
Type : tristate
Defined at drivers/input/touchscreen/Kconfig:1325
Prompt: Zinitix touchscreen support
Depends on: !UML && INPUT [=y] && INPUT_TOUCHSCREEN [=y] && I2C [=y]
Location:
-> Device Drivers
-> Input device support
-> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-> Touchscreens (INPUT_TOUCHSCREEN [=y])
---
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_LEDS_RT8515:
This option enables support for the Richtek RT8515 flash
and torch LEDs found on some mobile phones.
To compile this driver as a module, choose M here: the module
will be called leds-rt8515.
Symbol: LEDS_RT8515 [=n]
Type : tristate
Defined at drivers/leds/flash/Kconfig:5
Prompt: LED support for Richtek RT8515 flash/torch LED
Depends on: NEW_LEDS [=y] && LEDS_CLASS_FLASH [=m] && GPIOLIB [=y]
Location:
-> Device Drivers
-> LED Support (NEW_LEDS [=y])
---
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_LEDS_BLINK:
This option enables blink support for the leds class.
If unsure, say Y.
Symbol: LEDS_BLINK [=n]
Type : bool
Defined at drivers/leds/blink/Kconfig:1
Prompt: LED Blink support
Depends on: NEW_LEDS [=y] && LEDS_CLASS [=y]
Location:
-> Device Drivers
-> LED Support (NEW_LEDS [=y])
---
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
The CHARGER_GPIO is needed for the Pinebook Pro for the battery
fuel guage, probably other devices too.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Several of the options for mod-internal.list are now out of sync
with RHEL8. Adjust accordingly.
Cc: Waiman Long <longman@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Don Zickus <dzickus@redhat.com>
V2: rebase to latest
V3: Adjust CONFIG_NET_ACT_ options (Jiri B.)
V4: Update TORTURE_TEST configs (Waiman L.)
V5: Enable CONFIG_NET_ACT_{CTINFO|MPLS} to 'm' for Fedora (Jiri B.)
V6: Remove duplicate dmatest (Herton)
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1613522
Upstream: RHEL only
Enable CONFIG_WIREGUARD as requested in the bugzilla. Configs
CONFIG_CRYPTO_LIB_BLAKE2S, CONFIG_CRYPTO_LIB_CHACHA20POLY1305,
CONFIG_CRYPTO_LIB_CURVE25519 are needed by wireguard.
Remove the fedora specific configs and enable them in common folder.
Do not enable it on zfcpdump as it has "#CONFIG_INET is not set".
Disabling wireguard in FIPS mode will be fixed in another bug.
Signed-off-by: Hangbin Liu <haliu@redhat.com>
Started with a bunch of scripts to filter out duplicates. Then
ran into all the override quirks and quickly and to revert large
chunks of it.
What is left is duplicates and cleanups of a small set of configs.
The SPEAKUP stuff seemed easy to consolidate.
The DW_DMAC_* configs were tricky because I could not delete the Fedora
overrides.
The EXPOLINE_* configs are s390x specific and with a little manual
cleanup made it work.
The HOTPLUG_PCI_SHPC had some override quirks but a few tweaks I can
easily sync everything up.
One new exposure is TEST_MIN_HEAP is now enabled on fedora-debug. I
think that was the original intent but the feodra override accidentally
disabled it from common.
Verified by comparing the original 'make dist-configs; make
dist-fedora-configs' with the new version. Other than TEST_MIN_HEAP
everything else matches.
This whole exercise made me frown with how the common configs and the
overrides work. Maybe evaluate_configs -j isn't so bad after all...
Signed-off-by: Don Zickus <dzickus@redhat.com>
Fedora already disables parport on non x86 platforms, ark disabled
it in aarch64/s390x by random explicit disabled. Cleanup and unify
this by disabling it in common/generic and just enabling it for x86
with a single common config as the outcome was the same everywhere.
This makes the config more explicit and easier to see what is
enabled/disabled where.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1918888
The coresight tables on the latest Apollo 70, appear to be
damaged sufficiently to throw a few hundred lines of back-traces
during boot, lets disable it until we can get a firmware fix.
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
cc: Peter Robinson <pbrobinson@redhat.com>
cc: Justin M. Forbes <jforbes@fedoraproject.org>
cc: Al Stone <ahs3@redhat.com>
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_ARM64_BTI:
Branch Target Identification (part of the ARMv8.5 Extensions)
provides a mechanism to limit the set of locations to which computed
branch instructions such as BR or BLR can jump.
To make use of BTI on CPUs that support it, say Y.
BTI is intended to provide complementary protection to other control
flow integrity protection mechanisms, such as the Pointer
authentication mechanism provided as part of the ARMv8.3 Extensions.
For this reason, it does not make sense to enable this option without
also enabling support for pointer authentication. Thus, when
enabling this option you should also select ARM64_PTR_AUTH=y.
Userspace binaries must also be specifically compiled to make use of
this mechanism. If you say N here or the hardware does not support
BTI, such binaries can still run, but you get no additional
enforcement of branch destinations.
Symbol: ARM64_BTI [=y]
Type : bool
Defined at arch/arm64/Kconfig:1594
Prompt: Branch Target Identification support
Location:
-> Kernel Features
-> ARMv8.5 architectural features
---
Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: CKI@GitLab <cki-project@redhat.com>
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_SURFACE_HOTPLUG:
Driver for out-of-band hot-plug event signaling on Microsoft Surface
devices with hot-pluggable PCIe cards.
This driver is used on Surface Book (2 and 3) devices with a
hot-pluggable discrete GPU (dGPU). When not in use, the dGPU on those
devices can enter D3cold, which prevents in-band (standard) PCIe
hot-plug signaling. Thus, without this driver, detaching the base
containing the dGPU will not correctly update the state of the
corresponding PCIe device if it is in D3cold. This driver adds support
for out-of-band hot-plug notifications, ensuring that the device state
is properly updated even when the device in question is in D3cold.
Select M or Y here, if you want to (fully) support hot-plugging of
dGPU devices on the Surface Book 2 and/or 3 during D3cold.
Symbol: SURFACE_HOTPLUG [=n]
Type : tristate
Defined at drivers/platform/surface/Kconfig:89
Prompt: Surface Hot-Plug Driver
Depends on: SURFACE_PLATFORMS [=y] && GPIOLIB [=y]
Location:
-> Device Drivers
-> Microsoft Surface Platform-Specific Device Drivers (SURFACE_PLATFORMS [=y])
---
CONFIG_X86_PLATFORM_DRIVERS_DELL:
Say Y here to get to see options for device drivers for various
Dell x86 platforms, including vendor-specific laptop extension drivers.
This option alone does not add any kernel code.
If you say N, all options in this submenu will be skipped and disabled.
Symbol: X86_PLATFORM_DRIVERS_DELL [=n]
Type : bool
Defined at drivers/platform/x86/dell/Kconfig:6
Prompt: Dell X86 Platform Specific Device Drivers
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
---
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
This is desired to reduce the risk of kernel heap overflows
being able to overwrite objects from merged caches, and it
changes the requirements for cache layout control, increasing
the difficulty of these attacks.
It also in increases the reliability and protection against
object data corruption due to use-after-free and double-free
class of bugs, as by keeping caches unmerged, these kinds of
issues can only damage objects in the same cache.
CONFIG_SLAB_MERGE_DEFAULT=n has been the default setting
since RHEL-8
Signed-off-by: Rafael Aquini <aquini@redhat.com>
An rpm define _legacy_common_support was added to as a short term
workaround for gcc10 issues with upstream projects. As upstream is now
fixed for gcc10, this is no longer required. This has been tested with
scratch builds against gcc10 in F33 and gcc11 in rawhide.
Resolves kernel-ark issue 21.
Signed-off-by: Justin M. Forbes <jforbes@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_PPC_RTAS_FILTER:
The RTAS syscall API has security issues that could be used to
compromise system integrity. This option enforces restrictions on the
RTAS calls and arguments passed by userspace programs to mitigate
these issues.
Say Y unless you know what you are doing and the filter is causing
problems for you.
Symbol: PPC_RTAS_FILTER [=y]
Type : bool
Defined at arch/powerpc/Kconfig:991
Prompt: Enable filtering of RTAS syscalls
Depends on: PPC_RTAS [=y]
Location:
-> Kernel options
---
Cc: kernel-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@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_NVIDIA_CARMEL_CNP_ERRATUM:
If CNP is enabled on Carmel cores, non-sharable TLBIs on a core will not
invalidate shared TLB entries installed by a different core, as it would
on standard ARM cores.
If unsure, say Y.
Symbol: NVIDIA_CARMEL_CNP_ERRATUM [=y]
Type : bool
Defined at arch/arm64/Kconfig:813
Prompt: NVIDIA Carmel CNP: CNP on Carmel semantically different than ARM cores
Location:
-> Kernel Features
-> ARM errata workarounds via the alternatives framework
---
Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_TMPFS_INODE64:
tmpfs has historically used only inode numbers as wide as an unsigned
int. In some cases this can cause wraparound, potentially resulting
in multiple files with the same inode number on a single device. This
option makes tmpfs use the full width of ino_t by default, without
needing to specify the inode64 option when mounting.
But if a long-lived tmpfs is to be accessed by 32-bit applications so
ancient that opening a file larger than 2GiB fails with EINVAL, then
the INODE64 config option and inode64 mount option risk operations
failing with EOVERFLOW once 33-bit inode numbers are reached.
To override this configured default, use the inode32 or inode64
option when mounting.
If unsure, say N.
Symbol: TMPFS_INODE64 [=n]
Type : bool
Defined at fs/Kconfig:204
Prompt: Use 64-bit ino_t by default in tmpfs
Depends on: TMPFS [=y] && 64BIT [=y]
Location:
-> File systems
-> Pseudo filesystems
-> Tmpfs virtual memory file system support (former shm fs) (TMPFS [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
The modules in the kernel-modules-extra sub-packages are no longer
added to a separate /lib/modules/$(uname -r)/extra dir, instead
they are now installed in the standard /lib/modules/$(uname -r)/kernel
dir.
Adjust the floppy module blacklisting in mod-blacklist.sh accordingly
fixing the floppy module no longer being blacklisted by default.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1789155
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
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_KGDB_HONOUR_BLOCKLIST:
If set to Y the debug core will use the kprobe blocklist to
identify symbols where it is unsafe to set breakpoints.
In particular this disallows instrumentation of functions
called during debug trap handling and thus makes it very
difficult to inadvertently provoke recursive trap handling.
If unsure, say Y.
Symbol: KGDB_HONOUR_BLOCKLIST [=y]
Type : bool
Defined at lib/Kconfig.kgdb:27
Prompt: KGDB: use kprobe blocklist to prohibit unsafe breakpoints
Depends on: KGDB [=y] && HAVE_KPROBES [=y] && MODULES [=y]
Location:
-> Kernel hacking
-> Generic Kernel Debugging Instruments
-> KGDB: kernel debugger (KGDB [=y])
Selects: KPROBES [=y]
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_FAULT_INJECTION_USERCOPY:
Provides fault-injection capability to inject failures
in usercopy functions (copy_from_user(), get_user(), ...).
Symbol: FAULT_INJECTION_USERCOPY [=n]
Type : bool
Defined at lib/Kconfig.debug:1771
Prompt: Fault injection capability for usercopy functions
Depends on: FAULT_INJECTION [=y]
Location:
-> Kernel hacking
-> Kernel Testing and Coverage
-> Fault-injection framework (FAULT_INJECTION [=y])
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_DEBUG_IRQFLAGS:
Enables checks for potentially unsafe enabling or disabling of
interrupts, such as calling raw_local_irq_restore() when interrupts
are enabled.
Symbol: DEBUG_IRQFLAGS [=n]
Type : bool
Defined at lib/Kconfig.debug:1427
Prompt: Debug IRQ flag manipulation
Location:
-> Kernel hacking
Selected by [n]:
- DEBUG_LOCKDEP [=n] && DEBUG_KERNEL [=y] && LOCKDEP [=n]
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_PSTORE_BLK:
This enables panic and oops message to be logged to a block dev
where it can be read back at some later point.
For more information, see Documentation/admin-guide/pstore-blk.rst
If unsure, say N.
Symbol: PSTORE_BLK [=n]
Type : tristate
Defined at fs/pstore/Kconfig:164
Prompt: Log panic/oops to a block device
Depends on: MISC_FILESYSTEMS [=y] && PSTORE [=y] && BLOCK [=y]
Location:
-> File systems
-> Miscellaneous filesystems (MISC_FILESYSTEMS [=y])
-> Persistent store support (PSTORE [=y])
Selects: PSTORE_ZONE [=n]
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: Al Stone <ahs3@redhat.com>
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_PPC_PROT_SAO_LPAR:
This option adds support for PROT_SAO mappings from userspace
inside LPARs on supported CPUs.
This may cause issues when performing guest migration from
a CPU that supports SAO to one that does not.
If unsure, say N here.
Symbol: PPC_PROT_SAO_LPAR [=n]
Type : bool
Defined at arch/powerpc/Kconfig:863
Prompt: Support PROT_SAO mappings in LPARs
Depends on: PPC_BOOK3S_64 [=y]
Location:
-> Kernel options
Cc: kernel-patches@redhat.com
We are going to want to enable BPF LSM in RHEL, so start building it on
ARK and update the default LSM list so that it is enabled on boot by
default (to enable testing). It should have almost no performance impact
unless userspace attaches some BPF programs to the hooks. Users can
still completely turn it off by adding lsm="yama,integrity,selinux" to
the kernel command line.
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
1. Set CONFIG_SECURITY_LOCKDOWN_LSM=y on both Fedora and ARK and move
the associated configs from fedora/ to common/. On both this is
required for proper UEFI secure boot support.
2. Remove ark/generic/CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE - this
config has been removed upstream.
3. Deduplicate default value of CONFIG_LSM_MMAP_MIN_ADDR - set it to
65536 under common/ and only override it in
fedora/generic/arm/armv7/.
4. Trim LSMs that are not build-enabled from CONFIG_LSM on Fedora/ARK,
which can now be unified under common/.
Note that this commit adds the Lockdown LSM to the default LSM list and
therefore effectively enables it on both Fedora (where it was enabled in
build, but disabled on boot) and ARK (where it wasn't even enabled at
build). According to Peter Robinson and Al Stone it should be enabled,
so hopefully this is the expected result.
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
Currently CRYPTO_CHACHA20* and CRYPTO_*POLY1305* configs are not in order.
Unify them by merging and moving to configs/common/. Also enable CRYPTO_
CHACHA20POLY1305 on PowerPC as it was done in rhbz#1734711.
Detailed actions taken:
Move:
configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20:CONFIG_CRYPTO_CHACHA20=y
configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305:CONFIG_CRYPTO_POLY1305=y
configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305:CONFIG_CRYPTO_CHACHA20POLY1305=y
to
configs/common/generic/s390x/zfcpdump/
Delete (per rhbz#1734711):
configs/ark/generic/powerpc/CONFIG_CRYPTO_CHACHA20POLY1305:# CONFIG_CRYPTO_CHACHA20POLY1305 is not set
Delete: configs/pending-common/generic/CONFIG_CRYPTO_POLY1305_NEON:# CONFIG_CRYPTO_POLY1305_NEON is not set
And move:
configs/fedora/generic/arm/aarch64/CONFIG_CRYPTO_POLY1305_NEON:CONFIG_CRYPTO_POLY1305_NEON=m
to:
configs/common/generic/arm/aarch64/CONFIG_CRYPTO_POLY1305_NEON
Merge:
configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_NEON:CONFIG_CRYPTO_NHPOLY1305_NEON=m
configs/fedora/generic/arm/CONFIG_CRYPTO_NHPOLY1305_NEON:CONFIG_CRYPTO_NHPOLY1305_NEON=m
to:
configs/common/generic/arm/CONFIG_CRYPTO_NHPOLY1305_NEON
Merge:
configs/ark/generic/CONFIG_CRYPTO_CHACHA20_NEON:CONFIG_CRYPTO_CHACHA20_NEON=m
configs/fedora/generic/arm/CONFIG_CRYPTO_CHACHA20_NEON:CONFIG_CRYPTO_CHACHA20_NEON=m
to:
configs/common/generic/arm/CONFIG_CRYPTO_CHACHA20_NEON
Merge:
configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_AVX2:CONFIG_CRYPTO_NHPOLY1305_AVX2=m
configs/fedora/generic/x86/CONFIG_CRYPTO_NHPOLY1305_AVX2:CONFIG_CRYPTO_NHPOLY1305_AVX2=m
to (depends on X86 && 64BIT):
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_AVX2
Merge:
configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_SSE2:CONFIG_CRYPTO_NHPOLY1305_SSE2=m
configs/fedora/generic/x86/CONFIG_CRYPTO_NHPOLY1305_SSE2:CONFIG_CRYPTO_NHPOLY1305_SSE2=m
to (depends on X86 && 64BIT):
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_SSE2
The result:
$ git grep -e CRYPTO_CHACHA20 -e CRYPTO_POLY1305 -e CRYPTO_NHPOLY1305
configs/common/generic/CONFIG_CRYPTO_CHACHA20:CONFIG_CRYPTO_CHACHA20=m
configs/common/generic/CONFIG_CRYPTO_CHACHA20POLY1305:CONFIG_CRYPTO_CHACHA20POLY1305=m
configs/common/generic/CONFIG_CRYPTO_POLY1305:CONFIG_CRYPTO_POLY1305=m
configs/common/generic/arm/CONFIG_CRYPTO_CHACHA20_NEON:CONFIG_CRYPTO_CHACHA20_NEON=m
configs/common/generic/arm/CONFIG_CRYPTO_NHPOLY1305_NEON:CONFIG_CRYPTO_NHPOLY1305_NEON=m
configs/common/generic/arm/aarch64/CONFIG_CRYPTO_POLY1305_NEON:CONFIG_CRYPTO_POLY1305_NEON=m
configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20:CONFIG_CRYPTO_CHACHA20=y
configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305:CONFIG_CRYPTO_CHACHA20POLY1305=y
configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305:CONFIG_CRYPTO_POLY1305=y
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_CHACHA20_X86_64:CONFIG_CRYPTO_CHACHA20_X86_64=m
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_AVX2:CONFIG_CRYPTO_NHPOLY1305_AVX2=m
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_SSE2:CONFIG_CRYPTO_NHPOLY1305_SSE2=m
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_POLY1305_X86_64:CONFIG_CRYPTO_POLY1305_X86_64=m
configs/fedora/generic/arm/armv7/CONFIG_CRYPTO_POLY1305_ARM:CONFIG_CRYPTO_POLY1305_ARM=m
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
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_XFS_SUPPORT_V4:
The V4 filesystem format lacks certain features that are supported
by the V5 format, such as metadata checksumming, strengthened
metadata verification, and the ability to store timestamps past the
year 2038. Because of this, the V4 format is deprecated. All users
should upgrade by backing up their files, reformatting, and restoring
from the backup.
Administrators and users can detect a V4 filesystem by running
xfs_info against a filesystem mountpoint and checking for a string
beginning with "crc=". If the string "crc=0" is found, the
filesystem is a V4 filesystem. If no such string is found, please
upgrade xfsprogs to the latest version and try again.
This option will become default N in September 2025. Support for the
V4 format will be removed entirely in September 2030. Distributors
can say N here to withdraw support earlier.
To continue supporting the old V4 format (crc=0), say Y.
To close off an attack surface, say N.
Symbol: XFS_SUPPORT_V4 [=y]
Type : bool
Defined at fs/xfs/Kconfig:25
Prompt: Support deprecated V4 (crc=0) format
Depends on: BLOCK [=y] && XFS_FS [=m]
Location:
-> File systems
-> XFS filesystem support (XFS_FS [=m])
---
Cc: Brian Foster <bfoster@redhat.com>
Cc: Carlos Maiolino <cmaiolin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_INTEL_SCU_PCI:
This driver is used to bridge the communications between kernel
and SCU on some embedded Intel x86 platforms. It also creates
devices that are connected to the SoC through the SCU.
Platforms supported:
Medfield
Clovertrail
Merrifield
Broxton
Apollo Lake
Symbol: INTEL_SCU_PCI [=n]
Type : bool
Defined at drivers/platform/x86/Kconfig:1354
Prompt: Intel SCU PCI driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && PCI [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
Selects: INTEL_SCU [=n]
Selected by [n]:
- X86_INTEL_MID [=n] && X86_EXTENDED_PLATFORM [=y] && X86_PLATFORM_DEVICES [=y] && PCI [=y] && (X86_64 [=y] || PCI_GOANY [=n] && X86_32 [=n]) && X86_IO_APIC [=y]
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
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_EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER:
Select this config option to add support for the initrd= command
line parameter, allowing an initrd that resides on the same volume
as the kernel image to be loaded into memory.
This method is deprecated.
Symbol: EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER [=y]
Type : bool
Defined at drivers/firmware/efi/Kconfig:127
Prompt: Enable the command line initrd loader
Depends on: EFI [=y] && EFI_STUB [=y] && (EFI_GENERIC_STUB [=y] || X86)
Visible if: EFI [=y] && EFI_STUB [=y] && (EFI_GENERIC_STUB [=y] || X86) && !X86
Location:
-> Firmware Drivers
-> EFI (Extensible Firmware Interface) Support
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
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_SND_SOC_INTEL_CATPT:
Enable support for Intel(R) Haswell and Broadwell platforms
with I2S codec present. This is a recommended option.
Say Y or m if you have such device.
If unsure, say N.
Symbol: SND_SOC_INTEL_CATPT [=n]
Type : tristate
Defined at sound/soc/intel/Kconfig:37
Prompt: Haswell and Broadwell
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_SST_TOPLEVEL [=y] && (ACPI [=y] || COMPILE_TEST [=n]) && DMADEVICES [=y] && SND_DMA_SGBUF [=y]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> Intel ASoC SST drivers (SND_SOC_INTEL_SST_TOPLEVEL [=y])
Selects: DW_DMAC_CORE [=y] && SND_SOC_ACPI_INTEL_MATCH [=m]
Selected by [n]:
- SND_SOC_INTEL_HASWELL [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_SST_TOPLEVEL [=y]
---
Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE:
Set Y to default enable DEBUGFS for SCSI_HISI_SAS
Symbol: SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE [=n]
Type : bool
Defined at drivers/scsi/hisi_sas/Kconfig:22
Prompt: HiSilicon SAS debugging default enable
Depends on: SCSI_LOWLEVEL [=y] && SCSI [=y] && SCSI_HISI_SAS [=m]
Location:
-> Device Drivers
-> SCSI device support
-> SCSI low-level drivers (SCSI_LOWLEVEL [=y])
-> HiSilicon SAS (SCSI_HISI_SAS [=m])
---
Cc: "Ewan D. Milne" <emilne@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_SERIAL_BCM63XX:
This enables the driver for the onchip UART core found on
the following chipsets:
BCM33xx (cable modem)
BCM63xx/BCM63xxx (DSL)
BCM68xx (PON)
BCM7xxx (STB) - DOCSIS console
Symbol: SERIAL_BCM63XX [=n]
Type : tristate
Defined at drivers/tty/serial/Kconfig:1117
Prompt: Broadcom BCM63xx/BCM33xx UART support
Depends on: TTY [=y] && HAS_IOMEM [=y] && COMMON_CLK [=y]
Location:
-> Device Drivers
-> Character devices
-> Enable TTY (TTY [=y])
-> Serial drivers
Selects: SERIAL_CORE [=y]
---
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_DMC620_PMU:
Support for PMU events monitoring on the ARM DMC-620 memory
controller.
Symbol: ARM_DMC620_PMU [=n]
Type : tristate
Defined at drivers/perf/Kconfig:133
Prompt: Enable PMU support for the ARM DMC-620 memory controller
Depends on: PERF_EVENTS [=y] && (ARM64 [=y] && ACPI [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Performance monitor support
---
Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_QCOM_IPCC:
Qualcomm Technologies, Inc. Inter-Processor Communication Controller
(IPCC) driver for MSM devices. The driver provides mailbox support for
sending interrupts to the clients. On the other hand, the driver also
acts as an interrupt controller for receiving interrupts from clients.
Say Y here if you want to build this driver.
Symbol: QCOM_IPCC [=n]
Type : bool
Defined at drivers/mailbox/Kconfig:247
Prompt: Qualcomm Technologies, Inc. IPCC driver
Depends on: MAILBOX [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Mailbox Hardware Support (MAILBOX [=y])
Cc: Al Stone <ahs3@redhat.com>
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_BCM54140_PHY:
Support the Broadcom BCM54140 Quad SGMII/QSGMII PHY.
This driver also supports the hardware monitoring of this PHY and
exposes voltage and temperature sensors.
Symbol: BCM54140_PHY [=n]
Type : tristate
Defined at drivers/net/phy/Kconfig:357
Prompt: Broadcom BCM54140 PHY
Depends on: NETDEVICES [=y] && PHYLIB [=y] && (HWMON [=y] || HWMON [=y]=n)
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> PHY Device support and infrastructure (PHYLIB [=y])
Selects: BCM_NET_PHYLIB [=m]
Cc: Petr Oros <poros@redhat.com>
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_GUP_TEST:
Provides /sys/kernel/debug/gup_test, which in turn provides a way
to make ioctl calls that can launch kernel-based unit tests for
the get_user_pages*() and pin_user_pages*() family of API calls.
These tests include benchmark testing of the _fast variants of
get_user_pages*() and pin_user_pages*(), as well as smoke tests of
the non-_fast variants.
There is also a sub-test that allows running dump_page() on any
of up to eight pages (selected by command line args) within the
range of user-space addresses. These pages are either pinned via
pin_user_pages*(), or pinned via get_user_pages*(), as specified
by other command line arguments.
See tools/testing/selftests/vm/gup_test.c
Symbol: GUP_TEST [=n]
Type : bool
Defined at mm/Kconfig:824
Prompt: Enable infrastructure for get_user_pages()-related unit tests
Depends on: DEBUG_FS [=y]
Location:
-> Memory Management options
---
Cc: Rafael Aquini <aquini@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_DM_MULTIPATH_IOA:
This path selector selects the path based on the CPU the IO is
executed on and the CPU to path mapping setup at path addition time.
If unsure, say N.
Symbol: DM_MULTIPATH_IOA [=n]
Type : tristate
Defined at drivers/md/Kconfig:466
Prompt: I/O Path Selector based on CPU submission
Depends on: MD [=y] && DM_MULTIPATH [=m]
Location:
-> Device Drivers
-> Multiple devices driver support (RAID and LVM) (MD [=y])
-> Device mapper support (BLK_DEV_DM [=m])
-> Multipath target (DM_MULTIPATH [=m])
---
Cc: Nigel Croxon <ncroxon@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_ZSMALLOC_PGTABLE_MAPPING:
By default, zsmalloc uses a copy-based object mapping method to
access allocations that span two pages. However, if a particular
architecture (ex, ARM) performs VM mapping faster than copying,
then you should select this. This causes zsmalloc to use page table
mapping rather than copying for object mapping.
You can check speed with zsmalloc benchmark:
https://github.com/spartacus06/zsmapbench
Symbol: ZSMALLOC_PGTABLE_MAPPING [=n]
Type : bool
Defined at mm/Kconfig:708
Prompt: Use page table mapping to access object in zsmalloc
Depends on: ZSMALLOC [=y]=y
Location:
-> Memory Management options
-> Memory allocator for compressed pages (ZSMALLOC [=y])
Cc: Rafael Aquini <aquini@redhat.com>
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_PMU_SYSFS:
This option enables sysfs file creation for PMU SPRs like MMCR* and PMC*.
Symbol: PMU_SYSFS [=n]
Type : bool
Defined at arch/powerpc/platforms/Kconfig.cputype:428
Prompt: Create PMU SPRs sysfs file
Location:
-> Processor support
Cc: kernel-patches@redhat.com
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_COMPAT:
Enable support for 32bit binaries
Symbol: COMPAT [=n]
Type : bool
Defined at arch/powerpc/Kconfig:268
Depends on: PPC64
Default: y if !CPU_LITTLE_ENDIAN
Selects: COMPAT_BINFMT_ELF
ARCH_WANT_OLD_COMPAT_IPC
COMPAT_OLD_SIGACTION
Cc: kernel-patches@redhat.com
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_INPUT_IQS269A:
Say Y to enable support for the Azoteq IQS269A capacitive
touch controller.
To compile this driver as a module, choose M here: the
module will be called iqs269a.
Symbol: INPUT_IQS269A [=n]
Type : tristate
Defined at drivers/input/misc/Kconfig:721
Prompt: Azoteq IQS269A capacitive touch controller
Depends on: !UML && INPUT [=y] && INPUT_MISC [=y] && I2C [=y]
Location:
-> Device Drivers
-> Input device support
-> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-> Miscellaneous devices (INPUT_MISC [=y])
Selects: REGMAP_I2C [=m]
Cc: Tony Camuso <tcamuso@redhat.com>
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_MLX5_CLS_ACT:
mlx5 ConnectX offloads support for TC classifier action (NET_CLS_ACT),
works in both native NIC mode and Switchdev SRIOV mode.
Actions get attached to a Hardware offloaded classifiers and are
invoked after a successful classification. Actions are used to
overwrite the classification result, instantly drop or redirect and/or
reformat packets in wire speeds without involving the host cpu.
If set to N, TC offloads in both NIC and switchdev modes will be disabled.
If unsure, set to Y
Symbol: MLX5_CLS_ACT [=y]
Type : bool
Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:81
Prompt: MLX5 TC classifier action support
Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_ESWITCH [=y] && NET_CLS_ACT [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Ethernet driver support (ETHERNET [=y])
-> Mellanox devices (NET_VENDOR_MELLANOX [=y])
-> Mellanox 5th generation network adapters (ConnectX series) Ethernet support (MLX5_CORE_EN [=y])
-> Mellanox Technologies MLX5 SRIOV E-Switch support (MLX5_ESWITCH [=y])
---
Signed-off-by: Justin M. Forbes <jforbes@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_BT_MSFTEXT:
This options enables support for the Microsoft defined HCI
vendor extensions.
Symbol: BT_MSFTEXT [=n]
Type : bool
Defined at net/bluetooth/Kconfig:96
Prompt: Enable Microsoft extensions
Depends on: NET [=y] && BT [=m]
Location:
-> Networking support (NET [=y])
-> Bluetooth subsystem support (BT [=m])
Cc: Gopal Tiwari <gtiwari@redhat.com>
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_ICST:
Supports clocking on ARM Reference designs:
- Integrator/AP and Integrator/CP
- RealView PB1176, EB, PB11MP and PBX
Symbol: ICST [=n]
Type : bool
Defined at drivers/clk/versatile/Kconfig:7
Prompt: Clock driver for ARM Reference designs ICST
Depends on: COMMON_CLK [=y] && (ARCH_INTEGRATOR || ARCH_REALVIEW || ARCH_VERSATILE || ARCH_VEXPRESS [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Common Clock Framework
-> Clock driver for ARM Reference designs
Selects: REGMAP_MMIO [=y]
Cc: Mark Salter <msalter@redhat.com>
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_WATCH_QUEUE:
This is a general notification queue for the kernel to pass events to
userspace by splicing them into pipes. It can be used in conjunction
with watches for key/keyring change notifications and device
notifications.
See Documentation/watch_queue.rst
Symbol: WATCH_QUEUE [=n]
Type : bool
Defined at init/Kconfig:370
Prompt: General notification queue
Location:
-> General setup
Cc: Prarit Bhargava <prarit@redhat.com>
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_HARDLOCKUP_DETECTOR:
Say Y here to enable the kernel to act as a watchdog to detect
hard lockups.
Hardlockups are bugs that cause the CPU to loop in kernel mode
for more than 10 seconds, without letting other interrupts have a
chance to run. The current stack trace is displayed upon detection
and the system will stay locked up.
Symbol: HARDLOCKUP_DETECTOR [=n]
Type : bool
Defined at lib/Kconfig.debug:1000
Prompt: Detect Hard Lockups
Depends on: DEBUG_KERNEL [=y] && !S390 && (HAVE_HARDLOCKUP_DETECTOR_PERF [=y] || HAVE_HARDLOCKUP_DETECTOR_ARCH [=n])
Location:
-> Kernel hacking
-> Debug Oops, Lockups and Hangs
Selects: LOCKUP_DETECTOR [=y] && HARDLOCKUP_DETECTOR_PERF [=n] && HARDLOCKUP_DETECTOR_ARCH
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
This option can be enabled by passing --with toolchain_clang to rpmbuild
or mock. Enabling this option will cause the kernel to be built with
clang instead of gcc.
Signed-off-by: Tom Stellard <tstellar@redhat.com>
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_PINCTRL_SC8180X:
This is the pinctrl, pinmux, pinconf and gpiolib driver for the
Qualcomm Technologies Inc TLMM block found on the Qualcomm
Technologies Inc SC8180x platform.
Symbol: PINCTRL_SC8180X [=n]
Type : tristate
Defined at drivers/pinctrl/qcom/Kconfig:223
Prompt: Qualcomm Technologies Inc SC8180x pin controller driver
Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINCTRL_MSM [=n]
---
CONFIG_PINCTRL_SM8350:
This is the pinctrl, pinmux, pinconf and gpiolib driver for the
Qualcomm Technologies Inc TLMM block found on the Qualcomm
Technologies Inc SM8350 platform.
Symbol: PINCTRL_SM8350 [=n]
Type : tristate
Defined at drivers/pinctrl/qcom/Kconfig:277
Prompt: Qualcomm Technologies Inc SM8350 pin controller driver
Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINCTRL_MSM [=n]
---
Cc: Brian Masney <bmasney@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Since the rename of all targets to dist-* targets, the specific config
target for RHEL configs do not work when called outside of the redhat directory:
the makefile filters only dist-% and distg-% targets, so it doesn't run against
redhat/Makefile and thus calling those targets do not work, unless you
cd into the redhat directory.
To allow running the specific config targets outside of redhat/
directory, we have two approaches: change makefile to accept those old
config targets, or create new ones starting with dist-*.
I chose the latter approach with this change: fedora-configs target
has a new dist-fedora-configs, while rh-configs target can now be
called as dist-rhel-configs. I also removed the old targets from the
help output replacing them in favour of the new ones.
v2: keep rh-configs and fedora-configs targets for compatibility, which
now calls the new dist-* ones.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
This change introduces some initial centos stream support, mainly what's
needed for a dist-git sync. The dist-git sync is initially proposed to
be a fork + merge request model, and thus we need some changes for the
Makefiles. I also dropped IS_FEDORA variable, and replace it with
DISTRO, which can have either "fedora" or "centos" (and could be set
later to "rhel" or anything else if needed through the code).
While at it, I also fixed the default RHPKG_BIN to rhpkg instead of
rhpkg-sha512 in the default RHEL case, the former was a wrapper for
the sha512 transition on dist-git at RHEL 8 time and is not needed
anymore, it is now deprecated and will be removed from rhpkg.
Example of a dist-git sync with new centos dist-git:
make DIST=".el9" GL_DISTGIT_USER=<gitlab user> BUILDID="" RHDISTGIT_BRANCH=c9s dist-git
v2: use PACKAGE_NAME in Makefile.rhpkg as suggested by Jan Stancek
v3: make the default DISTRO rhel in case DIST is not fc*, to not break
folks building kernel-ark on rhel which are used to not have to
specify an extra variable, as reported by Don Zickus
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
CONFIG_SCHED_STACK_END_CHECK checks for stack overrun in calls to
schedule(). In internal testing, it had no measurable performance
impact.
Enable it for Fedora and ARK.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1856174
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
This has been turned off for Fedora stable releases for quite some time
now, but still causes issues for rawhide and test release users. Fedora
does not support CONFIG_MODVERSIONS or KABI, so the weak-modules script
offers no value, but does consume a large amount of CPU on major version
updates.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1939095
The CONFIG_FW_LOADER_COMPRESS have been kept enabled only for Fedora.
However in RHEL 9, we inherit the linux-firmware as is from Fedora, and
it installs firmware files compressed in .xz format for RHEL too.
However, the ARK/rhel config does not enable the needed support for
loading compressed firmware files, and thus firmware loading fails.
This fixes that by also enabling CONFIG_FW_LOADER_COMPRESS on ARK/rhel
config too (since ARK and Fedora have the same setting now, the config
file is moved to common/).
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
The dfl-emif module is part of the FPGA functionality which all resides
in the modules sub-package so filter this through to there too.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
We had to temporarily build in DEVFREQ_GOV_SIMPLE_ONDEMAND on ARMv7 but
we fixed that so this is now a dupe and can be dropped.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
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_MOUSE_SERIAL:
Say Y here if you have a serial (RS-232, COM port) mouse connected
to your system. This includes Sun, MouseSystems, Microsoft,
Logitech and all other compatible serial mice.
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called sermouse.
Symbol: MOUSE_SERIAL [=n]
Type : tristate
Defined at drivers/input/mouse/Kconfig:203
Prompt: Serial mouse
Depends on: !UML && INPUT [=y] && INPUT_MOUSE [=y]
Location:
-> Device Drivers
-> Input device support
-> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-> Mice (INPUT_MOUSE [=y])
Selects: SERIO [=y]
---
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Since !777 CONFIG_MOUSE_SERIAL is only enabled for x86. That's fine, but
the config item does not declare a default so we must unset it for the
default case.
Cc: Peter Robinson <pbrobinson@gmail.com>
Cc: Dan Horák <dan@danny.cz>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
EFI is enabled on arm platforms, lets unify the config
options.
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
ptalbert@redhat.com: removed CONFIG_EFI_VARS due to !825.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
Statistical profiling is a feature of recent arm cores
lets move the driver to the common directories.
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
The hotplug mem option is used to enable a number of other
kernel features and should be enabled for ark.
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
As of upstream commit 963fabf the EFI_VARS option is set to x86
only as it's long been deprecated pre !intel support and is due to
be removed so it now does nothing on arm platforms.
Fedora actually disabled this on x86 too, I do wonder if it's
worth considering disabling it in ark platforms too?
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
Cc: Mark Salter <msalter@redhat.com>
Cc: Al Stone <ahs3@redhat.com>
We already enable RTC_HCTOSYS in common config, this is the inverse
for syncing NTP to HW RTCs, and seems slightly better/preferred on
non x86-style CMOS RTCa than update_persistent_clock.
Set the device to rtc0, the same as we set RTC_HCTOSYS to.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
The Arm System Control and Management Interface (SCMI) specification is
a new standard firmware interface for Arm devices from Arm.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
Cc: ahs3@redhat.com
Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
The Bosch C_CAN stopped shipping in 2006, it's successor D_CAN also
supported by the same driver it seems around 2010, the CC770 is also
based on the original C_CAN, and the SJA1000 is of similar vintage.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
The Microchip MCP251x/MCP251xFD CAN controllers are widely deployed
across IoT/Edge devices such as the Compulabs Fitlet2 (RHEL for Edge)
and are often attached in host systems via FTDI serial interfaces.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
The Intel IoT/Edge Elkhart Lake SoC has onboard Bosch MCAN controller IP.
This is scheduled to be a supported RHEL for Edge platform so we want
MCAN support.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
The CAN_PEAK_PCIEFD is a PEAK-System PCAN-PCIe FD cards driver
and the one that should have been eabled instead of CAN_PEAK_PCIEC.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Enable vxcan (for virtual can tunneling), ISO 15765-2:2016 CAN transport protocol
(for londer datagram protocols needed for certain L3 protocols such as
IP-over-CAN traffic) and SAE J1939 (for j1939 socket type used by datalink &
transport protocol as well as management).
These are all common protocols needed for modern CAN deployments.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
The CONFIG_CAN_LEDS is marked as broken in the kernel, we don't
want to enable it for general CAN use cases anyway.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
The WM8804 codec is required for Intel Apollo Lake support so enable it as it's a supported RHEL for Edge platform.
Some minor cleanups for the WM8804 codec configs while we're at it.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
The following EL0, Point of Sale and related, and Wacom touchscreens
are serial based touch screens and are only really used on x86 systems.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
The serio touchscreens in Fedora aren't used out side of x86 so move the ark
configs to generic and the Fedora configs to fedora/x86. No change on ARK kernels.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
THe i8042 PC Keyboard controller and AT keyboard are x86 only so
only enable them on that architecture.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
Disable the ancient DEC VSXXXAA mouse, needs a special adapter to be
used over RS-232, only enable RS-232 mice on x86.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
PS2 mice aren't supported on all current architectures other than x86
so move the generic option to x86 and the ark aarch64 options that
disabled them to generic so it applies to all non x86 architectures.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
Mostly arm related updates but there's a few minor x86 and generic
bits, plus a few minor debug/prod dmabuf updates.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Intel has confirmed that QAT hardware is x86 only. Unify all the related
configs under redhat/configs/common/generic/x86/.
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
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_COMMON_CLK_AXI_CLKGEN:
Support for the Analog Devices axi-clkgen pcore clock generator for Xilinx
FPGAs. It is commonly used in Analog Devices' reference designs.
Symbol: COMMON_CLK_AXI_CLKGEN [=n]
Type : tristate
Defined at drivers/clk/Kconfig:248
Prompt: AXI clkgen driver
Depends on: COMMON_CLK [=y] && (HAS_IOMEM [=y] || COMPILE_TEST [=n]) && OF [=y]
Location:
-> Device Drivers
-> Common Clock Framework (COMMON_CLK [=y])
---
Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_SENSORS_AHT10:
If you say yes here, you get support for the Aosong AHT10
temperature and humidity sensors
This driver can also be built as a module. If so, the module
will be called aht10.
Symbol: SENSORS_AHT10 [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:247
Prompt: Aosong AHT10
Depends on: HWMON [=y] && I2C [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
CONFIG_SENSORS_TPS23861:
If you say yes here you get support for Texas Instruments
TPS23861 802.3at PoE PSE chips.
This driver can also be built as a module. If so, the module
will be called tps23861.
Symbol: SENSORS_TPS23861 [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:1136
Prompt: Texas Instruments TPS23861 PoE PSE
Depends on: HWMON [=y] && I2C [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
Selects: REGMAP_I2C [=m]
---
Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT:
The implicit default version of DWARF debug info produced by a
toolchain changes over time.
This can break consumers of the debug info that haven't upgraded to
support newer revisions, and prevent testing newer versions, but
those should be less common scenarios.
If unsure, say Y.
Symbol: DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT [=n]
Type : bool
Defined at lib/Kconfig.debug:264
Prompt: Rely on the toolchain's implicit default DWARF version
Depends on: <choice>
Location:
-> Kernel hacking
-> Compile-time checks and compiler options
-> Compile the kernel with debug info (DEBUG_INFO [=y])
-> DWARF version (<choice> [=y])
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_PCIE_MICROCHIP_HOST:
Say Y here if you want kernel to support the Microchip AXI PCIe
Host Bridge driver.
Symbol: PCIE_MICROCHIP_HOST [=n]
Type : bool
Defined at drivers/pci/controller/Kconfig:278
Prompt: Microchip AXI PCIe host bridge support
Depends on: PCI [=y] && PCI_MSI [=y] && OF [=y]
Location:
-> Device Drivers
-> PCI support (PCI [=y])
-> PCI controller drivers
Selects: PCI_MSI_IRQ_DOMAIN [=y] && GENERIC_MSI_IRQ_DOMAIN [=y] && PCI_HOST_COMMON [=n]
---
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_BCM_VK:
Select this option to enable support for Broadcom
VK Accelerators. VK is used for performing
multiple specific offload processing tasks in parallel.
Such offload tasks assist in such operations as video
transcoding, compression, and crypto tasks.
This driver enables userspace programs to access these
accelerators via /dev/bcm-vk.N devices.
If unsure, say N.
Symbol: BCM_VK [=n]
Type : tristate
Defined at drivers/misc/bcm-vk/Kconfig:5
Prompt: Support for Broadcom VK Accelerators
Depends on: PCI_MSI [=y]
Location:
-> Device Drivers
-> Misc devices
---
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_ACPI_FPDT:
Enable support for the Firmware Performance Data Table (FPDT).
This table provides information on the timing of the system
boot, S3 suspend and S3 resume firmware code paths.
Symbol: ACPI_FPDT [=n]
Type : bool
Defined at drivers/acpi/Kconfig:90
Prompt: ACPI Firmware Performance Data Table (FPDT) support
Depends on: ACPI [=y] && X86_64 [=y]
Location:
-> Power management and ACPI options
-> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])
---
Cc: Al Stone <ahs3@redhat.com>
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_KFENCE:
KFENCE is a low-overhead sampling-based detector of heap out-of-bounds
access, use-after-free, and invalid-free errors. KFENCE is designed
to have negligible cost to permit enabling it in production
environments.
See <file:Documentation/dev-tools/kfence.rst> for more details.
Note that, KFENCE is not a substitute for explicit testing with tools
such as KASAN. KFENCE can detect a subset of bugs that KASAN can
detect, albeit at very different performance profiles. If you can
afford to use KASAN, continue using KASAN, for example in test
environments. If your kernel targets production use, and cannot
enable KASAN due to its cost, consider using KFENCE.
Symbol: KFENCE [=n]
Type : bool
Defined at lib/Kconfig.kfence:6
Prompt: KFENCE: low-overhead sampling-based memory safety error detector
Depends on: HAVE_ARCH_KFENCE [=y] && (SLAB [=n] || SLUB [=y])
Location:
-> Kernel hacking
-> Memory Debugging
Selects: STACKTRACE [=y]
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_KASAN_MODULE_TEST:
This is a part of the KASAN test suite that is incompatible with
KUnit. Currently includes tests that do bad copy_from/to_user
accesses.
Symbol: KASAN_MODULE_TEST [=n]
Type : tristate
Defined at lib/Kconfig.kasan:195
Prompt: KUnit-incompatible tests of KASAN bug detection capabilities
Depends on: m && MODULES [=y] && KASAN [=y] && !KASAN_HW_TAGS [=n]
Location:
-> Kernel hacking
-> Memory Debugging
-> KASAN: runtime memory debugger (KASAN [=y])
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_CMDLINE_EXTEND:
The command-line arguments provided by the boot loader will be
appended to the default kernel command string.
Symbol: CMDLINE_EXTEND [=n]
Type : bool
Defined at arch/arm64/Kconfig:1859
Prompt: Extend bootloader kernel arguments
Depends on: <choice>
Location:
-> Boot options
-> Default kernel command string (CMDLINE [=console=ttyAMA0])
-> Kernel command line type (<choice> [=y])
---
CONFIG_CMDLINE_FROM_BOOTLOADER:
Uses the command-line options passed by the boot loader. If
the boot loader doesn't provide any, the default kernel command
string provided in CMDLINE will be used.
Symbol: CMDLINE_FROM_BOOTLOADER [=y]
Type : bool
Defined at arch/arm64/Kconfig:1852
Prompt: Use bootloader kernel arguments if available
Depends on: <choice>
Location:
-> Boot options
-> Default kernel command string (CMDLINE [=console=ttyAMA0])
-> Kernel command line type (<choice> [=y])
---
Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_STACK_HASH_ORDER:
Select the hash size as a power of 2 for the stackdepot hash table.
Choose a lower value to reduce the memory impact.
Symbol: STACK_HASH_ORDER [=20]
Type : integer
Range : [12 20]
Defined at lib/Kconfig:654
Prompt: stack depot hash size (12 => 4KB, 20 => 1024KB)
Depends on: STACKDEPOT [=y]
Location:
-> Library routines
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_INTEL_LDMA:
Enable support for Intel Lightning Mountain SOC DMA controllers.
These controllers provide DMA capabilities for a variety of on-chip
devices such as HSNAND and GSWIP (Gigabit Switch IP).
Symbol: INTEL_LDMA [=n]
Type : bool
Defined at drivers/dma/lgm/Kconfig:2
Prompt: Lightning Mountain centralized DMA controllers
Depends on: DMADEVICES [=y] && (X86 [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> DMA Engine support (DMADEVICES [=y])
Selects: DMA_ENGINE [=y] && DMA_VIRTUAL_CHANNELS [=y]
---
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
We reverted the commit "drm: panel: add Xingbangda XBD599 panel", which
introduced this config option. Thus also remove the corresponding config
file.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
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_CMDLINE:
On some platforms, there is currently no way for the boot loader to
pass arguments to the kernel. For these platforms, you can supply
some command-line options at build time by entering them here. In
most cases you will need to specify the root device here.
Symbol: CMDLINE [=]
Type : string
Defined at arch/powerpc/Kconfig:882
Prompt: Initial kernel command string
Location:
-> Kernel options
Cc: kernel-patches@redhat.com
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_N5X:
This enables support for Intel's eASIC N5X SoCFPGA Family.
Symbol: ARCH_N5X [=n]
Type : bool
Defined at arch/arm64/Kconfig.platforms:16
Prompt: Intel's eASIC N5X SoCFPGA Family
Location:
-> Platform selection
---
Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
There are still some leftover dmilburn references. I thought I had got
rid of these.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: gtiwari@redhat.com
Cc: darcari@redhat.com
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_MLX5_SF:
Build support for subfuction device in the NIC. A Mellanox subfunction
device can support RDMA, netdevice and vdpa device.
It is similar to a SRIOV VF but it doesn't require SRIOV support.
Symbol: MLX5_SF [=n]
Type : bool
Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:205
Prompt: Mellanox Technologies subfunction device support using auxiliary device
Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_CORE [=m] && MLX5_CORE_EN [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Ethernet driver support (ETHERNET [=y])
-> Mellanox devices (NET_VENDOR_MELLANOX [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_SND_JACK_INJECTION_DEBUG:
This option can be used to enable or disable sound jack
software injection.
Say Y if you are debugging via jack injection interface.
If unsure select "N".
Symbol: SND_JACK_INJECTION_DEBUG [=n]
Type : bool
Defined at sound/core/Kconfig:190
Prompt: Sound jack injection interface via debugfs
Depends on: SOUND [=m] && !UML && SND [=m] && SND_JACK [=y] && SND_DEBUG [=y] && DEBUG_FS [=y]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> Debug (SND_DEBUG [=y])
---
Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_IP_VS_TWOS:
The weighted random twos choice least-connection scheduling
algorithm picks two random real servers and directs network
connections to the server with the least active connections
normalized by the server weight.
If you want to compile it in kernel, say Y. To compile it as a
module, choose M here. If unsure, say N.
Symbol: IP_VS_TWOS [=n]
Type : tristate
Defined at net/netfilter/ipvs/Kconfig:274
Prompt: weighted random twos choice least-connection scheduling
Depends on: NET [=y] && NETFILTER [=y] && IP_VS [=m]
Location:
-> Networking support (NET [=y])
-> Networking options
-> Network packet filtering framework (Netfilter) (NETFILTER [=y])
-> IP virtual server support (IP_VS [=m])
---
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Antoine Tenart <atenart@redhat.com>
Cc: Balazs Nemeth <bnemeth@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_DTPM:
This enables support for the power capping for the dynamic
thermal power management userspace engine.
Symbol: DTPM [=n]
Type : bool
Defined at drivers/powercap/Kconfig:47
Prompt: Power capping for Dynamic Thermal Power Management
Depends on: POWERCAP [=y]
Location:
-> Device Drivers
-> Generic powercap sysfs driver (POWERCAP [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_MT7921E:
This adds support for MT7921E 802.11ax 2x2:2SS wireless devices.
To compile this driver as a module, choose M here.
Symbol: MT7921E [=n]
Type : tristate
Defined at drivers/net/wireless/mediatek/mt76/mt7921/Kconfig:2
Prompt: MediaTek MT7921E (PCIe) support
Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_MEDIATEK [=y] && MAC80211 [=m] && PCI [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Wireless LAN (WLAN [=y])
-> MediaTek devices (WLAN_VENDOR_MEDIATEK [=y])
Selects: MT76_CONNAC_LIB [=n] && WANT_DEV_COREDUMP [=y]
---
Cc: Jarod Wilson <jarod@redhat.com>
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_TCG_TIS_I2C_CR50:
This is a driver for the Google cr50 I2C TPM interface which is a
custom microcontroller and requires a custom i2c protocol interface
to handle the limitations of the hardware. To compile this driver
as a module, choose M here; the module will be called tcg_tis_i2c_cr50.
Symbol: TCG_TIS_I2C_CR50 [=n]
Type : tristate
Defined at drivers/char/tpm/Kconfig:89
Prompt: TPM Interface Specification 2.0 Interface (I2C - CR50)
Depends on: TCG_TPM [=y] && I2C [=y]
Location:
-> Device Drivers
-> Character devices
-> TPM Hardware Support (TCG_TPM [=y])
Selects: TCG_CR50
---
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_FTRACE_RECORD_RECURSION:
All callbacks that attach to the function tracing have some sort
of protection against recursion. Even though the protection exists,
it adds overhead. This option will create a file in the tracefs
file system called "recursed_functions" that will list the functions
that triggered a recursion.
This will add more overhead to cases that have recursion.
If unsure, say N
Symbol: FTRACE_RECORD_RECURSION [=n]
Type : bool
Defined at kernel/trace/Kconfig:737
Prompt: Record functions that recurse in function tracing
Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && FUNCTION_TRACER [=y]
Location:
-> Kernel hacking
-> Tracers (FTRACE [=y])
---
CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS:
This will audit the time stamps on the ring buffer sub
buffer to make sure that all the time deltas for the
events on a sub buffer matches the current time stamp.
This audit is performed for every event that is not
interrupted, or interrupting another event. A check
is also made when traversing sub buffers to make sure
that all the deltas on the previous sub buffer do not
add up to be greater than the current time stamp.
NOTE: This adds significant overhead to recording of events,
and should only be used to test the logic of the ring buffer.
Do not use it on production systems.
Only say Y if you understand what this does, and you
still want it enabled. Otherwise say N
Symbol: RING_BUFFER_VALIDATE_TIME_DELTAS [=n]
Type : bool
Defined at kernel/trace/Kconfig:846
Prompt: Verify ring buffer time stamp deltas
Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && RING_BUFFER [=y]
Location:
-> Kernel hacking
-> Tracers (FTRACE [=y])
---
Cc: Jerome Marchand <jmarchan@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_ACPI_PLATFORM_PROFILE:
This driver adds support for platform-profiles on platforms that
support it.
Platform-profiles can be used to control the platform behaviour. For
example whether to operate in a lower power mode, in a higher
power performance mode or between the two.
This driver provides the sysfs interface and is used as the registration
point for platform specific drivers.
Which profiles are supported is determined on a per-platform basis and
should be obtained from the platform specific driver.
Symbol: ACPI_PLATFORM_PROFILE [=m]
Type : tristate
Defined at drivers/acpi/Kconfig:329
Prompt: ACPI Platform Profile Driver
Depends on: ACPI [=y]
Location:
-> Power management and ACPI options
-> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])
---
Cc: Al Stone <ahs3@redhat.com>
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
CONFIG_TYPEC_UCSI now depends on CONFIG_USB_ROLE_SWITCH, and must have
the same tristate.
CONFIG_HSA_AMD now will select CONFIG_DRM_AMDGPU_USERPTR, so it must be
turned on if CONFIG_HSA_AMD is on, or we will have a config mismatch
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
The gpio-watch tool is shipped within the kernel-tools package. However,
when it was added some time ago, the debuginfo pattern inside the spec
file was not updated, so the gpio-watch.debug file ends up in the
kernel-debuginfo-common package instead of the kernel-tools-debuginfo.
This change fixes the problem, and also it's likely will fix an
update/downgrade test done on CI for RHEL that reports:
Error: Transaction test error:
file /usr/lib/debug/usr/bin/gpio-watch.debug from install of
kernel-debuginfo-common-x86_64-5.11.0-0.rc7.151.el9.x86_64 conflicts
with file from package kernel-debuginfo-common-x86_64-5.11.0-1.el9.x86_64
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
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@redhat.com>
Cc: Donald Dutile <ddutile@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_SMMU_V3_SVA:
Support for sharing process address spaces with devices using the
SMMUv3.
Say Y here if your system supports SVA extensions such as PCIe PASID
and PRI.
Symbol: ARM_SMMU_V3_SVA [=n]
Type : bool
Defined at drivers/iommu/Kconfig:311
Prompt: Shared Virtual Addressing support for the ARM SMMUv3
Depends on: IOMMU_SUPPORT [=y] && ARM_SMMU_V3 [=y]
Location:
-> Device Drivers
-> IOMMU Hardware Support (IOMMU_SUPPORT [=y])
-> ARM Ltd. System MMU Version 3 (SMMUv3) Support (ARM_SMMU_V3 [=y])
---
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>
Cc: Don Dutile <ddutile@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_CHELSIO_INLINE_CRYPTO:
Enable support for inline crypto.
Allows enable/disable from list of inline crypto drivers.
Symbol: CHELSIO_INLINE_CRYPTO [=y]
Type : bool
Defined at drivers/net/ethernet/chelsio/inline_crypto/Kconfig:6
Prompt: Chelsio Inline Crypto support
Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_CHELSIO [=y] && CHELSIO_T4 [=m]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Ethernet driver support (ETHERNET [=y])
-> Chelsio devices (NET_VENDOR_CHELSIO [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_DMABUF_HEAPS_SYSTEM:
Choose this option to enable the system dmabuf heap. The system heap
is backed by pages from the buddy allocator. If in doubt, say Y.
Symbol: DMABUF_HEAPS_SYSTEM [=n]
Type : bool
Defined at drivers/dma-buf/heaps/Kconfig:1
Prompt: DMA-BUF System Heap
Depends on: DMABUF_HEAPS [=y]
Location:
-> Device Drivers
-> DMABUF options
-> DMA-BUF Userland Memory Heaps (DMABUF_HEAPS [=y])
Cc: Lyude Paul <lyude@redhat.com>
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_NFT_REJECT_NETDEV:
This option enables the REJECT support from the netdev table.
The return packet generation will be delegated to the IPv4
or IPv6 ICMP or TCP RST implementation depending on the
protocol of the packet.
Symbol: NFT_REJECT_NETDEV [=n]
Type : tristate
Defined at net/netfilter/Kconfig:685
Prompt: Netfilter nf_tables netdev REJECT support
Depends on: NET [=y] && INET [=y] && NETFILTER [=y] && NF_TABLES [=m] && NF_TABLES_NETDEV [=y] && NFT_REJECT_IPV4 [=m] && NFT_REJECT_IPV6 [=m]
Location:
-> Networking support (NET [=y])
-> Networking options
-> Network packet filtering framework (Netfilter) (NETFILTER [=y])
-> Core Netfilter Configuration
-> Netfilter nf_tables support (NF_TABLES [=m])
---
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
In reality we don't have a need for more than 16 CPUs and
it appears in certain circumstances it can cause us problems.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
We shouldn't have DEBUG_HIGHMEM for default kernels so disable it
and any of the bits that try to enable it on standard kernels but
leave it in place for debug kernels.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
`xargs -0` expects arguments delimited by \0 on stdin, but instead it
recieves a list of filenames delimited by \n from `find`. Fix that by
adding `-print0` to `find` so that it outputs the filenames delimited by
\0 as xargs expects.
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
Add myself to be the maintainer for the rdma_rxe driver.
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Kamal Heib <kheib@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Add myself to be the maintainer for the siw driver.
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Kamal Heib <kheib@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Add myself to be the maintainer for the vmw_pvrdma driver.
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Kamal Heib <kheib@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Add myself to be the maintainer for the efa driver.
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Kamal Heib <kheib@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Add Selvin to be the maintainer for the bnxt_re driver.
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Kamal Heib <kheib@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
As discussed on the Fedora kernel list add a redhat/rebase-notes.txt
file with notes about things to keep in mind when rebasing the
Fedora kernel packages to a new upstream release.
And populate this file with a note about disabling
SND_INTEL_BYT_PREFER_SOF for Fedora 33 and older.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Bugzilla: INTERNAL
Upstream: RHEL only
As I am also tracking upstream changes in futex code, I may as well add
the futex subsystem entry.
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Waiman Long <longman@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Balazs is now part of the networking team.
RH-Acked-by: Balazs Nemeth <bnemeth@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Xin Long <lxin@redhat.com>
Signed-off-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
While this is not breaking ARK testing as the pipeline is not fully
building the kernel but only SRPM, we should fix this repo as well to
not run into any suprises in the future. The name is used to grab the
correct ccache file, and using the MR ID in there would render the whole
ccache setup useless.
Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
On s390 more and more code from the early boot stage is moved to the
decompressor. With this the code complexity and thus the chances to
introduce bugs increases. In order to be able to debug these early boot
bugs package the decompressors vmlinux together with the other debuginfo
for s390.
This change requires kernel commit 7a84ffc047 ("s390/boot: add
build-id to decompressor") to work.
Upstream Status: RHEL only
Signed-off-by: Philipp Rudo <prudo@redhat.com>
We were not including yet the DUP and kpatch additional certificates in the
build process for RHEL. Do it by creating the required pem file and setting
the related kernel config option.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Yesterday, dist-git in Fedora was change, renaming the master branch to
either rawhide or main depending on the context. In our case, rawhide
is the correct default branch going forward. You can not run 'make
dist-git' successfully until this is merged.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
* dist-tarball
* dist-kernelrelease
* dist-kernelversion
* dist-specfile
dist-tarball echoes the path to the tarball, starting with redhat/.
dist-kernelrelease echoes the package name and full version;
dist-kernelversion echoes just the full version strin.
dist-specfile (possibly) invokes setup-source, then echoes a path to
the (possibly newly-generated) specfile.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
CONFIG_KEY_NOTIFICATIONS
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.
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
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_KVM_ARM_PMU:
Adds support for a virtual Performance Monitoring Unit (PMU) in
virtual machines.
Symbol: KVM_ARM_PMU [=y]
Type : bool
Defined at arch/arm64/kvm/Kconfig:52
Prompt: Virtual Performance Monitoring Unit (PMU) support
Depends on: VIRTUALIZATION [=y] && KVM [=y] && HW_PERF_EVENTS [=y]
Location:
-> Virtualization (VIRTUALIZATION [=y])
-> Kernel-based Virtual Machine (KVM) support (KVM [=y])
Cc: Mark Salter <msalter@redhat.com>
The Intel MIC drivers were removed in 5.10, in commit 80ade22,
so these driver configs are now irrelvent so remove them. This
primarilly affects Fedora as they were disabled in ARK anyway.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Upstream Status: RHEL only
Tested: verified changelog created after make rh-release
This wires in the genlog.py script call in genspec.sh, replacing the
previous inline awk script.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Upstream Status: RHEL only
Tested: verified changelog created after make rh-release
This change adds a separate python script that will generate changelog
items for the kernel RPM package, based on git log contents. It aims to
be a straight replacement of the current awk logic in redhat/genspec.sh.
I received review feedback from Jan Stancek, Frantisek Hrbata, Don
Zickus on an earlier version of the script, and this version contains
suggestions made by them.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Add a new dist-buildreq-check target that checks for missing
packages via rpmspec -q --buildrequires, and make dist-configs-prep
dependent on it.
This change is based on suggestions from Josh Poimboeuf, Don Zickus,
and Herton Krzesinski. Ultimately this is Herton's version, which
generates the list of missing packages from an already-created
kernel.spec file.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
In the commit "Rename RH_DISABLE_DEPRECATED to RHEL_DIFFERENCES", the change
in kernel/Makefile was an addition instead of a rename. This change fixes
that by removing the old line still referencing CONFIG_RH_DISABLE_DEPRECATED.
Also, the redhat/configs tree still have the old config option files, remove
them too.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
With upstream commit 7fe2de246e
powerpc/vdso: Stripped VDSO is not needed, don't build it
the make targets for vdso_install are gone for ppc. If we call them, the
build fails. This just turns them off.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
Consolidate rpmbuild commands into a new target, do-rpmbuild,
and invoke it from dist-all-rpms, dist-srpm, etc. via, e.g.,
dist-srpm: RPMBUILDOPTS=--nodeps -bs
dist-srpm: dist-sources do-rpmbuild
This works for all the targets that invoke rpmbuild EXCEPT
dist-kernel-%, which we rewrite:
dist-kernel-%: dist-sources
RPMBUILDOPTS="--target $(MACH) --with $* --without vdso_install --without perf --without tools -bb" make do-rpmbuild
i.e., setting RPMBUILDOPTS and then invoking make again,
and dist-srpm-gcov, which already had an extra 'make' in its
recipe.
The cost of the dist-kernel-% rewrite is an extra trip through the Makefile,
and the extra prologue (4 lines) and epilogue (1 line) output that goes with it.
The newly rewritten dist-* targets require some ordering constraints,
which are not a bad idea even in the absence of these modifications,
and which can be accomplished by moving
setup-source, dist-configs-check
FROM dist-sources TO sources-rh, thus making sure that
setup-source and dist-configs-check get made strictly before
sources-rh.
With these ordering constraints in place, commands like the following
work as expected:
% make -j 64 dist-rpms
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
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_DEBUG_FS_ALLOW_ALL:
No restrictions apply. Both API and filesystem registration
is on. This is the normal default operation.
Symbol: DEBUG_FS_ALLOW_ALL [=y]
Type : bool
Defined at lib/Kconfig.debug:500
Prompt: Access normal
Depends on: <choice>
Location:
-> Kernel hacking
-> Generic Kernel Debugging Instruments
-> Debug Filesystem (DEBUG_FS [=y])
-> Debugfs default access (<choice> [=y])
Cc: Prarit Bhargava <prarit@redhat.com>
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_SPI_AMD:
Enables SPI controller driver for AMD SoC.
Symbol: SPI_AMD [=n]
Type : tristate
Defined at drivers/spi/Kconfig:917
Prompt: AMD SPI controller
Depends on: SPI [=y] && SPI_MASTER [=y] && (SPI_MASTER [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> SPI support (SPI [=y])
---
Signed-off-by: CKI@GitLab <cki-project@redhat.com>
Upstream commit 9f30eb29c5 changed
VIRTIO_CONSOLE from depending on VIRTIO to selecting VIRTIO. This made
it possible to build in the console with virtio drivers being modular.
Before this change, VIRTIO_CONSOLE status did not matter for the
zfcpdump kernel, because VIRTIO which it depends on was turned off.
After that change, having VIRTIO_CONSOLE on will select VIRTIO and turn
on those drivers as modules. This really sets things back to the way
they were.
Signed-off-by: Justin M. Forbes <jforbes@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_COMMON_CLK:
The common clock framework is a single definition of struct
clk, useful across many platforms, as well as an
implementation of the clock API in include/linux/clk.h.
Architectures utilizing the common struct clk should select
this option.
Symbol: COMMON_CLK [=n]
Type : bool
Defined at drivers/clk/Kconfig:25
Prompt: Common Clock Framework
Depends on: !HAVE_LEGACY_CLK [=n]
Location:
-> Device Drivers
Selects: HAVE_CLK_PREPARE [=n] && CLKDEV_LOOKUP [=n] && SRCU [=y] && RATIONAL [=n]
Selected by [n]:
- MFD_INTEL_LPSS [=n] && HAS_IOMEM [=y]
- INTEL_ATOMISP [=n] && STAGING [=n] && STAGING_MEDIA [=n] && MEDIA_SUPPORT [=n] && X86 && EFI && PCI [=y] && ACPI
- PMC_ATOM [=n] && X86 && PCI [=y]
Cc: Mark Salter <msalter@redhat.com>
This regression has been hit in the CoreOS pipeline as it utilizes
it to gather build logs from build VMs during build of the CoreOS.
Fixes RHBZ1917575
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_DEBUG_VM_PGTABLE:
This option provides a debug method which can be used to test
architecture page table helper functions on various platforms in
verifying if they comply with expected generic MM semantics. This
will help architecture code in making sure that any changes or
new additions of these helpers still conform to expected
semantics of the generic MM. Platforms will have to opt in for
this through ARCH_HAS_DEBUG_VM_PGTABLE.
If unsure, say N.
Symbol: DEBUG_VM_PGTABLE [=n]
Type : bool
Defined at lib/Kconfig.debug:702
Prompt: Debug arch page table for semantics compliance
Depends on: MMU [=y] && ARCH_HAS_DEBUG_VM_PGTABLE [=y]
Location:
-> Kernel hacking
-> Memory Debugging
Cc: Prarit Bhargava <prarit@redhat.com>
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_PINCTRL_EMMITSBURG:
This pinctrl driver provides an interface that allows configuring
of Intel Emmitsburg pins and using them as GPIOs.
Symbol: PINCTRL_EMMITSBURG [=n]
Type : tristate
Defined at drivers/pinctrl/intel/Kconfig:98
Prompt: Intel Emmitsburg pinctrl and GPIO driver
Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINCTRL_INTEL [=m]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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@redhat.com>
Cc: Eric Auger <eric.auger@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@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_MFD_INTEL_PMT:
The Intel Platform Monitoring Technology (PMT) is an interface that
provides access to hardware monitor registers. This driver supports
Telemetry, Watcher, and Crashlog PMT capabilities/devices for
platforms starting from Tiger Lake.
Symbol: MFD_INTEL_PMT [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:685
Prompt: Intel Platform Monitoring Technology (PMT) support
Depends on: HAS_IOMEM [=y] && PCI [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: MFD_CORE [=y]
---
Cc: Torez Smith <torez@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_EDAC_IGEN6:
Support for error detection and correction on the Intel
client SoC Integrated Memory Controller using In-Band ECC IP.
This In-Band ECC is first used on the Elkhart Lake SoC but
may appear on others in the future.
Symbol: EDAC_IGEN6 [=n]
Type : tristate
Defined at drivers/edac/Kconfig:272
Prompt: Intel client SoC Integrated MC
Depends on: EDAC [=y] && PCI [=y] && X86_64 [=y] && PCI_MMCONFIG [=y] && ARCH_HAVE_NMI_SAFE_CMPXCHG [=y]
Location:
-> Device Drivers
-> EDAC (Error Detection And Correction) reporting (EDAC [=y])
---
Cc: Aristeu Rozanski <aris@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_MHU_V2:
Say Y here if you want to build the ARM MHUv2 controller driver,
which provides unidirectional mailboxes between processing elements.
Symbol: ARM_MHU_V2 [=n]
Type : tristate
Defined at drivers/mailbox/Kconfig:19
Prompt: ARM MHUv2 Mailbox
Depends on: MAILBOX [=y] && ARM_AMBA [=y]
Location:
-> Device Drivers
-> Mailbox Hardware Support (MAILBOX [=y])
---
Cc: Al Stone <ahs3@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_HID_VIVALDI:
Say Y here if you want to enable support for Vivaldi keyboards.
Vivaldi keyboards use a vendor-specific (Google) HID usage to report
how the keys in the top row are physically ordered.
Symbol: HID_VIVALDI [=n]
Type : tristate
Defined at drivers/hid/Kconfig:400
Prompt: Vivaldi Keyboard
Depends on: INPUT [=y] && HID [=y]
Location:
-> Device Drivers
-> HID support
-> HID bus support (HID [=y])
-> Special HID drivers
---
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1915073
Upstream Status: RHEL only
Forward port update from RHEL-8 to add the following modules to the
mod-internal.list file:
dmatest
test_klp_*
In RHEL builds, these modules are packaged into the
kernel-modules-internal rpm and not kernel-core.
Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>
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_QCOM_GPI_DMA:
Enable support for the QCOM GPI DMA controller. This controller
provides DMA capabilities for a variety of peripheral buses such
as I2C, UART, and SPI. By using GPI dmaengine driver, bus drivers
can use a standardize interface that is protocol independent to
transfer data between DDR and peripheral.
Symbol: QCOM_GPI_DMA [=n]
Type : tristate
Defined at drivers/dma/qcom/Kconfig:22
Prompt: Qualcomm Technologies GPI DMA support
Depends on: DMADEVICES [=y] && ARCH_QCOM [=y]
Location:
-> Device Drivers
-> DMA Engine support (DMADEVICES [=y])
Selects: DMA_ENGINE [=y] && DMA_VIRTUAL_CHANNELS [=n]
---
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_UV_SYSFS:
This driver supports a sysfs tree describing information about
UV systems at /sys/firmware/sgi_uv/.
To compile this driver as a module, choose M here: the module will
be called uv_sysfs.
Symbol: UV_SYSFS [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:81
Prompt: Sysfs structure for UV systems
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && X86_UV [=y] && SYSFS [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
---
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_DRM_ANALOGIX_ANX7625:
ANX7625 is an ultra-low power 4K mobile HD transmitter
designed for portable devices. It converts MIPI/DPI to
DisplayPort1.3 4K.
Symbol: DRM_ANALOGIX_ANX7625 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/analogix/Kconfig:29
Prompt: Analogix Anx7625 MIPI to DP interface support
Depends on: HAS_IOMEM [=y] && DRM_BRIDGE [=y] && DRM [=m] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
---
CONFIG_DRM_LONTIUM_LT9611UXC:
Driver for Lontium LT9611UXC DSI to HDMI bridge
chip driver that converts dual DSI and I2S to
HDMI signals
Please say Y if you have such hardware.
Symbol: DRM_LONTIUM_LT9611UXC [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:64
Prompt: Lontium LT9611UXC DSI/HDMI bridge
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: SND_SOC_HDMI_CODEC [=n] && DRM_PANEL_BRIDGE [=y] && DRM_KMS_HELPER [=m] && REGMAP_I2C [=m]
---
CONFIG_DRM_PANEL_ABT_Y030XX067A:
Say Y here to enable support for the Asia Better Technology Ltd.
Y030XX067A 320x480 3.0" panel as found in the YLM RG-280M, RG-300
and RG-99 handheld gaming consoles.
Symbol: DRM_PANEL_ABT_Y030XX067A [=n]
Type : tristate
Defined at drivers/gpu/drm/panel/Kconfig:11
Prompt: ABT Y030XX067A 320x480 LCD panel
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_PANEL [=y] && OF [=y] && SPI [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Panels
Selects: REGMAP_SPI [=m]
---
Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_BRIDGE_CFM:
If you say Y here, then the Ethernet bridge will be able to run CFM
protocol according to 802.1Q section 12.14
Say N to exclude this support and reduce the binary size.
If unsure, say N.
Symbol: BRIDGE_CFM [=n]
Type : bool
Defined at net/bridge/Kconfig:77
Prompt: CFM protocol
Depends on: NET [=y] && BRIDGE [=m]
Location:
-> Networking support (NET [=y])
-> Networking options
-> 802.1d Ethernet Bridging (BRIDGE [=m])
---
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
In RHBZ 1576593 we had issues with ARMv7 builders pausing, it turned out to be a
silicon bug and we could work around it by disabling HIGHPTE. For some reason
that workaround was lost in the 5.7-rc1 merge.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
As RHMAINTAINERS is used for mapping acks and such. I would rather
change it to use the jforbes@fedoraproject.org address that I use for
commits and such.
Signed-off-by: Justin M. Forbes <jforbes@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_HW_RANDOM_XIPHERA:
This driver provides kernel-side support for Xiphera True Random
Number Generator Intellectual Property Core.
To compile this driver as a module, choose M here: the
module will be called xiphera-trng.
Symbol: HW_RANDOM_XIPHERA [=n]
Type : tristate
Defined at drivers/char/hw_random/Kconfig:529
Prompt: Xiphera FPGA based True Random Number Generator support
Depends on: HW_RANDOM [=y] && HAS_IOMEM [=y]
Location:
-> Device Drivers
-> Character devices
-> Hardware Random Number Generator Core support (HW_RANDOM [=y])
---
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_ATH11K:
This module adds support for Qualcomm Technologies 802.11ax family of
chipsets.
If you choose to build a module, it'll be called ath11k.
Symbol: ATH11K [=n]
Type : tristate
Defined at drivers/net/wireless/ath/ath11k/Kconfig:2
Prompt: Qualcomm Technologies 802.11ax chipset support
Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_ATH [=y] && MAC80211 [=m] && HAS_DMA [=y] && CRYPTO_MICHAEL_MIC [=m]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Wireless LAN (WLAN [=y])
-> Atheros/Qualcomm devices (WLAN_VENDOR_ATH [=y])
Selects: ATH_COMMON [=m] && QCOM_QMI_HELPERS [=n]
---
Cc: Jarod Wilson <jarod@redhat.com>
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
CONFIG_PCI_NR_FUNCTIONS limits the number of PCI functions the kernel
can handle on s390. In some situations (e.g. with the ROCE Express
adapter in z15) the number of available functions can easily exceed the
the current maximum. Thus increase the limit to 512, which is also the
default upstream.
Signed-off-by: Dan Horák <dan@danny.cz>
CC: Philipp Rudo <prudo@redhat.com>
CC: Steve Best <sbest@redhat.com>
The spec file has a potential issue: when released_kernel is defined, the
secureboot_ppc.cer source definition will clash with mod-blacklist.sh
definition, as both are using Source17 in the kernel spec file. To avoid
that, change the source numbers for x509 and certificate files so they
don't collide.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
When we create the src.rpm, we don't need to copy all certificate files,
only a set of them are needed depending on the RELEASED_KERNEL status.
This is necessary because when you do a make dist-git, the script
rh-dist-git.sh will create a diff to compare what was copied against what
is on dist-git clone, and this report will be bogus if we copy uneeded
files (it'll show in the diff that some files are not in the dist-git
copy, since the src.rpm created doesn't contain all certificate files,
because it's conditionally added based on released_kernel value).
Also while at it, delete old certificate files (secureboot.cer,
securebootca.cer) which are not used anymore since last grub related
security update.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
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_PMC:
The driver provides support for AMD Power Management Controller
primarily responsible for S2Idle transactions that are driven from
a platform firmware running on SMU. This driver also provides a debug
mechanism to investigate the S2Idle transactions and failures.
Say Y or M here if you have a notebook powered by AMD RYZEN CPU/APU.
If you choose to compile this driver as a module the module will be
called amd-pmc.
Symbol: AMD_PMC [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:194
Prompt: AMD SoC PMC driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y] && PCI [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
---
CONFIG_DELL_WMI_SYSMAN:
This driver allows changing BIOS settings on many Dell machines from
2018 and newer without the use of any additional software.
To compile this driver as a module, choose M here: the module will
be called dell-wmi-sysman.
Symbol: DELL_WMI_SYSMAN [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:458
Prompt: Dell WMI-based Systems management driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI_WMI [=m] && DMI [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
Selects: NLS [=y]
---
CONFIG_INTEL_PMT_CLASS:
The Intel Platform Monitoring Technology (PMT) class driver provides
the basic sysfs interface and file hierarchy uses by PMT devices.
For more information, see:
<file:Documentation/ABI/testing/sysfs-class-intel_pmt>
To compile this driver as a module, choose M here: the module
will be called intel_pmt_class.
Symbol: INTEL_PMT_CLASS [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:1371
Prompt: Intel Platform Monitoring Technology (PMT) Class driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
Selected by [n]:
- INTEL_PMT_TELEMETRY [=n] && X86 [=y] && X86_PLATFORM_DEVICES [=y]
- INTEL_PMT_CRASHLOG [=n] && X86 [=y] && X86_PLATFORM_DEVICES [=y]
---
CONFIG_INTEL_PMT_CRASHLOG:
The Intel Platform Monitoring Technology (PMT) crashlog driver provides
access to hardware crashlog capabilities on devices that support the
feature.
To compile this driver as a module, choose M here: the module
will be called intel_pmt_crashlog.
Symbol: INTEL_PMT_CRASHLOG [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:1394
Prompt: Intel Platform Monitoring Technology (PMT) Crashlog driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
Selects: INTEL_PMT_CLASS [=n]
---
CONFIG_INTEL_PMT_TELEMETRY:
The Intel Platform Monitory Technology (PMT) Telemetry driver provides
access to hardware telemetry metrics on devices that support the
feature.
To compile this driver as a module, choose M here: the module
will be called intel_pmt_telemetry.
Symbol: INTEL_PMT_TELEMETRY [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:1383
Prompt: Intel Platform Monitoring Technology (PMT) Telemetry driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
Selects: INTEL_PMT_CLASS [=n]
---
CONFIG_MLXBF_PMC:
Say y here to enable PMC support. The PMC driver provides access
to performance monitoring counters within various blocks in the
Mellanox BlueField SoC via a sysfs interface.
Symbol: MLXBF_PMC [=n]
Type : tristate
Defined at drivers/platform/mellanox/Kconfig:59
Prompt: Mellanox BlueField Performance Monitoring Counters driver
Depends on: MELLANOX_PLATFORM [=y] && ARM64 [=y] && HWMON [=y] && ACPI [=y]
Location:
-> Device Drivers
-> Platform support for Mellanox hardware (MELLANOX_PLATFORM [=y])
---
CONFIG_SURFACE_GPE:
This driver marks the GPEs related to the ACPI lid device found on
Microsoft Surface devices as wakeup sources and prepares them
accordingly. It is required on those devices to allow wake-ups from
suspend by opening the lid.
Symbol: SURFACE_GPE [=n]
Type : tristate
Defined at drivers/platform/surface/Kconfig:43
Prompt: Surface GPE/Lid Support Driver
Depends on: SURFACE_PLATFORMS [=y] && ACPI [=y] && DMI [=y]
Location:
-> Device Drivers
-> Microsoft Surface Platform-Specific Device Drivers (SURFACE_PLATFORMS [=y])
---
CONFIG_SURFACE_PLATFORMS:
Say Y here to get to see options for platform-specific device drivers
for Microsoft Surface devices. This option alone does not add any
kernel code.
If you say N, all options in this submenu will be skipped and disabled.
Symbol: SURFACE_PLATFORMS [=y]
Type : bool
Defined at drivers/platform/surface/Kconfig:6
Prompt: Microsoft Surface Platform-Specific Device Drivers
Location:
-> Device Drivers
---
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_SND_SOC_AMD_RENOIR_MACH:
This option enables machine driver for DMIC
Symbol: SND_SOC_AMD_RENOIR_MACH [=n]
Type : tristate
Defined at sound/soc/amd/Kconfig:47
Prompt: AMD Renoir support for DMIC
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_AMD_RENOIR [=m]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> AMD Audio Coprocessor - Renoir support (SND_SOC_AMD_RENOIR [=m])
Selects: SND_SOC_DMIC [=m]
---
Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Copr only permits to use --with conditionals but no --target
This allows to cross compile the kernel and is specially relevant for arm
Signed-off-by: Nicolas Chauvet <kwizart@gmail.com>
!419 enabled CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH but missed also
setting CONFIG_SND_SOC_WM8804_I2C. Fix it.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
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_SENSORS_CORSAIR_PSU:
If you say yes here you get support for Corsair PSUs with a HID
interface.
Currently this driver supports the (RM/HX)550i, (RM/HX)650i,
(RM/HX)750i, (RM/HX)850i, (RM/HX)1000i and HX1200i power supplies
by Corsair.
This driver can also be built as a module. If so, the module
will be called corsair-psu.
Symbol: SENSORS_CORSAIR_PSU [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:452
Prompt: Corsair PSU HID controller
Depends on: HWMON [=y] && HID [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
CONFIG_SENSORS_LTC2992:
If you say yes here you get support for Linear Technology LTC2992
I2C System Monitor. The LTC2992 measures current, voltage, and
power of two supplies.
This driver can also be built as a module. If so, the module will
be called ltc2992.
Symbol: SENSORS_LTC2992 [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:874
Prompt: Linear Technology LTC2992
Depends on: HWMON [=y] && I2C [=y] && GPIOLIB [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
CONFIG_SENSORS_MAX127:
Say y here to support Maxim's MAX127 DAS chips.
This driver can also be built as a module. If so, the module
will be called max127.
Symbol: SENSORS_MAX127 [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:965
Prompt: Maxim MAX127 12-bit 8-channel Data Acquisition System
Depends on: HWMON [=y] && I2C [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
CONFIG_SENSORS_PM6764TR:
If you say yes here you get hardware monitoring support for ST
PM6764TR.
This driver can also be built as a module. If so, the module will
be called pm6764tr.
Symbol: SENSORS_PM6764TR [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:223
Prompt: ST PM6764TR
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
CONFIG_SENSORS_Q54SJ108A2:
If you say yes here you get hardware monitoring support for Delta
Q54SJ108A2 series Power Supplies.
This driver can also be built as a module. If so, the module will
be called q54sj108a2.
Symbol: SENSORS_Q54SJ108A2 [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:241
Prompt: Delta Power Supplies Q54SJ108A2
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
CONFIG_SENSORS_SBTSI:
If you say yes here you get support for emulated temperature
sensors on AMD SoCs with SB-TSI interface connected to a BMC device.
This driver can also be built as a module. If so, the module will
be called sbtsi_temp.
Symbol: SENSORS_SBTSI [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:1536
Prompt: Emulated SB-TSI temperature sensor
Depends on: HWMON [=y] && I2C [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Fix the lasttag/MARKER logic ca. lines 40ff.: if MARKER
is a SHA1 (i.e. pure hexadecimal number), then
lasttag=$(git describe --match="$MARKER" --abbrev=0)
results in
fatal: No names found, cannot describe anything.
Once the new if-block is executed, lasttag will always have
a non-null value, so the second 'if [ -z "$lasttag" ]' will
never be executed and can be dropped.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
New self test to check consistency of version amongst
commit log, Makefile.rhelver, and changelog.
* Test 1:
Performing
% make dist-release
more than once in succession results in only one commit remaining in
the log.
* Test 2:
Release # in commit message matches release # in Makefile.rhelver
* Test 3:
Release # in commit message matches release # in change log.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
Like ARK does only enable these options in debug kernels, there's security
implications in particular for the later option, and they're not options
for day to day use.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Cc: Justin M. Forbes <jforbes@fedoraproject.org>
Fedora already enables ACPI_TABLE_UPGRADE so EFI_CUSTOM_SSDT_OVERLAYS doesn't
add much, it's also disabled when the kernels locked down such as for
secure boot.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
This is modular on Fedora x86/aarch64 and ARK x86, but it's built-in
on ARK aarch64 which doesn't really make sense as it's an ACPI rev4
spec and aarch64 was only supported in ACPI 5.1 (reduced hardware model)
so it's likely it's never been supported on shipping hardware so let's
make it modular there like everywhere else.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
Cc: Al Stone <ahs3@redhat.com>
No functional change, just move the x86 acpi configs that Fedora/ARK
share to the common location.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Enable the Intel Dynamic Platform and Thermal Framework on all
x86 kernels, and sync the sub components in common/generic/x86.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
This only actually changes ACPI_BGRT for ark:aarch64, all
others enabled it. We want this for ark:aarch64 too as we have
upcoming aarch64 edge devices that will support this and it's
useful for boot/firmware updates.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
Cc: Al Stone <ahs3@redhat.com>
As per the Kconfig help ACPI_EC_DEBUGFS is for poking at the
system's Embedded Controller via a /sys/kernel/debug interface
and we really shouldn't encourage this for standard use as it's
explicitly designed for debugging drivers/hardware.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
The Intel Classmate PC's were x86-32 only with the last generation
being a first gen Atom. This option is hence unused across all
kernels.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
There's a mass duplications of ACPI options across aarch64/x86 on both Fedora
and ARK kernels. Moving them into common doesn't affect non ACPI arches as
all the options are under the ACPI menu which only gets selected if the arch
presents ARCH_SUPPORTS_ACPI and some options were already in common/geneic.
There's no functional change here, this is purely de-dupe.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
This is built as a module on RHEL and is useful for testing and for
running X (or similar) on headless machines.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Antoine is now part of the networking team.
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Hangbin Liu <haliu@redhat.com>
RH-Acked-by: Antoine Tenart <atenart@redhat.com>
Acked-by: Antoine Tenart <atenart@redhat.com>
Signed-off-by: Guillaume Nault <gnault@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Add Patrick Talbert as an ARK kernel maintainer and Don Zickus as a
reviewer.
[prarit: dzickus was added in a previous patch]
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
Signed-off-by: Brian Masney <bmasney@redhat.com>
CC: Justin Forbes <jforbes@redhat.com>
CC: Patrick Talbert <ptalbert@redhat.com>
CC: Don Zickus <dzickus@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Let's make it official and add Don Zickus as a reviewer for ARK's
redhat/ directory.
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Brian Masney <bmasney@redhat.com>
CC: Donald Zickus <dzickus@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
viskulka and zyan are no longer at Red Hat.
RH-Acked-by: John W. Linville <linville@redhat.com>
RH-Acked-by: Ilya Dryomov <idryomov@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Ilya Dryomov <idryomov@redhat.com>
Cc: John W. Linville <linville@redhat.com>
Configs listed in arch/Kconfig are not covered in RHMAINTAINERS. Add the
arch maintainers to cover this file.
RH-Acked-by: Mark Salter <msalter@redhat.com>
RH-Acked-by: Steve Best <sbest@redhat.com>
RH-Acked-by: David Arcari <darcari@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
Cc: Steve Best <sbest@redhat.com>
Adding AWS Nitro Enclaves driver to the 'RHEL on third party hypervisors
and public clouds' team's responsibilities.
RH-Acked-by: Mohammed Gamal <mgamal@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
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_X86_SGX:
Intel(R) Software Guard eXtensions (SGX) is a set of CPU instructions
that can be used by applications to set aside private regions of code
and data, referred to as enclaves. An enclave's private memory can
only be accessed by code running within the enclave. Accesses from
outside the enclave, including other enclaves, are disallowed by
hardware.
If unsure, say N.
Symbol: X86_SGX [=n]
Type : bool
Defined at arch/x86/Kconfig:1937
Prompt: Software Guard eXtensions (SGX)
Depends on: X86_64 [=y] && CPU_SUP_INTEL [=y] && CRYPTO [=y]=y && CRYPTO_SHA256 [=y]=y
Location:
-> Processor type and features
Selects: SRCU [=y] && MMU_NOTIFIER [=y]
---
Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_XEN_UNPOPULATED_ALLOC:
Use unpopulated memory ranges in order to create mappings for guest
memory regions, including grant maps and foreign pages. This avoids
having to balloon out RAM regions in order to obtain physical memory
space to create such mappings.
Symbol: XEN_UNPOPULATED_ALLOC [=n]
Type : bool
Defined at drivers/xen/Kconfig:328
Prompt: Use unpopulated memory ranges for guest mappings
Depends on: XEN [=y] && X86 [=y] && ZONE_DEVICE [=y]
Location:
-> Device Drivers
-> Xen driver support
---
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_SND_SOC_ADI:
Audio support for various reference designs by Analog Devices.
Symbol: SND_SOC_ADI [=n]
Type : tristate
Defined at sound/soc/adi/Kconfig:2
Prompt: Audio support for Analog Devices reference designs
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
---
CONFIG_SND_SOC_FSL_XCVR:
Say Y if you want to add Audio Transceiver (XCVR) support for NXP
iMX CPUs. XCVR is a digital module that supports HDMI2.1 eARC,
HDMI1.4 ARC and SPDIF.
Symbol: SND_SOC_FSL_XCVR [=n]
Type : tristate
Defined at sound/soc/fsl/Kconfig:98
Prompt: NXP Audio Transceiver (XCVR) module support
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> SoC Audio for Freescale CPUs
Selects: REGMAP_MMIO [=n] && SND_SOC_IMX_PCM_DMA [=n] && SND_SOC_GENERIC_DMAENGINE_PCM [=n]
---
CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT:
This adds support for Sound Open Firmware for Intel(R) platforms
using the Alderlake processors.
Say Y if you have such a device.
If unsure select "N".
Symbol: SND_SOC_SOF_ALDERLAKE_SUPPORT [=n]
Type : bool
Defined at sound/soc/sof/intel/Kconfig:274
Prompt: SOF support for Alderlake
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_SOF_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_PCI [=m]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> Sound Open Firmware Support (SND_SOC_SOF_TOPLEVEL [=y])
-> SOF support for Intel audio DSPs (SND_SOC_SOF_INTEL_TOPLEVEL [=y])
---
Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_SND_SOC_AMD_RENOIR:
This option enables ACP support for Renoir platform
Symbol: SND_SOC_AMD_RENOIR [=n]
Type : tristate
Defined at sound/soc/amd/Kconfig:40
Prompt: AMD Audio Coprocessor - Renoir support
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && X86 [=y] && PCI [=y]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
---
CONFIG_SND_SOC_INTEL_EHL_RT5660_MACH:
This adds support for ASoC machine driver for Elkhart Lake
platform with RT5660 I2S audio codec.
Symbol: SND_SOC_INTEL_EHL_RT5660_MACH [=n]
Type : tristate
Defined at sound/soc/intel/boards/Kconfig:545
Prompt: EHL with RT5660 in I2S mode
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_MACH [=y] && SND_SOC_SOF_ELKHARTLAKE [=m] && I2C [=y] && ACPI [=y] && GPIOLIB [=y] && (MFD_INTEL_LPSS [=y] || COMPILE_TEST [=n]) && SND_HDA_CODEC_HDMI [=m] && SND_SOC_SOF_HDA_AUDIO_CODEC [=y]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> Intel Machine drivers (SND_SOC_INTEL_MACH [=y])
Selects: SND_SOC_RT5660 [=m] && SND_SOC_DMIC [=m]
---
CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH:
This adds support for ASoC machine driver for Intel platforms
with the Wolfson/Cirrus WM8804 I2S audio codec.
Say Y or m if you have such a device. This is a recommended option.
If unsure select "N".
Symbol: SND_SOC_INTEL_SOF_WM8804_MACH [=n]
Type : tristate
Defined at sound/soc/intel/boards/Kconfig:329
Prompt: SOF with Wolfson/Cirrus WM8804 codec
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_MACH [=y] && SND_SOC_SOF_APOLLOLAKE [=m] && I2C [=y] && ACPI [=y] && (MFD_INTEL_LPSS [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> Intel Machine drivers (SND_SOC_INTEL_MACH [=y])
Selects: SND_SOC_WM8804_I2C [=n]
---
CONFIG_SND_SOC_ZL38060:
Support for ZL38060 Connected Home Audio Processor from Microsemi,
which consists of a Digital Signal Processor (DSP), several Digital
Audio Interfaces (DAIs), analog outputs, and a block of 14 GPIOs.
Symbol: SND_SOC_ZL38060 [=n]
Type : tristate
Defined at sound/soc/codecs/Kconfig:1660
Prompt: Microsemi ZL38060 Connected Home Audio Processor
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SPI_MASTER [=y]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> CODEC drivers
Selects: GPIOLIB [=y] && REGMAP [=y]
Implied by [n]:
- SND_SOC_ALL_CODECS [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n]
---
Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Updates for the arm architectures for 5.11, some cleanups of general
Fedora arch configs.
Deletion of some old/obsolete configs. No functional changes to non
Fedora specific configs.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
The ARCH_BCM4908 option is in pending and fedora and disabled in both.
These SOCs are used in home WiFi routers and we won't currently support
them anywhere.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Build the Cadence USB3 controller for Arm, the Renasas PCI XHCI
controller as a module, minor other cleanups
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Only affects Fedora but all the AVS drivers have been moved
to SoC specific drivers so there's no functional change.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Don't set it in generic as enterprise never enabled v1 like
Fedora has has. Leave it on in Fedora for the time being
even though the libgpiod tools support v2.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
None of the Fedora architectures other than x86 support PCMCIA cards
and arm/s390 arches had already disabled the support, as had ARK in
general so move all the configs to reside in fedora/x86 as it's
config would actually be the only consumers of the drivers now.
No functional change to non Fedora configs.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
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_PTP_1588_CLOCK_OCP:
This driver adds support for an OpenCompute time card.
The OpenCompute time card is an atomic clock along with
a GPS receiver that provides a Grandmaster clock source
for a PTP enabled network.
More information is available at http://www.timingcard.com/
Symbol: PTP_1588_CLOCK_OCP [=n]
Type : tristate
Defined at drivers/ptp/Kconfig:154
Prompt: OpenCompute TimeCard as PTP clock
Depends on: PTP_1588_CLOCK [=y] && HAS_IOMEM [=y] && PCI [=y]
Location:
-> Device Drivers
-> PTP clock support
---
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_CRYPTO_DEV_HISI_TRNG:
Support for HiSilicon TRNG Driver.
Symbol: CRYPTO_DEV_HISI_TRNG [=n]
Type : tristate
Defined at drivers/crypto/hisilicon/Kconfig:75
Prompt: Support for HISI TRNG Driver
Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && ARM64 [=y] && ACPI [=y]
Location:
-> Cryptographic API (CRYPTO [=y])
-> Hardware crypto devices (CRYPTO_HW [=y])
Selects: HW_RANDOM [=y] && CRYPTO_RNG [=y]
---
CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4:
Support for Intel Keem Bay Offload and Crypto Subsystem (OCS) AES and
SM4 cihper hardware acceleration for use with Crypto API.
Provides HW acceleration for the following transformations:
cbc(aes), ctr(aes), ccm(aes), gcm(aes), cbc(sm4), ctr(sm4), ccm(sm4)
and gcm(sm4).
Optionally, support for the following transformations can also be
enabled: ecb(aes), cts(cbc(aes)), ecb(sm4) and cts(cbc(sm4)).
Symbol: CRYPTO_DEV_KEEMBAY_OCS_AES_SM4 [=n]
Type : tristate
Defined at drivers/crypto/keembay/Kconfig:1
Prompt: Support for Intel Keem Bay OCS AES/SM4 HW acceleration
Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && (OF [=y] || COMPILE_TEST [=n])
Location:
-> Cryptographic API (CRYPTO [=y])
-> Hardware crypto devices (CRYPTO_HW [=y])
Selects: CRYPTO_SKCIPHER [=y] && CRYPTO_AEAD [=y] && CRYPTO_ENGINE [=n]
---
CONFIG_CRYPTO_DEV_QAT_4XXX:
Support for Intel(R) QuickAssist Technology QAT_4xxx
for accelerating crypto and compression workloads.
To compile this as a module, choose M here: the module
will be called qat_4xxx.
Symbol: CRYPTO_DEV_QAT_4XXX [=n]
Type : tristate
Defined at drivers/crypto/qat/Kconfig:49
Prompt: Support for Intel(R) QAT_4XXX
Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && X86 [=y] && PCI [=y]
Location:
-> Cryptographic API (CRYPTO [=y])
-> Hardware crypto devices (CRYPTO_HW [=y])
Selects: CRYPTO_DEV_QAT [=m]
---
Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_XEN_PVHVM_GUEST:
Support running as a Xen PVHVM guest.
Symbol: XEN_PVHVM_GUEST [=y]
Type : bool
Defined at arch/x86/xen/Kconfig:62
Prompt: Xen PVHVM guest support
Depends on: HYPERVISOR_GUEST [=y] && XEN_PVHVM [=y] && PCI [=y]
Location:
-> Processor type and features
-> Linux guest support (HYPERVISOR_GUEST [=y])
-> Xen guest support (XEN [=y])
---
Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_STATIC_CALL_SELFTEST:
Boot time self-test of the call patching code.
Symbol: STATIC_CALL_SELFTEST [=n]
Type : bool
Defined at arch/Kconfig:109
Prompt: Static call selftest
Depends on: HAVE_STATIC_CALL [=y]
Location:
-> General architecture-dependent options
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_RTC_DRV_RV3032:
If you say yes here you get support for the Micro Crystal
RV3032.
This driver can also be built as a module. If so, the module
will be called rtc-rv3032.
Symbol: RTC_DRV_RV3032 [=n]
Type : tristate
Defined at drivers/rtc/Kconfig:672
Prompt: Micro Crystal RV3032
Depends on: RTC_CLASS [=y] && I2C [=y]
Location:
-> Device Drivers
-> Real Time Clock (RTC_CLASS [=y])
Selects: REGMAP_I2C [=m]
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
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_I2C_MLXBF:
Enabling this option will add I2C SMBus support for Mellanox BlueField
system.
This driver can also be built as a module. If so, the module will be
called i2c-mlxbf.
This driver implements an I2C SMBus host controller and enables both
master and slave functions.
Symbol: I2C_MLXBF [=n]
Type : tristate
Defined at drivers/i2c/busses/Kconfig:734
Prompt: Mellanox BlueField I2C controller
Depends on: I2C [=y] && HAS_IOMEM [=y] && ARM64 [=y]
Location:
-> Device Drivers
-> I2C support
-> I2C support (I2C [=y])
-> I2C Hardware Bus support
---
CONFIG_I2C_SLAVE_TESTUNIT:
This backend can be used to trigger test cases for I2C bus masters
which require a remote device with certain capabilities, e.g.
multi-master, SMBus Host Notify, etc. Please read
Documentation/i2c/slave-testunit-backend.rst for further details.
Symbol: I2C_SLAVE_TESTUNIT [=n]
Type : tristate
Defined at drivers/i2c/Kconfig:128
Prompt: I2C eeprom testunit driver
Depends on: I2C [=y] && I2C_SLAVE [=y]
Location:
-> Device Drivers
-> I2C support
-> I2C support (I2C [=y])
-> I2C slave support (I2C_SLAVE [=y])
---
Cc: Gopal Tiwari <gtiwari@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Enable CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL for both fedora and ARK.
This prevents a lot of uninitialized stack variable exploits, with a
minimal impact on performance.
This feature is incompatible with CONFIG_KASAN, so it can't be enabled
on debug kernels.
Also, it's mutually exclusive with CONFIG_INIT_STACK_NONE=y.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1856176
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
Enable CONFIG_GCC_PLUGINS on ARK so CONFIG_GCC_PLUGIN_STRUCTLEAK can be
enabled.
Fedora already has CONFIG_GCC_PLUGINS, so move it to the common
directory so it can be shared with ARK.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1856176
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
KASAN is useful for finding bugs. Enable it in the Fedora debug kernel
for x86 and arm64, for consistency with ARK.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1856176
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
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_SECCOMP_CACHE_DEBUG:
This enables the /proc/pid/seccomp_cache interface to monitor
seccomp cache data. The file format is subject to change. Reading
the file requires CAP_SYS_ADMIN.
This option is for debugging only. Enabling presents the risk that
an adversary may be able to infer the seccomp filter logic.
If unsure, say N.
Symbol: SECCOMP_CACHE_DEBUG [=n]
Type : bool
Defined at arch/Kconfig:520
Prompt: Show seccomp filter cache status in /proc/pid/seccomp_cache
Depends on: SECCOMP_FILTER [=y] && !HAVE_SPARSE_SYSCALL_NR [=n] && PROC_FS [=y]
Location:
-> General architecture-dependent options
-> Enable seccomp to safely execute untrusted bytecode (SECCOMP [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_KERNEL_ZSTD:
ZSTD is a compression algorithm targeting intermediate compression
with fast decompression speed. It will compress better than GZIP and
decompress around the same speed as LZO, but slower than LZ4. You
will need at least 192 KB RAM or more for booting. The zstd command
line tool is required for compression.
Symbol: KERNEL_ZSTD [=n]
Type : bool
Defined at init/Kconfig:282
Prompt: ZSTD
Depends on: <choice> && HAVE_KERNEL_ZSTD [=y]
Location:
-> General setup
-> Kernel compression mode (<choice> [=y])
Cc: Prarit Bhargava <prarit@redhat.com>
SC2001: See if you can use ${variable//search/replace} instead.
SC2046: Quote this to prevent word splitting.
SC2086: Double quote to prevent globbing and word splitting.
SC2162: read without -r will mangle backslashes.
SC2181: Check exit code directly with e.g. 'if mycmd;', not indirectly with $?.
Disable:
SC2010: Don't use ls | grep. Use a glob or a for loop with a condition to allow non-alphanumeric filenames.
as any alternative is worse, i.e. harder to understand. Filenames are known
to be well-formed (i.e. no blanks or special characters) in our situation.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2002: Useless cat. Consider 'cmd < file | ..' or 'cmd file | ..' instead.
SC2086: Double quote to prevent globbing and word splitting.
SC2196: egrep is non-standard and deprecated. Use grep -E instead.
SC2034: <variable; in this case, STAMP> appears unused.
Change to #!/bin/bash explicitly to allow
SC2039: bash-isms
Eliminate a couple of MS-DOS-era archaisms.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
Changes actually consist of disabling shellcheck on a few lines:
• SC2086: Double quote to prevent globbing and word splitting.
• SC2059: Don't use variables in the printf format string. Use printf...
For the former, in the two gitlab commands involved,
GITLAB_CONFIG_OPT DEPENDS on word splitting.
For the latter, the ShellCheck wiki actually recommend disabling the warning
because a multi-line pattern is in use and there is no good rewrite.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
Fix syntax flagged by shellcheck:
SC2086: Double quote to prevent globbing and word splitting.
(There is only one instance.)
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2162: read without -r will mangle backslashes
SC2086: Double quote to prevent globbing and word splitting
Rewrote main loop so it will work.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
merge-subtrees.h: fix
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2086: Double quote to prevent globbing and word splitting.
SC2145: Argument mixes string and array. Use * or separate argument.
SC2164: Use 'cd ... || exit' or 'cd ... || return' in case cd fails.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2231: Quote expansions in this for loop glob to prevent wordsplitting.
SC2086: Double quote to prevent globbing and word splitting.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2034: tree appears unused. Verify use (or export if used externally).
SC2035: Use ./*glob* or -- *glob* so names with dashes won't become options.
SC2086: Double quote to prevent globbing and word splitting.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2006: Use $(...) notation instead of legacy backticked `...`.
SC1083: This { is literal. Check expression (missing ;/\n?) or quote it.
SC2086: Double quote to prevent globbing and word splitting.
BUT:
Disable shellcheck on last step:
On the last step, we DEPEND on word splitting for correct interpretation
of XZ_OPTIONS and XZ_THREADS, so remove quotes and, just before the
xz step:
shellcheck disable=SC2086
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2086: Double quote to prevent globbing and word splitting.
Ignoring:
SC1091: Not following: /etc/os-release was not specified as input (see shellcheck -x).
SC2154: bootprefix is referenced but not assigned.
It is perfectly OK for bootprefix not to be assigned in this script.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2006: Use $(...) notation instead of legacy backticked `...`.
SC2013: To read lines rather than words, pipe/redirect to a 'while read' loop.
SC2086: Double quote to prevent globbing and word splitting.
SC2166: Prefer [ p ] && [ q ] as [ p -a q ] is not well defined.
EVEN BETTER: use [[ p || q ]]
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2007: Use $((..)) instead of deprecated $[..]
SC2086: Double quote to prevent globbing and word splitting.
SC2166: Prefer [ p ] || [ q ] as [ p -o q ] is not well defined.
EVEN BETTER: use [[ p || q ]].
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2068: Double quote array expansions to avoid re-splitting elements.
SC2086: Double quote to prevent globbing and word splitting.
SC2181: Check exit code directly with e.g. 'if mycmd;', not indirectly with $?.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2002: Useless cat. Consider 'cmd < file | ..' or 'cmd file | ..' instead.
SC2006: Use $(...) notation instead of legacy backticked `...`.
SC2086: Double quote to prevent globbing and word splitting.
SC2181: Check exit code directly with e.g. 'if mycmd;', not indirectly with $?.
Disable by changing to #!/bin/bash:
SC2039: In POSIX sh, echo flags are undefined.
SC2039: In POSIX sh, >& is undefined.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2039: In POSIX sh, == in place of = is undefined.
SC2086: Double quote to prevent globbing and word splitting.
Ignore:
SC2164: Use 'cd ... || exit' or 'cd ... || return' in case cd fails.
Also, change 'if..elif..else..fi' block to case..esac.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2006: Use $(...) notation instead of legacy backticked `...`.
SC2013: To read lines rather than words, pipe/redirect to a 'while read' loop. ???
SC2086: Double quote to prevent globbing and word splitting.
SC2144: -f doesn't work with globs. Use a for loop.
SC2155: Declare and assign separately to avoid masking return values. ???
SC2162: read without -r will mangle backslashes.
SC2236: Use -z instead of ! -n.
Disable:
SC2164: Use 'pushd ... || exit' or 'pushd ... || return' in case pushd fails.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2001: See if you can use ${variable//search/replace} instead.
SC2045: Iterating over ls output is fragile. Use globs.
SC2046: Quote this (command) to prevent word splitting.
SC2086: Double quote to prevent globbing and word splitting.
SC2162: read without -r will mangle backslashes.
SC2231: Quote expansions in this for loop glob to prevent wordsplitting, e.g. "$dir"/*.txt .
Also, change to #!/bin/bash so bash-isms won't be flagged, e.g.
SC2039: In POSIX sh, [[ ]] is undefined.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
The Speakup accessiblility driver is no longer in staging as of 5.9, and is a useful accessibility tool. This enables Speakup core, and all of the synth drivers which do not depend on ISA. More information can be found at http://www.linux-speakup.org/
Signed-off-by: Justin M. Forbes <jforbes@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_DEFAULT_INIT:
This option determines the default init for the system if no init=
option is passed on the kernel command line. If the requested path is
not present, we will still then move on to attempting further
locations (e.g. /sbin/init, etc). If this is empty, we will just use
the fallback list when init= is not passed.
Symbol: DEFAULT_INIT [=]
Type : string
Defined at init/Kconfig:267
Prompt: Default init path
Location:
-> General setup
Cc: Prarit Bhargava <prarit@redhat.com>
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_PINCTRL_ALDERLAKE:
This pinctrl driver provides an interface that allows configuring
of Intel Alder Lake PCH pins and using them as GPIOs.
Symbol: PINCTRL_ALDERLAKE [=n]
Type : tristate
Defined at drivers/pinctrl/intel/Kconfig:58
Prompt: Intel Alder Lake pinctrl and GPIO driver
Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINCTRL_INTEL [=y]
---
CONFIG_PINCTRL_ELKHARTLAKE:
This pinctrl driver provides an interface that allows configuring
of Intel Elkhart Lake SoC pins and using them as GPIOs.
Symbol: PINCTRL_ELKHARTLAKE [=n]
Type : tristate
Defined at drivers/pinctrl/intel/Kconfig:98
Prompt: Intel Elkhart Lake SoC pinctrl and GPIO driver
Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINCTRL_INTEL [=y]
---
CONFIG_PINCTRL_LAKEFIELD:
This pinctrl driver provides an interface that allows configuring
of Intel Lakefield SoC pins and using them as GPIOs.
Symbol: PINCTRL_LAKEFIELD [=n]
Type : tristate
Defined at drivers/pinctrl/intel/Kconfig:138
Prompt: Intel Lakefield SoC pinctrl and GPIO driver
Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINCTRL_INTEL [=y]
---
CONFIG_PINCTRL_LPASS_LPI:
This is the pinctrl, pinmux, pinconf and gpiolib driver for the
Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI
(Low Power Island) found on the Qualcomm Technologies Inc SoCs.
Symbol: PINCTRL_LPASS_LPI [=n]
Type : tristate
Defined at drivers/pinctrl/qcom/Kconfig:268
Prompt: Qualcomm Technologies Inc LPASS LPI pin controller driver
Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINMUX [=n] && PINCONF [=y] && GENERIC_PINCONF [=y]
---
CONFIG_PINCTRL_MICROCHIP_SGPIO:
Support for the serial GPIO interface used on Microsemi and
Microchip SoC's. By using a serial interface, the SIO
controller significantly extends the number of available
GPIOs with a minimum number of additional pins on the
device. The primary purpose of the SIO controller is to
connect control signals from SFP modules and to act as an
LED controller.
Symbol: PINCTRL_MICROCHIP_SGPIO [=n]
Type : bool
Defined at drivers/pinctrl/Kconfig:378
Prompt: Pinctrl driver for Microsemi/Microchip Serial GPIO
Depends on: PINCTRL [=y] && OF [=y] && HAS_IOMEM [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: GPIOLIB [=y] && GPIOLIB_IRQCHIP [=y] && GENERIC_PINCONF [=y] && GENERIC_PINCTRL_GROUPS [=n] && GENERIC_PINMUX_FUNCTIONS [=n] && OF_GPIO [=y]
---
Cc: Brian Masney <bmasney@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_CHELSIO_TLS_DEVICE:
This flag enables support for kernel tls offload over Chelsio T6
crypto accelerator. CONFIG_CHELSIO_TLS_DEVICE flag can be enabled
only if CONFIG_TLS and CONFIG_TLS_DEVICE flags are enabled.
Symbol: CHELSIO_TLS_DEVICE [=y]
Type : bool
Defined at drivers/crypto/chelsio/Kconfig:46
Prompt: Chelsio Inline KTLS Offload
Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && CHELSIO_T4 [=m] && TLS_DEVICE [=y]
Location:
-> Cryptographic API (CRYPTO [=y])
-> Hardware crypto devices (CRYPTO_HW [=y])
Selects: CRYPTO_DEV_CHELSIO [=m]
Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
V2: Update CONFIG_CHELSIO_TLS_DEVICE to =m because inline is not allowed.
All configs enable ENERGY_MODEL so just enable it in generic
and remove the duplicates.
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
CC: Phil Auld <pauld@redhat.com>
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_VIDEO_CCS:
This is a generic driver for MIPI CCS, SMIA++ and SMIA compliant
camera sensors.
Symbol: VIDEO_CCS [=n]
Type : tristate
Defined at drivers/media/i2c/ccs/Kconfig:2
Prompt: MIPI CCS/SMIA++/SMIA sensor support
Depends on: MEDIA_SUPPORT [=m] && I2C [=y] && VIDEO_V4L2 [=m] && HAVE_CLK [=y]
Visible if: MEDIA_SUPPORT [=m] && I2C [=y] && VIDEO_V4L2 [=m] && HAVE_CLK [=y] && MEDIA_CAMERA_SUPPORT [=y]
Location:
-> Device Drivers
-> Multimedia support (MEDIA_SUPPORT [=m])
-> Media ancillary drivers
-> Camera sensor devices
Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && VIDEO_CCS_PLL [=n] && V4L2_FWNODE [=n]
---
CONFIG_VIDEO_OV02A10:
This is a Video4Linux2 sensor driver for the OmniVision
OV02A10 camera.
To compile this driver as a module, choose M here: the
module will be called ov02a10.
Symbol: VIDEO_OV02A10 [=n]
Type : tristate
Defined at drivers/media/i2c/Kconfig:828
Prompt: OmniVision OV02A10 sensor support
Depends on: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y]
Visible if: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y] && MEDIA_CAMERA_SUPPORT [=y]
Location:
-> Device Drivers
-> Multimedia support (MEDIA_SUPPORT [=m])
-> Media ancillary drivers
-> Camera sensor devices
Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && V4L2_FWNODE [=n]
---
CONFIG_VIDEO_OV9734:
This is a Video4Linux2 sensor driver for the OmniVision
OV9734 camera.
To compile this driver as a module, choose M here: the
module's name is ov9734.
Symbol: VIDEO_OV9734 [=n]
Type : tristate
Defined at drivers/media/i2c/Kconfig:1067
Prompt: OmniVision OV9734 sensor support
Depends on: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y] && (ACPI [=y] || COMPILE_TEST [=n])
Visible if: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y] && (ACPI [=y] || COMPILE_TEST [=n]) && MEDIA_CAMERA_SUPPORT [=y]
Location:
-> Device Drivers
-> Multimedia support (MEDIA_SUPPORT [=m])
-> Media ancillary drivers
-> Camera sensor devices
Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && V4L2_FWNODE [=n]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_PCIE_HISI_ERR:
Say Y here if you want error handling support
for the PCIe controller's errors on HiSilicon HIP SoCs
Symbol: PCIE_HISI_ERR [=n]
Type : bool
Defined at drivers/pci/controller/Kconfig:301
Prompt: HiSilicon HIP PCIe controller error handling driver
Depends on: PCI [=y] && ACPI_APEI_GHES [=y] && (ARM64 [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> PCI support (PCI [=y])
-> PCI controller drivers
---
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_ARM64_ERRATUM_1508412:
This option adds a workaround for Arm Cortex-A77 erratum 1508412.
Affected Cortex-A77 cores (r0p0, r1p0) could deadlock on a sequence
of a store-exclusive or read of PAR_EL1 and a load with device or
non-cacheable memory attributes. The workaround depends on a firmware
counterpart.
KVM guests must also have the workaround implemented or they can
deadlock the system.
Work around the issue by inserting DMB SY barriers around PAR_EL1
register reads and warning KVM users. The DMB barrier is sufficient
to prevent a speculative PAR_EL1 read.
If unsure, say Y.
Symbol: ARM64_ERRATUM_1508412 [=y]
Type : bool
Defined at arch/arm64/Kconfig:639
Prompt: Cortex-A77: 1508412: workaround deadlock on sequence of NC/Device load and store exclusive or PAR read
Location:
-> Kernel Features
-> ARM errata workarounds via the alternatives framework
---
Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
In file included from scripts/sorttable.c:191:
scripts/sorttable.h:89:10: fatal error: asm/orc_types.h: No such file or directory
89 | #include <asm/orc_types.h>
| ^~~~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [scripts/Makefile.host:103: scripts/sorttable] Error 1
make: *** [Makefile:1155: scripts] Error 2
Signed-off-by: Paulo E. Castro <pecastro@wormholenet.com>
Enabling kheaders module that carries kernel headers
to compile eBPF programs and will allow bcc-tools rpm
to get rid of kernel-devel dependency.
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
Closes: #34
Long ago, we needed the ability to filter out files and directories
from patches. Now that ability is built into git a few years ago,
let's use that instead of filterdiff.
One less tool to depend on and require.
V2: rebase and fix conflicts
Cc: Bastien Nocera <bnocera@redhat.com>
Cc: Herton Krzesinski <hkrzesin@redhat.com>
Signed-off-by: Don Zickus <dzickus@redhat.com>
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_RD_ZSTD:
Support loading of a ZSTD encoded initial ramdisk or cpio buffer.
If unsure, say N.
Symbol: RD_ZSTD [=y]
Type : bool
Defined at usr/Kconfig:103
Prompt: Support initial ramdisk/ramfs compressed using ZSTD
Depends on: BLK_DEV_INITRD [=y]
Location:
-> General setup
-> Initial RAM filesystem and RAM disk (initramfs/initrd) support (BLK_DEV_INITRD [=y])
Selects: DECOMPRESS_ZSTD [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_NET_ACT_GATE:
Say Y here to allow to control the ingress flow to be passed at
specific time slot and be dropped at other specific time slot by
the gate entry list.
If unsure, say N.
To compile this code as a module, choose M here: the
module will be called act_gate.
Symbol: NET_ACT_GATE [=n]
Type : tristate
Defined at net/sched/Kconfig:984
Prompt: Frame gate entry list control tc action
Depends on: NET [=y] && NET_SCHED [=y] && NET_CLS_ACT [=y]
Location:
-> Networking support (NET [=y])
-> Networking options
-> QoS and/or fair queueing (NET_SCHED [=y])
-> Actions (NET_CLS_ACT [=y])
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Xin Long <lxin@redhat.com>
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_USB_XHCI_PCI_RENESAS:
Say 'Y' to enable the support for the Renesas xHCI controller with
firwmare. Make sure you have the firwmare for the device and
installed on your system for this device to work.
If unsure, say 'N'.
Symbol: USB_XHCI_PCI_RENESAS [=n]
Type : tristate
Defined at drivers/usb/host/Kconfig:46
Prompt: Support for additional Renesas xHCI controller with firwmare
Depends on: USB_SUPPORT [=y] && USB [=y] && USB_XHCI_HCD [=y]
Location:
-> Device Drivers
-> USB support (USB_SUPPORT [=y])
-> xHCI HCD (USB 3.0) support (USB_XHCI_HCD [=y])
---
Cc: Torez Smith <torez@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_MFD_INTEL_PMC_BXT:
This driver provides support for the PMC (Power Management
Controller) on Intel Broxton and Apollo Lake. The PMC is a
multi-function device that exposes IPC, General Control
Register and P-unit access. In addition this creates devices
for iTCO watchdog and telemetry that are part of the PMC.
Symbol: MFD_INTEL_PMC_BXT [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:650
Prompt: Intel PMC Driver for Broxton
Depends on: HAS_IOMEM [=y] && X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: INTEL_SCU_IPC [=n] && MFD_CORE [=y]
Cc: Torez Smith <torez@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
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_MFD_MP2629:
Select this option to enable support for Monolithic Power Systems
battery charger. This provides ADC, thermal and battery charger power
management functions.
Symbol: MFD_MP2629 [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:452
Prompt: Monolithic Power Systems MP2629 ADC and Battery charger
Depends on: HAS_IOMEM [=y] && I2C [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: REGMAP_I2C [=m]
Cc: Torez Smith <torez@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
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_EFI_CUSTOM_SSDT_OVERLAYS:
Allow loading of an ACPI SSDT overlay from an EFI variable specified
by a kernel command line option.
See Documentation/admin-guide/acpi/ssdt-overlays.rst for more
information.
Symbol: EFI_CUSTOM_SSDT_OVERLAYS [=y]
Type : bool
Defined at drivers/firmware/efi/Kconfig:282
Prompt: Load custom ACPI SSDT overlay from an EFI variable
Depends on: EFI_VARS [=y] && ACPI [=y]
Location:
-> Firmware Drivers
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
For quite some time, the parallel_xz.sh script has been hanging up
builds in koji. While it may be a benefit to get this fixed, it is much
better to back that change out in the short term. This reverts us to
the way that Fedora used to compress the modules.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
To avoid warnings during dist-configs we need to explicitly set a value for
this options, which should be disabled.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
Both CONFIG_EVM_LOAD_X509 and CONFIG_EVM_X509_PATH are complementary and
should be enabled. It behaves in the same way as the x509 certificates on
IMA, which can be added to '.evm' keyring once they are signed with a
trusted key placed in the '.platform_keyring'.
And, as dependency, CONFIG_ENCRYPTED_KEYS must be also set to =y in all
arches.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
Make it default to all arches on ARK. x86_64 and powerpc already had it
enabled, and keep it disabled elsewhere.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
The same way IMA should be enabled in all arches, EVM also should be.
EVM is independent, but also complementary, from IMA.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
Both options CONFIG_IMA_LOAD_X509 and CONFIG_IMA_X509_PATH are complementary
and should be enabled for all ARK flavors: IBM requested it for powerpc some
time ago on RHEL and others arches should be in sync.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
x86 and powerpc have this config to let IMA know it can check for secure
and/or trusted boot state during runtime, allowing other features to be
initialized.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
Fedora and ARK uses different IMA templates, and that's fine, but the
templates should be kept the same across arches in the same flavor (ARK in
this case).
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
IMA default hash was already defaulted to SHA256 on Fedora.
It's time to make it the default for all arches in ARK too.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
CONFIG_IMA_DEFAULT_HASH_SHA1 is already disabled for all Fedora arches and
ARK should also drop it and use SHA256 instead.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
Upstream kernel supports specific architecture IMA policies and has been
requested by IBM on RHEL. With that, enable it on ARK and Fedora too.
Two another options: PPC_SECURE_BOOT and PPC_SECVAR_SYSFS, are brought as
dependency for IMA_ARCH_POLICY on PPC.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
Fedora was already enabling it to all arches. ARK had it only disabled for
aarch64 because this arch hand't INTEGRITY subsystem enabled. This patch
only make it enabled for all arches and flavors and remove the
pending-common/ referent file.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
CONFIG_IMA_APPRAISE_BOOTPARAM was enabled for all Fedora flavor arches. It's
now also being enabled for all ARK supported arches, with that, enable it
by default in all arches and flavors.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
It's one of the basic operations offered by IMA, there isn't any reason to
keep it disabled. Make it enabled by default in all flavors and arches.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
It was disabled when RHEL was experimenting AARCH64 and was left in that way
since then. There is no good reason for keep it disabled on aarch64
architecture today.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
Check via 'test -x' whether /usr/bin/shellcheck is present; if not,
skip the test and print a message.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
1003-rpminspect.bats: initial commit.
Like the 1001-rpmlint.bats test, this test
• tests for exactly one SRPM
• runs rpminspect (instead of rpmlint) on that SRPM,
after checking for the presence of the /usr/bin/rpminspect.
Both 1001-rpmlint.bats and 1003-rpminspect.bats
Check via 'test -x' whether the /usr/bin/rpmlint or rpminspect,
respectively, is installed; if not, skip the test and print a message.
For now, skip both tests entirely, pending fixes to kernel.spec.template.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
• Makefile:
Create new dist-dump-variables target for dynamically deriving variables
from Makefile.common and dumping them.
Create new dist-clean-scripts target to clean up generated scripts.
Create new dist-self-test target and hook up the BATS
self tests. Check for the presence of /usr/bin/bats
(via 'test -x') and complain if it is not installed.
Add a description of the new dist-self-test target to dist-full-help.
• Makefile.common: make HEAD an overridable variable.
Change
GITID:= $(shell $(GIT) log --max-count=1 --pretty=format:%H)
to
GITID:= $(shell $(GIT) log --max-count=1 --pretty=format:%H $(HEAD))
making the argument to 'git log' explicit and allowing it to be
overridden by, e.g., self-tests.
• self-test/egit.sh: Initial commit
This is a sample script providing a thin layer over the git command.
It is meant to substitute in redhat/Makefile and Makefile.common via the
GIT macro defined in Makefile.
Each git subcommand currently used by Makefile and Makefile.common can
be broken out into its own case. At the moment, the output of
'git describe' can be overridden by means of an
environment variable, EGIT_OVERRIDE_DESCRIBE.
Use case: self test with test values for 'git describe'.
Other git subcommands are simply passed through.
Usage:
GIT=<path to egit.sh> EGIT_OVERRIDE_DESCRIBE=v5.9-rc8 DIST=.elrdy make dist-srpm
• self-test/1005-dist-dump-variables.bats: initial commit
The four tests in 1005-dist-dump-variables.bats test the RPM version
generation, name generation, and snapshot designation for several
previously chosen tags/commits.
The tags/commits chosen are:
a) v5.8
b) v5.8-rc7
c) v5.8-9-g565674d613d7
d) v5.8-rc5-99-g25ccd24ffd91
and the expected results are:
a) RPMVERSION = 5.8.0, no rc
b) RPMVERSION = 5.8.0, .rc7
c) RPMVERSION = 5.9.0, .rc0, snapshot
d) RPMVERSION = 5.8.0, .rc5, snapshot
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
GIT ?= git
and replace literal occurrences of 'git' with $(GIT).
This change enables us to override 'git' with, e.g., some
arbitrary shell script that prints additional information
and/or does additional processing before and/or after (or
even instead of) invoking /usr/bin/git.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
Coresight is a hardware assisted debug and trace technology.
Now that 5.10 allows them to be built as modules lets
enable the functionality in fedora.
More information about coresight may be found here:
https://developer.arm.com/ip-products/system-ip/coresight-debug-and-trace
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
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_INET6_ESPINTCP:
Support for RFC 8229 encapsulation of ESP and IKE over
TCP/IPv6 sockets.
If unsure, say N.
Symbol: INET6_ESPINTCP [=n]
Type : bool
Defined at net/ipv6/Kconfig:91
Prompt: IPv6: ESP in TCP encapsulation (RFC 8229)
Depends on: NET [=y] && INET [=y] && IPV6 [=y] && XFRM [=y] && INET6_ESP [=m]
Location:
-> Networking support (NET [=y])
-> Networking options
-> TCP/IP networking (INET [=y])
-> The IPv6 protocol (IPV6 [=y])
-> IPv6: ESP transformation (INET6_ESP [=m])
Selects: STREAM_PARSER [=y] && NET_SOCK_MSG [=y] && XFRM_ESPINTCP [=y]
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Move CONFIG_RTC_NVMEM to common so Fedora is enabled and the same as ARK kernels.
No changes to ARK kernels
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
This option is needed to allow the latest features of bpftool
to compile correctly. Currently it was disabled because of
a gcc bug around DWARF info. That has been resolved with the
latest gcc and/or dwarves package. Re-enable.
Signed-off-by: Don Zickus <dzickus@redhat.com>
V2: Add dwarves BuildRequires to eln
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_BACKLIGHT_LED:
If you have a LCD backlight adjustable by LED class driver, say Y
to enable this driver.
Symbol: BACKLIGHT_LED [=n]
Type : tristate
Defined at drivers/video/backlight/Kconfig:459
Prompt: Generic LED based Backlight Driver
Depends on: HAS_IOMEM [=y] && BACKLIGHT_CLASS_DEVICE [=y] && LEDS_CLASS [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Backlight & LCD device support
-> Lowlevel Backlight controls (BACKLIGHT_CLASS_DEVICE [=y])
Lyude isn't aware of anything that uses this currently, but noted that
that it's likely it will be needed for newer laptops and so recommended
"m".
---
Cc: Lyude Paul <lyude@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
XBox 360 and XBox One controllers are very common as PC joypads.
iOS, macOS, Android and Windows all support those joypads out of the
box, so Fedora should too.
There's a bunch of interest around various phones ATM such as the Librem 5
so enable the options that are upstream.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
The kernel changelog which is created also have a wrong release number eg.:
...
+RHEL_RELEASE = 69
--- a/redhat/kernel.changelog-8.99
+++ b/redhat/kernel.changelog-8.99
@@ -1,3 +1,7 @@
+* Wed Nov 11 2020 Fedora Kernel Team <kernel-team@fedoraproject.org> [5.10.0-0.rc3.20201111giteccc87672492.68.test]
...
That's because of stale data/changelog which is created before the release
bump is done. We need to revert changes and recreate the changelog after
the diff-index check and release bump, so we get the updated number and do
not have a duplicate changelog entry.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
The git diff-index has a catch which you must pay attention, if you eg.
do this:
touch redhat/Makefile
git diff-index HEAD
It'll show there is a change even if contents didn't change. This makes
the current logic to not work since we may not really have changed the
contents, but the redirection will act similar as a touch on those files.
We need to run update-index before it so diff-index check works properly.
Also, the "exit 0" was not working as intended, and the Makefile commands
after the check were still running, thus I changed the code to use an if
conditional to make it work.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
The first release commit was always being created with the test
suffix because the default is to append ".test" if there is no
localversion or BUILDID given to dist-release. Move up the touch
localversion so we avoid it.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
When doing dist-release, the release commit will have the wrong release
number, eg.:
commit db61196cc6aab3f6ece65027551ebfb2f5edea90
...
[redhat] kernel-5.10.0-0.rc3.20201111giteccc87672492.69.test
...
-RHEL_RELEASE = 69
+RHEL_RELEASE = 70
...
While the new release is 70 in example above, the commit title has the wrong
value. That mismatch happens because the release number is a Makefile.rhelver
variable included and used by make rules, and make doesn't see the updated
value, you need to eg. reload it through a sub make process. This change adds
a new rule and new make invocation so the proper RHEL_RELEASE value is used when
doing the release commit.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Enable Intel Shared Virtual Memory config option. Since it is already
enabled for Fedora, move it to common/x86/x86_64 to enable it
for both RHEL and Fedora.
Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>
While debugging LTO issues, I disabled kernel-selftests
temporarily. This exposed an issue in turbostat that
required libcap to compile. Add the BuildRequires to
the spec file.
I don't expect this scenario to happen at all. This
fix is for completeness and less headaches in the future.
Signed-off-by: Don Zickus <dzickus@redhat.com>
For CKI and its cross-compile environment, it can not cross
compile userspace tools. Instead we will native compiles them.
To allow this split, the kernel.spec needs to support only
building userspace stuff and not the kernel itself.
However the userspace tools need some vars defined. This
patch creates a new function and sets up those vars.
Also very useful for debugging userspace tools and skipping
the hour long kernel build times (like LTO).
To use this effectively, one would use
--without_up
--without_debug
--without_zfcpdump
Original author is Brian Masney <bmasney@redhat.com>, which
I took from his RHEL-8 contribution. His original changelog
The kernel.spec file initializes the .config file and Arch variable
in the BuildKernel() function. This works fine when the user space
tools are built at the same time as the kernel, however this fails
when attempting to build the user space tools in isolation.
Specifically, this fails when debug, zfcpdump, and up are all
disabled. The kernel-tools and kernel-selftests packages fail to
build.
Let's fix this by adding a new function InitBuildKernel() that
initializes a kernel build. This function is called when debug,
zfcpdump, and up are all disabled.
V2: Fix inline comment and add original changelog.
Cc: Brian Masney <bmasney@redhat.com>
Signed-off-by: Don Zickus <dzickus@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1821565
Upstream Status: 2a379716f3
kexec_file_load() syscall interface is now supported for
arm64 architecture as well via upstream commits:
3751e728ce ("arm64: kexec_file: add crash dump support") and
3ddd9992a5 ("arm64: enable KEXEC_FILE config")].
This patch enables config KEXEC_FILE by default in the fedora
arm64 defconfig, so that user-space tools like kexec-tools
can use the same as the default interface for kexec/kdump
on arm64 fedora systems.
Cc: kernel-team@fedoraproject.org
Signed-off-by: Bhupesh Sharma <bhsharma@redhat.com>
Sending new version, previous version not acked.
P.
--8<--
dzickus pointed out that my change is not optimal. CONFIG_CRYPTO_SHA512
can be moved to the common/generic directory since it is enabled on
both Fedora and ARK.
Cleanup the CONFIG_CRYPTO_SHA512 files.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: dzickus@redhat.com
Cc: jforbes@redhat.com
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.
Cc: Torez Smith <torez@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
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_TYPEC_QCOM_PMIC:
Driver for supporting role switch over the Qualcomm PMIC. This will
handle the USB Type-C role and orientation detection reported by the
QCOM PMIC if the PMIC has the capability to handle USB Type-C
detection.
It will also enable the VBUS output to connected devices when a
DFP connection is made.
Symbol: TYPEC_QCOM_PMIC [=n]
Type : tristate
Defined at drivers/usb/typec/Kconfig:88
Prompt: Qualcomm PMIC USB Type-C driver
Depends on: USB_SUPPORT [=y] && TYPEC [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> USB support (USB_SUPPORT [=y])
-> USB Type-C Support (TYPEC [=y])
---
CONFIG_TYPEC_STUSB160X:
Say Y or M here if your system has STMicroelectronics STUSB160x
Type-C port controller.
If you choose to build this driver as a dynamically linked module, the
module will be called stusb160x.ko.
Symbol: TYPEC_STUSB160X [=n]
Type : tristate
Defined at drivers/usb/typec/Kconfig:76
Prompt: STMicroelectronics STUSB160x Type-C controller driver
Depends on: USB_SUPPORT [=y] && TYPEC [=y] && I2C [=y] && REGMAP_I2C [=m] && (USB_ROLE_SWITCH [=m] || !USB_ROLE_SWITCH [=m])
Location:
-> Device Drivers
-> USB support (USB_SUPPORT [=y])
-> USB Type-C Support (TYPEC [=y])
---
CONFIG_TYPEC_TCPCI_MAXIM:
MAXIM TCPCI based Type-C/PD chip driver. Works with
with Type-C Port Controller Manager.
Symbol: TYPEC_TCPCI_MAXIM [=n]
Type : tristate
Defined at drivers/usb/typec/tcpm/Kconfig:38
Prompt: Maxim TCPCI based Type-C chip driver
Depends on: USB_SUPPORT [=y] && TYPEC [=y] && TYPEC_TCPM [=m] && TYPEC_TCPCI [=m]
Location:
-> Device Drivers
-> USB support (USB_SUPPORT [=y])
-> USB Type-C Support (TYPEC [=y])
-> USB Type-C Port Controller Manager (TYPEC_TCPM [=m])
-> Type-C Port Controller Interface driver (TYPEC_TCPCI [=m])
---
CONFIG_USB_FEW_INIT_RETRIES:
When a new USB device is detected, the kernel tries very hard
to initialize and enumerate it, with lots of nested retry loops.
This almost always works, but when it fails it can take a long time.
This option tells the kernel to make only a few retry attempts,
so that the total time required for a failed initialization is
no more than 30 seconds (as required by the USB OTG spec).
Say N here unless you require new-device enumeration failure to
occur within 30 seconds (as might be needed in an embedded
application).
Symbol: USB_FEW_INIT_RETRIES [=n]
Type : bool
Defined at drivers/usb/core/Kconfig:35
Prompt: Limit USB device initialization to only a few retries
Depends on: USB_SUPPORT [=y] && USB [=y]
Location:
-> Device Drivers
-> USB support (USB_SUPPORT [=y])
---
Cc: Torez Smith <torez@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_XFRM_USER_COMPAT:
Transformation(XFRM) user configuration interface like IPsec
used by compatible Linux applications.
If unsure, say N.
Symbol: XFRM_USER_COMPAT [=n]
Type : tristate
Defined at net/xfrm/Kconfig:31
Prompt: Compatible ABI support
Depends on: NET [=y] && INET [=y] && XFRM_USER [=y] && COMPAT_FOR_U64_ALIGNMENT [=y] && HAVE_EFFICIENT_UNALIGNED_ACCESS [=y]
Location:
-> Networking support (NET [=y])
-> Networking options
-> Transformation user configuration interface (XFRM_USER [=y])
Selects: WANT_COMPAT_NETLINK_MESSAGES [=n]
---
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_RCU_SCALE_TEST:
This option provides a kernel module that runs performance
tests on the RCU infrastructure. The kernel module may be built
after the fact on the running kernel to be tested, if desired.
Say Y here if you want RCU performance tests to be built into
the kernel.
Say M if you want the RCU performance tests to build as a module.
Say N if you are unsure.
Symbol: RCU_SCALE_TEST [=n]
Type : tristate
Defined at kernel/rcu/Kconfig.debug:26
Prompt: performance tests for RCU
Depends on: DEBUG_KERNEL [=y]
Location:
-> Kernel hacking
-> RCU Debugging
Selects: TORTURE_TEST [=n] && SRCU [=y] && TASKS_RCU [=n] && TASKS_RUDE_RCU [=y] && TASKS_TRACE_RCU [=y]
---
Cc: Waiman Long <longman@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_QCOM_CPR:
Say Y here to enable support for the CPR hardware found on Qualcomm
SoCs like QCS404.
This driver populates CPU OPPs tables and makes adjustments to the
tables based on feedback from the CPR hardware. If you want to do
CPUfrequency scaling say Y here.
To compile this driver as a module, choose M here: the module will
be called qcom-cpr
Symbol: QCOM_CPR [=n]
Type : tristate
Defined at drivers/soc/qcom/Kconfig:29
Prompt: QCOM Core Power Reduction (CPR) support
Depends on: ARCH_QCOM [=y] && HAS_IOMEM [=y]
Location:
-> Device Drivers
-> SOC (System On Chip) specific Drivers
-> Qualcomm SoC drivers
Selects: PM_OPP [=n] && REGMAP [=y]
---
Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
There are two parts to this fix. One is using the recommended way
to disable LTO. The other is to make it work for the kernel.spec
file.
Various kernel-tool programs (like perf) can not handle LTO yet, so
they are disabled.
This is done with '%define _lto_cflags {nil}'.
However that doesn't quite work for the kernel for the %install
section. It works for the %build section.
Oddly, back at the birth of dist-git, the initial kernel.spec
file was imported with a line at the top
%global __spec_install_pre %{___build_pre}
For whatever reason, the kernel was deemed special and that line
pre-built the %install scripts _before_ the lto_cflags could
dynamically be disabled.
Moving the _lto_cflags line above the _pre line disables LTO for both the
%build and %install sections of the spec file successfully.
However, because that _pre line is unintiutive and caused hours
of debugging headache, I hacked up the output to see what the
%__spec_install_pre and ___build_pre looked like at the
beginning of the %install section. The idea was __build_pre
is what we want going forward.
Unfortunately, after examining the results, I learned the %install
section expects a clean RPM_BUILD_ROOT. But the kernel %build
section puts each compiled variant into the RPM_BUILD_ROOT as
it completes. Thus is gets removed on %install setup. So the
%__spec_install_pre line has to stay.
Instead I add a bunch of comments explaining why it is necessary
and where to add changes like _lto_cflags. This hopefully
reduces headaches in the future.
V2: restore __spec_install_pre line and add comments.
Cc: Jeff Law <law@redhat.com>
Signed-off-by: Don Zickus <dzickus@redhat.com>
The existing call for pathfix.py fails because
scripts/gen_compile_commands.py is no longer present. It has been moved
to scripts/clang-tools and another script has been added there as well,
so fix up the directory.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
The functionality has been deprecated upstream, so let's disable it
procatively in Fedora to not delay the inevitable. We are ready to
inherit this in RHEL-9, so do the change directly in
redhat/configs/common.
Quoting basic information from the Fedora change proposal [1]:
"""
Currently, SELinux can be disabled using selinux=0 on the kernel command
line, or in userspace via /etc/selinux/config. In the latter case,
/etc/selinux/config is read by libselinux userspace library during boot
and if it contains SELINUX=disabled, it writes 1 into
/sys/fs/selinux/disable and unmounts /sys/fs/selinux.
Support for SELinux runtime disable via /etc/selinux/config was
originally developed to make it easier for Linux distributions to
support architectures where adding parameters to the kernel command line
was difficult. Unfortunately, supporting runtime disable meant we had to
make some security trade-offs when it comes to the kernel LSM hooks.
Marking the kernel LSM hooks as read only provides some very nice
security benefits, but it does mean that we can no longer disable
SELinux at runtime. Toggling between enforcing and permissive mode while
booted will remain unaffected and it will still be possible to disable
SELinux by adding selinux=0 to the kernel command line via the boot
loader (GRUB).
System with SELINUX=disabled in /etc/selinux/config will come up with
/sys/fs/selinux unmounted, userspace will detect SELinux as disabled.
Internally SELinux will be enabled but not initialized so that there
will be no SELinux checks applied. This state is very similar to SELinux
disabled - the hooks are active, but they mostly do almost nothing so
there should be very little effect on the time spent in syscalls
compared to SELinux fully disabled.
Runtime disable is considered deprecated by upstream, and using it will
become increasingly painful (e.g. sleeping/blocking) through future
kernel releases until eventually it is removed completely. Current
kernel reports the following message during runtime disable:
SELinux: Runtime disable is deprecated, use selinux=0 on the kernel
cmdline
Additional info:
* https://lwn.net/Articles/666550
* https://lore.kernel.org/selinux/159110207843.57260.5661475689740939480.stgit@chester/
* https://lore.kernel.org/selinux/157836784986.560897.13893922675143903084.stgit@chester/#t
"""
[1] https://fedoraproject.org/wiki/Changes/Remove_Support_For_SELinux_Runtime_Disable
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
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_PHY_INTEL_KEEMBAY_EMMC:
Choose this option if you have an Intel Keem Bay SoC.
To compile this driver as a module, choose M here: the module
will be called phy-keembay-emmc.ko.
Symbol: PHY_INTEL_KEEMBAY_EMMC [=n]
Type : tristate
Defined at drivers/phy/intel/Kconfig:5
Prompt: Intel Keem Bay EMMC PHY driver
Depends on: (OF [=y] && ARM64 [=y] || COMPILE_TEST [=n]) && HAS_IOMEM [=y]
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=y] && REGMAP_MMIO [=y]
---
CONFIG_PHY_INTEL_LGM_EMMC:
Enable this to support the Intel EMMC PHY
Symbol: PHY_INTEL_LGM_EMMC [=n]
Type : tristate
Defined at drivers/phy/intel/Kconfig:31
Prompt: Intel Lightning Mountain EMMC PHY driver
Depends on: X86 [=y] || COMPILE_TEST [=n]
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=n]
---
CONFIG_USB_LGM_PHY:
Enable this to support Intel DWC3 PHY USB phy. This driver provides
interface to interact with USB GEN-II and USB 3.x PHY that is part
of the Intel network SOC.
Symbol: USB_LGM_PHY [=n]
Type : tristate
Defined at drivers/phy/Kconfig:52
Prompt: INTEL Lightning Mountain USB PHY Driver
Depends on: USB_SUPPORT [=y]
Location:
-> Device Drivers
-> PHY Subsystem
Selects: USB_PHY [=n] && REGULATOR [=n] && REGULATOR_FIXED_VOLTAGE [=n]
---
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_HISI_HIKEY_USB:
If you say yes here this adds support for the on-board USB GPIO hub
found on HiKey 960/970 boards, which is necessary to support
switching between the dual-role USB-C port and the USB-A host ports
using only one USB controller.
Symbol: HISI_HIKEY_USB [=n]
Type : tristate
Defined at drivers/misc/Kconfig:459
Prompt: USB GPIO Hub on HiSilicon Hikey 960/970 Platform
Depends on: (OF [=y] && GPIOLIB [=y] || COMPILE_TEST [=n]) && USB_ROLE_SWITCH [=m]
Location:
-> Device Drivers
-> Misc devices
---
CONFIG_INTEL_MEI_VIRTIO:
This module implements mei hw emulation over virtio transport.
The module will be called mei_virtio.
Enable this if your virtual machine supports virtual mei
device over virtio.
Symbol: INTEL_MEI_VIRTIO [=n]
Type : tristate
Defined at drivers/misc/mei/Kconfig:49
Prompt: Intel MEI interface emulation with virtio framework
Depends on: X86 [=y] && PCI [=y] && VIRTIO_PCI [=y]
Location:
-> Device Drivers
-> Misc devices
Selects: INTEL_MEI [=m]
---
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
A few configs changed their dependencies and that affects what options
the configs can be. Two configs can no longer be inline and one brings
in more confgs that are unnecessary. Fix them quickly for a review
later.
Signed-off-by: Don Zickus <dzickus@redhat.com>
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_DRM_AMD_DC_SI:
Choose this option to enable new AMD DC support for SI asics
by default. This includes Tahiti, Pitcairn, Cape Verde, Oland.
Hainan is not supported by AMD DC and it has no physical DCE6.
Symbol: DRM_AMD_DC_SI [=n]
Type : bool
Defined at drivers/gpu/drm/amd/display/Kconfig:34
Prompt: AMD DC support for Southern Islands ASICs
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_AMDGPU [=m]
Location:
-> Device Drivers
-> Graphics support
-> AMD GPU (DRM_AMDGPU [=m])
-> Display Engine Configuration
---
CONFIG_DRM_CDNS_MHDP8546:
Support Cadence DPI to DP bridge. This is an internal
bridge and is meant to be directly embedded in a SoC.
It takes a DPI stream as input and outputs it encoded
in DP format.
Symbol: DRM_CDNS_MHDP8546 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/cadence/Kconfig:2
Prompt: Cadence DPI/DP bridge
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_KMS_HELPER [=m] && DRM_PANEL_BRIDGE [=y]
---
CONFIG_DRM_LONTIUM_LT9611:
Driver for Lontium LT9611 DSI to HDMI bridge
chip driver that converts dual DSI and I2S to
HDMI signals
Please say Y if you have such hardware.
Symbol: DRM_LONTIUM_LT9611 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:51
Prompt: Lontium LT9611 DSI/HDMI bridge
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: SND_SOC_HDMI_CODEC [=n] && DRM_PANEL_BRIDGE [=y] && DRM_KMS_HELPER [=m] && REGMAP_I2C [=m]
---
CONFIG_DRM_TOSHIBA_TC358762:
Toshiba TC358762 DSI/DPI bridge driver.
Symbol: DRM_TOSHIBA_TC358762 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:169
Prompt: TC358762 DSI/DPI bridge
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_MIPI_DSI [=n] && DRM_PANEL_BRIDGE [=y]
---
CONFIG_DRM_TOSHIBA_TC358775:
Toshiba TC358775 DSI/LVDS bridge chip driver.
Symbol: DRM_TOSHIBA_TC358775 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:205
Prompt: Toshiba TC358775 DSI/LVDS bridge
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_KMS_HELPER [=m] && REGMAP_I2C [=m] && DRM_PANEL [=y] && DRM_MIPI_DSI [=n]
---
Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_BACKLIGHT_KTD253:
Say y to enabled the backlight driver for the Kinetic KTD253
which is a 1-wire GPIO-controlled backlight found in some mobile
phones.
Symbol: BACKLIGHT_KTD253 [=n]
Type : tristate
Defined at drivers/video/backlight/Kconfig:185
Prompt: Backlight Driver for Kinetic KTD253
Depends on: HAS_IOMEM [=y] && BACKLIGHT_CLASS_DEVICE [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Graphics support
-> Backlight & LCD device support
-> Lowlevel Backlight controls (BACKLIGHT_CLASS_DEVICE [=y])
---
Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Add myself and darcari as maintainers for the GPIO and pinctrl
subsystems.
CC: David Arcari <darcari@redhat.com>
Signed-off-by: Brian Masney <bmasney@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>
Cc: Don Dutile <ddutile@redhat.com>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
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.
---
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>
Cc: Don Dutile <ddutile@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_XILINX_ZYNQMP_DPDMA:
Enable support for Xilinx ZynqMP DisplayPort DMA. Choose this option
if you have a Xilinx ZynqMP SoC with a DisplayPort subsystem. The
driver provides the dmaengine required by the DisplayPort subsystem
display driver.
Symbol: XILINX_ZYNQMP_DPDMA [=n]
Type : tristate
Defined at drivers/dma/Kconfig:711
Prompt: Xilinx DPDMA Engine
Depends on: DMADEVICES [=y]
Location:
-> Device Drivers
-> DMA Engine support (DMADEVICES [=y])
Selects: DMA_ENGINE [=y] && DMA_VIRTUAL_CHANNELS [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_BPF_PRELOAD:
This builds kernel module with several embedded BPF programs that are
pinned into BPF FS mount point as human readable files that are
useful in debugging and introspection of BPF programs and maps.
Symbol: BPF_PRELOAD [=n]
Type : bool
Defined at kernel/bpf/preload/Kconfig:6
Prompt: Preload BPF file system with kernel specific program and map iterators
Depends on: BPF [=y] && !COMPILE_TEST [=n]
Location:
-> General setup
Selects: USERMODE_DRIVER [=n]
---
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Yauheni Kaliuta <ykaliuta@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_TEST_KASAN_MODULE:
This is a part of the KASAN test suite that is incompatible with
KUnit. Currently includes tests that do bad copy_from/to_user
accesses.
Symbol: TEST_KASAN_MODULE [=n]
Type : tristate
Defined at lib/Kconfig.kasan:181
Prompt: KUnit-incompatible tests of KASAN bug detection capabilities
Depends on: m && MODULES [=y] && KASAN [=y]
Location:
-> Kernel hacking
-> Memory Debugging
-> KASAN: runtime memory debugger (KASAN [=y])
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_TEST_FREE_PAGES:
Test that a memory leak does not occur due to a race between
freeing a block of pages and a speculative page reference.
Loading this module is safe if your kernel has the bug fixed.
If the bug is not fixed, it will leak gigabytes of memory and
probably OOM your system.
Symbol: TEST_FREE_PAGES [=n]
Type : tristate
Defined at lib/Kconfig.debug:2370
Prompt: Test freeing pages
Depends on: RUNTIME_TESTING_MENU [=y]
Location:
-> Kernel hacking
-> Kernel Testing and Coverage
-> Runtime Testing (RUNTIME_TESTING_MENU [=y])
---
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_HIST_TRIGGERS_DEBUG:
Add "hist_debug" file for each event, which when read will
dump out a bunch of internal details about the hist triggers
defined on that event.
The hist_debug file serves a couple of purposes:
- Helps developers verify that nothing is broken.
- Provides educational information to support the details
of the hist trigger internals as described by
Documentation/trace/histogram-design.rst.
The hist_debug output only covers the data structures
related to the histogram definitions themselves and doesn't
display the internals of map buckets or variable values of
running histograms.
If unsure, say N.
Symbol: HIST_TRIGGERS_DEBUG [=n]
Type : bool
Defined at kernel/trace/Kconfig:850
Prompt: Hist trigger debug support
Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && HIST_TRIGGERS [=y]
Location:
-> Kernel hacking
-> Tracers (FTRACE [=y])
Cc: Jerome Marchand <jmarchan@redhat.com>
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_CAN_ISOTP:
CAN Transport Protocols offer support for segmented Point-to-Point
communication between CAN nodes via two defined CAN Identifiers.
As CAN frames can only transport a small amount of data bytes
(max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
segmentation is needed to transport longer PDUs as needed e.g. for
vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN traffic.
This protocol driver implements data transfers according to
ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.
If you want to perform automotive vehicle diagnostic services (UDS),
say 'y'.
Symbol: CAN_ISOTP [=n]
Type : tristate
Defined at net/can/Kconfig:58
Prompt: ISO 15765-2:2016 CAN transport protocol
Depends on: NET [=y] && CAN [=m]
Location:
-> Networking support (NET [=y])
-> CAN bus subsystem support (CAN [=m])
---
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_DPTF_PCH_FIVR:
This driver adds support for Dynamic Platform and Thermal Framework
(DPTF) PCH FIVR Participant device support. This driver allows to
switch PCH FIVR (Fully Integrated Voltage Regulator) frequency.
This participant is responsible for exposing:
freq_mhz_low_clock
freq_mhz_high_clock
To compile this driver as a module, choose M here:
the module will be called dptf_pch_fivr.
Symbol: DPTF_PCH_FIVR [=n]
Type : tristate
Defined at drivers/acpi/dptf/Kconfig:18
Prompt: DPTF PCH FIVR Participant
Depends on: ACPI [=y] && X86 [=y]
Location:
-> Power management and ACPI options
-> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])
---
Cc: Al Stone <ahs3@redhat.com>
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_PINCTRL_MSM8226:
This is the pinctrl, pinmux, pinconf and gpiolib driver for the
Qualcomm Technologies Inc TLMM block found on the Qualcomm
Technologies Inc MSM8226 platform.
Symbol: PINCTRL_MSM8226 [=n]
Type : tristate
Defined at drivers/pinctrl/qcom/Kconfig:65
Prompt: Qualcomm 8226 pin controller driver
Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINCTRL_MSM [=y]
---
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_MFD_INTEL_M10_BMC:
Support for the Intel MAX 10 board management controller using the
SPI interface.
This driver provides common support for accessing the device,
additional drivers must be enabled in order to use the functionality
of the device.
Symbol: MFD_INTEL_M10_BMC [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:2156
Prompt: Intel MAX 10 Board Management Controller
Depends on: HAS_IOMEM [=y] && SPI_MASTER [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: REGMAP_SPI_AVMM [=n] && MFD_CORE [=y]
---
CONFIG_MFD_SL28CPLD:
Say yes here to enable support for the Kontron sl28cpld board
management controller.
It can be found on the following boards:
* SMARC-sAL28
Symbol: MFD_SL28CPLD [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:1189
Prompt: Kontron sl28cpld Board Management Controller
Depends on: HAS_IOMEM [=y] && I2C [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: MFD_SIMPLE_MFD_I2C [=n]
---
Cc: Torez Smith <torez@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Currently the CTS algo is built as a module. This is a problem if any
ciphers using CTS are marked as FIPS-enabled and the system is booted
in FIPS mode, as dracut does not include cts.ko in the initramfs. This
change is necessary for NFS with sec=krb5{,i,p} to work in FIPS mode.
Otherwise, the following panic would result:
[ 8.462065] alg: skcipher: Failed to load transform for cts(cbc(aes)): -2
[ 8.463705] Kernel panic - not syncing: cts(cbc(aes)): cts(cbc(aes)) alg self test failed in fips mode!
Fix this by embedding the CTS code into a kernel, the same way as Fedora
already does. This was tested by a reproducer in bz1855161 #c24, #c28.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1855161
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
I created an optimization to speed up the automated scripts when there was
nothing to merge in redhat/scripts/ci/ark-update-configs.sh under
2d1d129bbe
The thought was, if 'master' wasn't updated or needed merging, how can there be
any new configs to add?
Well it turns out that when merge conflicts arise, the merge of master into
os-build has to be done by hand and pushed manually. This usually skips the
new config generation.
The above optimization then skips the config generation on later cron jobs
because the merge already happened (until the master is actually updated).
There is nothing wrong with re-running the config generation script even if
there is nothing to do. Just undo the optimization.
Signed-off-by: Don Zickus <dzickus@redhat.com>
Recently the maintainer workflow has been changed to include a single os-build
branch for development and various makefile scripts to help with automation.
Update the docs to reflect that.
Signed-off-by: Don Zickus <dzickus@redhat.com>
The kernel-ark wiki needs an update after the inclusion of the single
branch workflow patches.
Update documentation for the single branch workflow.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Cc: Justin Forbes <jforbes@redhat.com>
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_SENSORS_ADM1266:
If you say yes here you get hardware monitoring support for Analog
Devices ADM1266 Cascadable Super Sequencer.
This driver can also be built as a module. If so, the module will
be called adm1266.
Symbol: SENSORS_ADM1266 [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:29
Prompt: Analog Devices ADM1266 Sequencer
Depends on: HWMON [=y] && PMBUS [=m] && GPIOLIB [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
Selects: CRC8 [=m]
---
CONFIG_SENSORS_MP2975:
If you say yes here you get hardware monitoring support for MPS
MP2975 Dual Loop Digital Multi-Phase Controller.
This driver can also be built as a module. If so, the module will
be called mp2975.
Symbol: SENSORS_MP2975 [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:214
Prompt: MPS MP2975
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
CONFIG_SENSORS_MR75203:
If you say yes here you get support for Moortec MR75203
PVT controller.
This driver can also be built as a module. If so, the module
will be called mr75203.
Symbol: SENSORS_MR75203 [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:1115
Prompt: Moortec Semiconductor MR75203 PVT Controller
Depends on: HWMON [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
Selects: REGMAP_MMIO [=n]
---
Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Add new entries for
- drivers/bus
- drivers/dma
- drivers/firmware
- drivers/leds
- drivers/mailbox
- drivers/mfd
- drivers/platform
- drivers/power
- drivers/spi
- usr/
Also make a small change and rename "LINUX FOR POWERPC" to just "POWERPC".
RH-Acked-by: Torez Smith <torez@redhat.com>
RH-Acked-by: Lenny Szubowicz <lszubowi@redhat.com>
RH-Acked-by: John W. Linville <linville@redhat.com>
RH-Acked-by: Al Stone <ahs3@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Steve Best <sbest@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
Cc: Torez Smith <torez@redhat.com>
Cc: Al Stone <ahs3@redhat.com>
Based on a suggestion from Thorsten Leemhuis.
Thorsten suggested making it easier to see that individual change
by embedding the url to the commit in the patchlist.changelog file.
This change does exactly that.
Old output:
e338eecf3f PCI: rockchip: Fix bus checks in rockchip_pcie_valid_device()
850280156f phy: ti: am654: Fix a leak in serdes_am654_probe()
43557447af gitattributes: Remove unnecesary export restrictions
f003c79ead Add RHMAINTAINERS file and supporting conf
825b7aa116 gitlab: Add CI job for packaging scripts
New output:
e338eecf3fe338eecf3f PCI: rockchip: Fix bus checks in rockchip_pcie_valid_device()
850280156f850280156f phy: ti: am654: Fix a leak in serdes_am654_probe()
43557447af43557447af gitattributes: Remove unnecesary export restrictions
f003c79eadf003c79ead Add RHMAINTAINERS file and supporting conf
825b7aa116825b7aa116 gitlab: Add CI job for packaging scripts
Signed-off-by: Don Zickus <dzickus@redhat.com>
Currently drivers/nvme/Kconfig is not identified as belonging to the
NVM EXPRESS DRIVER maintainers. Add the entire drivers/nvme/ directory
to capture all code.
RH-Acked-by: Gopal Tiwari <gtiwari@redhat.com>
RH-Acked-by: David Arcari <darcari@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: David Milburn <dmilburn@redhat.com>
Cc: Gopal Tiwari <gtiwari@redhat.com>
Put entries back in alphabetical order.
RH-Acked-by: David Arcari <darcari@redhat.com>
RH-Acked-by: Bruno Meneguele <bmeneg@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Add an entry for the common Linux Security Module infrastructure, which
is crucical for SELinux and other security features. Add myself as the
maintainer, since I already need to maintain it because of SELinux.
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
• SC2006: Use $(...) notation instead of legacy backticked `...`.
• SC2034: <variable> appears unused. Verify use (or export if used externally).
• SC2038: Use -print0/-0 or find -exec + to allow for non-alphanumeric filenames.
• SC2045: Iterating over ls output is fragile. Use globs.
• SC2046: Quote this to prevent word splitting.
• SC2086: Double quote to prevent globbing and word splitting.
• SC2231: Quote expansions in this for-loop glob to prevent wordsplitting, e.g. "$dir"/*.txt .
Ignore:
• SC2164: Use 'cd ... || exit' or 'cd ... || return' in case cd fails.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
SC2006: Use $(...) notation instead of legacy backticked `...`.
SC2039: In POSIX sh, == in place of = is undefined. (NOTE: works fine in bash.)
SC2086: Double quote to prevent globbing and word splitting.
SC2231: Quote expansions in this for-loop glob to prevent wordsplitting, e.g. "$dir"/*.txt .
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
0001-shellcheck.bats
• tests whether all scripts under redhat/ pass shellcheck
1001-rpmlint.bats
• tests for exactly one SRPM
• runs rpmlint on that SRPM
1002-basic-structural-test.bats
• tests whether SRPM unpacks OK
• tests whether Linux tree unpacks OK
• runs top-level structural check on Linux tree
Nothing is hooked up yet, i.e. there is no Makefile target that
invokes these tests; however, tests may be run manually using the
bats command, e.g.
• bats 0001-shellcheck.bats
• bats *.bats
Requires installation of the 'bats' package; shellcheck tests require
the 'ShellCheck' package (note capitalization):
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
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_FB_ARMCLCD:
This framebuffer device driver is for the ARM PrimeCell PL110
Colour LCD controller. ARM PrimeCells provide the building
blocks for System on a Chip devices.
If you want to compile this as a module (=code which can be
inserted into and removed from the running kernel), say M
here and read <file:Documentation/kbuild/modules.rst>. The module
will be called amba-clcd.
Symbol: FB_ARMCLCD [=n]
Type : tristate
Defined at drivers/video/fbdev/Kconfig:275
Prompt: ARM PrimeCell PL110 support
Depends on: (ARM || ARM64 [=y] || COMPILE_TEST [=n]) && FB [=y] && ARM_AMBA [=y] && HAS_IOMEM [=y]
Location:
-> Device Drivers
-> Graphics support
-> Frame buffer Devices
-> Support for frame buffer devices (FB [=y])
Selects: FB_CFB_FILLRECT [=y] && FB_CFB_COPYAREA [=y] && FB_CFB_IMAGEBLIT [=y] && FB_MODE_HELPERS [=n] && VIDEOMODE_HELPERS [=n] && BACKLIGHT_CLASS_DEVICE [=y]
---
Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
The ACPI prefernce is RHEL specific, in Fedora we use upstream defaults so
it doesn't randomly change the expectations as to how certain hardware works
that generally isn't classed as "enterprise". So wrap it in the special RHEL
check as it should be for the ARK kernels.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
CC: Mark Salter <msalter@redhat.com>
Upstream Status: RHEL only
After discussions with Devel, QE, Support, and Certification we have
decided to drop the CPU specific checks in rh_check_supported().
Certification is adopting a new process in which CPU certifications will
be tracked on https://catalog.redhat.com.
Remove the vendor specific CPU ID checks from rh_check_supported().
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Resending ... did not get any reviews.
P.
---8<---
Bugzilla: http://bugzilla.redhat.com/1810301
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=27902812
Local Tree: git://git.engineering.redhat.com/users/prarit/rhel8 1810301
Upstream Status: RHEL only
For almost a decade, RHEL kernels have output the message
"this hardware has not undergone testing by Red Hat and might not be
certified. Please consult https://hardware.redhat.com for certified
hardware."
for unsupported hardware. This link should be now be updated to the
new catalog.redhat.com location. The old hardware.redhat.com is now
redirecting to catalog.redhat.com for older releases.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Upstream status: RHEL only
The function rh_check_supported is a RHEL function to limit the
platforms RHEL does not want to support.
To avoid imposing this requirement on Fedora, the function was
wrapped with CONFIG_RHEL_DIFFERENCES so Fedora can disable this.
However, this has a few compile warnings that need to be cleaned up
when disabled.
Move CONFIG_RHEL_DIFFERENCES to include the functions themselves
instead of the call. As the unused functions created warnings.
V2: modified stub definition
Signed-off-by: Don Zickus <dzickus@redhat.com>
This patch completes commit 278311e417 ("kexec, KEYS: Make use of
platform keyring for signature verify") which, while adding the
platform keyring for bzImage verification, neglected to also add
this keyring for module verification.
As such, kernel modules signed with keys from the MokList variable
were not successfully verified.
Signed-off-by: Robert Holmes <robeholmes@gmail.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
The IRQ from rmi4 may interfere with the one we currently use on i2c-hid.
Given that there is already a need for an external API from rmi4 to
forward the attention data, we can, in this particular case rely on a
separate workqueue to prevent cursor jumps.
Reported-by: Cameron Gutman <aicommander@gmail.com>
Reported-by: Thorsten Leemhuis <linux@leemhuis.info>
Reported-by: Jason Ekstrand <jason@jlekstrand.net>
Tested-by: Andrew Duggan <aduggan@synaptics.com>
Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Lyude <lyude@redhat.com>
RH-Acked-by: Bruno Meneguele <bmeneg@redhat.com>
RH-Acked-by: Jesper Brouer <brouer@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jiri Olsa <jolsa@redhat.com>
RH-Acked-by: Toke Høiland-Jørgensen <toke@redhat.com>
Upstream status: RHEL only
We don't really need the field names to be globally unique, it is enough
when they are unique in the given struct. Since structs do not generally
span mutliple files, using the line number is enough to ensure an unique
identifier. It means that we can't use two RH_KABI_RENAME macros on the same
line but that's not happening anyway.
This allows pahole to deduplicate the type info of structs using kABI
macros, lowering the size of vmlinuz from 26M to 8.5M.
Upstream Status: RHEL only
Signed-off-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Don Zickus <dzickus@redhat.com>
Upstream status: RHEL only
We've seen attempts of incorrect RH_KABI_EXCLUDE usage. The macro is
dangerous and any structure marked by it becomes fragile. It completely
mutes the kABI checker and a future attempt to whitelist anything using
a structure annotated by RH_KABI_EXCLUDE will generate easily broken, error
prone code. Also, it bypasses module loading checks for the structure and
can lead to kernel crashes triggered by 3rd party modules unless carefully
prevented by RH_KABI_FORCE_CHANGE.
As such, it should not be used routinely. The only valid usage is a code
heavily in flux upstream that is going to be refactored and turned upside
down, which is indirectly whitelisted and which we expect to need
backported.
Any usage of this macro requires deep understanding of how kABI works.
Add a big fat warning to stop the misuse.
Upstream Status: RHEL only
Signed-off-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Toke Høiland-Jørgensen <toke@redhat.com>
RH-Acked-by: Hangbin Liu <haliu@redhat.com>
Upstream status: RHEL only
This allows addition of a struct into struct while reserving extra space.
See the documentation in rh_kabi.h for details.
The check for size is automatically disabled in -debug kernels that have
many fields larger than the production kernels (mutexes etc.) and that are
not under kABI guarantee.
I'm also moving a misplaced comment for RH_KABI_FILL_HOLE.
(Pointed out by Sabrina:) We need to force align the added field to 8 byte
offset. Otherwise, if the required alignment of the added field changed
later (e.g. it was a structure with only a single field that was changed
from int to char) and the previous field was smaller than long, it could
lead to the whole union shifting position and offsets of the following
fields could change. It's also safer to align the size, too.
Let the 'size' parameter specify number of longs to be added and not number
of bytes. Note we assume a 64 bit architecture, which is the case for RHEL.
Upstream Status: RHEL only
Signed-off-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
Upstream Status: RHEL only
Since this macro is intended to record the sizeof extension structs that
are dynamically allocated, using the structure dereference operator '->'
is a better choice, else the macro would have to be invoked with the
_name argument dereferenced as (*_name).
Also added a short note explaining that, unlike the other RH_KABI
macros that are invoked from within structs, this macro is invoked
outside a struct and therefore needs a semicolon termination.
Upstream Status: RHEL only
Signed-off-by: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Ivan Vecera <ivecera@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
Upstream: RHEL-only
As noted in the reviews, there are some areas of future work:
1) A further restriction on the access of the extended struct fields
would be to require the addition of an accessor function.
2) Additional macros to use RH_KABI_EXTEND fields.
3) Additional macros to mark extended struts' field for internal kernel
versus module use.
The RHEL7 code contains macros to extend kernel structs. For example, the
RH_KABI_EXTEND() can be used to extend a struct when used appropriately.
This macro (and others similar to it) has a significant shortcoming as it
cannot be used in the case where a struct is known to allocate the struct
within a 3rd party module. For example, in RHELX.0, suppose there exists
a struct,
struct in_kernel {
int foo0;
};
and an exported function,
void in_kernel_set_foo(struct in_kernel *ink)
{
...
ink->foo0 = 0xBA5EBA11;
...
}
Let's also suppose a struct in_kernel is statically defined within a 3rd
party module, or dynamically allocated as
struct in_kernel *3rd_party_ink;
...
ink = kmalloc(sizeof(*3rd_party_ink), GFP_KERNEL);
...
In RHELX.1, suppose the struct is expanded by
struct in_kernel {
int foo0;
RH_KABI_EXTEND(foo1)
};
and the exported function is modified as
void in_kernel_set_foo(struct in_kernel *ink)
{
...
ink->foo0 = 0xBA5EBA11;
ink->foo1 = 0xBA5EBA11;
...
}
The 3rd party module, compiled against RHELX.0, will not have allocated
memory for foo1, and in_kernel_set_foo() will reference garbage in memory.
To fix this problem, Jiri Benc came up with an great solution that should
be unified for all future RHELX.0 expansions of structs. RHEL7 commit
e33a3c136b56 ("[net] introduce net_device_ops_extended") adds a size
parameter to net_device_ops that can be queried to validate memory
accesses. In the patch, net_device_ops is expanded by embedding a
net_device_ops_extended struct and addig a size parameter. The size
parameter is used to compare the offset of a parameter in the
net_device_ops_extended struct to the size of the struct at compile time,
and if valid, the memory access can be programmatically allowed to occur.
I have taken his idea and created several new standard macros that allow
structs to be expanded by embedding a new struct or by adding a pointer
to a new struct.
There are, however, some rules that must be followed when using these
new macros:
1. The default name of the extended struct is ##name##_rh. For example,
pci_dev_rh, device_rh, net_device_ops_rh, etc.
2. _rh structs cannot be shrunk in size as such changes would break the
size & offset comparison.
3. The size field _must_ be set at the spot of allocation for use. Use of the
_rh fields without setting the size field via RH_KABI_SET_SIZE|_PTR() is
invalid in the kernel or in a 3rd party module.
4. These new macros do not preclude expansions like
struct in_kernel_rh {
};
struct in_kernel {
...
RH_KABI_EXTEND(void *ptr1)
RH_KABI_EXTEND(void *ptr2)
RH_KABI_EXTEND(void *ptr3)
RH_KABI_EXTEND(void *ptr4)
RH_KABI_SIZE_AND_EXTEND_PTR(in_kernel)
};
These macros are generally intended for pre-KABI freeze use, however,
there may be cases where these macros can be used post-KABI freeze.
Due to the design of RH_KABI_EXTEND() which embeds __GENKSYMS__ care must
be taken when using RH_KABI_SIZE_AND_EXTEND|_PTR() post-KABI freeze to
ensure that structs are not embedded within another struct, verifying
offsets, etc.
Add RH_KABI_SIZE_AND_EXTEND(), RH_KABI_SIZE_AND_EXTEND_PTR(), and
other macros that allow for safe expansion of structs.
v2: Cleanup comments.
v3: Cleanup comments.
Upstream Status: RHEL only
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Message-id: <1525206184-20470-1-git-send-email-dkennedy@redhat.com>
Patchwork-id: 212089
O-Subject: [RHEL8 PATCH e-stor] Removing Obsolete hba pci-ids from rhel8.
Bugzilla: 1572321
RH-Acked-by: Chris Leech <cleech@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
These adapters printed an Obsolete Unsupported message is rhel7. They
are being removed for rhel8
brew-id: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID^U948800
bugzilla: 1572321
tested on: rhel-storage-44 and on rhel-storage-07
RHEL Specific
Upstream Status: RHEL only
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Backport Notes: Simplify by filtering using pci_ids
-
Author: Tomas Henzl <thenzl@redhat.com>
Date: Thu Jan 31 16:54:51 2019 -0500
[message] mptsas: pci-id table changes
Message-id: <20190131165452.7562-3-thenzl@redhat.com>
Patchwork-id: 239765
O-Subject: [RHEL8 e-stor 2/3] mptsas: pci-id table changes
Bugzilla: 1666730
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
RHEL-only
We want to provide this driver only for the virtualisation use case,
so we remove all other entries from the pci-id table and add only the
single entry needed for virtualisation.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Upstream Status: RHEL only
Signed-off-by: Laura Abbott <labbott@redhat.com>
Author: Tomas Henzl <thenzl@redhat.com>
Date: Thu Jan 31 16:54:50 2019 -0500
[message] mptsas: Taint kernel if mptsas is loaded
Message-id: <20190131165452.7562-2-thenzl@redhat.com>
Patchwork-id: 239764
O-Subject: [RHEL8 e-stor 1/3] mptsas: Taint kernel if mptsas is loaded
Bugzilla: 1666730
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
RHEL-only
We are only keeping it to ease developer transitions, we're not
supporting it, so mark it as unsupported by tainting the kernel and
issuing an impossible to misunderstand message to the log
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Upstream Status: RHEL only
Signed-off-by: Laura Abbott <labbott@redhat.com>
Author: Tomas Henzl <thenzl@redhat.com>
Date: Thu Jan 10 16:11:44 2019 -0500
[message] mptspi: pci-id table changes
Message-id: <20190110161145.5117-3-thenzl@redhat.com>
Patchwork-id: 237190
O-Subject: [RHEL-8.0 e-stor 2/3] mptspi: pci-id table changes
Bugzilla: 1651803
RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Chris Leech <cleech@redhat.com>
RHEL-only
We want to provide this driver only for the virtualisation use case,
so we remove all other entries from the pci-id table and add only the
single entry needed for virtualisation.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Upstream Status: RHEL only
Signed-off-by: Laura Abbott <labbott@redhat.com>
Message-id: <20180503194032.1461134-1-cleech@redhat.com>
Patchwork-id: 212454
O-Subject: [RHEL8 PATCH e-stor] scsi: be2iscsi: remove unsupported device IDs
Bugzilla: 1574502
RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
RH-Acked-by: Tom Coughlan <coughlan@redhat.com>
RH-Acked-by: Ewan Milne <emilne@redhat.com>
Bugzilla: 1574502
Upstream Status: RHEL Specific
Build Info: brew 15975638
BladeEngine 2 generation devices are deprecated in RHEL 7
and not supported in RHEL 8
Signed-off-by: Chris Leech <cleech@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
be2iscsi: remove BE3 family support
Message-id: <1530890927-5792-1-git-send-email-mlombard@redhat.com>
Patchwork-id: 223576
O-Subject: [RHEL8 e-stor PATCH] be2iscsi: remove BE3 family support
Bugzilla: 1598366
RH-Acked-by: Tomas Henzl <thenzl@redhat.com>
RH-Acked-by: Chris Leech <cleech@redhat.com>
BZ: https://bugzilla.redhat.com/show_bug.cgi?id98366
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID996775
Upstream: RHEL-only, they tried to mark BE3 as unsupported
in upstream kernel but the patch has been rejected.
See: https://marc.info/?l=linux-scsi&m2835991600881&w=2
Broadcom doesn't want to provide support for the BE3 device family
in RHEL8.
This patch removes the BE3's PCI-IDs.
Upstream Status: RHEL only
Signed-off-by: Maurizio Lombardi <mlombard@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Author: Tomas Henzl <thenzl@redhat.com>
Date: Thu Jan 10 16:11:43 2019 -0500
[message] mptspi: Taint kernel if mptspi is loaded
Message-id: <20190110161145.5117-2-thenzl@redhat.com>
Patchwork-id: 237188
O-Subject: [RHEL-8.0 e-stor 1/3] mptspi: Taint kernel if mptspi is loaded
Bugzilla: 1651803
RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Chris Leech <cleech@redhat.com>
RHEL-only
We are only keeping it to ease developer transitions, we're not
supporting it, so mark it as unsupported by tainting the kernel and
issuing an impossible to misunderstand message to the log
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Upstream Status: RHEL only
Signed-off-by: Laura Abbott <labbott@redhat.com>
Message-id: <1524750809-43700-2-git-send-email-jszczype@redhat.com>
Patchwork-id: 211573
O-Subject: [RHEL8 e-stor PATCH 1/2] hpsa: remove old cciss-based smartarray pci ids
Bugzilla: 1471185
RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
RH-Acked-by: Tomas Henzl <thenzl@redhat.com>
Per discussion with Microsemi, the old PCI IDs for smartarrays
originally used with the old cciss driver are not being
supported with RHEL8. They are also not supported with RHEL7.
Therefore the PCI IDs and the catch-all are being removed.
Acked-by: Don Brace <don.brace@microsemi.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Upstream Status: RHEL only
Message-id: <1524063895-23086-1-git-send-email-cdupuis@redhat.com>
Patchwork-id: 209742
O-Subject: [RHEL 8 e-stor PATCH] qla4xxx: Remove depricated PCI IDs from RHEL 8.
Bugzilla: 1518874
RH-Acked-by: Tomas Henzl <thenzl@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
Bugzilla: 1518874
RHEL 8 specific
Brew build: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID822250
Three PCI device IDs are marked as deprecated in RHEL 7:
PCI_DEVICE_ID_QLOGIC_ISP8022
PCI_DEVICE_ID_QLOGIC_ISP8324
PCI_DEVICE_ID_QLOGIC_ISP8042
This patch removes them from the PCI table in RHEL 8 so the
qla4xxx driver will not bind to the hardware.
Upstream Status: RHEL only
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Message-id: <20190708192032.20922-1-jcline@redhat.com>
Patchwork-id: 266421
O-Subject: [ARK INTERNAL PATCH] mpt*: remove certain deprecated pci-ids
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
Commit 8f8384503e ("scsi: mpt3sas: Add support for NVMe Switch
Adapter") introduced a new PCI device ID which broke the patch context.
Message-id: <20180403143030.4971-1-thenzl@redhat.com>
Patchwork-id: 7431
O-Subject: [kernel team] [RHEL8 e-stor PATCH] mpt*: remove certain deprecated pci-ids
Bugzilla: 1511953
RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
RH-Acked-by: Chris Leech <cleech@redhat.com>
bz#1511953
brew - task_15594743
RH specific - remove EOL devices from the pci-id table
(devices to remove were selected by Broadcom)
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Upstream Status: RHEL only
Signed-off-by: Jeremy Cline <jcline@redhat.com>
The intent of RH_DISABLE_DEPRECATED was to provide Red Hat a
simple way to disable drivers it did not want to support in RHEL.
As the config option was applied to more drivers and infra, it became
clear the option was being used for not only deprecating drivers (which
implied limited support) to disabling drivers (implying no support).
Using the word 'deprecated' seemed confusing in the second scenario.
Rename the option to be more generic and useable across more parts
of the kernel tree.
The new wording is RHEL_DIFFERENCES.
Upstream Status: RHEL only
This is a hack, but it's what the other distros currently use
for aarch64 with 4K pages so we'll do the same while upstream
decides what the best outcome is (which isn't this).
Upstream Status: RHEL only
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
[Add a dependency on RHEL_DIFFERENCES]
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Automatically lock down the kernel to LOCKDOWN_CONFIDENTIALITY_MAX if
the IPL secure flag is set.
Upstream Status: RHEL only
Suggested-by: Philipp Rudo <prudo@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
UEFI Secure Boot provides a mechanism for ensuring that the firmware
will only load signed bootloaders and kernels. Certain use cases may
also require that all kernel modules also be signed. Add a
configuration option that to lock down the kernel - which includes
requiring validly signed modules - if the kernel is secure-booted.
Upstream Status: RHEL only
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
UEFI machines can be booted in Secure Boot mode. Add an EFI_SECURE_BOOT
flag that can be passed to efi_enabled() to find out whether secure boot is
enabled.
Move the switch-statement in x86's setup_arch() that inteprets the
secure_boot boot parameter to generic code and set the bit there.
Upstream Status: RHEL only
Suggested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
cc: linux-efi@vger.kernel.org
[Rebased for context; efi_is_table_address was moved to arch/x86]
Signed-off-by: Jeremy Cline <jcline@redhat.com>
In order to automatically lock down kernels running on UEFI machines
booted in Secure Boot mode, expose the lock_kernel_down() hook.
Upstream Status: RHEL only
Signed-off-by: Jeremy Cline <jcline@redhat.com>
This adds efi_status_to_str() for use when printing efi_status_t
messages, and reworks efi_status_to_err() so that the two use a common
list of errors.
Upstream Status: RHEL only
Signed-off-by: Peter Jones <pjones@redhat.com>
Message-id: <20191113144431.9403-4-labbott@redhat.com>
Patchwork-id: 286081
O-Subject: [ARK INTERNAL PATCHv2 3/4] [redhat] Add support for deprecating processors
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
This is the squashed version of the following patches
modifed to use the new CONFIG_RH_DISABLE_DEPRECATED option
add rh_check_supported
Message-id: <1525313397-75200-1-git-send-email-darcari@redhat.com>
Patchwork-id: 212189
O-Subject: [RHEL8.0 BZ 1565717 v2] x86: add rh_check_supported
Bugzilla: 1565717
RH-Acked-by: Steve Best <sbest@redhat.com>
RH-Acked-by: Mikulas Patocka <mpatocka@redhat.com>
Description:
Add code to verify that the booted x86 processor is supported by
Red Hat. In cases where the processor is not supported a critical
message is logged.
Initially the supported set of processors for RHEL8 remains the same
as RHEL7.
Bugzilla: http://bugzilla.redhat.com/1565717
Brew: https://brewweb.devel.redhat.com/taskinfo?taskID=15966242
Test: Booted brew build on supported (Haswell) and unsupported processor (CNL)
and achieved desired results.
Upstream: RHEL Only
Cc: David Arcari <darcari@redhat.com>
Cc: Mikulas Patocka <mpatocka@redhat.com>
Cc: Dave Young <dyoung@redhat.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
update rh_check_supported processor list
Message-id: <1530618602-17477-1-git-send-email-darcari@redhat.com>
Patchwork-id: 223452
O-Subject: [RHEL8.0 BZ 1595918] x86: update rh_check_supported processor list
Bugzilla: 1595918
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Steve Best <sbest@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1595918
Upstream Status: RHEL_only
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16916208
Tested: Verified on a varity of supported and unsupported Intel and AMD systems.
Results as expected.
In RHEL8, we are marking some of the older processors as unsupported. No code
is being removed; however, the older processors are not supported and as such
are not candidates for certification.
Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Steve Best <sbest@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Signed-off-by: Jakub Racek <jracek@redhat.com>
refresh: rename FAM6_ATOM again, see f2c4db1bd
mark whiskey-lake processor supported
Message-id: <1533125629-12870-1-git-send-email-darcari@redhat.com>
Patchwork-id: 225809
O-Subject: [ BZ 1609604] mark whiskey-lake processor supported
Bugzilla: 1609604
RH-Acked-by: Steve Best <sbest@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1609604
Build Info: https://brewweb.devel.redhat.com/taskinfo?taskID=17474338
Upstream Status: RHEL Only
Tested: Successful excecution of platform-test suite.
Whiskey Lake is cpu model 142 with stepping 11. Stepping > 11 for cpu model
142 is not supported.
For model 158, the highest supported stepping is 10.
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Dave Young <dyoung@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
mark intel knights landing and knights mill unsupported
Message-id: <1533580277-126323-1-git-send-email-darcari@redhat.com>
Patchwork-id: 226187
O-Subject: [RHEL8.0 BZ 1610493] mark intel knights landing and knights mill unsupported
Bugzilla: 1610493
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Steve Best <sbest@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1610493
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=17625348
Tested: verified on KNL/KNM system
Upstream Status: RHEL Only
Depends: http://bugzilla.redhat.com/1609604
We are marking KNL/KNM processors as unsupported. No code is being removed;
however, the older processors are not supported and as such are not
candidates for certification.
Upstream Status: RHEL only
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Dave Young <dyoung@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Message-id: <20191001181256.22935-1-jcline@redhat.com>
Patchwork-id: 275498
O-Subject: [ARK INTERNAL PATCH] [ARK INTERNAL PATCH] [redhat] Add patch
to drop the EXPERT setting from ARM64_FORCE_52BIT
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>
We don't turn on EXPERT as there are few settings we actually want to
mess with. Remove the dependency for ARM64_FORCE_52BIT as we do want
that on in debug builds to help find 52-bit bugs.
Upstream Status: RHEL only
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190520222102.19488-1-labbott@redhat.com>
Patchwork-id: 259215
O-Subject: [ARK INTERNAL PATCH] iommu/arm-smmu: workaround DMA mode issues
Bugzilla:
RH-Acked-by: Mark Langsdorf <mlangsdo@redhat.com>
RH-Acked-by: Mark Salter <msalter@redhat.com>
From: Mark Salter <msalter@redhat.com>
Rebased for v5.2-rc1
Bugzilla: 1652259
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=19244562
Upstream status: RHEL only.
rhel8 commit 65feb1ed0ec9a088a63a90d46c0f7563ac96ad0f
Author: Mark Salter <msalter@redhat.com>
Date: Wed Nov 21 17:15:59 2018 +0100
[iommu] iommu/arm-smmu: workaround DMA mode issues
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1624077
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=18112820
Testing: Verified iommu.passthrough=1 no longer needed on gigabyte platforms.
Upstream Status: RHEL-only
In RHEL_ALT 7.5 we carried a RHEL-only patch which forced the arm smmuv2
into bypass mode due to performance issues on CN88xx. This was intended
to be a temporary hack until the issues were resolved. Another vendor
had issues with the iommu in bypass mode so we reverted the RHEL-only
patch so that iommu is in DMA mode by default (upstream default).
It turns on that there are remaining SMMU DMA mode issues on Gigabyte
platformws with CN88xx cpus. The problem manifests itself by pcie
card drivers failing to initialize the cards when SMMU is in DMA mode.
The root cause has not been determined yet, but looks likely to be
a hw or firmware issue. This patch forces bypass mode for Gigabyte
platforms. CN88xx isn't officially supported in RHEL but we have a
lot of them being used internally for testing, so I think we want
this to support that use case in RHEL8.
Signed-off-by: Mark Salter <msalter@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Acked-by: Mark Salter <msalter@redhat.com>
Acked-by: Donald Dutile <ddutile@redhat.com>
Upstream Status: RHEL only
Signed-off-by: Laura Abbott <labbott@redhat.com>
Message-id: <1542891606-8048-24-git-send-email-jracek@redhat.com>
Patchwork-id: 233503
O-Subject: [ARK PATCH 23/44] [kernel] rh_kabi: introduce RH_KABI_EXCLUDE
Bugzilla: 1652256
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
From: Jiri Benc <jbenc@redhat.com>
Bugzilla: 1652256
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=19244562
rhel8 commit 1c588b1bbe6ea3e9e1701ccf10e22f73f687ad02
Author: Jiri Benc <jbenc@redhat.com>
Date: Wed Nov 21 17:15:39 2018 +0100
[kernel] rh_kabi: introduce RH_KABI_EXCLUDE
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1568551
Add a way to exclude certain fields of a structure that would be otherwise
kABI whitelisted. The new RH_KABI_EXCLUDE macro serves two purposes:
1. Not adding the excluded fields to symbol checksums, making their later
changes easier.
2. Document that the given fields are not considered to be kABI whitelisted
by Red Hat.
Note that:
- This needs to be done _before_ the actual structure gets whitelisted.
- It still allows later conversion of the excluded fields to whitelist
covered fields by simply changing RH_KABI_EXCLUDE to RH_KABI_EXTEND.
- The excluded fields can be modified at will but extra care needs to be
taken to not cause problems with 3rd party drivers using the fields. See
the comment inside the patch for details.
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Upstream Status: RHEL only
Signed-off-by: Jakub Racek <jracek@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1670017
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=20147017
Commit 913a89f009 ("ipmi: Don't initialize anything in the core until
something uses it") added new locking which broke context.
Message-id: <20180713142210.15700-1-tcamuso@redhat.com>
Patchwork-id: 224899
O-Subject: [RHEL8 BZ 1583537 1/1] ipmi: do not configure ipmi for HPE m400
Bugzilla: 1583537
RH-Acked-by: Dean Nelson <dnelson@redhat.com>
RH-Acked-by: Al Stone <ahs3@redhat.com>
RH-Acked-by: Mark Salter <msalter@redhat.com>
bugzilla:https://bugzilla.redhat.com/show_bug.cgi?id=1583537
brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=17150528
RHEL-only
The ARM-based HPE m400 reports host-side ipmi as residing in intel
port-io space, which does not exist in ARM processors. Therefore, when
running on an m400, host-side ipmi configuration code must simply return
zero without trying to configure the host-side ipmi.
This patch prevents panic on boot by averting attempts to configure
host-side ipmi on this platform.
Though HPE m400 is not certified with RHEL, and HPE has relegated it to
EOL status, the platform is still used extensively in ARM development
and test for RHEL.
Testing:
Boot without blacklisting ipmi and check to see that no ipmi modules
are loaded.
Signed-off-by: Tony Camuso <tcamuso@redhat.com>
cc: Prarit Bhargava <prarit@redhat.com>
cc: Brendan Conoboy <blc@redhat.com>
cc: Jeff Bastian <jbastian@redhat.com>
cc: Scott Herold <sherold@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Upstream Status: RHEL only
Signed-off-by: Laura Abbott <labbott@redhat.com>
Acked-by: Tony Camuso <tcamuso@redhat.com>
Acked-by: Dean Nelson <dnelson@redhat.com>
Acked-by: Jarod Wilson <jarod@redhat.com>
Acked-by: Mark Salter <msalter@redhat.com>
Message-id: <20180629200436.151355.18581.stgit@tak.stowe>
Patchwork-id: 223206
O-Subject: [RHEL8.0 PATCH v3] kABI: Add generic kABI macros to use for kABI workarounds
Bugzilla: 1546831
RH-Acked-by: Larry Woodman <lwoodman@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
Some kernel subsystem maintainers have asked about kABI for RHEL8.0
- getting kABI related "extension" structures and such into place. The
consensus was to wait until the 4.17 re-base. Now that that's occurred,
lets get this first step, kABI macros, into RHEL8.0 so developers will
notice, and use, them in subsequent kABI related efforts.
Content taken from RHEL 7. No functional change intended.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1546831
Brew: https://brewweb.devel.redhat.com/taskinfo?taskID=16694565
Upstream Status: N/A (RHEL only)
Testing: Passed through brew build.
Upstream Status: RHEL only
Signed-off-by: Myron Stowe <myron.stowe@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Message-id: <1529326285-28560-1-git-send-email-mlombard@redhat.com>
Patchwork-id: 222337
O-Subject: [RHEL8 PATCH] pci: add pci_hw_vendor_status()
Bugzilla: 1590829
RH-Acked-by: Tomas Henzl <thenzl@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
This patch adds pci_hw_vendor_status() like in RHEL7 which should be called
during the driver's probe to identify deprecated devices.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1590829
Brew: https://brewweb.devel.redhat.com/taskinfo?taskID=16761315
See RHEL7 commits e0dddd9a63403ec82077ed410074fc6485873d4b and
3fcddde5ddf4b190c84ce9d83d56a75137513bd7
RHEL_only.
Upstream Status: RHEL only
Signed-off-by: Maurizio Lombardi <mlombard@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Message-id: <1528412373-19128-3-git-send-email-rrichter@redhat.com>
Patchwork-id: 220952
O-Subject: [RHEL-8.0 BZ 1563590 v2 2/2] ahci: thunderx2: Fix for errata that affects stop engine
Bugzilla: 1563590
RH-Acked-by: Dean Nelson <dnelson@redhat.com>
RH-Acked-by: Mark Langsdorf <mlangsdo@redhat.com>
RH-Acked-by: Mark Salter <msalter@redhat.com>
From: Jayachandran C <jnair@caviumnetworks.com>
Apply workaround for this errata:
Synopsis: Resetting PxCMD.ST may hang the SATA device
Description: An internal ping-pong buffer state is not reset
correctly for an PxCMD.ST=0 command for a SATA channel. This
may cause the SATA interface to hang when a PxCMD.ST=0 command
is received.
Workaround: A SATA_BIU_CORE_ENABLE.sw_init_bsi must be asserted
by the driver whenever the PxCMD.ST needs to be de-asserted. This
will reset both the ports. So, it may not always work in a 2
channel SATA system.
Resolution: Fix in B0.
Add the code to ahci_stop_engine() to do this. It is not easy to
stop the other "port" since it is associated with a different AHCI
interface. Please note that with this fix, SATA reset does not
hang any more, but it can cause failures on the other interface
if that is in active use.
Unfortunately, we have nothing other the the CPU ID to check if the
SATA block has this issue.
RHEL-only:
Both patches are in RHEL-7.6 also. Inclusion of the patches into RHEL-8
was discussed. Since there are partners with Ax system configurations it
was decided to carry them in RHEL8 too. See:
https://bugzilla.redhat.com/show_bug.cgi?id=1563590#c1
[v3 with new delays]
Signed-off-by: Jayachandran C <jnair@caviumnetworks.com>
Upstream Status: RHEL only
Signed-off-by: Robert Richter <rrichter@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Message-id: <1528412373-19128-2-git-send-email-rrichter@redhat.com>
Patchwork-id: 220950
O-Subject: [RHEL-8.0 BZ 1563590 v2 1/2] PCI: Vulcan: AHCI PCI bar fix for Broadcom Vulcan early silicon
Bugzilla: 1563590
RH-Acked-by: Dean Nelson <dnelson@redhat.com>
RH-Acked-by: Mark Langsdorf <mlangsdo@redhat.com>
RH-Acked-by: Mark Salter <msalter@redhat.com>
From: Ashok Kumar Sekar <asekar@redhat.com>
PCI BAR 5 is not setup correctly for the on-board AHCI
controller on Broadcom's Vulcan processor. Added a quirk to fix BAR 5
by using BAR 4's resources which are populated correctly but NOT used
by the AHCI controller actually.
RHEL-only:
Both patches are in RHEL-7.6 also. Inclusion of the patches into RHEL-8
was discussed. Since there are partners with Ax system configurations it
was decided to carry them in RHEL8 too. See:
https://bugzilla.redhat.com/show_bug.cgi?id=1563590#c1
Upstream Status: RHEL only
Signed-off-by: Ashok Kumar Sekar <asekar@redhat.com>
Signed-off-by: Jayachandran C <jchandra@broadcom.com>
Signed-off-by: Robert Richter <rrichter@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Message-id: <133022c6c389ca16060bd20ef69199de0800200b.1528991396.git.esyr@redhat.com>
Patchwork-id: 8250
O-Subject: [kernel team] [RHEL8 PATCH v4 2/5] [bpf] bpf: set unprivileged_bpf_disabled to 1 by default, add a boot parameter
Bugzilla: 1561171
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>
This patch sets kernel.unprivileged_bpf_disabled sysctl knob to 1
by default, and provides an ability (in a form of a boot-time parameter)
to reset it to 0, as it is impossible to do so in runtime. Since
unprivileged BPF is considered unsupported, it also taints the kernel.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1561171
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16716594
Upstream: RHEL only. The patch (in a more generic form) has been
proposed upstream[1] and subsequently rejected.
[1] https://lkml.org/lkml/2018/5/21/344
Upstream Status: RHEL only
Signed-off-by: Eugene Syromiatnikov <esyr@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Rebased for v5.3-rc1. Commit 95fd3f87bf ("kbuild: add a flag to force
absolute path for srctree") changed the context.
Message-id: <20180529180112.28376-1-prarit@redhat.com>
Patchwork-id: 8101
O-Subject: [kernel team] [RHEL8.0 BZ 1582586] scripts/tags.sh: Ignore redhat/rpm
Bugzilla: 1582586
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Neil Horman <nhorman@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1582586
Brew: https://brewweb.devel.redhat.com/taskinfo?taskID=16502319
RHEL_only.
If 'make cscope' is run on a tree which has had 'make rh-rpm',
'make rh-cross-*', etc., on it, the tags information contains entries
from the redhat/rpm/ directories.
Ignore the tags search in redhat/rpm.
Backport of RHEL7 464ad7779507 ("[scripts] tags.sh: ignore redhat/rpm").
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Upstream Status: RHEL only
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1663728
Commit 43fee2b238 ("kbuild: do not redirect the first prerequisite for
filechk") upstream introduced some context diff. This just fixes that up.
Bugzilla: http://bugzilla.redhat.com/1544999
kernel-alt commit b3bbf3db12b8a48491eb4175eae25eb907f092ac
Author: Prarit Bhargava <prarit@redhat.com>
Date: Fri Feb 9 18:09:25 2018 -0500
[kernel] put RHEL info into generated headers
Message-id: <20180209180926.5955-2-prarit@redhat.com>
Patchwork-id: 205585
O-Subject: [RHEL-ALT-7.5 BZ 1542796 1/2] put RHEL info into generated headers
Bugzilla: 1542796
RH-Acked-by: David Arcari <darcari@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Steve Best <sbest@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1542796
rhel7 commit 6199c642a685fba61a298901190659dbedb7c3c3
Author: Jarod Wilson <jarod@redhat.com>
Date: Thu Oct 10 20:14:33 2013 -0400
[redhat] put RHEL info into generated headers
Message-id: <1381436073-8850-1-git-send-email-jarod@redhat.com>
Patchwork-id: 69475
O-Subject: [RHEL7 PATCH] [redhat] put RHEL info into generated headers
Bugzilla:
RH-Acked-by: Neil Horman <nhorman@redhat.com>
RH-Acked-by: Rafael Aquini <aquini@redhat.com>
RH-Acked-by: Kyle McMartin <kmcmarti@redhat.com>
While glancing at the differences between RHEL6 and RHEL7's modifications to the
top-level Makefile, some discrepancies popped up... This brings RHEL7 in line
with all of the customizations we make in RHEL6 to get distro info propagated.
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Upstream Status: RHEL only
Acked-by: Don Zickus <dzickus@redhat.com>
Acked-by: Prarit Bhargava <prarit@redhat.com>
Message-id: <20180511210117.10457-1-msalter@redhat.com>
Patchwork-id: 214708
O-Subject: [RHEL-8 BZ1576869] [RHEL only] acpi: prefer booting with ACPI over DTS
Bugzilla: 1576869
RH-Acked-by: Jonathan Toppins <jtoppins@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Bhupesh Sharma <bhsharma@redhat.com>
RH-Acked-by: Dean Nelson <dnelson@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1576869
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16208479
Testing: Verified kernel defaults to ACPI on Mustang
From: Jonathan Toppins <jtoppins@redhat.com>
This patch forces ACPI boot tables to be preferred over DTS.
Currently for ACPI to be used a user either has to set acpi=on on the
kernel command line or make sure any device tree passed to the kernel
is empty. If the dtb passed to the kernel is non-empty then device-tree
will be chosen as the boot method of choice.
RHEL does not wish to support this boot method so change table boot
preferences to use ACPI. In the event ACPI table checks fail the kernel
will fallback to using DTS to boot.
Signed-off-by: Jonathan Toppins <jtoppins@redhat.com>
Upstream Status: RHEL only
Signed-off-by: Mark Salter <msalter@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Message-id: <20180510173844.29580-4-msalter@redhat.com>
Patchwork-id: 214381
O-Subject: [RHEL-8 BZ1519554 3/3] aarch64: acpi scan: Fix regression related to X-Gene UARTs
Bugzilla: 1519554
RH-Acked-by: Al Stone <astone@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1519554
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16144520
Commit e361d1f858 ("ACPI / scan: Fix enumeration for special UART
devices") caused a regression with some X-Gene based platforms (Mustang
and M400) with invalid DSDT. The DSDT makes it appear that the UART
device is also a slave device attached to itself. With the above commit
the UART won't be enumerated by ACPI scan (slave serial devices shouldn't
be). So check for X-Gene UART device and skip slace device check on it.
Upstream Status: RHEL only
Signed-off-by: Mark Salter <msalter@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Message-id: <20180510173844.29580-3-msalter@redhat.com>
Patchwork-id: 214383
O-Subject: [RHEL-8 BZ1519554 2/3] ACPI / irq: Workaround firmware issue on X-Gene based m400
Bugzilla: 1519554
RH-Acked-by: Al Stone <astone@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1519554
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16144520
The ACPI firmware on the xgene-based m400 platorms erroneously
describes its UART interrupt as ACPI_PRODUCER rather than
ACPI_CONSUMER. This leads to the UART driver being unable to
find its interrupt and the kernel unable find a console.
Work around this by avoiding the producer/consumer check
for X-Gene UARTs.
Upstream Status: RHEL only
Signed-off-by: Mark Salter <msalter@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
There were several changes in the 5.0-rc1 kernel that required
this patch to be rebased with some context diff.
Patchwork-id: 7379
O-Subject: [kernel team] [RHEL8.0 BZ 1544999 1/2] modules: add rhelversion MODULE_INFO tag
Bugzilla: 1544999
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Oleg Nesterov <oleg@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1544999
kernel-alt commit 9816b4b6ca5d4c0504d8806ce99442c90afbc8e6
Author: Prarit Bhargava <prarit@redhat.com>
Date: Fri Feb 9 18:09:26 2018 -0500
[kernel] modules: add rhelversion MODULE_INFO tag
Message-id: <20180209180926.5955-3-prarit@redhat.com>
Patchwork-id: 205587
O-Subject: [RHEL-ALT-7.5 BZ 1542796 2/2] modules: add rhelversion MODULE_INFO tag
Bugzilla: 1542796
RH-Acked-by: David Arcari <darcari@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Steve Best <sbest@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1542796
rhel7 commit 9af8c3992ce5fff253c49abc0dedb3ec77badba4
Author: Kyle McMartin <kmcmarti@redhat.com>
Date: Fri Sep 12 17:46:12 2014 -0400
[kernel] modules: add rhelversion MODULE_INFO tag
Message-id: <20140912174612.GS29420@redacted.bos.redhat.com>
Patchwork-id: 94052
O-Subject: [RHEL7.1 PATCH 2/6 v4] modules: add rhelversion MODULE_INFO tag
Bugzilla: 1110315
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Johannes Weiner <jweiner@redhat.com>
RH-Acked-by: Don Zickus <dzickus@redhat.com>
From: Kyle McMartin <kmcmarti@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1110315
>From kylem's RHEL8 post:
Let's not lose this ability in RHEL8. Sadly can't be applied to RHEL7
because it breaks KABI due to the struct module change.
Inspired by bits of a147e4729d9920ccae2c717ca65c811cc0f93a1d in RHEL6,
which got lost for RHEL7.0. :/
Kyle is correct and doing this would break RHEL7's KABI. I'm taking this
patch in as a base and the next patch will resolve the KABI issues.
[v2]: dzickus, cleanup add_rhelversion()
[v4]: resubmitted along with 16k stacks change
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Cc: Richard Guy Briggs <rgb@redhat.com>
Cc: Peter Rajnoha <prajnoha@redhat.com>
Cc: Laura Abbott <labbott@redhat.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Upstream Status: RHEL only
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Acked-by: Don Zickus <dzickus@redhat.com>
Acked-by: Prarit Bhargava <prarit@redhat.com>
Message-id: <20180227002123.21608-1-ahs3@redhat.com>
Patchwork-id: 206052
O-Subject: [RHEL8 BZ1518076 PATCH] ACPI: APEI: arm64: Ignore broken HPE moonshot APEI support
Bugzilla: 1518076
RH-Acked-by: Mark Salter <msalter@redhat.com>
RH-Acked-by: Jeremy McNicoll <jmcnicol@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1518076
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=15417197
Tested: compile-only; several other patches are required for full booting
QE has tested limited boot (see comment#12 of BZ)
This is a re-post of a RHEL-ALT-7.5 patch specific to aarch64 moonshots
that we use in beaker. It is required for these machines to boot.
commit 8a663a264863efedf8bb4a9d76ac603920fdd739
Author: Robert Richter <rrichter@redhat.com>
Date: Wed Aug 16 19:49:30 2017 -0400
[acpi] APEI: arm64: Ignore broken HPE moonshot APEI support
From: Mark Salter <msalter@redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1344237
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=13768971
Tested: Booted on moonshot with patched 4.11.0-20 kernel
Upstream: RHEL-only
The aarch64 HP moonshot platforms we have in beaker and elsewhere have
a firmware bug which causes a spurious fatal memory error via APEI at
boot time. This platform is no longer supported and no further firmware
updates are expected. This is a downstream-only hack to avoid the problem
by bailing out of HEST table probing if we detect a moonshot HEST table.
Signed-off-by: Mark Salter <msalter@redhat.com>
Signed-off-by: Robert Richter <rrichter@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Upstream Status: RHEL only
Signed-off-by: Al Stone <ahs3@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Message-id: <20191113144431.9403-5-labbott@redhat.com>
Patchwork-id: 286078
O-Subject: [ARK INTERNAL PATCHv2 4/4] [redhat] Add Red Hat tainting
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
This is a combination of the following commits including support
for adding CONFIG_RH_DEPRECATED support
rh_taint: add support
Message-id: <1524831536-47239-1-git-send-email-darcari@redhat.com>
Patchwork-id: 211655
O-Subject: [RHEL8.0 BZ 1565704 v2] rh_taint: add support
Bugzilla: 1565704
RH-Acked-by: Jonathan Toppins <jtoppins@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1565704
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=15910441
Upstream: RHEL Only
Test: Sanity boot of brew build. Previous private build testing of functions.
rh_taint.c adds the following functions which are utilized by Red Hat to
indicate limited or no support for hardware and/or drivers.
mark_hardware_unsupported
mark_hardware_deprecated
mark_tech_preview
See code comments for usage.
RHEL8 change: TAINT_AUX will be used in place of TAINT_TECH_PREVIEW as it
limits the number RHEL only changes that must be made to the kernel.
If at a later date it is determined that additional flags are required,
the associated RHEL only infrastructure can be added at that time.
Cc: David Arcari <darcari@redhat.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
rh_taint: add support for marking driver as unsupported
Message-id: <f42d35b07bd02f34b14a6341a219c80b21a8aff9.1524523802.git.jtoppins@redhat.com>
Patchwork-id: 211020
O-Subject: [RHEL8.0] rh_taint: add support for marking driver as unsupported
Bugzilla: 1565704
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: David Arcari <darcari@redhat.com>
In some cases a driver needs to be enabled by Red Hat to support internal
testing but the driver is not intended to be supported on customer hardware.
This adds a function "make_driver_unsupported()" to facilitate such
situations. The function will print a kernel log message.
Bugzilla: 1565704
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=15873552
Tested: compile only
Signed-off-by: Jonathan Toppins <jtoppins@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
rh_taint: correct loaddable module support dependencies
Message-id: <20181123111337.26898-5-prudo@redhat.com>
Patchwork-id: 233658
O-Subject: [ARK PATCH RESEND v2 4/8] [kernel] rh_taint: correct loaddable module support dependencies
Bugzilla: 1652266
RH-Acked-by: Jakub Racek <jracek@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Cornelia Huck <cohuck@redhat.com>
Bugzilla: 1652266
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=19252944
Upstream Status: RHEL_only
The kernel configuration for the s390/zfcpdump kernel variant turns
loaddable module support off. The build breaks in rh_taint.c due to
compiler errors caused by dereferencing struct module variables which
is just a declaration if CONFIG_MODULES is not set.
To solve this build break, access struct module members only if
CONFIG_MODULES is enabled.
Upstream Status: RHEL only
Signed-off-by: Philipp Rudo <prudo@redhat.com>
Message-id: <20191113144431.9403-2-labbott@redhat.com>
Patchwork-id: 286080
O-Subject: [ARK INTERNAL PATCHv2 1/4] [redhat] Introduce CONFIG_RH_DISABLE_DEPRECATED
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
For many drivers that RHEL doesn't want to support, we've typically deleted
PCI ids from the tree. This precludes those drivers from being used at all
which is fine for RHEL but a problem if we want to use a similar source base
for Fedora. Instead of just deleting IDs, introduce a config
CONFIG_RH_DISABLE_DEPRECATED. This way RHEL can remove IDs while still allowing
kernels to be built with the option off from the same source.
Upstream Status: RHEL only
Signed-off-by: Laura Abbott <labbott@redhat.com>
With the new single workflow, ark-patches is rolled into the os-build
branch. There is no more need to merge the external branch.
Signed-off-by: Don Zickus <dzickus@redhat.com>
The ark-update-configs.sh script is written to be executed from the top of the
git tree. However, from a make -C redhat/ command it is executed from the
redhat/ path. This breaks the script when it needs to generate new configs
(redhat/gen_config_patches.sh).
A simple fix is to execute the script inside the redhat/Makefile from the top
level. The alternative is to teach the script to be location agnostic, but
there is a handful of hardcoded places across 2 scripts that I thought it
wasn't worth it.
Tested by running the 'scheduled' merge-upstream job using my test-os-build
branch where it passed
(https://gitlab.com/cki-project/kernel-ark/-/pipelines/199415525)
Signed-off-by: Don Zickus <dzickus@redhat.com>
This in spirit reverts 0409b21839
and converts the broken out Red Hat patches back into a single diff.
The original idea was to make it easy for the Fedora community to see
what changes Red Hat was making on top of upstream's tarball. The
concept was good, the reality with a source git tree had a flaw.
While 'git merging' with upstream, various conflicts were resolved
through git or the merge. However, when broken out into individual
patches and placed on top of a tarball, this becomes a rebase.
The conflicts could not be resolved with later patches as the initial
patch was a problem. The only solution was to periodically rebase
the source git tree which dampens the spirit of the idea of source-git.
This patch takes another apporach to solve the original problem:
- create a diff from upstream as a single patch
- create a Patchlist.changelog file to list the individual patches
and their shas1 as seen in the source git tree.
This is what was there original and hence the partial revert (though
that patch went through many changes since then).
It isn't perfect, but we are still evolving. This should resolve the
CKI build failures they continuously run into.
Signed-off-by: Don Zickus <dzickus@redhat.com>
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_UACCE:
UACCE provides interface for the user process to access the hardware
without interaction with the kernel space in data path.
The user-space interface is described in
include/uapi/misc/uacce/uacce.h
See Documentation/misc-devices/uacce.rst for more details.
If you don't know what to do here, say N.
Symbol: UACCE [=n]
Type : tristate
Defined at drivers/misc/uacce/Kconfig:1
Prompt: Accelerator Framework for User Land
Depends on: IOMMU_API [=y]
Location:
-> Device Drivers
-> Misc devices
Cc: John Linville <linville@redhat.com>
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_MT7663U:
This adds support for MT7663U 802.11ax 2x2:2 wireless devices.
To compile this driver as a module, choose M here.
Symbol: MT7663U [=n]
Type : tristate
Defined at drivers/net/wireless/mediatek/mt76/mt7615/Kconfig:31
Prompt: MediaTek MT7663U (USB) support
Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_MEDIATEK [=y] && MAC80211 [=m] && USB [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Wireless LAN (WLAN [=y])
-> MediaTek devices (WLAN_VENDOR_MEDIATEK [=y])
Selects: MT76_USB [=m] && MT7615_COMMON [=n]
Cc: Jarod Wilson <jarod@redhat.com>
Cc: John Linville <linville@redhat.com>
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_PHY_QCOM_IPQ806X_USB:
This option enables support for the Synopsis PHYs present inside the
Qualcomm USB3.0 DWC3 controller on ipq806x SoC. This driver supports
both HS and SS PHY controllers.
Symbol: PHY_QCOM_IPQ806X_USB [=n]
Type : tristate
Defined at drivers/phy/qualcomm/Kconfig:108
Prompt: Qualcomm IPQ806x DWC3 USB PHY driver
Depends on: HAS_IOMEM [=y] && OF [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=y]
Cc: John Linville <linville@redhat.com>
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_SERIAL_LANTIQ:
Support for UART on Lantiq and Intel SoCs.
To compile this driver as a module, select M here. The
module will be called lantiq.
Symbol: SERIAL_LANTIQ [=n]
Type : tristate
Defined at drivers/tty/serial/Kconfig:1036
Prompt: Lantiq serial driver
Depends on: TTY [=y] && HAS_IOMEM [=y] && (LANTIQ || X86 [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Character devices
-> Enable TTY (TTY [=y])
-> Serial drivers
Selects: SERIAL_CORE [=y]
Cc: John Linville <linville@redhat.com>
I discovered that several kernel configuration options related to SquashFS decompression are set sub-optimally in Fedora. But the optimal configuration is used in RHEL 8.
If we set those options to match RHEL, a performance improvement could be achieved while reading from compressed SquashFS filesystem.
Please see my original message in Fedora kernel mailing list archive:
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org/thread/4M6WYFOZAZYIEVNZTBVM2BTT7SIEZBNQ/
There you can find an excerpt from Linux documentation for the changed options.
I found the disparity while working on Fedora change proposal:
https://fedoraproject.org/wiki/Changes/OptimizeSquashFS
Signed-off-by: Bohdan Khomutskyi <bkhomuts@redhat.com>
CONFIG_ENERGY_MODEL will help make the schedutil frequency governor
more accurate. This will be useful in the future. It also enables
the use of the energy aware scheduler.
Signed-off-by: Phil Auld <pauld@redhat.com>
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_INFINIBAND_RTRS_CLIENT:
RDMA transport client module.
RDMA Transport (RTRS) client implements a reliable transport layer
and also multipathing functionality and that it is intended to be
the base layer for a block storage initiator over RDMA.
Symbol: INFINIBAND_RTRS_CLIENT [=n]
Type : tristate
Defined at drivers/infiniband/ulp/rtrs/Kconfig:7
Prompt: RTRS client module
Depends on: INFINIBAND [=m] && INFINIBAND_ADDR_TRANS [=y]
Location:
-> Device Drivers
-> InfiniBand support (INFINIBAND [=m])
Selects: INFINIBAND_RTRS [=n]
---
CONFIG_INFINIBAND_RTRS_SERVER:
RDMA transport server module.
RDMA Transport (RTRS) server module processing connection and IO
requests received from the RTRS client module, it will pass the
IO requests to its user eg. RNBD_server.
Symbol: INFINIBAND_RTRS_SERVER [=n]
Type : tristate
Defined at drivers/infiniband/ulp/rtrs/Kconfig:18
Prompt: RTRS server module
Depends on: INFINIBAND [=m] && INFINIBAND_ADDR_TRANS [=y]
Location:
-> Device Drivers
-> InfiniBand support (INFINIBAND [=m])
Selects: INFINIBAND_RTRS [=n]
---
Cc: Kamal Heib <kheib@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_PINCTRL_JASPERLAKE:
This pinctrl driver provides an interface that allows configuring
of Intel Jasper Lake PCH pins and using them as GPIOs.
Symbol: PINCTRL_JASPERLAKE [=n]
Type : tristate
Defined at drivers/pinctrl/intel/Kconfig:114
Prompt: Intel Jasper Lake PCH pinctrl and GPIO driver
Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINCTRL_INTEL [=m]
v2: enable for JASPERLAKE on x86
Cc: David Arcari <darcari@redhat.com>
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_THERMAL_NETLINK:
The thermal framework has a netlink interface to do thermal
zones discovery, temperature readings and events such as
trip point crossed, cooling device update or governor
change. It is recommended to enable the feature.
Symbol: THERMAL_NETLINK [=n]
Type : bool
Defined at drivers/thermal/Kconfig:20
Prompt: Thermal netlink management
Depends on: THERMAL [=y] && NET [=y]
Location:
-> Device Drivers
-> Thermal drivers (THERMAL [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Now that the merge-upstream stage is separated and working, let's
remove it from the release stage. These scripts are already excuted by the
'merge-upstream' stage. This changes just removes the duplication. Trivial
change.
Signed-off-by: Don Zickus <dzickus@redhat.com>
These areas are unassigned in the kernel
- lib/
- drivers/phy
- init/
- drivers/input
- drivers/clk
- drivers/tty
- drivers/misc
- drivers/soc
- mm/
Also fix an out-of-order entry (MMC).
v2: Remove darcari from SYSTEM ON CHIP (darcari)
v3: Helps to actually send the right version of the patch.
RH-Acked-by: David Arcari <darcari@redhat.com>
RH-Acked-by: John W. Linville <linville@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: prarit@redhat.com
Cc: linville@redhat.com
Cc: darcari@redhat.com
Cc: tcamuso@redhat.com
Cc: msalter@redhat.com
Cc: aquini@redhat.com
The serial IR driver is needed for Fedora media-centers.
Re-enable the serial IR module for Fedora.
Suggested-by: Craig Gelowitz <craig@gelowitz.org>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: jbastian@redhat.com
A source git tree's workflow and Fedora's separation of upstream and distro
contributions don't overlap well.
A source git tree is always merging upstream content and downstream content
while avoiding a rebase. By separating the tarballs and patches out, this
effectively causes a rebase. This 'rebase' causes patches to not apply
correctly as git took care of it previously.
This patch creates a Patchlist.changelog file that lists all the SHAs that
are added to the upstream tree.
The goal is to create a useful file such that the source git tree can
create a single tarball and use the Patchlist.changelog file to adhere
to the spirit of the Fedora's separation rules.
No technical changes, just a new file added to the srpm.
Signed-off-by: Don Zickus <dzickus@redhat.com>
I updated the release code to include more changelog info
in the os-build branch. This resulted in adding upstream
merge commits. This is not interesting for a Fedora tree
as it is covered by a generic 'merge' entry.
Use a simple git trick to filter those upstream commits out, "^master".
See 'man gitrevisions' for more tricks.
Signed-off-by: Don Zickus <dzickus@redhat.com>
As part of splitting the merge-upstream and release stages apart,
the merge upstream wasn't working quite right. These are cleanup
fixes to fix that.
The main change is to drop the ark rebase patches script. Running
that through a Makefile through gitlab CI creates a funky environment
where the next script (update-configs.sh) no longer exists because
of the git checkout changes. Keep rebase-patches in the gitlab-ci
script for now.
That will be removed soon enough. No effect on normal workflow.
The other fixes are self-explanatory.
Signed-off-by: Don Zickus <dzickus@redhat.com>
An empty /usr/share/doc/kernel-keys/VR directory is left after executing
an 'rpm -e kernel-core-VR'.
Remove the directory when the rpm is erased.
v2: Only list directory and simplify code (bmeneg)
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
The process_configs.sh created temporary *.config.orig files for each
config variant which were not being properly cleaned up.
Remove *.config.orig files.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: dzickus@redhat.com
Cc: jforbes@redhat.com
Cc: mleitner@redhat.com
Cc: jbenc@redhat.com
The 'process_configs.sh -n -w -c' command on the fedora configs terminates with
Processing /home/prarit/git-kernel/kernel-ark/redhat/configs/kernel-5.8.0-aarch64-debug.config ... Error: Mismatches found in configuration files
Found CONFIG_FORCE_MAX_ZONEORDER=11 after generation, had CONFIG_FORCE_MAX_ZONEORDER=13 in Source tree
make: *** [Makefile:149: fedora-configs] Error 1
The fedora aarch64 CONFIG entry for CONFIG_FORCE_MAX_ZONEORDER notes that
the warning can only be fixed through an out-of-tree patch. Unfortunately
this means that the process_configs checkoptions check cannot be run on
fedora aarch64 configs.
To work around this problem, add a special tag
"process_configs_known_broken" which can be added as a comment to a known
broken CONFIG file. Adding the tag will result in process_configs
checkoptions skipping the CONFIG's error.
Add the process_configs_known_broken flag to process_config.sh and fix
'make fedora-configs' by adding process_configs_known_broken to
CONFIG_FORCE_MAX_ZONEORDER.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: dzickus@redhat.com
Cc: jforbes@redhat.com
Cc: mleitner@redhat.com
Cc: jbenc@redhat.com
The 'dist-configs' is not working properly as it only creates ELN
configs. The 'rh-configs' and 'fedora-configs' targets are not
working properly and should be creating ELN and Fedora configs but they
only create some temporary/intermediate build files. These targets
should output final .config files for each supported arch.
There are several fixes necessary to get the *-configs targets working
properly:
- Fix dist-configs to use a specified flavor instead of only ELN. By
default, dist-configs will build ELN configs.
- Add a flavor parameter to build_config.sh. By default build_config.sh
will use still the configs/flavors file, o/w build_config will only build
the flavor specified.
- Silence a warning in generate_all_configs.sh
Fix the '*-configs' targets to output final .config files for each
supported flavor arch.
Cleanup: Remove unused DIST_TARGET and TARGET variables.
v2: Fix 'make dist-configs' by removing the default setting of FLAVOR (jforbes)
v3: Fix process_configs.sh
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Reported-by: mleitner@redhat.com
Cc: dzickus@redhat.com
Cc: jforbes@redhat.com
Cc: mleitner@redhat.com
Cc: jbenc@redhat.com
As I am also tracking upstream changes in futex code, I may as well add
the futex subsystem entry.
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Waiman Long <longman@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Add myself as maintainer for these two areas
Acked-by: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: David Arcari <darcari@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
mcroce is no longer with Red Hat.
RH-Acked-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
nhorman is no longer at Red Hat.
These are some cleanups and a removal of the SIERRA_NET USB BROADBAND MODEM
which will be captured through other areas.
tcamuso has volunteered to take the ISMT SMBUS driver.
v2: rebase on top of latest tree
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: David Arcari <darcari@redhat.com>
RH-Acked-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: tcamuso@redhat.com
Cc: mleitner@redhat.com
Cc: cleech@redhat.com
Cc: jbenc@redhat.com
SC2006: Use $(...) notation instead of legacy backticked `...`.
SC2086: Double quote to prevent globbing and word splitting.
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
Today ark-latest is built by starting with ark-patches, merging
os-build and applying 'extra' patches from gitlab, and finally
tagged.
In preparation for a single tree workflow where ark-patches disappears,
lets swap the process to make it easier for ark-patches to be
removed.
Instead let's build ark-latest by starting with os-build, merge
ark-patches, apply 'extra' patches and tag it.
Later, it becomes easy to drop the ark-patches merge and when no
'extra' patches exist, ark-latest and os-build are identical.
However, this leads to a changelog quirk. The genspec logic
thinks all the ark-patches are new additions and adds entries
for that whole branch into the changelog because the MARKER has
not changed.
This is noise. For now I created a temporary hack to work around
this until a single workflow is implemented and the problem naturally
goes away.
Signed-off-by: Don Zickus <dzickus@redhat.com>
Currently, ark-latest is built, version bumped and the gitlab-ci.yml
file secretly copies that changelog back to os-build.
I think we can improve that process, but it requires a change in
the release behaviour, version bump os-build first, then create
ark-latest and version bump a second time.
The second version bump should have a small changelog and only
captures the 'extra' patches that are necessary for the release.
This _is_ a behaviour change for the changelog and kernel NVR.
Signed-off-by: Don Zickus <dzickus@redhat.com>
The dist-release target allows the caller to repeatedly bump
the version in Makefile.rhelver, even though no changes was
added.
Change this behaviour to _only_ bump the version when either
a changelog entry was detected or the marker file was updated,
otherwise skip the version bump.
This becomes necessary for the next patch, when I change the
behaviour of the release script. I intend to version bump
the os-build branch first, then create ark-latest and version
bump again. Later when we consolidate to a single tree workflow,
there will be scenarios where os-build and ark-latest are identical
and the second version bump will be unnecessary.
This change is not expected to change anything, unless blind version
bumps are expected in certain scenarios.
Signed-off-by: Don Zickus <dzickus@redhat.com>
This is a target that will create the rawhide branch, ark-latest.
It is mostly copied from the gitlab-ci.yml and turned into a
Makefile target for easier understanding and execution.
An optimization is to move some of the duplicate code to
git-tree-check and replace git-status with git-diff-index
to make it easier to detect a dirty tree.
This target will be called by the maintainer and the gitlab-ci.yml
file. Currently unused.
No noticable changes.
Signed-off-by: Don Zickus <dzickus@redhat.com>
Back with commit 3a65b42715, make
dist-git was changed to depend on dist-srpm instead of the spec
file. As a result some legacy optimizations are now redundant,
remove them.
In dist-git, dist-srpm depends on TARBALL, so remove the explict
dependency in dist-git.
In dist-release-finish, dist-srpm calls dist-configs, dist-kabi,
dist-kabi-dup, sources-rh, so remove them too.
These cleanups also help speed up release testing. :-)
No noticable changes expected.
Signed-off-by: Don Zickus <dzickus@redhat.com>
I would like to use the TAG variable as input to the make merge and
release targets. This allows the maintainer to control where the
merge or release starts from.
The internal variable TAG conflicts with this when the external TAG
is empty. The Makefile accidentally chooses the internal TAG variable.
Resolve this by renaming the internal TAG variable to _TAG. This
allows the scripts to pass in an external TAG variable with no
conflict.
The internal TAG variable is not used anywhere outside
Makefile.common.
No expected changes, purely cosmetic.
Signed-off-by: Don Zickus <dzickus@redhat.com>
Delete Neil from NETWORKING [GENERAL] and SCTP PROTOCOL, since he left Red
Hat. Add Marcelo as a networking maintainer.
RH-Acked-by: John W. Linville <linville@redhat.com>
RH-Acked-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Reassign the QAT maintenance to vdronov and tcamuso.
RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
RH-Acked-by: John W. Linville <linville@redhat.com>
RH-Acked-by: Steve Best <sbest@redhat.com>
Signed-off-by: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Assign sections of the kernel to the appropriate entities
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: John W. Linville <linville@redhat.com>
[Prarit - This patch was lost and brought forward with a simple rebase.]
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Cc: Eric Sandeen <esandeen@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Jakub Racek <jracek@redhat.com>
Cc: John Linville <linville@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Rob Clark <rclark@redhat.com>
I'm taking over the primary role for DMA Mapping
so update the maintainers entry.
RH-Acked-by: Myron Stowe <mstowe@redhat.com
RH-Acked-by: Don Dutile <ddutile@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Donald Dutile <ddutile@redhat.com>
Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
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_NVME_TARGET_PASSTHRU:
This enables target side NVMe passthru controller support for the
NVMe Over Fabrics protocol. It allows for hosts to manage and
directly access an actual NVMe controller residing on the target
side, incuding executing Vendor Unique Commands.
If unsure, say N.
Symbol: NVME_TARGET_PASSTHRU [=n]
Type : bool
Defined at drivers/nvme/target/Kconfig:19
Prompt: NVMe Target Passthrough support
Depends on: NVME_TARGET [=m] && (NVME_CORE [=m]=y || NVME_CORE [=m]=NVME_TARGET [=m])
Location:
-> Device Drivers
-> NVME Support
-> NVMe Target support (NVME_TARGET [=m])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_SPI_CADENCE_QUADSPI:
Enable support for the Cadence Quad SPI Flash controller.
Cadence QSPI is a specialized controller for connecting an SPI
Flash over 1/2/4-bit wide bus. Enable this option if you have a
device with a Cadence QSPI controller and want to access the
Flash as an MTD device.
Symbol: SPI_CADENCE_QUADSPI [=n]
Type : tristate
Defined at drivers/spi/Kconfig:204
Prompt: Cadence Quad SPI controller
Depends on: SPI [=y] && SPI_MASTER [=y] && OF [=y] && (ARM || ARM64 [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> SPI support (SPI [=y])
---
CONFIG_SPI_LANTIQ_SSC:
This driver supports the Lantiq SSC SPI controller in master
mode. This controller is found on Intel (former Lantiq) SoCs like
the Danube, Falcon, xRX200, xRX300, Lightning Mountain.
Symbol: SPI_LANTIQ_SSC [=n]
Type : tristate
Defined at drivers/spi/Kconfig:502
Prompt: Lantiq SSC SPI controller
Depends on: SPI [=y] && SPI_MASTER [=y] && (LANTIQ || X86 [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> SPI support (SPI [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
move from 'fedora' to 'common', and remove the explicit disable from ark,
so it's enabled in the same way both on ark and fedora.
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
move from 'fedora' to 'common', and remove the explicit disable from ark,
so it's enabled in the same way both on ark and fedora.
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
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_KEEMBAY:
This enables support for Intel Movidius SoC code-named Keem Bay.
Symbol: ARCH_KEEMBAY [=n]
Type : bool
Defined at arch/arm64/Kconfig.platforms:139
Prompt: Keem Bay SoC
Location:
-> Platform selection
---
CONFIG_ARCH_SPARX5:
This enables support for the Microchip Sparx5 ARMv8-based
SoC family of TSN-capable gigabit switches.
The SparX-5 Ethernet switch family provides a rich set of
switching features such as advanced TCAM-based VLAN and QoS
processing enabling delivery of differentiated services, and
security through TCAM-based frame processing using versatile
content aware processor (VCAP).
Symbol: ARCH_SPARX5 [=n]
Type : bool
Defined at arch/arm64/Kconfig.platforms:92
Prompt: ARMv8 based Microchip Sparx5 SoC family
Location:
-> Platform selection
Selects: PINCTRL [=y] && DW_APB_TIMER_OF [=n]
---
Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_HW_RANDOM_BA431:
This driver provides kernel-side support for the Random Number
Generator hardware based on Silex Insight BA431 IP.
To compile this driver as a module, choose M here: the
module will be called ba431-rng.
Symbol: HW_RANDOM_BA431 [=n]
Type : tristate
Defined at drivers/char/hw_random/Kconfig:77
Prompt: Silex Insight BA431 Random Number Generator support
Depends on: HW_RANDOM [=y] && HAS_IOMEM [=y]
Location:
-> Device Drivers
-> Character devices
-> Hardware Random Number Generator Core support (HW_RANDOM [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_SMCCC_SOC_ID:
Include support for the SoC bus on the ARM SMCCC firmware based
platforms providing some sysfs information about the SoC variant.
Symbol: ARM_SMCCC_SOC_ID [=y]
Type : bool
Defined at drivers/firmware/smccc/Kconfig:18
Prompt: SoC bus device for the ARM SMCCC SOC_ID
Depends on: HAVE_ARM_SMCCC_DISCOVERY [=y]
Location:
-> Firmware Drivers
Selects: SOC_BUS [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_MT7663S:
This adds support for MT7663S 802.11ac 2x2:2 wireless devices.
To compile this driver as a module, choose M here.
Symbol: MT7663S [=n]
Type : tristate
Defined at drivers/net/wireless/mediatek/mt76/mt7615/Kconfig:46
Prompt: MediaTek MT7663S (SDIO) support
Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_MEDIATEK [=y] && MAC80211 [=m] && MMC [=m]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Wireless LAN (WLAN [=y])
-> MediaTek devices (WLAN_VENDOR_MEDIATEK [=y])
Selects: MT76_SDIO [=n] && MT7663_USB_SDIO_COMMON [=n]
---
CONFIG_RTW88_8821CE:
Select this option will enable support for 8821CE chipset
802.11ac PCIe wireless network adapter
Symbol: RTW88_8821CE [=n]
Type : tristate
Defined at drivers/net/wireless/realtek/rtw88/Kconfig:64
Prompt: Realtek 8821CE PCI wireless network adapter
Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_REALTEK [=y] && RTW88 [=m] && PCI [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Wireless LAN (WLAN [=y])
-> Realtek devices (WLAN_VENDOR_REALTEK [=y])
-> Realtek 802.11ac wireless chips support (RTW88 [=m])
Selects: RTW88_CORE [=m] && RTW88_PCI [=m] && RTW88_8821C [=n]
---
CONFIG_WLAN_VENDOR_MICROCHIP:
If you have a wireless card belonging to this class, say Y.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all the
questions about these cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol: WLAN_VENDOR_MICROCHIP [=y]
Type : bool
Defined at drivers/net/wireless/microchip/Kconfig:2
Prompt: Microchip devices
Depends on: NETDEVICES [=y] && WLAN [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Wireless LAN (WLAN [=y])
---
Cc: Jarod Wilson <jarod@redhat.com>
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_SND_HDA_INTEL_HDMI_SILENT_STREAM:
Intel hardware has a feature called 'silent stream', that
keeps external HDMI receiver's analog circuitry powered on
avoiding 2-3 sec silence during playback start. This mechanism
relies on setting channel_id as 0xf, sending info packet and
preventing codec D3 entry (increasing platform static power
consumption when HDMI receiver is plugged-in). 2-3 sec silence
at the playback start is expected whenever there is format change.
(default is 2 channel format).
Say Y to enable Silent Stream feature.
Symbol: SND_HDA_INTEL_HDMI_SILENT_STREAM [=n]
Type : bool
Defined at sound/pci/hda/Kconfig:243
Prompt: Enable Silent Stream always for HDMI
Depends on: SOUND [=m] && !UML && SND [=m] && SND_HDA [=m] && SND_HDA_INTEL [=m]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> HD-Audio
---
Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Updates for aarch64/ARMv7 for the first part of the 5.9 merge window
and catch up on the outstanding pending-fedora ones I missed.
There's two deletion of obolete Kconfig options for ark too.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
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_RCU_REF_SCALE_TEST:
This option provides a kernel module that runs performance tests
useful comparing RCU with various read-side synchronization mechanisms.
The kernel module may be built after the fact on the running kernel to be
tested, if desired.
Say Y here if you want these performance tests built into the kernel.
Say M if you want to build it as a module instead.
Say N if you are unsure.
Symbol: RCU_REF_SCALE_TEST [=n]
Type : tristate
Defined at kernel/rcu/Kconfig.debug:64
Prompt: Scalability tests for read-side synchronization (RCU and others)
Depends on: DEBUG_KERNEL [=y]
Location:
-> Kernel hacking
-> RCU Debugging
Selects: TORTURE_TEST [=n] && SRCU [=y] && TASKS_RCU [=n] && TASKS_RUDE_RCU [=y] && TASKS_TRACE_RCU [=n]
---
Cc: Waiman Long <longman@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_TEST_FPU:
Enable this option to add /sys/kernel/debug/selftest_helpers/test_fpu
which will trigger a sequence of floating point operations. This is used
for self-testing floating point control register setting in
kernel_fpu_begin().
If unsure, say N.
Symbol: TEST_FPU [=n]
Type : tristate
Defined at lib/Kconfig.debug:2317
Prompt: Test floating point operations in kernel space
Depends on: RUNTIME_TESTING_MENU [=y] && X86 [=y] && !KCOV_INSTRUMENT_ALL [=n]
Location:
-> Kernel hacking
-> Kernel Testing and Coverage
-> Runtime Testing (RUNTIME_TESTING_MENU [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_GPIO_PCA9570:
Say yes here to enable the GPO driver for the NXP PCA9570 chip.
To compile this driver as a module, choose M here: the module will
be called gpio-pca9570.
Symbol: GPIO_PCA9570 [=n]
Type : tristate
Defined at drivers/gpio/Kconfig:965
Prompt: PCA9570 4-Bit I2C GPO expander
Depends on: GPIOLIB [=y] && I2C [=y]
Location:
-> Device Drivers
-> GPIO Support (GPIOLIB [=y])
-> I2C GPIO expanders
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_INV_ICM42600_I2C:
This driver supports the InvenSense ICM-426xx motion tracking
devices over I2C.
This driver can be built as a module. The module will be called
inv-icm42600-i2c.
Symbol: INV_ICM42600_I2C [=n]
Type : tristate
Defined at drivers/iio/imu/inv_icm42600/Kconfig:7
Prompt: InvenSense ICM-426xx I2C driver
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Inertial measurement units
Selects: INV_ICM42600 [=n] && REGMAP_I2C [=m]
---
CONFIG_INV_ICM42600_SPI:
This driver supports the InvenSense ICM-426xx motion tracking
devices over SPI.
This driver can be built as a module. The module will be called
inv-icm42600-spi.
Symbol: INV_ICM42600_SPI [=n]
Type : tristate
Defined at drivers/iio/imu/inv_icm42600/Kconfig:19
Prompt: InvenSense ICM-426xx SPI driver
Depends on: IIO [=m] && SPI_MASTER [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Inertial measurement units
Selects: INV_ICM42600 [=n] && REGMAP_SPI [=m]
---
CONFIG_SCD30_CORE:
Say Y here to build support for the Sensirion SCD30 sensor with carbon
dioxide, relative humidity and temperature sensing capabilities.
To compile this driver as a module, choose M here: the module will
be called scd30_core.
Symbol: SCD30_CORE [=n]
Type : tristate
Defined at drivers/iio/chemical/Kconfig:88
Prompt: SCD30 carbon dioxide sensor driver
Depends on: IIO [=m]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Chemical Sensors
Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_SENSORS_CORSAIR_CPRO:
If you say yes here you get support for the Corsair Commander Pro
controller.
This driver can also be built as a module. If so, the module
will be called corsair-cpro.
Symbol: SENSORS_CORSAIR_CPRO [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:442
Prompt: Corsair Commander Pro controller
Depends on: HWMON [=y] && HID [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_LEDS_CLASS_MULTICOLOR:
This option enables the multicolor LED sysfs class in /sys/class/leds.
It wraps LED class and adds multicolor LED specific sysfs attributes
and kernel internal API to it. You'll need this to provide support
for multicolor LEDs that are grouped together. This class is not
intended for single color LEDs. It can be built as a module.
Symbol: LEDS_CLASS_MULTICOLOR [=n]
Type : tristate
Defined at drivers/leds/Kconfig:33
Prompt: LED Multicolor Class Support
Depends on: NEW_LEDS [=y] && LEDS_CLASS [=y]
Location:
-> Device Drivers
-> LED Support (NEW_LEDS [=y])
-> LED Class Support (LEDS_CLASS [=y])
---
CONFIG_LEDS_LP55XX_COMMON:
This option supports common operations for LP5521/5523/55231/5562/8501
devices.
Symbol: LEDS_LP55XX_COMMON [=n]
Type : tristate
Defined at drivers/leds/Kconfig:398
Prompt: Common Driver for TI/National LP5521/5523/55231/5562/8501
Depends on: NEW_LEDS [=y] && (LEDS_CLASS_MULTICOLOR [=n] || !LEDS_CLASS_MULTICOLOR [=n]) && OF [=y] && I2C [=y]
Location:
-> Device Drivers
-> LED Support (NEW_LEDS [=y])
Selects: FW_LOADER [=y] && FW_LOADER_USER_HELPER [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_CEC_CH7322:
This is a driver for the Chrontel CH7322 CEC controller. It uses the
generic CEC framework interface.
CEC bus is present in the HDMI connector and enables communication
between compatible devices.
Symbol: CEC_CH7322 [=n]
Type : tristate
Defined at drivers/media/cec/i2c/Kconfig:5
Prompt: Chrontel CH7322 CEC controller
Depends on: MEDIA_CEC_SUPPORT [=y] && I2C [=y]
Location:
-> Device Drivers
-> HDMI CEC drivers (MEDIA_CEC_SUPPORT [=y])
Selects: REGMAP_I2C [=m] && CEC_CORE [=m]
---
CONFIG_VIDEO_DW9768:
This is a driver for the DW9768 camera lens voice coil.
DW9768 is a 10 bit DAC with 100mA output current sink
capability. This is designed for linear control of
voice coil motors, controlled via I2C serial interface.
Symbol: VIDEO_DW9768 [=n]
Type : tristate
Defined at drivers/media/i2c/Kconfig:1283
Prompt: DW9768 lens voice coil support
Depends on: MEDIA_SUPPORT [=m] && I2C [=y] && VIDEO_V4L2 [=m]
Visible if: MEDIA_SUPPORT [=m] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
Location:
-> Device Drivers
-> Multimedia support (MEDIA_SUPPORT [=m])
-> Media ancillary drivers
-> Lens drivers
Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && V4L2_FWNODE [=n]
---
CONFIG_VIDEO_RDACM20:
This driver supports the IMI RDACM20 GMSL camera, used in
ADAS systems.
This camera should be used in conjunction with a GMSL
deserialiser such as the MAX9286.
Symbol: VIDEO_RDACM20 [=n]
Type : tristate
Defined at drivers/media/i2c/Kconfig:1174
Prompt: IMI RDACM20 camera support
Depends on: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y]
Visible if: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y] && MEDIA_CAMERA_SUPPORT [=y]
Location:
-> Device Drivers
-> Multimedia support (MEDIA_SUPPORT [=m])
-> Media ancillary drivers
-> Camera sensor devices
Selects: V4L2_FWNODE [=n] && VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_MLX5_IPSEC:
Build IPsec support for the Connect-X family of network cards by Mellanox
Technologies.
Note: If you select this option, the mlx5_core driver will include
IPsec support for the Connect-X family.
Symbol: MLX5_IPSEC [=n]
Type : bool
Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:137
Prompt: Mellanox Technologies IPsec Connect-X support
Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_CORE_EN [=y] && XFRM_OFFLOAD [=y] && (INET_ESP_OFFLOAD [=m] || INET6_ESP_OFFLOAD [=m])
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Ethernet driver support (ETHERNET [=y])
-> Mellanox devices (NET_VENDOR_MELLANOX [=y])
Selects: MLX5_ACCEL [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_PCI_J721E_HOST:
Say Y here if you want to support the TI J721E PCIe platform
controller in host mode. TI J721E PCIe controller uses Cadence PCIe
core.
Symbol: PCI_J721E_HOST [=n]
Type : bool
Defined at drivers/pci/controller/cadence/Kconfig:48
Prompt: TI J721E PCIe platform host controller
Depends on: PCI [=y] && OF [=y]
Location:
-> Device Drivers
-> PCI support (PCI [=y])
-> PCI controller drivers
-> Cadence PCIe controllers support
Selects: PCIE_CADENCE_HOST [=n] && PCI_J721E [=n]
---
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@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_CHARGER_BQ2515X:
Say Y to enable support for the TI BQ2515X family of battery
charging integrated circuits. The BQ2515X are highly integrated
battery charge management ICs that integrate the most common
functions for wearable devices, namely a charger, an output voltage
rail, ADC for battery and system monitoring, and push-button
controller.
Symbol: CHARGER_BQ2515X [=n]
Type : tristate
Defined at drivers/power/supply/Kconfig:613
Prompt: TI BQ2515X battery charger family
Depends on: POWER_SUPPLY [=y] && I2C [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Power supply class support (POWER_SUPPLY [=y])
Selects: REGMAP_I2C [=m]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_SERIAL_IMX_EARLYCON:
If you have enabled the earlycon on the Freescale IMX
CPU you can make it the earlycon by answering Y to this option.
Symbol: SERIAL_IMX_EARLYCON [=n]
Type : bool
Defined at drivers/tty/serial/Kconfig:518
Prompt: Earlycon on IMX serial port
Depends on: TTY [=y] && HAS_IOMEM [=y] && OF [=y]
Location:
-> Device Drivers
-> Character devices
-> Enable TTY (TTY [=y])
-> Serial drivers
Selects: SERIAL_EARLYCON [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_USB_OTG_PRODUCTLIST:
If you say Y here, the "otg_productlist.h" file will be used as a
product list, so USB peripherals not listed there will be
rejected during enumeration. This behavior is required by the
USB OTG and EH specification for all devices not on your product's
"Targeted Peripherals List". "Embedded Hosts" are likewise
allowed to support only a limited number of peripherals.
Symbol: USB_OTG_PRODUCTLIST [=n]
Type : bool
Defined at drivers/usb/core/Kconfig:58
Prompt: Rely on OTG and EH Targeted Peripherals List
Depends on: USB_SUPPORT [=y] && USB [=y]
Location:
-> Device Drivers
-> USB support (USB_SUPPORT [=y])
---
Cc: Torez Smith <torez@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
The SND_HDA_INTEL is actually badly named as it covers HDMI audio in a number
of use cases such as discrete nvidia and amd GPUs on POWER and aarch64. It
may have originally been an Intel only option but now it's basically appears
to be a generic HDMI Audio config option so basically we should enable it
where ever we enable sound, it's enabled as a module already in configs/generic,
so we shouldn't actually need to override it anywhere so remove the other options
they are either the same or do override it.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
The new ZSTD compression algorithm is generally faster/smaller so we want to
support it in all kernels so turn the functionality on universally.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
We'll need this functionality on all arm kernels so enable it in generic
Cc: Al Stone <ahs3@redhat.com>
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
The following two chemical/partical sensors are quite common so enable
them to make them easier to use.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
Currently all the magic to sync upstream with os-build and ark-patches
is done through scripts in redhat/scripts/ci and .gitlab-ci.yml.
Make this easier by enabling this routine through a redhat/Makefile.
This allows:
* gitlab-ci.yml and maintainer to use same script
* allows maintainer to run local test runs before committing
* developers to hack on things a little more easily
This change also adds the ability to 'git push' the changes. This is
safe because os-build and ark-patches are considered 'protected'
branches meaning only the developers in the 'Maintainers' group can
push to those branches (which is a tiny group right now).
Because I can't atomically commit this change and the change to
kernel-ark-ci's gitlab-ci.yml file, I need this change to go in first.
Then I can modify the gitlab-ci.yml file.
Functionally, this change should be no different than what currently
runs today.
Avoid constantly running the config update scripts when the merge to
master did not update anything. This means there can be no new
configs to generate.
Same argument for ark-patches.
The only downside I see with this check is if the generate config
scripts fail and this needs to be re-run. But we should be able
to do that by hand.
Signed-off-by: Don Zickus <dzickus@redhat.com>
As a step towards switching away from the os-build branch start by
using more variables.
The patch does 2 things:
* adds a use of PROJECT_ID
* replace os-build with BRANCH in the update configs script
Signed-off-by: Don Zickus <dzickus@redhat.com>
'make setup-source' is failing with, for example,
fatal: Not a valid object name master
BUILDID is "hello". Update '/home/prarit/git-kernel/kernel-ark/localversion' to change.
Gathering new log entries since 2eb3eaedb74aa011774bb95fd6516d6d7858d0f8
fatal: ambiguous argument 'itd3590ebf6f91.1-1-..': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
As of 5.7.0 new tags were added to the tree of the form
kernel-5.8.0-0.rc7.20200730gitd3590ebf6f91.1
After applying a patch the value of "git describe" is
kernel-5.8.0-0.rc7.20200730gitd3590ebf6f91.1-1-gd76dfb51aa86. This string
is stored in TAG which is used by MARKER. The value of MARKER is set
using a cut command on 'g' which results in MARKER being set to
"it69119673bd50.1" instead of "d76dfb51aa86"
The problem with continuing to use cut and 'g' is that the tag string
may change again. It is safer to use awk and '-g'.
Use awk instead of cut to evaluate MARKER.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Both redhat/ and the makefile are publicly available. There is no reason
to exclude them from tarballs, etc.
Remove the export restrictions on redhat/ and the makefile.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
As part of the transition for the boothole vulnerability, we are signing
the kernel with both new keys and the old keys. These are the spec
changes to make that happen. We have actually been building with this
for some time, but didn't want to push the changes until it was public.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
Fixes found with 'evaluate_configs -j'
Verified via
make rh-configs
cp configs/*.config /tmp/rh-orig
evaluate_configs -j
make rh-configs
cp configs/*.config /tmp/rh-new
diff /tmp/rh-orig /tmp/rh-new
which shows no net changes to the final .config files.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Fixes found with './evaluate_configs -p priority.[rhel|fedora] -f'
Verified via
make rh-configs
cp configs/*.config /tmp/rh-orig
evaluate_configs -p priority.rhel -f
make rh-configs
cp configs/*.config /tmp/rh-new
diff /tmp/rh-orig /tmp/rh-new
and
make fedora-configs
cp configs/*.config /tmp/fedora-orig
evaluate_configs -p priority.fedora -f
make fedora-configs
cp configs/*.config /tmp/fedora-new
diff /tmp/fedora-orig /tmp/fedora-new
which shows no net changes to the final .config files.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
evaluate_configs is a tool that verifies the CONFIG setting hierarchy for
the kernel. It can display settings for a specific CONFIG, find and
remove extra CONFIG files and synchronize the CONFIG settings between
the common, ark, and fedora directories.
For example, to view a config,
[prarit@prarit configs]$ ./evaluate_configs -p priority.rhel -c CONFIG_HEADER_TEST
CONFIG_HEADER_TEST
legend g ga1 ga2 d da1 da2
common-x86_64 y - - - X -
common-ppc64le y - X - - X
common-s390x y - X - - X
common-s390x-zfcpdump y - - X X X
common-aarch64 y - - - X -
ark-x86_64 y - - - X -
ark-ppc64le y - X - - X
ark-s390x y - X - - X
ark-s390x-zfcpdump y - - X X X
ark-aarch64 y - - - X -
pending-common-x86_64 - - - - X -
pending-common-ppc64le - - X - - X
pending-common-s390x - - X - - X
pending-common-s390x-zfcpdump - - - X X X
pending-common-aarch64 - - - - X -
The legend row, shows the subdirectory entries. These can be mapped
back to the priority.rhel entries, for example, for x86_64
x86_64=generic:generic-x86:generic-x86-x86_64
x86_64-debug=generic:generic-x86:generic-x86-x86_64:debug:debug-x86-x86_64
are combined into one entry for x86_64 where
g maps to "generic"
ga1 maps to "generic-x86"
ga2 maps to "generic-x86-x86-64"
d maps to "debug"
da1 maps to nothing (more on this below)
da2 maps to debug-x86-x86_64
The left hand column indicates the directory and config-variant. For
example, ark-s390x-zfcpdump is the s390x-zfcpdump variant and the
row beside it shows the config settings in the ark directory.
The data contained in the output can have 5 values:
y = CONFIG is set to 'y'
m = CONFIG is set to 'm'
n = CONFIG is set to 'is not set'
- = CONFIG file does not exist
X = CONFIG file entry is not in priority file
As can be seen above in the CONFIG_HEADER_TEST output, da1 is not present
in the priority.rhel file and is marked with an 'X'.
The -f option can be used to evaluate all the CONFIGs by executing, for
example
|# evaluate_configs -p priority.rhel -f
or a single CONFIG
|# evaluate_configs -p priority.rhel -f -c CONFIG_HEADER_TEST
and similarily the common, ark and fedora CONFIGs can be verified by
executing
evaluate_configs -j
or
evaluate_configs -j -c CONFIG_HEADER_TEST
The two CONFIG patches in this patchset are runs of
evaluate_configs -p priority.rhel -f
evaluate_configs -p priority.fedora -f
and
evaluate_configs -j
v2: Documentation cleanup (herton)
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Resending ... no acks.
P.
---8<---
An engineer pinged me this morning trying to figure out how to build
fc32 builds in the ARK tree. There are no fc32 tags since we didn't
start tagging until very recently.
Add a comment about when we started tagging Fedora RPMs in the ARK tree.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: jforbes@redhat.com
The DRM_PANEL_XINGBANGDA_XBD599 panel was in fact a DRM_PANEL_SITRONIX_ST7703 so
it's being renamed upstream.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
This was enabled in Fedora kenels, except due to the weird KConfig bits
the actual config wasn't enabled in the end kernel build. This fixes is for
SPI which appears in some devices for RS-485 use cases.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
With Btrfs being used by default, having our debug kernels offer
more debugging information can be helpful for driving improvements
into the filesystem.
Signed-off-by: Neal Gompa <ngompa@fedoraproject.org>
Now that we are using Btrfs by default on most flavors of Fedora,
let's have the Btrfs filesystem built into the kernel to make
booting without an initramfs work.
Reference: https://fedoraproject.org/wiki/Changes/BtrfsByDefault
Signed-off-by: Neal Gompa <ngompa@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_DM_EBS:
dm-ebs emulates smaller logical block size on backing devices
with larger ones (e.g. 512 byte sectors on 4K native disks).
Symbol: DM_EBS [=n]
Type : tristate
Defined at drivers/md/Kconfig:340
Prompt: Emulated block size target (EXPERIMENTAL)
Depends on: MD [=y] && BLK_DEV_DM [=m]
Location:
-> Device Drivers
-> Multiple devices driver support (RAID and LVM) (MD [=y])
-> Device mapper support (BLK_DEV_DM [=m])
Selects: DM_BUFIO [=m]
---
CONFIG_DM_MULTIPATH_HST:
This path selector is a dynamic load balancer which selects
the path expected to complete the incoming I/O in the shortest
time by comparing estimated service time (based on historical
service time).
If unsure, say N.
Symbol: DM_MULTIPATH_HST [=n]
Type : tristate
Defined at drivers/md/Kconfig:455
Prompt: I/O Path Selector based on historical service time
Depends on: MD [=y] && DM_MULTIPATH [=m]
Location:
-> Device Drivers
-> Multiple devices driver support (RAID and LVM) (MD [=y])
-> Device mapper support (BLK_DEV_DM [=m])
-> Multipath target (DM_MULTIPATH [=m])
---
Cc: Nigel Croxon <ncroxon@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
In 5.8-rc1, a change was made to not always generate a Module.symvers
file if no modules were built. The s390x zfcpdump variant is a kernel
that is built with no modules enabled.
The kernel.spec file assumes Module.symvers always exists and fails to
build the zfcpdump variant.
Modify the spec file to detect the missing file and 'touch' it as a
workaround. This file is used utilized by the kabi technology. There
is probably a better long term fix, but this is the quick and easy fix.
Tested locally using cross-compilers.
Looking for reviews ... repost.
P.
---8<---
Config file commands create .tmp files which can be picked up by git
commands.
Add .tmp files to .gitignore.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
build of cdg in ARK is already disabled: disable hybla, hsctp, illinois,
lp, scalable, vegas, veno and yeah as well.
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
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_MFD_IQS62X:
Say Y here if you want to build core support for the Azoteq IQS620A,
IQS621, IQS622, IQS624 and IQS625 multi-function sensors. Additional
options must be selected to enable device-specific functions.
To compile this driver as a module, choose M here: the module will
be called iqs62x.
Symbol: MFD_IQS62X [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:645
Prompt: Azoteq IQS620A/621/622/624/625 core support
Depends on: HAS_IOMEM [=y] && I2C [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: MFD_CORE [=y] && REGMAP_I2C [=m]
---
A general update to RHMAINTAINERS.
All people and lists mentioned in this file have agreed to the
Fedora Privacy Policy here:
https://fedoraproject.org/wiki/Legal:PrivacyPolicy#Publicly_Available_Personal_Data
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Brian Masney <bmasney@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: Chris Leech <cleech@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Gopal Tiwari <gtiwari@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Jerome Marchand <jmarchan@redhat.com>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Josef Oskera <joskera@redhat.com>
Cc: Justin Forbes <jforbes@redhat.com>
Cc: Kamal Heib <kheib@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Michal Schmidt <mschmidt@redhat.com>
Cc: Miklos Szeredi <mszeredi@redhat.com>
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Patrick Talbert <ptalbert@redhat.com>
Cc: Rafael Aquini <aquini@redhat.com>
Cc: Richard Guy Briggs <rbriggs@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>
Cc: Toke Høiland-Jørgensen <toke@redhat.com>
Cc: Tom Rix <trix@redhat.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Cc: Yauheni Kaliuta <ykaliuta@redhat.com>
There are times when I have to generate both Fedora and RHEL configs.
Add fedora-configs and rh-configs make targets.
v2: Add rh-help entries.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
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_I2C_QCOM_CCI:
If you say yes to this option, support will be included for the
built-in camera control interface on the Qualcomm SoCs.
This driver can also be built as a module. If so, the module
will be called i2c-qcom-cci.
Symbol: I2C_QCOM_CCI [=n]
Type : tristate
Defined at drivers/i2c/busses/Kconfig:900
Prompt: Qualcomm Camera Control Interface
Depends on: I2C [=y] && HAS_IOMEM [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> I2C support
-> I2C support (I2C [=y])
-> I2C Hardware Bus support
---
Cc: Gopal Tiwari <gtiwari@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
I was playing around with SINGLE_TARBALL=1 to workaround an issue and
noticed the patch for breaking out individual patches did not account
for that scenario.
The srpm fails to generate due to the missing Patchlist file, which
is used to track the individual patch files.
Fix this by creating a empty file to use or 'touch $SOURCES/Patchlist'.
This allows the srpm to package all the necessary files. I tested the
'prep' stage of rpmbuild and this empty file has no side effects.
Signed-off-by: Don Zickus <dzickus@redhat.com>
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_HW_RANDOM_CCTRNG:
Say 'Y' to enable the True Random Number Generator driver for the
Arm TrustZone CryptoCell family of processors.
Currently the CryptoCell 713 and 703 are supported.
The driver is supported only in SoC where Trusted Execution
Environment is not used.
Choose 'M' to compile this driver as a module. The module
will be called cctrng.
If unsure, say 'N'.
Symbol: HW_RANDOM_CCTRNG [=n]
Type : tristate
Defined at drivers/char/hw_random/Kconfig:477
Prompt: Arm CryptoCell True Random Number Generator support
Depends on: HW_RANDOM [=y] && HAS_IOMEM [=y] && OF [=y]
Location:
-> Device Drivers
-> Character devices
-> Hardware Random Number Generator Core support (HW_RANDOM [=y])
---
Signed-off-by: CKI@GitLab <cki-project@redhat.com>
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_DMABUF_HEAPS:
Choose this option to enable the DMA-BUF userland memory heaps.
This options creates per heap chardevs in /dev/dma_heap/ which
allows userspace to allocate dma-bufs that can be shared
between drivers.
Symbol: DMABUF_HEAPS [=n]
Type : bool
Defined at drivers/dma-buf/Kconfig:47
Prompt: DMA-BUF Userland Memory Heaps
Location:
-> Device Drivers
-> DMABUF options
Selects: DMA_SHARED_BUFFER [=y]
Enabled at the request of Lyude Paul.
---
Cc: Don Dutile <ddutile@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
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_MFD_GATEWORKS_GSC:
Enable support for the Gateworks System Controller (GSC) found
on Gateworks Single Board Computers supporting system functions
such as push-button monitor, multiple ADC's for voltage and
temperature monitoring, fan controller and watchdog monitor.
This driver provides common support for accessing the device.
Additional drivers must be enabled in order to use the
functionality of the device.
Symbol: MFD_GATEWORKS_GSC [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:410
Prompt: Gateworks System Controller
Depends on: HAS_IOMEM [=y] && I2C [=y] && OF [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: MFD_CORE [=m] && REGMAP_I2C [=m] && REGMAP_IRQ [=n]
---
Signed-off-by: CKI@GitLab <cki-project@redhat.com>
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_HIBERNATION_SNAPSHOT_DEV:
Device used by the uswsusp tools.
Say N if no snapshotting from userspace is needed, this also
reduces the attack surface of the kernel.
If in doubt, say Y.
Symbol: HIBERNATION_SNAPSHOT_DEV [=y]
Type : bool
Defined at kernel/power/Kconfig:83
Prompt: Userspace snapshot device
Depends on: HIBERNATION [=y]
Location:
-> Power management and ACPI options
-> Hibernation (aka 'suspend to disk') (HIBERNATION [=y])
---
Signed-off-by: CKI@GitLab <cki-project@redhat.com>
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_TEST_HMM:
This is a pseudo device driver solely for testing HMM.
Say M here if you want to build the HMM test module.
Doing so will allow you to run tools/testing/selftest/vm/hmm-tests.
If unsure, say N.
Symbol: TEST_HMM [=n]
Type : tristate
Defined at lib/Kconfig.debug:2221
Prompt: Test HMM (Heterogeneous Memory Management)
Depends on: RUNTIME_TESTING_MENU [=y] && TRANSPARENT_HUGEPAGE [=y] && DEVICE_PRIVATE [=y]
Location:
-> Kernel hacking
-> Kernel Testing and Coverage
-> Runtime Testing (RUNTIME_TESTING_MENU [=y])
Selects: HMM_MIRROR [=n] && MMU_NOTIFIER [=y]
---
Signed-off-by: CKI@GitLab <cki-project@redhat.com>
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_GPIO_AGGREGATOR:
Say yes here to enable the GPIO Aggregator, which provides a way to
aggregate existing GPIO lines into a new virtual GPIO chip.
This can serve the following purposes:
- Assign permissions for a collection of GPIO lines to a user,
- Export a collection of GPIO lines to a virtual machine,
- Provide a generic driver for a GPIO-operated device in an
industrial control context, to be operated from userspace using
the GPIO chardev interface.
Symbol: GPIO_AGGREGATOR [=n]
Type : tristate
Defined at drivers/gpio/Kconfig:1548
Prompt: GPIO Aggregator
Depends on: GPIOLIB [=y]
Location:
-> Device Drivers
-> GPIO Support (GPIOLIB [=y])
---
CONFIG_GPIO_PCA953X_IRQ:
Say yes here to enable the pca953x to be used as an interrupt
controller. It requires the driver to be built in the kernel.
Symbol: GPIO_PCA953X_IRQ [=n]
Type : bool
Defined at drivers/gpio/Kconfig:957
Prompt: Interrupt controller support for PCA953x
Depends on: GPIOLIB [=y] && I2C [=y] && GPIO_PCA953X [=m]
Location:
-> Device Drivers
-> GPIO Support (GPIOLIB [=y])
-> I2C GPIO expanders
-> PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports (GPIO_PCA953X [=m])
Selects: GPIOLIB_IRQCHIP [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_DEBUG_INFO_COMPRESSED:
Compress the debug information using zlib. Requires GCC 5.0+ or Clang
5.0+, binutils 2.26+, and zlib.
Users of dpkg-deb via scripts/package/builddeb may find an increase in
size of their debug .deb packages with this config set, due to the
debug info being compressed with zlib, then the object files being
recompressed with a different compression scheme. But this is still
preferable to setting $KDEB_COMPRESS to "none" which would be even
larger.
Symbol: DEBUG_INFO_COMPRESSED [=n]
Type : bool
Defined at lib/Kconfig.debug:216
Prompt: Compressed debugging information
Depends on: DEBUG_INFO [=y]
Location:
-> Kernel hacking
-> Compile-time checks and compiler options
-> Compile the kernel with debug info (DEBUG_INFO [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_AD9467:
Say yes here to build support for Analog Devices:
* AD9467 16-Bit, 200 MSPS/250 MSPS Analog-to-Digital Converter
The driver requires the assistance of the AXI ADC IP core to operate,
since SPI is used for configuration only, while data has to be
streamed into memory via DMA.
To compile this driver as a module, choose M here: the module will be
called ad9467.
Symbol: AD9467 [=n]
Type : tristate
Defined at drivers/iio/adc/Kconfig:249
Prompt: Analog Devices AD9467 High Speed ADC driver
Depends on: IIO [=m] && SPI [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Analog to digital converters
Selects: ADI_AXI_ADC [=n]
---
CONFIG_ADIS16475:
Say yes here to build support for Analog Devices ADIS16470, ADIS16475,
ADIS16477, ADIS16465, ADIS16467, ADIS16500, ADIS16505, ADIS16507 inertial
sensors.
To compile this driver as a module, choose M here: the module will be
called adis16475.
Symbol: ADIS16475 [=n]
Type : tristate
Defined at drivers/iio/imu/Kconfig:32
Prompt: Analog Devices ADIS16475 and similar IMU driver
Depends on: IIO [=m] && SPI [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Inertial measurement units
Selects: IIO_ADIS_LIB [=n] && IIO_ADIS_LIB_BUFFER [=n]
---
CONFIG_ADI_AXI_ADC:
Say yes here to build support for Analog Devices Generic
AXI ADC IP core. The IP core is used for interfacing with
analog-to-digital (ADC) converters that require either a high-speed
serial interface (JESD204B/C) or a source synchronous parallel
interface (LVDS/CMOS).
Typically (for such devices) SPI will be used for configuration only,
while this IP core handles the streaming of data into memory via DMA.
Link: https://wiki.analog.com/resources/fpga/docs/axi_adc_ip
If unsure, say N (but it's safe to say "Y").
To compile this driver as a module, choose M here: the
module will be called adi-axi-adc.
Symbol: ADI_AXI_ADC [=n]
Type : tristate
Defined at drivers/iio/adc/Kconfig:264
Prompt: Analog Devices Generic AXI ADC IP core driver
Depends on: IIO [=m]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Analog to digital converters
Selects: IIO_BUFFER [=y] && IIO_BUFFER_HW_CONSUMER [=n] && IIO_BUFFER_DMAENGINE [=n]
Selected by [n]:
- AD9467 [=n] && IIO [=m] && SPI [=y]
---
CONFIG_ATLAS_EZO_SENSOR:
Say Y here to build I2C interface support for the following
Atlas Scientific EZO sensors
* CO2 EZO Sensor
To compile this driver as module, choose M here: the
module will be called atlas-ezo-sensor.
Symbol: ATLAS_EZO_SENSOR [=n]
Type : tristate
Defined at drivers/iio/chemical/Kconfig:25
Prompt: Atlas Scientific EZO sensors
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Chemical Sensors
---
CONFIG_MAX1241:
Say yes here to build support for Maxim max1241 12-bit, single-channel
ADC.
To compile this driver as a module, choose M here: the module will be
called max1241.
Symbol: MAX1241 [=n]
Type : tristate
Defined at drivers/iio/adc/Kconfig:633
Prompt: Maxim max1241 ADC driver
Depends on: IIO [=m] && SPI_MASTER [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Analog to digital converters
---
CONFIG_SX9310:
Say Y here to build a driver for Semtech's SX9310/SX9311 capacitive
proximity/button sensor.
To compile this driver as a module, choose M here: the
module will be called sx9310.
Symbol: SX9310 [=n]
Type : tristate
Defined at drivers/iio/proximity/Kconfig:104
Prompt: SX9310/SX9311 Semtech proximity sensor
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Proximity and distance sensors
Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] && REGMAP_I2C [=m]
---
CONFIG_VCNL3020:
Say Y here if you want to build a driver for the Vishay VCNL3020
proximity sensor.
To compile this driver as a module, choose M here: the
module will be called vcnl3020.
Symbol: VCNL3020 [=n]
Type : tristate
Defined at drivers/iio/proximity/Kconfig:143
Prompt: VCNL3020 proximity sensor
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Proximity and distance sensors
Selects: REGMAP_I2C [=m]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_PHY_CADENCE_SALVO:
Enable this to support the Cadence SALVO PHY driver,
this PHY is a legacy PHY, and only are used for USB3
and USB2.
Symbol: PHY_CADENCE_SALVO [=n]
Type : tristate
Defined at drivers/phy/cadence/Kconfig:31
Prompt: Cadence Salvo PHY Driver
Depends on: OF [=y] && HAS_IOMEM [=y]
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=n]
---
CONFIG_PHY_QCOM_IPQ4019_USB:
Support for the USB PHY-s on Qualcomm IPQ40xx SoC-s.
Symbol: PHY_QCOM_IPQ4019_USB [=n]
Type : tristate
Defined at drivers/phy/qualcomm/Kconfig:21
Prompt: Qualcomm IPQ4019 USB PHY driver
Depends on: OF [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=y]
---
CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2:
Enable support for the USB high-speed SNPS Femto phy on Qualcomm
chipsets. This PHY has differences in the register map compared
to the V1 variants. The PHY is paired with a Synopsys DWC3 USB
controller on Qualcomm SOCs.
Symbol: PHY_QCOM_USB_SNPS_FEMTO_V2 [=n]
Type : tristate
Defined at drivers/phy/qualcomm/Kconfig:95
Prompt: Qualcomm SNPS FEMTO USB HS PHY V2 module
Depends on: OF [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Either both sides need to be quoted or neither, otherwise the condition
won't work as intended.
Fixes: efa3fc15df ("Correctly name tarball for single tarball builds")
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
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_BATTERY_CW2015:
Say Y here to enable support for the cellwise cw2015
battery fuel gauge (used in the Pinebook Pro & others)
This driver can also be built as a module. If so, the module will be
called cw2015_battery.
Symbol: BATTERY_CW2015 [=n]
Type : tristate
Defined at drivers/power/supply/Kconfig:119
Prompt: CW2015 Battery driver
Depends on: POWER_SUPPLY [=y] && I2C [=y]
Location:
-> Device Drivers
-> Power supply class support (POWER_SUPPLY [=y])
Selects: REGMAP_I2C [=m]
---
CONFIG_CHARGER_BD99954:
Say Y here to enable support for getting battery and charger
information and altering charger configurations from the ROHM
BD99954 charger IC.
Symbol: CHARGER_BD99954 [=n]
Type : tristate
Defined at drivers/power/supply/Kconfig:724
Prompt: ROHM bd99954 charger driver
Depends on: POWER_SUPPLY [=y] && I2C [=y]
Location:
-> Device Drivers
-> Power supply class support (POWER_SUPPLY [=y])
Selects: LINEAR_RANGES [=n]
---
Signed-off-by: Justin M. Forbes <jforbes@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_KEYBOARD_BCM:
Say Y here if you want to use Broadcom keypad.
To compile this driver as a module, choose M here: the
module will be called bcm-keypad.
Symbol: KEYBOARD_BCM [=n]
Type : tristate
Defined at drivers/input/keyboard/Kconfig:774
Prompt: Broadcom keypad driver
Depends on: !UML && INPUT [=y] && INPUT_KEYBOARD [=y] && OF [=y] && HAVE_CLK [=y]
Location:
-> Device Drivers
-> Input device support
-> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-> Keyboards (INPUT_KEYBOARD [=y])
Selects: INPUT_MATRIXKMAP [=n]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_MMC_SDHCI_OF_DWCMSHC:
This selects Synopsys DesignWare Cores Mobile Storage Controller
support.
If you have a controller with this interface, say Y or M here.
If unsure, say N.
Symbol: MMC_SDHCI_OF_DWCMSHC [=n]
Type : tristate
Defined at drivers/mmc/host/Kconfig:205
Prompt: SDHCI OF support for the Synopsys DWC MSHC
Depends on: MMC [=m] && MMC_SDHCI_PLTFM [=m] && OF [=y] && COMMON_CLK [=y]
Location:
-> Device Drivers
-> MMC/SD/SDIO card support (MMC [=m])
-> Secure Digital Host Controller Interface support (MMC_SDHCI [=m])
-> SDHCI platform and OF driver helper (MMC_SDHCI_PLTFM [=m])
---
Cc: Gopal Tiwari <gtiwari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
When building during the merge window, we need to bump PATCHLEVEL in the
Makefile because Linus doesn't bump it until rc1. Something similar has
been in the Fedora spec forever. Using 5.8 as an example, without this
change we build a kernel rpm version
kernel-5.8.0-0.rc0.20200608gitaf7b4801030c.1.fc33 but with a uname of
kernel-5.7.0-0.rc0.20200608gitaf7b4801030c.1.fc33 which places the
modules in the rpm versioned directory where the kernel does not know to
look for them. With this change, both the rpm and the uname would be
the kernel-5.8 version.
While it might be cleaner to only run this replacement if we are in the
merge window, this is much simpler than making changes across 2
additional Makefiles, and the end result should always be the same.
Signed-off-by: Justin M. Forbes <jforbes@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_PRIME_NUMBERS:
This option provides a simple prime number generator for test
modules.
If unsure, say N.
Symbol: PRIME_NUMBERS [=n]
Type : tristate
Defined at lib/math/Kconfig:8
Prompt: Simple prime number generator for testing
Location:
-> Library routines
Selected by [n]:
- DRM_DEBUG_SELFTEST [=n] && HAS_IOMEM [=y] && DRM [=m] && DEBUG_KERNEL [=y]
- DRM_I915_SELFTEST [=n] && HAS_IOMEM [=y] && EXPERT [=n] && DRM_I915 [=m]
---
Signed-off-by: Fedora Kernel Team <kernel-team@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_MDIO_IPQ8064:
This driver supports the MDIO interface found in the network
interface units of the IPQ8064 SoC
Symbol: MDIO_IPQ8064 [=n]
Type : tristate
Defined at drivers/net/phy/Kconfig:160
Prompt: Qualcomm IPQ8064 MDIO interface support
Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y] && MDIO_BUS [=y] && HAS_IOMEM [=y] && OF_MDIO [=y] && MFD_SYSCON [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> MDIO bus device drivers (MDIO_DEVICE [=y])
---
CONFIG_MDIO_MVUSB:
A USB to MDIO converter present on development boards for
Marvell's Link Street family of Ethernet switches.
Symbol: MDIO_MVUSB [=n]
Type : tristate
Defined at drivers/net/phy/Kconfig:182
Prompt: Marvell USB to MDIO Adapter
Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y] && MDIO_BUS [=y] && USB [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> MDIO bus device drivers (MDIO_DEVICE [=y])
---
CONFIG_MDIO_XPCS:
This module provides helper functions for Synopsys DesignWare XPCS
controllers.
Symbol: MDIO_XPCS [=n]
Type : tristate
Defined at drivers/net/phy/Kconfig:224
Prompt: Synopsys DesignWare XPCS controller
Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y] && MDIO_BUS [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> MDIO bus device drivers (MDIO_DEVICE [=y])
Selected by [n]:
- STMMAC_ETH [=n] && NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_STMICRO [=n] && HAS_IOMEM [=y] && HAS_DMA [=y]
---
Cc: Petr Oros <poros@redhat.com>
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_BPF_LSM:
Enables instrumentation of the security hooks with eBPF programs for
implementing dynamic MAC and Audit Policies.
If you are unsure how to answer this question, answer N.
Symbol: BPF_LSM [=n]
Type : bool
Defined at init/Kconfig:1623
Prompt: LSM Instrumentation with BPF
Depends on: BPF_EVENTS [=y] && BPF_SYSCALL [=y] && SECURITY [=y] && BPF_JIT [=y]
Location:
-> General setup
---
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_SENSORS_AMD_ENERGY:
If you say yes here you get support for core and package energy
sensors, based on RAPL MSR for AMD family 17h and above CPUs.
This driver can also be built as a module. If so, the module
will be called as amd_energy.
Symbol: SENSORS_AMD_ENERGY [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:327
Prompt: AMD RAPL MSR based Energy driver
Depends on: HWMON [=y] && X86 [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
CONFIG_SENSORS_MAX16601:
If you say yes here you get hardware monitoring support for Maxim
MAX16601.
This driver can also be built as a module. If so, the module will
be called max16601.
Symbol: SENSORS_MAX16601 [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:149
Prompt: Maxim MAX16601
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: CKI@GitLab <cki-project@redhat.com>
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_DRM_CHRONTEL_CH7033:
Enable support for the Chrontel CH7033 VGA/DVI/HDMI Encoder, as
found in the Dell Wyse 3020 thin client.
If in doubt, say "N".
Symbol: DRM_CHRONTEL_CH7033 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:30
Prompt: Chrontel CH7033 Video Encoder
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_KMS_HELPER [=m]
---
CONFIG_DRM_NWL_MIPI_DSI:
This enables the Northwest Logic MIPI DSI Host controller as
for example found on NXP's i.MX8 Processors.
Symbol: DRM_NWL_MIPI_DSI [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:71
Prompt: Northwest Logic MIPI DSI Host controller
Depends on: DRM_BRIDGE [=y] && DRM [=m] && COMMON_CLK [=y] && OF [=y] && HAS_IOMEM [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_KMS_HELPER [=m] && DRM_MIPI_DSI [=n] && DRM_PANEL_BRIDGE [=y] && GENERIC_PHY_MIPI_DPHY [=n] && MFD_SYSCON [=y] && MULTIPLEXER [=n] && REGMAP_MMIO [=y]
---
Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Signed-off-by: CKI@GitLab <cki-project@redhat.com>
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_BRIDGE_MRP:
If you say Y here, then the Ethernet bridge will be able to run MRP
protocol to detect loops
Say N to exclude this support and reduce the binary size.
If unsure, say N.
Symbol: BRIDGE_MRP [=n]
Type : bool
Defined at net/bridge/Kconfig:65
Prompt: MRP protocol
Depends on: NET [=y] && BRIDGE [=m]
Location:
-> Networking support (NET [=y])
-> Networking options
-> 802.1d Ethernet Bridging (BRIDGE [=m])
---
Signed-off-by: Justin M. Forbes <jforbes@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_BLK_INLINE_ENCRYPTION:
Build the blk-crypto subsystem. Enabling this lets the
block layer handle encryption, so users can take
advantage of inline encryption hardware if present.
Symbol: BLK_INLINE_ENCRYPTION [=n]
Type : bool
Defined at block/Kconfig:189
Prompt: Enable inline encryption support in block layer
Depends on: BLOCK [=y]
Location:
-> Enable the block layer (BLOCK [=y])
---
Cc: Ming Lei <minlei@redhat.com>
Cc: Jeff Moyer <jmoyer@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: CKI@GitLab <cki-project@redhat.com>
From https://www.paul-moore.com/blog/d/2020/06/linux_v57.html
"Deprecate setting “/sys/fs/selinux/checkreqprot” to 1. This flag was
originally created to deal with legacy userspace and the READ_IMPLIES_EXEC
personality flag. We changed the default from 1 to 0 back in Linux v4.4 and
now we are taking the next step of deprecating it, at some point in the future
we will take the final step of rejecting 1."
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
Because of the way the trees are mangled, the hash for patches
change with each build. This creates an unnecessary line of diff in
each patch file which is makes a diff in dist-git difficult to read.
Let's zero it to clean it up.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
Include Makefile.rhelver by treating it as a source file rather than
generating it in a patch. This avoids depending on the tree being
prepared having a reference to the master branch, which should fix the
CKI build failures. It's also simpler.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
While we only add broken out patches if we aren't doing a single tarball
we still need to remove the template markers if we are.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
People like to go look at the dist-git instead of a source tree for
patch files and there were complaints about the big diff file. Jump
through some hoops to generate a list of patches from the release branch
so the patches are preserved in dist-git.
Denys Vlasenko <dvlasenk@redhat.com>
Rado Vrbovsky <rvrbovsk@redhat.com>
Clark Williams <williams@redhat.com>
Jan Stancek <jstancek@redhat.com>
Juri Lelli <jlelli@redhat.com>
"Herton R. Krzesinski" <herton@redhat.com>
Frantisek Hrbata <fhrbata@redhat.com>
Luis Claudio Goncalves <lgoncalv@redhat.com>
Jeremy Cline <jcline@redhat.com>
Justin Forbes <jforbes@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
The update_scripts.sh script doesn't correctly strip the suffix from the
end of the pathname, but will substitute for it anywhere in the path. The
pattern really ought to have been /[.]$TARGET$//.
Fix this by using a special shell expansion to do it instead of invoking a
sed pipeline.
Signed-off-by: David Howells <dhowells@redhat.com>
cc: Jeremy Cline <jcline@redhat.com>
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_PWM_DEBUG:
This option enables some additional checks to help lowlevel driver
authors to get their callbacks implemented correctly.
It is expected to introduce some runtime overhead and diagnostic
output to the kernel log, so only enable while working on a driver.
Symbol: PWM_DEBUG [=n]
Type : bool
Defined at drivers/pwm/Kconfig:36
Prompt: PWM lowlevel drivers additional checks and debug messages
Depends on: PWM [=y] && DEBUG_KERNEL [=y]
Location:
-> Device Drivers
-> Pulse-Width Modulation (PWM) Support (PWM [=y])
---
If we enable CONFIG_DRM_DP_CEC as is currently enabled in the RHEL
config, and should be enabled in the Fedora config, the build fails
because drm_kms_helper.ko in kernel-core requires symbols from cec.ko
which is filtered to kernel-modules. This brings the cec.ko module into
kernel-core to satisfy this dependency
This change also turns CONFIG_DRM_DP_CEC back on for Fedora.
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
This adds an overrides list to filter-modules.sh and a section to
process this list. It is to be used when a specific module which would
be filtered to kernel-modules needs to remain in kernel-core for depmod
reasons. A current example of this is cec.ko. The drm_kms_helper.ko
module needs symbols from it if we enable CONFIG_DRM_DP_CEC.
Signed-off-by: Justin M. Forbes <jforbes@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_MAGIC_SYSRQ_SERIAL_SEQUENCE:
Specifies a sequence of characters that can follow BREAK to enable
SysRq on a serial console.
If unsure, leave an empty string and the option will not be enabled.
Symbol: MAGIC_SYSRQ_SERIAL_SEQUENCE [=]
Type : string
Defined at lib/Kconfig.debug:434
Prompt: Char sequence that enables magic SysRq over serial
Depends on: MAGIC_SYSRQ_SERIAL [=y]
Location:
-> Kernel hacking
-> Generic Kernel Debugging Instruments
-> Magic SysRq key (MAGIC_SYSRQ [=y])
-> Enable magic SysRq key over serial (MAGIC_SYSRQ_SERIAL [=y])
---
CONFIG_PROVE_RAW_LOCK_NESTING:
Enable the raw_spinlock vs. spinlock nesting checks which ensure
that the lock nesting rules for PREEMPT_RT enabled kernels are
not violated.
NOTE: There are known nesting problems. So if you enable this
option expect lockdep splats until these problems have been fully
addressed which is work in progress. This config switch allows to
identify and analyze these problems. It will be removed and the
check permanentely enabled once the main issues have been fixed.
If unsure, select N.
Symbol: PROVE_RAW_LOCK_NESTING [=n]
Type : bool
Defined at lib/Kconfig.debug:1099
Prompt: Enable raw_spinlock - spinlock nesting checks
Depends on: PROVE_LOCKING [=y]
Location:
-> Kernel hacking
-> Lock Debugging (spinlocks, mutexes, etc...)
-> Lock debugging: prove locking correctness (PROVE_LOCKING [=y])
---
CONFIG_TEST_MIN_HEAP:
Enable this to turn on min heap function tests. This test is
executed only once during system boot (so affects only boot time),
or at module load time.
If unsure, say N.
Symbol: TEST_MIN_HEAP [=n]
Type : tristate
Defined at lib/Kconfig.debug:1799
Prompt: Min heap test
Depends on: RUNTIME_TESTING_MENU [=y] && (DEBUG_KERNEL [=y] || m && MODULES [=y])
Location:
-> Kernel hacking
-> Kernel Testing and Coverage
-> Runtime Testing (RUNTIME_TESTING_MENU [=y])
Enabled on debug kernels at the request of Prarit Bhargava
---
Cc: prarit@redhat.com
Cc: clark@redhat.com
Bugzilla: http://bugzilla.redhat.com/1722136
Upstream Status: RHEL only
CONFIG_SMC91X requires CONFIG_NET_VENDOR_SMSC and all other SMSC config
options to be disabled. Even though CONFIG_SMC911X is listed as 'm' it is
currently disabled in the final .config for aarch64. CONFIG_SMC911X's
config entry should also list the config as disabled.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
The sharedbuffer_configuration.py selftests script uses an ambiguous
Python version, explicitly mangle it to Python 3.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Have the script sign off the configuration patches it generates.
Although it seems somewhat meaningless to have a script agree to the
terms of the DCO, the authors of the script authoring the patches have
and this makes running a CI job to check all patches for Signed-off-by
tags simpler.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_TRACE_EVENT_INJECT:
Allow user-space to inject a specific trace event into the ring
buffer. This is mainly used for testing purpose.
If unsure, say N.
Symbol: TRACE_EVENT_INJECT [=n]
Type : bool
Prompt: Trace event injection
Location:
-> Kernel hacking
-> Tracers (FTRACE [=y])
Defined at kernel/trace/Kconfig:674
Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && TRACING [=y]
---
There are no static files at this time. I don't know the first thing
about CSS and rely on my elders and betters to make the documentation
look presentable. Configuring a static directory also generates a Sphinx
warning when it isn't present (which it isn't on clean checkouts because
it's empty) so just remove it.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
For years we've had a useful kernel kernel module, dummy-module, in the
tree.
Add dummy-module to the redhat directory.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
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_SND_BCM63XX_I2S_WHISTLER:
Say Y if you want to add support for ASoC audio on Broadcom
DSL/PON chips (bcm63158, bcm63178)
If you don't know what to do here, say N
Symbol: SND_BCM63XX_I2S_WHISTLER [=n]
Type : tristate
Defined at sound/soc/bcm/Kconfig:21
Prompt: SoC Audio support for the Broadcom BCM63XX I2S module
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
Selects: REGMAP_MMIO [=n]
---
CONFIG_SND_SOC_INTEL_SOF_PCM512x_MACH:
This adds support for ASoC machine driver for SOF platforms
with TI PCM512x I2S audio codec.
Say Y or m if you have such a device.
If unsure select "N".
Symbol: SND_SOC_INTEL_SOF_PCM512x_MACH [=n]
Type : tristate
Defined at sound/soc/intel/boards/Kconfig:464
Prompt: SOF with TI PCM512x codec
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_MACH [=y] && (SND_SOC_SOF_HDA_LINK [=y] || SND_SOC_SOF_BAYTRAIL [=n]) && I2C [=y] && ACPI [=y] && (SND_SOC_SOF_HDA_AUDIO_CODEC [=y] && (MFD_INTEL_LPSS [=y] || COMPILE_TEST [=n]) || SND_SOC_SOF_BAYTRAIL [=n] && (X86_INTEL_LPSS [=y] || COMPILE_TEST [=n])) && SND_HDA_CODEC_HDMI [=m]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> Intel Machine drivers (SND_SOC_INTEL_MACH [=y])
Selects: SND_SOC_PCM512x_I2C [=n]
Enabled as a module at the request of Jaroslav Kysela. Note, enabling
this as m enables CONFIG_SND_SOC_PCM512x_I2C, which has been been
included in this commit.
---
CONFIG_SND_SOC_SOF_DEBUG_PROBES:
This option enables the data probing feature that can be used to
gather data directly from specific points of the audio pipeline.
Say Y if you want to enable probes.
If unsure, select "N".
Symbol: SND_SOC_SOF_DEBUG_PROBES [=n]
Type : bool
Defined at sound/soc/sof/Kconfig:44
Prompt: SOF enable data probing
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_SOF_TOPLEVEL [=y]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> Sound Open Firmware Support (SND_SOC_SOF_TOPLEVEL [=y])
Selects: SND_SOC_COMPRESS [=y]
Enabled for debug configurations at the request of Jaroslav Kysela.
Note, this exposes the following option:
CONFIG_SND_SOC_SOF_HDA_PROBES
bool "SOF enable probes over HDA"
depends on SND_SOC_SOF_DEBUG_PROBES
help
This option enables the data probing for Intel(R).
Intel(R) Skylake and newer platforms.
Say Y if you want to enable probes.
If unsure, select "N".
---
CONFIG_SND_SOC_TLV320ADCX140:
Add support for Texas Instruments tlv320adc3140, tlv320adc5140 and
tlv320adc6140 quad channel ADCs.
Symbol: SND_SOC_TLV320ADCX140 [=n]
Type : tristate
Defined at sound/soc/codecs/Kconfig:1345
Prompt: Texas Instruments TLV320ADCX140 CODEC family
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && I2C [=y]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> CODEC drivers
Selects: REGMAP_I2C [=m]
Implied by [n]:
- SND_SOC_ALL_CODECS [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n]
---
Cc: Jaroslav Kysela <jkysela@redhat.com>
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_TEST_LOCKUP:
This builds the "test_lockup" module that helps to make sure
that watchdogs and lockup detectors are working properly.
Depending on module parameters it could emulate soft or hard
lockup, "hung task", or locking arbitrary lock for a long time.
Also it could generate series of lockups with cooling-down periods.
If unsure, say N.
Symbol: TEST_LOCKUP [=n]
Type : tristate
Defined at lib/Kconfig.debug:979
Prompt: Test module to generate lockups
Location:
-> Kernel hacking
-> Debug Oops, Lockups and Hangs
---
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_MMC_HSQ:
This selects the MMC Host Software Queue support. This may increase
performance, if the host controller and its driver supports it.
If you have a controller/driver supporting this interface, say Y or M
here.
If unsure, say N.
Symbol: MMC_HSQ [=n]
Type : tristate
Defined at drivers/mmc/host/Kconfig:953
Prompt: MMC Host Software Queue support
Depends on: MMC [=m]
Location:
-> Device Drivers
-> MMC/SD/SDIO card support (MMC [=m])
Selected by [n]:
- MMC_SDHCI_SPRD [=n] && MMC [=m] && ARCH_SPRD && MMC_SDHCI_PLTFM [=m]
---
Cc: Gopal Tiwari <gtiwari@redhat.com>
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_PHY_CADENCE_TORRENT:
Support for Cadence Torrent PHY.
Symbol: PHY_CADENCE_TORRENT [=n]
Type : tristate
Defined at drivers/phy/cadence/Kconfig:6
Prompt: Cadence Torrent PHY driver
Depends on: OF [=y] && HAS_IOMEM [=y]
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=n]
---
CONFIG_PHY_QCOM_USB_HS_28NM:
Enable this to support the Qualcomm Synopsys DesignWare Core 28nm
High-Speed PHY driver. This driver supports the Hi-Speed PHY which
is usually paired with either the ChipIdea or Synopsys DWC3 USB
IPs on MSM SOCs.
Symbol: PHY_QCOM_USB_HS_28NM [=n]
Type : tristate
Defined at drivers/phy/qualcomm/Kconfig:95
Prompt: Qualcomm 28nm High-Speed PHY
Depends on: (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && (EXTCON [=y] || !EXTCON [=y])
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=y]
---
CONFIG_PHY_QCOM_USB_SS:
Enable this to support the Super-Speed USB transceiver on various
Qualcomm chipsets.
Symbol: PHY_QCOM_USB_SS [=n]
Type : tristate
Defined at drivers/phy/qualcomm/Kconfig:106
Prompt: Qualcomm USB Super-Speed PHY driver
Depends on: (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && (EXTCON [=y] || !EXTCON [=y])
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=y]
---
This was fixed in Fedora back in January, and then got dropped in the
ARK switch over for some reason. Kernel-devel needs
Documentation/Kconfig.
rhbz 1789641
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
Moving them clobbers them in the dist-git repository. People using the
dist-git to rebuild the SRPM might "fedpkg prep" and then "fedpkg local"
(or similar) which fails because the files got moved.
Cc: jforbes@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Upstream status: RHEL only
Running 'make scripts' in /usr/src/kernels/$VERSION triggers the
following error:
scripts/selinux/genheaders/genheaders.c:19:10: fatal error:
classmap.h: No such file or directory
Let's fix that by including the necessary two files from the
directory security/selinux/include/ in the kernel-devel package.
Once those files are added, another error is triggered:
scripts/sortextable.c:31:10: fatal error: tools/be_byteshift.h:
No such file or directory
Let's correct that error by adding two more files from tools/include/
to the kernel-devel package as well. This will get 'make scripts'
working.
This change adds 20K (before compression) to the kernel-devel package.
Signed-off-by: Brian Masney <bmasney@redhat.com>
Upstream Status: RHEL only
The dist-full-help target shows the target dist-cross-<arch>-rpm,
however it's really dist-cross-<arch>-rpms. Let's go ahead and correct
the help text.
Signed-off-by: Brian Masney <bmasney@redhat.com>
When building on a python2 system the following warning is displayed:
Processing /data/working-repos/kernel-ark/redhat/configs/kernel-x86_64-fedora.config ... done
Processing /data/working-repos/kernel-ark/redhat/configs/kernel-x86_64-rhel.config ... done
Processed config files are in /data/working-repos/kernel-ark/redhat/configs
ERROR: your build environment is not compatible with RHEL8.
To fix this, run:
ln -s /usr/bin/python3 /usr/libexec/platform-python
Change the message to be distribution agnostic.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
The distribution specific Makefile target names begin with rh-. Switch
them to be use the distro agnostic dist-.
rh-dist-git-test and rh-dist-git are renamed to dist-git-test and
dist-git.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
v2: Update to include jcline's newly added docs
v3: Clean up rh-help and rh-full-help output. I made all text conform
to 80 chars.
This is an old driver and no longer used. It can be disabled.
Disable the Serial IR driver.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Jeff Bastian <jbastian@redhat.com>
When built with_tools on %{cpupowerarchs}, %files for kernel-tools is duplicated, fix it so we use the correct one for each case
Signed-off-by: Pablo Greco <pgreco@centosproject.org>
Although the GitLab wiki is pretty nice for getting started, it doesn't
offer a great way for folks to contribute or provide reviews for
changes. Convert the current Wiki to RST and build it with Sphinx. This
should be nearly identical to the content of the wiki with the exception
of a new section on contributing to the documentation.
When this is accepted, a new CI job can be added to automatically lint,
build, and host the Sphinx documentation on GitLab pages[0].
[0] https://docs.gitlab.com/ee/user/project/pages/
Signed-off-by: Jeremy Cline <jcline@redhat.com>
ARK used to build against the RHEL-8 buildroots. Going forward,
it will build against the ELN buildroot (Fedora space). Adjust
the spec file to handle these changes.
This change still builds under RHEL-8 as llvm-toolset was a meta
package for clang and llvm.
V2: Remove llvm-toolset
Signed-off-by: Don Zickus <dzickus@redhat.com>
ARK's master branch tracks Linus's master branch, so drop the check for
a remote named "linus" (which might be wrong anyway) and use the local
master branch to calculate the snapshot.
While this does assume that the local master branch is up-to-date,
that's better than trying to guess the correct remote name and can be
easily scripted.
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Jeremy Cline <jcline@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Developers have mentioned that 'internal' sounds like a branch to avoid
instead of the first branch to merge. A suggestion by Prarit was to
use os-build.
Straight forward re-name of internal to os-build. The bulk of the
changes are documentation and script updates.
Without this flag, the release script pulls in any merge request labeled
for inclusion in a release, not just the currently open merge requests.
Applying a patch that already got merged fails, which is why this
morning's release job didn't succeed.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
A new binary, gpio-watch, was introduced with v5.7. Package it in
-tools.
Clark Williams <williams@redhat.com>
Rado Vrbovsky <rvrbovsk@redhat.com>
Luis Claudio Goncalves <lgoncalv@redhat.com>
"Herton R. Krzesinski" <herton@redhat.com>
Frantisek Hrbata <fhrbata@redhat.com>
Jan Stancek <jstancek@redhat.com>
Jeremy Cline <jcline@redhat.com>
Denys Vlasenko <dvlasenk@redhat.com>
Juri Lelli <jlelli@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
The CI job can't determine if the release already exists or not with
the current script, so it fails when it tries to run the follow-up
scripts. This allows us to skip the rest of the job when the tag already
exists so maintainers only see failed jobs when something is actually
wrong.
If the script exits 1 or 2 it's for reasons that require maintainer
intervention. This exits 3 to distinguish between those cases and the
case that there hasn't been an update to upstream.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
The other CI scripts don't push branches so they can be easily run
locally. Pushing is left as an exercise to the runner and it's easy for
CI to continue to push changes.
This also moves the script in with the rest of the ARK CI scripts.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
The rh-rpms target is described in the help text as the target to use if
you want to "create the binary RPMS for the kernel". However, the
rpmbuild command provided two --target arguments, one for $(MACH) and a
second one for noarch. Apparently rpmbuild just uses whatever is last
because rh-rpms was just building the noarch packages.
While the author believes documentation is critical, it's more useful
when the user has what it documents as well.
Fixes: #26
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_BAREUDP:
This adds a bare UDP tunnel module for tunnelling different
kinds of traffic like MPLS, IP, etc. inside a UDP tunnel.
To compile this driver as a module, choose M here: the module
will be called bareudp.
Symbol: BAREUDP [=n]
Type : tristate
Defined at drivers/net/Kconfig:262
Prompt: Bare UDP Encapsulation
Depends on: NETDEVICES [=y] && NET_CORE [=y] && INET [=y] && (IPV6 [=y] || !IPV6 [=y])
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Network core driver support (NET_CORE [=y])
Selects: NET_UDP_TUNNEL [=m] && GRO_CELLS [=y]
Enabled at the request of Jiri Benc
---
Cc: Jiri Benc <jbenc@redhat.com>
Fedora users are used to the dist-git repository being a particular way.
Add some documentation so the change is less confusing.
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Jeremy Cline <jcline@redhat.com>
Cc: Justin Forbes <jforbes@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Like ark-update-configs.sh, only report bugs if the REPORT_BUGS
environment variable is present. This is only really useful in the CI
environment.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_EXFAT_FS:
This allows you to mount devices formatted with the exFAT file system.
exFAT is typically used on SD-Cards or USB sticks.
To compile this as a module, choose M here: the module will be called
exfat.
Symbol: EXFAT_FS [=n]
Type : tristate
Defined at fs/exfat/Kconfig:3
Prompt: exFAT filesystem support
Depends on: BLOCK [=y]
Location:
-> File systems
-> DOS/FAT/EXFAT/NT Filesystems
Selects: NLS [=y]
---
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_DMABUF_MOVE_NOTIFY:
Don''t pin buffers if the dynamic DMA-buf interface is available on both the
exporter as well as the importer. This fixes a security problem where
userspace is able to pin unrestricted amounts of memory through DMA-buf.
But marked experimental because we don''t jet have a consistent execution
context and memory management between drivers.
Symbol: DMABUF_MOVE_NOTIFY [=n]
Type : bool
Defined at drivers/dma-buf/Kconfig:42
Prompt: Move notify between drivers (EXPERIMENTAL)
Location:
-> Device Drivers
-> DMABUF options
Enabled at the request of Prarit Bhargava to avoid the security issue.
---
Cc: Prarit Bhargava <prarit@redhat.com>
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_PAGE_REPORTING:
Free page reporting allows for the incremental acquisition of
free pages from the buddy allocator for the purpose of reporting
those pages to another entity, such as a hypervisor, so that the
memory can be freed within the host for other uses.
Symbol: PAGE_REPORTING [=n]
Type : bool
Defined at mm/Kconfig:246
Prompt: Free page reporting
Location:
-> Memory Management options
Selected by [n]:
- VIRTIO_BALLOON [=n] && VIRTIO_MENU [=y] && VIRTIO [=n]
---
CONFIG_ZSWAP_COMPRESSOR_DEFAULT_842:
Use the 842 algorithm as the default compression algorithm.
Symbol: ZSWAP_COMPRESSOR_DEFAULT_842 [=n]
Type : bool
Defined at mm/Kconfig:586
Prompt: 842
Depends on: <choice>
Location:
-> Memory Management options
-> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
-> Compressed cache for swap pages default compressor (<choice> [=y])
Selects: CRYPTO_842 [=n]
---
CONFIG_ZSWAP_COMPRESSOR_DEFAULT_DEFLATE:
Use the Deflate algorithm as the default compression algorithm.
Symbol: ZSWAP_COMPRESSOR_DEFAULT_DEFLATE [=n]
Type : bool
Defined at mm/Kconfig:574
Prompt: Deflate
Depends on: <choice>
Location:
-> Memory Management options
-> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
-> Compressed cache for swap pages default compressor (<choice> [=y])
Selects: CRYPTO_DEFLATE [=y]
---
CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4:
Use the LZ4 algorithm as the default compression algorithm.
Symbol: ZSWAP_COMPRESSOR_DEFAULT_LZ4 [=n]
Type : bool
Defined at mm/Kconfig:592
Prompt: LZ4
Depends on: <choice>
Location:
-> Memory Management options
-> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
-> Compressed cache for swap pages default compressor (<choice> [=y])
Selects: CRYPTO_LZ4 [=n]
---
CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4HC:
Use the LZ4HC algorithm as the default compression algorithm.
Symbol: ZSWAP_COMPRESSOR_DEFAULT_LZ4HC [=n]
Type : bool
Defined at mm/Kconfig:598
Prompt: LZ4HC
Depends on: <choice>
Location:
-> Memory Management options
-> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
-> Compressed cache for swap pages default compressor (<choice> [=y])
Selects: CRYPTO_LZ4HC [=n]
---
CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZO:
Use the LZO algorithm as the default compression algorithm.
Symbol: ZSWAP_COMPRESSOR_DEFAULT_LZO [=y]
Type : bool
Defined at mm/Kconfig:580
Prompt: LZO
Depends on: <choice>
Location:
-> Memory Management options
-> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
-> Compressed cache for swap pages default compressor (<choice> [=y])
Selects: CRYPTO_LZO [=y]
---
CONFIG_ZSWAP_COMPRESSOR_DEFAULT_ZSTD:
Use the zstd algorithm as the default compression algorithm.
Symbol: ZSWAP_COMPRESSOR_DEFAULT_ZSTD [=n]
Type : bool
Defined at mm/Kconfig:604
Prompt: zstd
Depends on: <choice>
Location:
-> Memory Management options
-> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
-> Compressed cache for swap pages default compressor (<choice> [=y])
Selects: CRYPTO_ZSTD [=n]
---
CONFIG_ZSWAP_DEFAULT_ON:
If selected, the compressed cache for swap pages will be enabled
at boot, otherwise it will be disabled.
The selection made here can be overridden by using the kernel
command line 'zswap.enabled=' option.
Symbol: ZSWAP_DEFAULT_ON [=n]
Type : bool
Defined at mm/Kconfig:663
Prompt: Enable the compressed cache for swap pages by default
Depends on: ZSWAP [=y]
Location:
-> Memory Management options
-> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
---
CONFIG_ZSWAP_ZPOOL_DEFAULT_Z3FOLD:
Use the z3fold allocator as the default allocator.
Symbol: ZSWAP_ZPOOL_DEFAULT_Z3FOLD [=n]
Type : bool
Defined at mm/Kconfig:642
Prompt: z3fold
Depends on: <choice>
Location:
-> Memory Management options
-> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
-> Compressed cache for swap pages default allocator (<choice> [=y])
Selects: Z3FOLD [=n]
---
CONFIG_ZSWAP_ZPOOL_DEFAULT_ZBUD:
Use the zbud allocator as the default allocator.
Symbol: ZSWAP_ZPOOL_DEFAULT_ZBUD [=y]
Type : bool
Defined at mm/Kconfig:636
Prompt: zbud
Depends on: <choice>
Location:
-> Memory Management options
-> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
-> Compressed cache for swap pages default allocator (<choice> [=y])
Selects: ZBUD [=y]
---
CONFIG_ZSWAP_ZPOOL_DEFAULT_ZSMALLOC:
Use the zsmalloc allocator as the default allocator.
Symbol: ZSWAP_ZPOOL_DEFAULT_ZSMALLOC [=n]
Type : bool
Defined at mm/Kconfig:648
Prompt: zsmalloc
Depends on: <choice>
Location:
-> Memory Management options
-> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
-> Compressed cache for swap pages default allocator (<choice> [=y])
Selects: ZSMALLOC [=y]
---
Cc: Larry Woodman <lwoodman@redhat.com>
The dist is defined in the build root. Including it in source tags is
confusing since a source rpm might be built in multiple build roots
(e.g. Fedora Rawhide, stable releases, and ELN).
The tag format for releases is now
kernel-<upstream_version>-<release>.<buildid>. For example, instead of
kernel-5.6.0-1.elrdy, the tag is now kernel-5.6.0-1.
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Fedora placed the buildid tag before the dist tag. Match that behavior
here and pipe the buildid into the specfile for users who want to
continue rebuilding from the dist-git repository.
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Jeremy Cline <jcline@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
This script merges the latest changes from mainline, creates the default
configs, and creates branches for all the changes. This is intended to
be run on a schedule and can optionally file issues against GitLab to
alert maintainers when manual intervention is required.
Branches are not pushed anywhere so developers can use this script
locally and the CI job can manage when branches are pushed.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Upstream commit a0f60f8431 ("s390/protvirt: Add sysfs firmware
interface for Ultravisor information") introduces a number of functions
if either CONFIG_KVM or CONFIG_PROTECTED_VIRTUALIZATION_GUEST are
enabled and make reference to uv_info, which is only defined if
CONFIG_KVM is enabled. Since CONFIG_KVM is disabled for the zfcpdump
kernel, disable CONFIG_PROTECTED_VIRTUALIZATION_GUEST.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_QETH_OSN:
This enables the qeth driver to support devices in OSN mode.
This feature will be removed in 2021.
If unsure, choose N.
Symbol: QETH_OSN [=y]
Type : bool
Defined at drivers/s390/net/Kconfig:94
Prompt: qeth OSN device support
Depends on: NETDEVICES [=y] && S390 [=y] && QETH [=m]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> S/390 network device drivers
-> Gigabit Ethernet device support (QETH [=m])
---
CONFIG_QETH_OSX:
This enables the qeth driver to support devices in OSX mode.
If unsure, choose N.
Symbol: QETH_OSX [=y]
Type : bool
Defined at drivers/s390/net/Kconfig:103
Prompt: qeth OSX device support
Depends on: NETDEVICES [=y] && S390 [=y] && QETH [=m]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> S/390 network device drivers
-> Gigabit Ethernet device support (QETH [=m])
---
Cc: Cornelia Huck <cohuck@redhat.com>
Provide a mapping to the RHEL kernel maintainers in various
subsystem trees. Useful for generating the right cc's on
patches to ARK/Fedora.
The main motivation is to find the right cc's for reviewing
config changes needed for ARK.
A .get_maintainers.conf file is added as an example usecase
but is currently disabled. I expect kernel development on this
tree will still send patches upstream and not to RHEL
developers. But when this tree forks for RHEL, the file
will get uncommented.
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_HID_GLORIOUS:
Support for Glorious PC Gaming Race mice such as
the Glorious Model O, O- and D.
Symbol: HID_GLORIOUS [=n]
Type : tristate
Defined at drivers/hid/Kconfig:365
Prompt: Glorious PC Gaming Race mice
Depends on: INPUT [=y] && HID [=y]
Location:
-> Device Drivers
-> HID support
-> HID bus support (HID [=y])
-> Special HID drivers
---
CONFIG_HID_MCP2221:
Provides I2C and SMBUS host adapter functionality over USB-HID
through MCP2221 device.
To compile this driver as a module, choose M here: the module
will be called hid-mcp2221.ko.
Symbol: HID_MCP2221 [=n]
Type : tristate
Defined at drivers/hid/Kconfig:1155
Prompt: Microchip MCP2221 HID USB-to-I2C/SMbus host support
Depends on: INPUT [=y] && HID [=y] && USB_HID [=y] && I2C [=y]
Location:
-> Device Drivers
-> HID support
-> HID bus support (HID [=y])
-> Special HID drivers
---
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
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_EDAC_DMC520:
Support for error detection and correction on the
SoCs with ARM DMC-520 DRAM controller.
Symbol: EDAC_DMC520 [=n]
Type : tristate
Defined at drivers/edac/Kconfig:526
Prompt: ARM DMC-520 ECC
Depends on: EDAC [=y] && ARM64 [=y]
Location:
-> Device Drivers
-> EDAC (Error Detection And Correction) reporting (EDAC [=y])
Enabled as a module at the request of Aristeu Rozanski
---
Cc: Aristeu Rozanski <aris@redhat.com>
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_GPIO_MLXBF2:
Say Y here if you want GPIO support on Mellanox BlueField 2 SoC.
Symbol: GPIO_MLXBF2 [=n]
Type : tristate
Defined at drivers/gpio/Kconfig:1402
Prompt: Mellanox BlueField 2 SoC GPIO
Depends on: GPIOLIB [=y] && PCI [=y] && (MELLANOX_PLATFORM [=y] && ARM64 [=y] && ACPI [=y] || 64BIT [=y] && COMPILE_TEST [=n])
Location:
-> Device Drivers
-> GPIO Support (GPIOLIB [=y])
-> PCI GPIO expanders
Selects: GPIO_GENERIC [=m]
Enabled at the request of Alaa Hleihel
---
Cc: Alaa Hleihel <ahleihel@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
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_DRM_DISPLAY_CONNECTOR:
Driver for display connectors with support for DDC and hot-plug
detection. Most display controller handle display connectors
internally and don't need this driver, but the DRM subsystem is
moving towards separating connector handling from display controllers
on ARM-based platforms. Saying Y here when this driver is not needed
will not cause any issue.
Symbol: DRM_DISPLAY_CONNECTOR [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:30
Prompt: Display connector support
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
---
CONFIG_DRM_PARADE_PS8640:
Choose this option if you have PS8640 for display
The PS8640 is a high-performance and low-power
MIPI DSI to eDP converter
Symbol: DRM_PARADE_PS8640 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:78
Prompt: Parade PS8640 MIPI DSI to eDP Converter
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_KMS_HELPER [=m] && DRM_MIPI_DSI [=n] && DRM_PANEL [=y]
---
CONFIG_DRM_SIMPLE_BRIDGE:
Support for non-programmable DRM bridges, such as ADI ADV7123, TI
THS8134 and THS8135 or passive resistor ladder DACs.
Symbol: DRM_SIMPLE_BRIDGE [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:116
Prompt: Simple DRM bridge support
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_KMS_HELPER [=m]
---
CONFIG_DRM_TIDSS:
The TI Keystone family SoCs introduced a new generation of
Display SubSystem. There is currently three Keystone family
SoCs released with DSS. Each with somewhat different version
of it. The SoCs are 66AK2Gx, AM65x, and J721E. Set this to Y
or M to add display support for TI Keystone family
platforms.
Symbol: DRM_TIDSS [=n]
Type : tristate
Defined at drivers/gpu/drm/tidss/Kconfig:1
Prompt: DRM Support for TI Keystone
Depends on: HAS_IOMEM [=y] && DRM [=m] && OF [=y] && (ARM || ARM64 [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Graphics support
Selects: DRM_KMS_HELPER [=m] && DRM_KMS_CMA_HELPER [=n] && DRM_GEM_CMA_HELPER [=n]
---
CONFIG_DRM_TI_TPD12S015:
Texas Instruments TPD12S015 HDMI level shifter and ESD protection
driver.
Symbol: DRM_TI_TPD12S015 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:175
Prompt: TI TPD12S015 HDMI level shifter and ESD protection
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_KMS_HELPER [=m]
---
CONFIG_DRM_TOSHIBA_TC358768:
Toshiba TC358768AXBG/TC358778XBG DSI bridge chip driver.
Symbol: DRM_TOSHIBA_TC358768 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:148
Prompt: Toshiba TC358768 MIPI DSI bridge
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_KMS_HELPER [=m] && REGMAP_I2C [=m] && DRM_PANEL [=y] && DRM_MIPI_DSI [=n]
---
CONFIG_TINYDRM_ILI9486:
DRM driver for the following Ilitek ILI9486 panels:
* PISCREEN 3.5" 320x480 TFT (Ozzmaker 3.5")
* RPILCD 3.5" 320x480 TFT (Waveshare 3.5")
If M is selected the module will be called ili9486.
Symbol: TINYDRM_ILI9486 [=n]
Type : tristate
Defined at drivers/gpu/drm/tiny/Kconfig:50
Prompt: DRM support for ILI9486 display panels
Depends on: HAS_IOMEM [=y] && DRM [=m] && SPI [=y]
Location:
-> Device Drivers
-> Graphics support
Selects: DRM_KMS_HELPER [=m] && DRM_KMS_CMA_HELPER [=n] && DRM_MIPI_DBI [=n] && BACKLIGHT_CLASS_DEVICE [=y]
---
Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Rob Clark <rclark@redhat.com>
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_SENSORS_AXI_FAN_CONTROL:
If you say yes here you get support for the Analog Devices
AXI HDL FAN monitoring core.
This driver can also be built as a module. If so, the module
will be called axi-fan-control
Symbol: SENSORS_AXI_FAN_CONTROL [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:283
Prompt: Analog Devices FAN Control HDL Core driver
Depends on: HWMON [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
Cc: Dean Nelson <dnelson@redhat.com>
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_AD5770R:
Say yes here to build support for Analog Devices AD5770R Digital to
Analog Converter.
To compile this driver as a module, choose M here: the
module will be called ad5770r.
Symbol: AD5770R [=n]
Type : tristate
Defined at drivers/iio/dac/Kconfig:191
Prompt: Analog Devices AD5770R IDAC driver
Depends on: IIO [=m] && SPI_MASTER [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Digital to analog converters
---
CONFIG_AL3010:
Say Y here if you want to build a driver for the Dyna Image AL3010
ambient light sensor.
To compile this driver as a module, choose M here: the
module will be called al3010.
Symbol: AL3010 [=n]
Type : tristate
Defined at drivers/iio/light/Kconfig:46
Prompt: AL3010 ambient light sensor
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Light sensors
---
CONFIG_GP2AP002:
Say Y here if you have a Sharp GP2AP002 proximity/ALS combo-chip
hooked to an I2C bus.
To compile this driver as a module, choose M here: the
module will be called gp2ap002.
Symbol: GP2AP002 [=n]
Type : tristate
Defined at drivers/iio/light/Kconfig:172
Prompt: Sharp GP2AP002 Proximity/ALS sensor
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Light sensors
Selects: REGMAP [=y]
---
CONFIG_HMC425:
Say yes here to build support for Analog Devices HMC425A and similar
gain amplifiers or step attenuators.
To compile this driver as a module, choose M here: the
module will be called hmc425a.
Symbol: HMC425 [=n]
Type : tristate
Defined at drivers/iio/amplifiers/Kconfig:25
Prompt: Analog Devices HMC425A and similar GPIO Gain Amplifiers
Depends on: IIO [=m] && GPIOLIB [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Amplifiers
---
CONFIG_ICP10100:
Say yes here to build support for InvenSense ICP-101xx barometric
pressure and temperature sensor.
To compile this driver as a module, choose M here: the module
will be called icp10100.
Symbol: ICP10100 [=n]
Type : tristate
Defined at drivers/iio/pressure/Kconfig:104
Prompt: InvenSense ICP-101xx pressure and temperature sensor
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Pressure sensors
Selects: CRC8 [=m]
---
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_PCIE_EDR:
This option adds Error Disconnect Recover support as specified
in the Downstream Port Containment Related Enhancements ECN to
the PCI Firmware Specification r3.2. Enable this if you want to
support hybrid DPC model which uses both firmware and OS to
implement DPC.
Symbol: PCIE_EDR [=n]
Type : bool
Defined at drivers/pci/pcie/Kconfig:145
Prompt: PCI Express Error Disconnect Recover support
Depends on: PCI [=y] && PCIE_DPC [=y] && ACPI [=y]
Location:
-> Device Drivers
-> PCI support (PCI [=y])
Enabled at the request of Myron Stowe.
---
CONFIG_PCIE_LAYERSCAPE_GEN4:
Say Y here if you want PCIe Gen4 controller support on
Layerscape SoCs.
Symbol: PCIE_LAYERSCAPE_GEN4 [=n]
Type : bool
Defined at drivers/pci/controller/mobiveil/Kconfig:25
Prompt: Freescale Layerscape PCIe Gen4 controller
Depends on: PCI [=y] && OF [=y] && (ARM64 [=y] || ARCH_LAYERSCAPE [=n]) && PCI_MSI_IRQ_DOMAIN [=y]
Location:
-> Device Drivers
-> PCI support (PCI [=y])
-> PCI controller drivers
-> Mobiveil PCIe Core Support
Selects: PCIE_MOBIVEIL_HOST [=n]
---
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
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_PINCTRL_IPQ6018:
This is the pinctrl, pinmux, pinconf and gpiolib driver for
the Qualcomm Technologies Inc. TLMM block found on the
Qualcomm Technologies Inc. IPQ6018 platform. Select this for
IPQ6018.
Symbol: PINCTRL_IPQ6018 [=n]
Type : tristate
Defined at drivers/pinctrl/qcom/Kconfig:53
Prompt: Qualcomm Technologies, Inc. IPQ6018 pin controller driver
Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINCTRL_MSM [=y]
---
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_SURFACE_3_POWER_OPREGION:
This driver provides support for ACPI operation
region of the Surface 3 battery platform driver.
Symbol: SURFACE_3_POWER_OPREGION [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:858
Prompt: Surface 3 battery platform operation region support
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y] && I2C [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
---
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_PTP_1588_CLOCK_IDT82P33:
This driver adds support for using the IDT 82P33xxx as a PTP
clock. This clock is only useful if your time stamping MAC
is connected to the IDT chip.
To compile this driver as a module, choose M here: the module
will be called ptp_idt82p33.
Symbol: PTP_1588_CLOCK_IDT82P33 [=n]
Type : tristate
Defined at drivers/ptp/Kconfig:118
Prompt: IDT 82P33xxx PTP clock
Depends on: PTP_1588_CLOCK [=y] && I2C [=y]
Location:
-> Device Drivers
-> PTP clock support
---
CONFIG_PTP_1588_CLOCK_VMW:
This driver adds support for using VMware virtual precision
clock device as a PTP clock. This is only useful in virtual
machines running on VMware virtual infrastructure.
To compile this driver as a module, choose M here: the module
will be called ptp_vmw.
Symbol: PTP_1588_CLOCK_VMW [=n]
Type : tristate
Defined at drivers/ptp/Kconfig:142
Prompt: VMware virtual PTP clock
Depends on: ACPI [=y] && HYPERVISOR_GUEST [=y] && X86 [=y] && PTP_1588_CLOCK [=y]
Location:
-> Device Drivers
-> PTP clock support
---
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
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_SPI_MUX:
This adds support for SPI multiplexers. Each SPI mux will be
accessible as a SPI controller, the devices behind the mux will appear
to be chip selects on this controller. It is still necessary to
select one or more specific mux-controller drivers.
Symbol: SPI_MUX [=n]
Type : tristate
Defined at drivers/spi/Kconfig:919
Prompt: SPI multiplexer support
Depends on: SPI [=y] && SPI_MASTER [=y]
Location:
-> Device Drivers
-> SPI support (SPI [=y])
Selects: MULTIPLEXER [=n]
---
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_SERIAL_SPRD:
This enables the driver for the Spreadtrum's serial.
Symbol: SERIAL_SPRD [=n]
Type : tristate
Defined at drivers/tty/serial/Kconfig:1443
Prompt: Support for Spreadtrum serial
Depends on: TTY [=y] && HAS_IOMEM [=y] && COMMON_CLK [=y]
Location:
-> Device Drivers
-> Character devices
-> Enable TTY (TTY [=y])
-> Serial drivers
Selects: SERIAL_CORE [=y]
---
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_APPLE_MFI_FASTCHARGE:
Say Y here if you want to control whether iOS devices will
fast charge from the USB interface, as implemented in "MFi"
chargers.
It is safe to say M here.
Symbol: APPLE_MFI_FASTCHARGE [=n]
Type : tristate
Defined at drivers/usb/misc/Kconfig:140
Prompt: Fast charge control for iOS devices
Depends on: USB_SUPPORT [=y] && USB [=y]
Location:
-> Device Drivers
-> USB support (USB_SUPPORT [=y])
Selects: POWER_SUPPLY [=y]
---
Cc: Torez Smith <torez@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
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_IPV6_RPL_LWTUNNEL:
Support for RFC6554 RPL Source Routing Header using the lightweight
tunnels mechanism.
If unsure, say N.
Symbol: IPV6_RPL_LWTUNNEL [=n]
Type : bool
Defined at net/ipv6/Kconfig:306
Prompt: IPv6: RPL Source Routing Header support
Depends on: NET [=y] && INET [=y] && IPV6 [=y]
Location:
-> Networking support (NET [=y])
-> Networking options
-> TCP/IP networking (INET [=y])
-> The IPv6 protocol (IPV6 [=y])
Selects: LWTUNNEL [=y]
---
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
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_MHI_BUS:
Bus driver for MHI protocol. Modem Host Interface (MHI) is a
communication protocol used by the host processors to control
and communicate with modem devices over a high speed peripheral
bus or shared memory.
Symbol: MHI_BUS [=n]
Type : tristate
Defined at drivers/bus/mhi/Kconfig:8
Prompt: Modem Host Interface (MHI) bus
Location:
-> Device Drivers
-> Bus devices
---
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_ARM64_AMU_EXTN:
The activity monitors extension is an optional extension introduced
by the ARMv8.4 CPU architecture. This enables support for version 1
of the activity monitors architecture, AMUv1.
To enable the use of this extension on CPUs that implement it, say Y.
Note that for architectural reasons, firmware _must_ implement AMU
support when running on CPUs that present the activity monitors
extension. The required support is present in:
* Version 1.5 and later of the ARM Trusted Firmware
For kernels that have this configuration enabled but boot with broken
firmware, you may need to say N here until the firmware is fixed.
Otherwise you may experience firmware panics or lockups when
accessing the counter registers. Even if you are not observing these
symptoms, the values returned by the register reads might not
correctly reflect reality. Most commonly, the value read will be 0,
indicating that the counter is not enabled.
Symbol: ARM64_AMU_EXTN [=y]
Type : bool
Defined at arch/arm64/Kconfig:1557
Prompt: Enable support for the Activity Monitors Unit CPU extension
Location:
-> Kernel Features
-> ARMv8.4 architectural features
---
Cc: Mark Salter <msalter@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
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_SND_SOC_INTEL_BDW_RT5650_MACH:
This adds the ASoC machine driver for Intel Broadwell platforms with
the RT5650 codec.
Say Y if you have such a device.
If unsure select "N".
Symbol: SND_SOC_INTEL_BDW_RT5650_MACH [=n]
Type : tristate
Prompt: Broadwell with RT5650 codec
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> Intel Machine drivers (SND_SOC_INTEL_MACH [=y])
Defined at sound/soc/intel/boards/Kconfig:47
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_MACH [=y] && (SND_SOC_INTEL_HASWELL [=m] || SND_SOC_SOF_BROADWELL [=n]) && I2C [=y] && (I2C_DESIGNWARE_PLATFORM [=m] || COMPILE_TEST [=n]) && (X86_INTEL_LPSS [=y] || COMPILE_TEST [=n])
Selects: SND_SOC_RT5645 [=m]
This has been set to "m" at the request of Jaroslav Kysela.
---
CONFIG_SND_SOC_INTEL_USER_FRIENDLY_LONG_NAMES:
Some drivers report the I/O configuration to userspace through the
soundcard's long card name in the control user space AP. An unfortunate
side effect is that this long name may also be used by the GUI,
confusing users with information they don't need.
This option prevents the long name from being modified, and the I/O
configuration will be provided through a different component interface.
Select Y if userspace like UCM (Use Case Manager) uses the component
interface.
If unsure select N.
Symbol: SND_SOC_INTEL_USER_FRIENDLY_LONG_NAMES [=n]
Type : bool
Prompt: Use more user friendly long card names
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> Intel Machine drivers (SND_SOC_INTEL_MACH [=y])
Defined at sound/soc/intel/boards/Kconfig:16
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_MACH [=y]
This has been set to "y" at the request of Jaroslav Kysela.
---
CONFIG_SND_SOC_MT6660:
MediaTek MT6660 is a smart power amplifier which contain
speaker protection, multi-band DRC, equalizer functions.
Select N if you don't have MT6660 on board.
Select M to build this as module.
Symbol: SND_SOC_MT6660 [=n]
Type : tristate
Prompt: Mediatek MT6660 Speaker Amplifier
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> CODEC drivers
Defined at sound/soc/codecs/Kconfig:1583
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && I2C [=y]
Selected by [n]:
- SND_SOC_ALL_CODECS [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n] && I2C [=y]
---
Cc: Jaroslav Kysela <jkysela@redhat.com>
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_SND_CTL_VALIDATION:
Say Y to enable the additional validation of each control element
access, including sanity-checks like whether the values returned
from the driver are in the proper ranges or the check of the invalid
access at out-of-array areas.
Symbol: SND_CTL_VALIDATION [=n]
Type : bool
Prompt: Perform sanity-checks for each control element access
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> Debug (SND_DEBUG [=y])
Defined at sound/core/Kconfig:181
Depends on: SOUND [=m] && !UML && SND [=m] && SND_DEBUG [=y]
---
This setting has been enabled on debug kernels at the request of
Jaroslav Kysela.
Cc: Jaroslav Kysela <jkysela@redhat.com>
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_AMDTEE:
This implements AMD's Trusted Execution Environment (TEE) driver.
Symbol: AMDTEE [=m]
Type : tristate
Prompt: AMD-TEE
Location:
-> Device Drivers
-> Trusted Execution Environment support (TEE [=m])
-> TEE drivers
Defined at drivers/tee/amdtee/Kconfig:3
Depends on: TEE [=m] && CRYPTO_DEV_SP_PSP [=y]
This has been disabled at the request of Prarit Bhargava:
"Keep this off for now until we get some confidence that
AMDTEE doesn't lead to any corruption."
---
Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: darcari@redhat.com
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_HISI_DMA:
Support HiSilicon Kunpeng DMA engine.
Symbol: HISI_DMA [=n]
Type : tristate
Prompt: HiSilicon DMA Engine support
Location:
-> Device Drivers
-> DMA Engine support (DMADEVICES [=y])
Defined at drivers/dma/Kconfig:242
Depends on: DMADEVICES [=y] && (ARM64 [=y] || COMPILE_TEST [=n] && PCI_MSI [=y])
Selects: DMA_ENGINE [=y] && DMA_VIRTUAL_CHANNELS [=n]
---
CONFIG_INTEL_IDXD:
Enable support for the Intel(R) data accelerators present
in Intel Xeon CPU.
Say Y if you have such a platform.
If unsure, say N.
Symbol: INTEL_IDXD [=n]
Type : tristate
Prompt: Intel Data Accelerators support
Location:
-> Device Drivers
-> DMA Engine support (DMADEVICES [=y])
Defined at drivers/dma/Kconfig:284
Depends on: DMADEVICES [=y] && PCI [=y] && X86_64 [=y]
Selects: DMA_ENGINE [=y] && SBITMAP [=y]
Enabled at the request of Prarit Bhargava <prarit@redhat.com>
---
CONFIG_PLX_DMA:
Some PLX ExpressLane PCI Switches support additional DMA engines.
These are exposed via extra functions on the switch's
upstream port. Each function exposes one DMA channel.
Symbol: PLX_DMA [=n]
Type : tristate
Prompt: PLX ExpressLane PEX Switch DMA Engine Support
Location:
-> Device Drivers
-> DMA Engine support (DMADEVICES [=y])
Defined at drivers/dma/Kconfig:521
Depends on: DMADEVICES [=y] && PCI [=y]
Selects: DMA_ENGINE [=y]
---
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Don Dutile <ddutile@redhat.com>
Add a CI job to assert every commit in a merge request contains a
signed-off-by tag from the commit author. This is intended to be used
with GitLab's CI. An example job definition would be something like
signed_off_by:
before_script:
- pip install --user python-gitlab
script: ./redhat/scripts/ci/sign_off_check.py
only:
refs:
- merge_requests
Cc: Marcelo Ricardo Leitner <mleitner@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Once upon a time redhat/configs/build_configs.sh was modified to handle another
kernel version release parameter. But redhat/Makefile::rh-configs-arch was
not updated to reflect that.
Later after that change a different approach was taken. build_configs.sh
does not utilize the KVERREL param no more. I beleive generate_all_configs.sh
was modified to handle that use case. This makes the KVERREL param useless
now.
Just remove the param and let 'make rh-configs-arch' work again.
Closes#23
Signed-off-by: Don Zickus <dzickus@redhat.com>
RH_FEDORA got introduced to differentiate between Fedora and RHEL. Now
the that the PCI patches finally got merged, we can exchange it for the
RHEL_DIFFERENCES setting that came along with them.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
This script rebases the ark-patches against the latest master branch. If
patches cannot be rebased, issues are filed in the GitLab issue tracker.
This script is really only intended to be run in CI on a regular
schedule (nightly, most likely). A sample .gitlab-ci.yml would be:
ark_patches_rebase:
script:
- dnf -y install python3-gitlab
- git config user.name "CKI@GitLab"
- git config user.email "cki-project@redhat.com"
- redhat/scripts/ci/ark-rebase-patches.sh "master" $CI_PROJECT_ID
- git push -f origin ark-patches
Signed-off-by: Jeremy Cline <jcline@redhat.com>
CONFIG_STRICT_DEVMEM, CONFIG_NODES_SHIFT, and
CONFIG_CPU_FREQ_GOV_SCHEDUTIL all change from their current settings
during the build. Add the configuration they change to into pending for
review.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
commit 6f5cea3de2f10788f05e7f6cb70bb4cca8865b35
Author: Prarit Bhargava <prarit@redhat.com>
Date: Fri Jun 7 18:00:38 2019 -0400
[redhat] kernel packaging: Combine mod-blacklist.sh and mod-extra-blacklist.sh
Message-id: <20190607180038.20685-5-prarit@redhat.com>
Patchwork-id: 263189
O-Subject: [RHEL8.1 BZ 1699868 v4 4/4] kernel packaging: Combine mod-blacklist.sh and mod-extra-blacklist.sh
Bugzilla: 1699868
RH-Acked-by: Marcelo Leitner <mleitner@redhat.com>
RH-Acked-by: Laura Abbott <labbott@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1699868
Combine mod-blacklist.sh and mod-extra-blacklist.sh. The two scripts
take the same arguments and are called after one another.
v4: Fix cat usage in spec file and scripts (jbenc).
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Philipp Rudo <prudo@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
NOTE: redhat/mod-extra.list is removed here because ARK uses that file
differently. Instead update_scripts.sh is run to include mod-extras.list.rhel
and mod-extras.list.fedora.
commit b2819ae00d4cd6380e1151dd0628f32e19a85d6f
Author: Prarit Bhargava <prarit@redhat.com>
Date: Fri Jun 7 18:00:37 2019 -0400
[rpmspec] kernel packaging: Fix extra namespace collision
Message-id: <20190607180038.20685-4-prarit@redhat.com>
Patchwork-id: 263188
O-Subject: [RHEL8.1 BZ 1699868 v4 3/4] kernel packaging: Fix extra namespace collision
Bugzilla: 1699868
RH-Acked-by: Marcelo Leitner <mleitner@redhat.com>
RH-Acked-by: Laura Abbott <labbott@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1699868
The kernel-modules-extra package collides with the 3rd party driver
location, /lib/modules/'uname -r'/extra. When the kernel-modules-extra
package has already been installed and a new kernel is installed, the
result is a significant increase to the install time of a kernel and the
wrong kernel modules being loaded into the new kernel.
The /lib/modules/'uname -r'/extra directory is designated as a spot
where 3rd party vendors can place their out-of-box drivers. When a new
kernel is installed (specifically the kernel-core package) a call is
made to /usr/sbin/weak-modules (from the kmod package) to examine
drivers in the previously installed kernels' extra directories to bring
those drivers forward into the new kernel.
The kernel-modules-extra package installs modules into the /extra
directory. As a result, when /usr/sbin/weak-modules is executed it
brings the modules from kernel-modules-extra forward into the new kernel
as well. This is a critical mistake as the wrong modules have now been
brought forward. Additionally, /usr/sbin/weak-modules takes longer to
execute every time a new kernel is installed. After five kernels are
installed the time to install the kernel-core package climbs to
approximately 10 minutes.
After some code investigation and discussion with the authors of the
original Fedora code, and input from Herton, this can be avoided by
installing the kernel-modules-extra modules to their original
directories in 8.0.z.
The existing build process copies all the modules into a temporary area
called restore, and leaving the original modules directory as a work
area. The modules listed in mod-extra.list are copied to extra/ and
removed from the work area, and core.list and modules.list files are
created. The restore area is then copied back, and the rpm build
process continues.
My changes create a mod-extra.list and a mod-internal.list (similar to
core.list and modules.list), and remove the files from the work area so
that the core.list and modules.list can be created. The list files are
used later on to create dynamic %files sections for the subpackages.
Remove the /lib/modules/'uname -r'/extra installation path from
the kernel-modules-extra package and install the modules in their
original directories.
v4: Make modules-internal.list and modules-extra.list use consistent (mleitner).
Fix cat usage in spec file and scripts (jbenc).
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
To build only armv7hl kernel headers, all the BuildKernel commands
need to be disabled. The following macros were still set
with_pae
with_zfcpdump
Make sure they are disabled for nobuildarches.
Due to our current odd branching strategy, the easiest way to maintain
the CI jobs is externally and including the external definition in each
branch. This way, users who fork the repository get the latest CI
definitions and we do not need to keep the two branches in sync.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
We export the set of patches we carry each time ark-patches is updated
so we can just download a patch bundle and apply it to any old tree.
However, we don't want to export the patches relating to gitlab-ci files
since the target in question might include this file (like, for example,
the internal branch of ARK). Strip any commits relating to gitlab-ci.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
We've got one oddball setting which we adjust the Kconfig default in a
patch in ark-patches. The setting is, therefore, invalid on vanilla
trees, which led to jumping through hoops to get the downstream patches
applied to the internal branch before testing.
This was painful because we needed to fetch the ark-patches branch to
some depth along with the master branch, figure out the merge base, and
yank all the patches out for application. It's more reasonable to just
set the one setting back to its upstream default and be careful about
further tweaks to Kconfigs in the downstream patch set.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
The create-tarball.sh script can occasionally hang non 64 bit systems
due to extreeme memory usage. Build farms will occasionally use older
32 bit systems to do arch independent work (like assembling
srpms/tarballs/etc), and when xz runs on those systems, it will, given a
sufficiently large input file, allocate more than the available 3G of
memory address space allocated to a user space process, causing swap
storms, and build failures due to resultant job timeouts.
Fix it by detecting if we are on a 64 bit arch or not, and setting the
xz memory usage limit accordingly
Signed-off-by: Neil Horman <nhorman@redhat.com>
Rawhide in the Fedora dist-git is on the master branch, so use it by
default for the RHPRODUCT which is used to determine the dist-git branch
name.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
With ARK and Fedora about to merge, make Fedora the default dist. ARK
will be built largely by automation, but Fedora will get a lot of
end-user usage, so default to what they'll likely want.
When ARK is forked, the default can be set to a sensible default for
RHEL 9.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
We've switched master to track Linus's tree, so use the ark-latest
branch when updating the changelog in internal. Also set -e so the next
time something changes the job fails.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Update the CI jobs with the latest definition from the external
repository, including jobs for the ark-patches tree and a job to export
the latest downstream patch set.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_BOOTTIME_TRACING:
Enable developer to setup ftrace subsystem via supplemental
kernel cmdline at boot time for debugging (tracing) driver
initialization and boot process.
Symbol: BOOTTIME_TRACING [=y]
Type : bool
Defined at kernel/trace/Kconfig:144
Prompt: Boot-time Tracing support
Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && BOOT_CONFIG [=y] && TRACING [=y]
Location:
-> Kernel hacking
-> Tracers (FTRACE [=y])
---
CONFIG_KPROBE_EVENTS_ON_NOTRACE:
This is only for the developers who want to debug ftrace itself
using kprobe events.
If kprobes can use ftrace instead of breakpoint, ftrace related
functions are protected from kprobe-events to prevent an infinit
recursion or any unexpected execution path which leads to a kernel
crash.
This option disables such protection and allows you to put kprobe
events on ftrace functions for debugging ftrace by itself.
Note that this might let you shoot yourself in the foot.
If unsure, say N.
Symbol: KPROBE_EVENTS_ON_NOTRACE [=n]
Type : bool
Defined at kernel/trace/Kconfig:550
Prompt: Do NOT protect notrace function from kprobe events
Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && KPROBE_EVENTS [=y] && KPROBES_ON_FTRACE [=y]
Location:
-> Kernel hacking
-> Tracers (FTRACE [=y])
-> Enable kprobes-based dynamic events (KPROBE_EVENTS [=y])
---
CONFIG_KPROBE_EVENT_GEN_TEST:
This option creates a test module to check the base
functionality of in-kernel kprobe event definition.
To test, insert the module, and then check the trace buffer
for the generated kprobe events.
If unsure, say N.
Symbol: KPROBE_EVENT_GEN_TEST [=n]
Type : tristate
Defined at kernel/trace/Kconfig:839
Prompt: Test module for in-kernel kprobe event generation
Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && KPROBE_EVENTS [=y]
Location:
-> Kernel hacking
-> Tracers (FTRACE [=y])
Enabled for debugging kernels at the request of Jiri Olsa
---
CONFIG_SYNTH_EVENT_GEN_TEST:
This option creates a test module to check the base
functionality of in-kernel synthetic event definition and
generation.
To test, insert the module, and then check the trace buffer
for the generated sample events.
If unsure, say N.
Symbol: SYNTH_EVENT_GEN_TEST [=n]
Type : tristate
Defined at kernel/trace/Kconfig:826
Prompt: Test module for in-kernel synthetic event generation
Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && HIST_TRIGGERS [=y]
Location:
-> Kernel hacking
-> Tracers (FTRACE [=y])
Enabled for debugging kernels at the request of Jiri Olsa
---
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Jerome Marchand <jmarchan@redhat.com>
Fedora includes a script in its dist-git that allows users to drop
config settings into the "kernel-local" file which is merged into the
final configuration. This is purely for users and is empty in the
dist-git tree so it has no effect.
A number of folks use this script, so in order to minimize the
disruption of ARK and Fedora this includes it and the associated
specfile changes.
Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
The script that generates the configuration commits appears to have a
bug where it's not deleting the corresponding pending file when it moves
it to common/. This drops any configs already listed in common/ and I'll
track down the script bug later.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_INTEL_UNCORE_FREQ_CONTROL:
This driver allows control of uncore frequency limits on
supported server platforms.
Uncore frequency controls RING/LLC (last-level cache) clocks.
To compile this driver as a module, choose M here: the module
will be called intel-uncore-frequency.
Symbol: INTEL_UNCORE_FREQ_CONTROL [=n]
Type : tristate
Prompt: Intel Uncore frequency control driver
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
Defined at drivers/platform/x86/Kconfig:1339
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && X86_64 [=y]
Set to m at the request of Prarit.
---
Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
This configuration is is exposed by CONFIG_MPTCP which got enabled in
commit b42134757b, but due to a bug in the configuration setting
scripts, the pending configuration was never removed so MPTCP was not
actually on. Help text is:
config MPTCP_IPV6
bool "MPTCP: IPv6 support for Multipath TCP"
select IPV6
default y
This commit enables MPTCP_IPV6 and removes the Fedora-specific config
for it.
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
ARK builds weekly, always based of a tag in Linus's tree. Fedora Rawhide
kernels are built daily and the policy is to use the debug
configurations except for RC and final releases.
redhat/Makefile.common determines if HEAD's merge base is a tag, and if
is, SNAPSHOT is set to 0. If HEAD's merge base is not a tag, SNAPSHOT is
1. Invert this and use it to dynamically set the debugbuildsenabled
boolean in the specfile.
Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
The build ID is used to link binaries and their debug info. Setting this
option will use the value in the calculation of the build id. This
aligns with Fedora which has been using it since July 2018.
Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
We've been doing a workaround of using a uuid for the build-id for
userspace binaries to let us get parallel debuginfo (the trick we
use for the kernel doesn't extend to userspace binaries). This
works but isn't ideal for reproducibility. Given we don't actually
care about this debuginfo, just remove it from the buildroot completely.
This is a back port of a patch in Fedora's kernel specfile.
Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Fedora's HDR_ARCH_LIST differs from ARK since ARM is still a target, so
define the list conditionally.
Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
If building in a Fedora buildroot, include a build dependency on
dwarves. This aligns with the current Fedora specfile.
Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
It's re-defined as 0 directly below it anyway and this produces a noisy
warning. Fedora's spec has it uncommented as well so this decreases the
diff between the two.
Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Builds in the Fedora buildroot fail with GCC 10. This adds -fcommon to
the build flags until upstream cleanly builds without it. This is
required to merge ARK with Fedora.
Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Update for the latest changes in Fedora's dist-git. Enables
BACKLIGHT_LED as a module and a number of ARM sound config options.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_PHY_INTEL_EMMC:
Enable this to support the Intel EMMC PHY
Symbol: PHY_INTEL_EMMC [=n]
Type : tristate
Defined at drivers/phy/intel/Kconfig:5
Prompt: Intel EMMC PHY driver
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=n]
---
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_MFD_ROHM_BD71828:
Select this option to get support for the ROHM BD71828 Power
Management IC. BD71828GW is a single-chip power management IC for
battery-powered portable devices. The IC integrates 7 buck
converters, 7 LDOs, and a 1500 mA single-cell linear charger.
Also included is a Coulomb counter, a real-time clock (RTC), and
a 32.768 kHz clock gate.
Symbol: MFD_ROHM_BD71828 [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:1910
Prompt: ROHM BD71828 Power Management IC
Depends on: HAS_IOMEM [=y] && I2C [=y]=y && OF [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: REGMAP_I2C [=m] && REGMAP_IRQ [=n] && MFD_CORE [=m]
---
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_NET_SCH_ETS:
The Enhanced Transmission Selection scheduler is a classful
queuing discipline that merges functionality of PRIO and DRR
qdiscs in one scheduler. ETS makes it easy to configure a set of
strict and bandwidth-sharing bands to implement the transmission
selection described in 802.1Qaz.
Say Y here if you want to use the ETS packet scheduling
algorithm.
To compile this driver as a module, choose M here: the module
will be called sch_ets.
If unsure, say N.
Symbol: NET_SCH_ETS [=n]
Type : tristate
Prompt: Enhanced transmission selection scheduler (ETS)
Location:
-> Networking support (NET [=y])
-> Networking options
-> QoS and/or fair queueing (NET_SCHED [=y])
Defined at net/sched/Kconfig:425
Depends on: NET [=y] && NET_SCHED [=y]
This has been enabled as module at the request of Jiri Benc and Marcelo
Ricardo Leitner
---
CONFIG_NET_SCH_FQ_PIE:
Say Y here if you want to use the Flow Queue Proportional Integral
controller Enhanced (FQ-PIE) packet scheduling algorithm.
For more information, please see https://tools.ietf.org/html/rfc8033
To compile this driver as a module, choose M here: the module
will be called sch_fq_pie.
If unsure, say N.
Symbol: NET_SCH_FQ_PIE [=n]
Type : tristate
Prompt: Flow Queue Proportional Integral controller Enhanced (FQ-PIE)
Location:
-> Networking support (NET [=y])
-> Networking options
-> QoS and/or fair queueing (NET_SCHED [=y])
-> Proportional Integral controller Enhanced (PIE) scheduler (NET_SCH_PIE [=m])
Defined at net/sched/Kconfig:369
Depends on: NET [=y] && NET_SCHED [=y] && NET_SCH_PIE [=m]
This has been disabled at the request of Jiri Benc
---
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
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_SMMU_LEGACY_DT_BINDINGS:
Support for the badly designed and deprecated "mmu-masters"
devicetree bindings. This allows some DMA masters to attach
to the SMMU but does not provide any support via the DMA API.
If you're lucky, you might be able to get VFIO up and running.
If you say Y here then you'll make me very sad. Instead, say N
and move your firmware to the utopian future that was 2016.
Symbol: ARM_SMMU_LEGACY_DT_BINDINGS [=n]
Type : bool
Defined at drivers/iommu/Kconfig:384
Prompt: Support the legacy "mmu-masters" devicetree bindings
Depends on: IOMMU_SUPPORT [=y] && ARM_SMMU [=y]=y && OF [=y]
Location:
-> Device Drivers
-> IOMMU Hardware Support (IOMMU_SUPPORT [=y])
-> ARM Ltd. System MMU (SMMU) Support (ARM_SMMU [=y])
---
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON:
Selecting this option will enable by default the scalable mode if
hardware presents the capability. The scalable mode is defined in
VT-d 3.0. The scalable mode capability could be checked by reading
/sys/devices/virtual/iommu/dmar*/intel-iommu/ecap. If this option
is not selected, scalable mode support could also be enabled by
passing intel_iommu=sm_on to the kernel. If not sure, please use
the default value.
Symbol: INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON [=n]
Type : bool
Defined at drivers/iommu/Kconfig:252
Prompt: Enable Intel IOMMU scalable mode by default
Depends on: IOMMU_SUPPORT [=y] && INTEL_IOMMU [=y]
Location:
-> Device Drivers
-> IOMMU Hardware Support (IOMMU_SUPPORT [=y])
-> Support for Intel IOMMU using DMA Remapping Devices (INTEL_IOMMU [=y])
---
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>
Cc: Don Dutile <ddutile@redhat.com>
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_NFSD_V4_2_INTER_SSC:
This option enables support for NFSv4.2 inter server to
server copy where the destination server calls the NFSv4.2
client to read the data to copy from the source server.
If unsure, say N.
Symbol: NFSD_V4_2_INTER_SSC [=n]
Type : bool
Defined at fs/nfsd/Kconfig:137
Prompt: NFSv4.2 inter server to server COPY
Depends on: NETWORK_FILESYSTEMS [=y] && NFSD_V4 [=y] && NFS_V4_1 [=y] && NFS_V4_2 [=y]
Location:
-> File systems
-> Network File Systems (NETWORK_FILESYSTEMS [=y])
---
Cc: Red Hat NFS Team <nfs-team@redhat.com>
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_MICROCHIP_PIT64B:
This option enables Microchip PIT64B timer for Atmel
based system. It supports the oneshot, the periodic
modes and high resolution. It is used as a clocksource
and a clockevent.
Symbol: MICROCHIP_PIT64B [=n]
Type : bool
Prompt: Microchip PIT64B support
Location:
-> Device Drivers
-> Clock Source drivers
Defined at drivers/clocksource/Kconfig:700
Depends on: GENERIC_CLOCKEVENTS [=y] && (OF [=y] || COMPILE_TEST [=n])
Selects: CLKSRC_MMIO [=n]
---
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_INET_ESPINTCP:
Support for RFC 8229 encapsulation of ESP and IKE over
TCP/IPv4 sockets.
If unsure, say N.
Symbol: INET_ESPINTCP [=n]
Type : bool
Prompt: IP: ESP in TCP encapsulation (RFC 8229)
Location:
-> Networking support (NET [=y])
-> Networking options
-> TCP/IP networking (INET [=y])
-> IP: ESP transformation (INET_ESP [=m])
Defined at net/ipv4/Kconfig:381
Depends on: NET [=y] && INET [=y] && XFRM [=y] && INET_ESP [=m]
Selects: STREAM_PARSER [=y] && NET_SOCK_MSG [=y]
This has been enabled at the request of Marcelo Ricardo Leitner
<mleitner@redhat.com>
---
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
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_TIME_NS:
In this namespace boottime and monotonic clocks can be set.
The time will keep going with the same pace.
Symbol: TIME_NS [=y]
Type : bool
Prompt: TIME namespace
Location:
-> General setup
-> Namespaces support (NAMESPACES [=y])
Defined at init/Kconfig:1084
Depends on: NAMESPACES [=y] && GENERIC_VDSO_TIME_NS [=y]
---
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_GPIO_SIFIVE:
Say yes here to support the GPIO device on SiFive SoCs.
Symbol: GPIO_SIFIVE [=n]
Type : bool
Prompt: SiFive GPIO support
Location:
-> Device Drivers
-> GPIO Support (GPIOLIB [=y])
-> Memory mapped GPIO drivers
Defined at drivers/gpio/Kconfig:482
Depends on: GPIOLIB [=y] && HAS_IOMEM [=y] && OF_GPIO [=y] && IRQ_DOMAIN_HIERARCHY [=y]
Selects: GPIO_GENERIC [=n] && GPIOLIB_IRQCHIP [=y] && REGMAP_MMIO [=n]
---
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_EFI_DISABLE_PCI_DMA:
Disable the busmaster bit in the control register on all PCI bridges
while calling ExitBootServices() and passing control to the runtime
kernel. System firmware may configure the IOMMU to prevent malicious
PCI devices from being able to attack the OS via DMA. However, since
firmware can't guarantee that the OS is IOMMU-aware, it will tear
down IOMMU configuration when ExitBootServices() is called. This
leaves a window between where a hostile device could still cause
damage before Linux configures the IOMMU again.
If you say Y here, the EFI stub will clear the busmaster bit on all
PCI bridges before ExitBootServices() is called. This will prevent
any malicious PCI devices from being able to perform DMA until the
kernel reenables busmastering after configuring the IOMMU.
This option will cause failures with some poorly behaved hardware
and should not be enabled without testing. The kernel commandline
options "efi=disable_early_pci_dma" or "efi=no_disable_early_pci_dma"
may be used to override this option.
Symbol: EFI_DISABLE_PCI_DMA [=n]
Type : bool
Prompt: Clear Busmaster bit on PCI bridges during ExitBootServices()
Location:
-> Firmware Drivers
-> EFI (Extensible Firmware Interface) Support
Defined at drivers/firmware/efi/Kconfig:218
Depends on: EFI [=y]
---
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_NFS_DISABLE_UDP_SUPPORT:
Choose Y here to disable the use of NFS over UDP. NFS over UDP
on modern networks (1Gb+) can lead to data corruption caused by
fragmentation during high loads.
Symbol: NFS_DISABLE_UDP_SUPPORT [=y]
Type : bool
Defined at fs/nfs/Kconfig:200
Prompt: NFS: Disable NFS UDP protocol support
Depends on: NETWORK_FILESYSTEMS [=y] && NFS_FS [=m]
Location:
-> File systems
-> Network File Systems (NETWORK_FILESYSTEMS [=y])
---
At the request of Benjamin Coddington, this has been disabled pending
the NFS team's decision on whether or not to support UDP in the future.
Cc: Red Hat NFS Team <nfs-team@redhat.com>
Configuration options come and go, and these have all gone as of
v5.6-rc2. Drop them from the configuration tree. In addition to being
tidy, this helps minimize the difference between the ARK configuration
tree and Fedora's dist-git.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_DRM_ANALOGIX_ANX6345:
ANX6345 is an ultra-low Full-HD DisplayPort/eDP
transmitter designed for portable devices. The
ANX6345 transforms the LVTTL RGB output of an
application processor to eDP or DisplayPort.
Symbol: DRM_ANALOGIX_ANX6345 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/analogix/Kconfig:2
Prompt: Analogix ANX6345 bridge
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_ANALOGIX_DP [=n] && DRM_KMS_HELPER [=m] && REGMAP_I2C [=m]
---
CONFIG_DRM_LVDS_CODEC:
Support for transparent LVDS encoders and decoders that don't
require any configuration.
Symbol: DRM_LVDS_CODEC [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:38
Prompt: Transparent LVDS encoders and decoders support
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_KMS_HELPER [=m] && DRM_PANEL_BRIDGE [=y]
---
Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Rob Clark <rclark@redhat.com>
Whenever upstream changes the COPYING file it leads to an RPM file
conflict because the name is set to, for example, 5.6.0 for the whole
release cycle, but multiple kernel packages need to be installed that
reference that same file. This rarely happens, but it's annoying and the
file is tiny so just have one per installed kernel.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_USB4:
USB4 and Thunderbolt driver. USB4 is the public speficiation
based on Thunderbolt 3 protocol. This driver is required if
you want to hotplug Thunderbolt and USB4 compliant devices on
Apple hardware or on PCs with Intel Falcon Ridge or newer.
To compile this driver a module, choose M here. The module will be
called thunderbolt.
Symbol: USB4 [=n]
Type : tristate
Defined at drivers/thunderbolt/Kconfig:2
Prompt: Unified support for USB4 and Thunderbolt
Depends on: PCI [=y] && (X86 [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
Selects: APPLE_PROPERTIES [=n] && CRC32 [=y] && CRYPTO [=y] && CRYPTO_HASH [=y] && NVMEM [=y]
---
Jarod requested that CONFIG_USB4=y since it's a direct replacement for
CONFIG_THUNDERBOLT which is currently y. This has exposed a further
configuration:
CONFIG_USB4_NET:
Select this if you want to create network between two computers
over a USB4 and Thunderbolt cables. The driver supports Apple
ThunderboltIP protocol and allows communication with any host
supporting the same protocol including Windows and macOS.
To compile this driver a module, choose M here. The module will be
called thunderbolt-net.
Symbol: USB4_NET [=n]
Type : tristate
Defined at drivers/net/Kconfig:535
Prompt: Networking over USB4 and Thunderbolt cables
Depends on: NETDEVICES [=y] && USB4 [=m] && INET [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
---
USB4_NET is a replacement for THUNDERBOLT_NET and its setting reflects
that.
Cc: Jarod Wilson <jarod@redhat.com>
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_SND_SOC_ADAU7118_HW:
Enable support for the Analog Devices ADAU7118 8 Channel PDM-to-I2S/TDM
Converter. In this mode, the device works in standalone mode which
means that there is no bus to comunicate with it. Stereo mode is not
supported in this mode.
To compile this driver as a module, choose M here: the module
will be called snd-soc-adau7118-hw.
Symbol: SND_SOC_ADAU7118_HW [=n]
Type : tristate
Prompt: Analog Devices ADAU7118 8 Channel PDM-to-I2S/TDM Converter - HW Mode
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> CODEC drivers
Defined at sound/soc/codecs/Kconfig:405
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
Selects: SND_SOC_ADAU7118 [=n]
Selected by [n]:
- SND_SOC_ALL_CODECS [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n]
---
CONFIG_SND_SOC_ADAU7118_I2C:
Enable support for the Analog Devices ADAU7118 8 Channel PDM-to-I2S/TDM
Converter over I2C. This gives full support over the device.
To compile this driver as a module, choose M here: the module
will be called snd-soc-adau7118-i2c.
Symbol: SND_SOC_ADAU7118_I2C [=n]
Type : tristate
Prompt: Analog Devices ADAU7118 8 Channel PDM-to-I2S/TDM Converter - I2C
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> CODEC drivers
Defined at sound/soc/codecs/Kconfig:417
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && I2C [=y]
Selects: SND_SOC_ADAU7118 [=n] && REGMAP_I2C [=y]
Selected by [n]:
- SND_SOC_ALL_CODECS [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n] && I2C [=y]
---
Cc: Jaroslav Kysela <jkysela@redhat.com>
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_SERIAL_8250_16550A_VARIANTS:
The 8250 driver can probe for many variants of the venerable 16550A
serial port. Doing so takes additional time at boot.
On modern systems, especially those using serial only for a simple
console, you can say N here.
Symbol: SERIAL_8250_16550A_VARIANTS [=n]
Type : bool
Defined at drivers/tty/serial/8250/Kconfig:63
Prompt: Support for variants of the 16550A serial port
Depends on: TTY [=y] && HAS_IOMEM [=y] && SERIAL_8250 [=y]
Location:
-> Device Drivers
-> Character devices
-> Serial drivers
-> 8250/16550 and compatible serial support (SERIAL_8250 [=y])
---
Prarit Bhargava requested that this be enabled: "Enabling this will make
virt systems boot faster. We want this to be enabled for RHEL"
Cc: Prarit Bhargava <prarit@redhat.com>
scripts/jobserver-exec is used in the documentation Makefile and
needs to be mangled to use Python 3 explicitly.
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
A new manual page, bpftool-gen, is being built as of v5.6-rc1. Include
it with bpftool.
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_PTDUMP_DEBUGFS:
Say Y here if you want to show the kernel pagetable layout in a
debugfs file. This information is only useful for kernel developers
who are working in architecture specific areas of the kernel.
It is probably not a good idea to enable this feature in a production
kernel.
If in doubt, say N.
Symbol: PTDUMP_DEBUGFS [=n]
Type : bool
Defined at mm/Kconfig.debug:127
Prompt: Export kernel pagetable layout to userspace via debugfs
Depends on: DEBUG_KERNEL [=y] && DEBUG_FS [=y] && GENERIC_PTDUMP [=y]
Location:
-> Kernel hacking
-> Memory Debugging
Selects: PTDUMP_CORE [=y]
---
At the request of Waiman Long, this has been enabled for debug kernels.
Cc: Waiman Long <longman@redhat.com>
Cc: Larry Woodman <lwoodman@redhat.com>
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_ZLIB_DFLTCC:
Enable s390x hardware support for zlib in the kernel.
Symbol: ZLIB_DFLTCC [=y]
Type : bool
Defined at lib/Kconfig:281
Prompt: Enable s390x DEFLATE CONVERSION CALL support for kernel zlib
Depends on: S390 [=y]
Location:
-> Library routines
---
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_BOOT_CONFIG:
Extra boot config allows system admin to pass a config file as
complemental extension of kernel cmdline when booting.
The boot config file must be attached at the end of initramfs
with checksum and size.
See <file:Documentation/admin-guide/bootconfig.rst> for details.
If unsure, say Y.
Symbol: BOOT_CONFIG [=y]
Type : bool
Defined at init/Kconfig:1227
Prompt: Boot config support
Depends on: BLK_DEV_INITRD [=y]
Location:
-> General setup
-> Initial RAM filesystem and RAM disk (initramfs/initrd) support (BLK_DEV_INITRD [=y])
Selects: LIBXBC [=y]
---
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_QUICC_ENGINE:
The QUICC Engine (QE) is a new generation of communications
coprocessors on Freescale embedded CPUs (akin to CPM in older chips).
Selecting this option means that you wish to build a kernel
for a machine with a QE coprocessor.
Symbol: QUICC_ENGINE [=n]
Type : bool
Defined at drivers/soc/fsl/qe/Kconfig:6
Prompt: QUICC Engine (QE) framework support
Depends on: OF [=y] && HAS_IOMEM [=y] && (PPC [=y] || ARM || ARM64 || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> SOC (System On Chip) specific Drivers
-> NXP/Freescale QorIQ SoC drivers
Selects: GENERIC_ALLOCATOR [=y] && CRC32 [=y]
Selected by [n]:
- KMETER1 [=n] && PPC_83xx [=n]
---
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_RESET_BRCMSTB_RESCAL:
This enables the RESCAL reset controller for SATA, PCIe0, or PCIe1 on
BCM7216.
Symbol: RESET_BRCMSTB_RESCAL [=n]
Type : bool
Defined at drivers/reset/Kconfig:52
Prompt: Broadcom STB RESCAL reset controller
Depends on: RESET_CONTROLLER [=y]
Location:
-> Device Drivers
-> Reset Controller Support (RESET_CONTROLLER [=y])
---
CONFIG_RESET_INTEL_GW:
This enables the reset controller driver for Intel Gateway SoCs.
Say Y to control the reset signals provided by reset controller.
Otherwise, say N.
Symbol: RESET_INTEL_GW [=n]
Type : bool
Defined at drivers/reset/Kconfig:74
Prompt: Intel Reset Controller Driver
Depends on: RESET_CONTROLLER [=y] && OF [=y]
Location:
-> Device Drivers
-> Reset Controller Support (RESET_CONTROLLER [=y])
Selects: REGMAP_MMIO [=y]
---
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_PINCTRL_LYNXPOINT:
Lynxpoint is the PCH of Intel Haswell. This pinctrl driver
provides an interface that allows configuring of PCH pins and
using them as GPIOs.
Symbol: PINCTRL_LYNXPOINT [=n]
Type : tristate
Defined at drivers/pinctrl/intel/Kconfig:34
Prompt: Intel Lynxpoint pinctrl and GPIO driver
Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINMUX [=y] && PINCONF [=y] && GENERIC_PINCONF [=y] && GPIOLIB [=y] && GPIOLIB_IRQCHIP [=y]
---
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_AD7091R5:
Say yes here to build support for Analog Devices AD7091R-5 ADC.
Symbol: AD7091R5 [=n]
Type : tristate
Defined at drivers/iio/adc/Kconfig:24
Prompt: Analog Devices AD7091R5 ADC Driver
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Analog to digital converters
Selects: REGMAP_I2C [=m]
---
CONFIG_BMA400:
Say Y here if you want to build a driver for the Bosch BMA400
triaxial acceleration sensor.
To compile this driver as a module, choose M here: the
module will be called bma400_core and you will also get
bma400_i2c if I2C is enabled.
Symbol: BMA400 [=n]
Type : tristate
Defined at drivers/iio/accel/Kconfig:115
Prompt: Bosch BMA400 3-Axis Accelerometer Driver
Depends on: IIO [=m]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Accelerometers
Selects: REGMAP [=y] && BMA400_I2C [=n]
---
CONFIG_DLHL60D:
Say yes here to build support for the All Sensors DLH series
pressure sensors driver.
To compile this driver as a module, choose M here: the module
will be called dlhl60d.
Symbol: DLHL60D [=n]
Type : tristate
Defined at drivers/iio/pressure/Kconfig:56
Prompt: All Sensors DLHL60D and DLHL60G low voltage digital pressure sensors
Depends on: IIO [=m] && I2C [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Pressure sensors
Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]
---
CONFIG_LTC2496:
Say yes here to build support for Linear Technology LTC2496
16-Bit 8-/16-Channel Delta Sigma ADC.
To compile this driver as a module, choose M here: the module will be
called ltc2496.
Symbol: LTC2496 [=n]
Type : tristate
Defined at drivers/iio/adc/Kconfig:533
Prompt: Linear Technology LTC2496 ADC driver
Depends on: IIO [=m] && SPI [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Analog to digital converters
---
CONFIG_PING:
Say Y here to build a driver for GPIO bitbanged ranger sensors
with just one GPIO for the trigger and echo. This driver can be
used to measure the distance of objects.
Actually supported are:
- Parallax PING))) (ultrasonic)
- Parallax LaserPING (time-of-flight)
To compile this driver as a module, choose M here: the
module will be called ping.
Symbol: PING [=n]
Type : tristate
Defined at drivers/iio/proximity/Kconfig:61
Prompt: Parallax GPIO bitbanged ranger sensors
Depends on: IIO [=m] && GPIOLIB [=y]
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Proximity and distance sensors
---
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_GPIO_LOGICVC:
Say yes here to support GPIO functionality of the Xylon LogiCVC
programmable logic block.
Symbol: GPIO_LOGICVC [=n]
Type : tristate
Defined at drivers/gpio/Kconfig:315
Prompt: Xylon LogiCVC GPIO support
Depends on: GPIOLIB [=y] && HAS_IOMEM [=y] && MFD_SYSCON [=y] && OF [=y]
Location:
-> Device Drivers
-> GPIO Support (GPIOLIB [=y])
-> Memory mapped GPIO drivers
---
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_APPLE_PROPERTIES:
Retrieve properties from EFI on Apple Macs and assign them to
devices, allowing for improved support of Apple hardware.
Properties that would otherwise be missing include the
Thunderbolt Device ROM and GPU configuration data.
If unsure, say Y if you have a Mac. Otherwise N.
Symbol: APPLE_PROPERTIES [=n]
Type : bool
Defined at drivers/firmware/efi/Kconfig:178
Prompt: Apple Device Properties
Depends on: EFI [=y] && EFI_STUB [=y] && X86 [=y]
Location:
-> Firmware Drivers
-> EFI (Extensible Firmware Interface) Support
Selects: EFI_DEV_PATH_PARSER [=n] && UCS2_STRING [=y]
Selected by [n]:
- USB4 [=n] && PCI [=y] && (X86 [=y] || COMPILE_TEST [=n]) && EFI_STUB [=y] && X86 [=y]
---
This is required to be on for CONFIG_USB4=m. As Jarod has requested
that, this has been set to y.
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
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_STRICT_KERNEL_RWX:
If this is set, kernel text and rodata memory will be made read-only,
and non-text memory will be made non-executable. This provides
protection against certain security exploits (e.g. executing the heap
or modifying text)
These features are considered standard security practice these days.
You should say Y here in almost all cases.
Symbol: STRICT_KERNEL_RWX [=n]
Type : bool
Defined at arch/Kconfig:865
Prompt: Make kernel text and rodata read-only
Depends on: ARCH_HAS_STRICT_KERNEL_RWX [=y]
Visible if: ARCH_HAS_STRICT_KERNEL_RWX [=y] && ARCH_OPTIONAL_KERNEL_RWX [=y]
Location:
-> General architecture-dependent options
---
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_SECURITY_SELINUX_SID2STR_CACHE_SIZE:
This option defines the size of the internal SID -> context string
cache, which improves the performance of context to string
conversion. Setting this option to 0 disables the cache completely.
If unsure, keep the default value.
Symbol: SECURITY_SELINUX_SID2STR_CACHE_SIZE [=256]
Type : integer
Prompt: NSA SELinux SID to context string translation cache size
Location:
-> Security options
-> NSA SELinux Support (SECURITY_SELINUX [=y])
Defined at security/selinux/Kconfig:105
Depends on: SECURITY_SELINUX [=y]
---
CONFIG_SECURITY_SELINUX_SIDTAB_HASH_BITS:
This option sets the number of buckets used in the sidtab hashtable
to 2^SECURITY_SELINUX_SIDTAB_HASH_BITS buckets. The number of hash
collisions may be viewed at /sys/fs/selinux/ss/sidtab_hash_stats. If
chain lengths are high (e.g. > 20) then selecting a higher value here
will ensure that lookups times are short and stable.
Symbol: SECURITY_SELINUX_SIDTAB_HASH_BITS [=9]
Type : integer
Range : [8 13]
Prompt: NSA SELinux sidtab hashtable size
Location:
-> Security options
-> NSA SELinux Support (SECURITY_SELINUX [=y])
Defined at security/selinux/Kconfig:93
Depends on: SECURITY_SELINUX [=y]
---
Cc: Ondrej Mosnacek <omosnace@redhat.com>
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_VSOCKETS_LOOPBACK:
This module implements a loopback transport for Virtual Sockets,
using vmw_vsock_virtio_transport_common.
To compile this driver as a module, choose M here: the module
will be called vsock_loopback. If unsure, say N.
Symbol: VSOCKETS_LOOPBACK [=m]
Type : tristate
Prompt: Virtual Sockets loopback transport
Location:
-> Networking support (NET [=y])
-> Networking options
-> Virtual Socket protocol (VSOCKETS [=m])
Defined at net/vmw_vsock/Kconfig:29
Depends on: NET [=y] && VSOCKETS [=m]
Selects: VIRTIO_VSOCKETS_COMMON [=m]
---
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
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_MPTCP:
Multipath TCP (MPTCP) connections send and receive data over multiple
subflows in order to utilize multiple network paths. Each subflow
uses the TCP protocol, and TCP options carry header information for
MPTCP.
Symbol: MPTCP [=n]
Type : bool
Prompt: MPTCP: Multipath TCP
Location:
-> Networking support (NET [=y])
-> Networking options
-> TCP/IP networking (INET [=y])
Defined at net/mptcp/Kconfig:2
Depends on: NET [=y] && INET [=y]
Selects: SKB_EXTENSIONS [=y] && CRYPTO_LIB_SHA256 [=y]
MPTCP has been enabled at the request of Davide Caratti.
---
CONFIG_MPTCP_HMAC_TEST:
This option enable boot time self-test for the HMAC implementation
used by the MPTCP code
Say N if you are unsure.
Symbol: MPTCP_HMAC_TEST [=n]
Type : bool
Prompt: Tests for MPTCP HMAC implementation
Location:
-> Networking support (NET [=y])
-> Networking options
-> TCP/IP networking (INET [=y])
Defined at net/mptcp/Kconfig:19
Depends on: NET [=y] && INET [=y]
---
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
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_ETHTOOL_NETLINK:
An alternative userspace interface for ethtool based on generic
netlink. It provides better extensibility and some new features,
e.g. notification messages.
Symbol: ETHTOOL_NETLINK [=y]
Type : bool
Prompt: Netlink interface for ethtool
Location:
-> Networking support (NET [=y])
Defined at net/Kconfig:453
Depends on: NET [=y]
---
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
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_SPI_HISI_SFC_V3XX:
This enables support for HiSilicon v3xx SPI-NOR flash controller
found in hi16xx chipsets.
Symbol: SPI_HISI_SFC_V3XX [=n]
Type : tristate
Prompt: HiSilicon SPI-NOR Flash Controller for Hi16XX chipsets
Location:
-> Device Drivers
-> SPI support (SPI [=y])
Defined at drivers/spi/Kconfig:284
Depends on: SPI [=y] && SPI_MASTER [=y] && (ARM64 [=y] && ACPI [=y] || COMPILE_TEST [=n]) && HAS_IOMEM [=y]
Selects: CONFIG_MTD_SPI_NOR
---
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_PTP_1588_CLOCK_INES:
This driver adds support for using the ZHAW InES 1588 IP
core. This clock is only useful if the MII bus of your MAC
is wired up to the core.
Symbol: PTP_1588_CLOCK_INES [=n]
Type : tristate
Prompt: ZHAW InES PTP time stamping IP core
Location:
-> Device Drivers
-> PTP clock support
Defined at drivers/ptp/Kconfig:78
Depends on: NETWORK_PHY_TIMESTAMPING [=y] && PHYLIB [=y] && PTP_1588_CLOCK [=y]
---
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
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_BCM84881_PHY:
Support the Broadcom BCM84881 PHY.
Symbol: BCM84881_PHY [=n]
Type : bool
Prompt: Broadcom BCM84881 PHY
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> PHY Device support and infrastructure (PHYLIB [=y])
Defined at drivers/net/phy/Kconfig:328
Depends on: NETDEVICES [=y] && PHYLIB [=y]=y
---
Cc: Petr Oros <poros@redhat.com>
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_WIREGUARD:
WireGuard is a secure, fast, and easy to use replacement for IPSec
that uses modern cryptography and clever networking tricks. It's
designed to be fairly general purpose and abstract enough to fit most
use cases, while at the same time remaining extremely simple to
configure. See www.wireguard.com for more info.
It's safe to say Y or M here, as the driver is very lightweight and
is only in use when an administrator chooses to add an interface.
Symbol: WIREGUARD [=n]
Type : tristate
Prompt: WireGuard secure network tunnel
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Network core driver support (NET_CORE [=y])
Defined at drivers/net/Kconfig:74
Depends on: NETDEVICES [=y] && NET_CORE [=y] && NET [=y] && INET [=y] && (IPV6 [=y] || !IPV6 [=y])
Selects: NET_UDP_TUNNEL [=m] && DST_CACHE [=y] && CRYPTO [=y] && CRYPTO_LIB_CURVE25519 [=n] && CRYPTO_LIB_CHACHA20POLY1305 [=n] && CRYPTO_LIB_BLAKE2S [=n] && CRYPTO_CHACHA20_X86_64 [=m] && CRYPTO_POLY1305_X86_64 [=m] && CRYPTO_BLAKE2S_X86 [=n] && CRYPTO_CURVE25519_X86 [=n] && ARM_CRYPTO && ARM64_CRYPTO && CRYPTO_CHACHA20_NEON && CRYPTO_POLY1305_NEON && CRYPTO_POLY1305_ARM && CRYPTO_CURVE25519_NEON && CRYPTO_CHACHA_MIPS [=n] && CRYPTO_POLY1305_MIPS [=n]
---
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_SENSORS_ADM1177:
If you say yes here you get support for Analog Devices ADM1177
sensor chips.
This driver can also be built as a module. If so, the module
will be called adm1177.
Symbol: SENSORS_ADM1177 [=n]
Type : tristate
Prompt: Analog Devices ADM1177 and compatibles
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
Defined at drivers/hwmon/Kconfig:167
Depends on: HWMON [=y] && I2C [=y]
---
CONFIG_SENSORS_DRIVETEMP:
If you say yes you get support for the temperature sensor on
hard disk drives.
This driver can also be built as a module. If so, the module
will be called satatemp.
Symbol: SENSORS_DRIVETEMP [=n]
Type : tristate
Prompt: Hard disk drives with temperature sensors
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
Defined at drivers/hwmon/Kconfig:398
Depends on: HWMON [=y] && SCSI [=y] && ATA [=m]
---
CONFIG_SENSORS_MAX20730:
If you say yes here you get hardware monitoring support for Maxim
MAX20730, MAX20734, and MAX20743.
This driver can also be built as a module. If so, the module will
be called max20730.
Symbol: SENSORS_MAX20730 [=n]
Type : tristate
Prompt: Maxim MAX20730, MAX20734, MAX20743
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
Defined at drivers/hwmon/pmbus/Kconfig:148
Depends on: HWMON [=y] && PMBUS [=m]
---
CONFIG_SENSORS_MAX31730:
Support for the Maxim Integrated MAX31730 3-Channel Remote
Temperature Sensor.
This driver can also be built as a module. If so, the module
will be called max31730.
Symbol: SENSORS_MAX31730 [=n]
Type : tristate
Prompt: MAX31730 temperature sensor
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
Defined at drivers/hwmon/Kconfig:921
Depends on: HWMON [=y] && I2C [=y]
---
CONFIG_SENSORS_XDPE122:
If you say yes here you get hardware monitoring support for Infineon
XDPE12254, XDPE12284, device.
This driver can also be built as a module. If so, the module will
be called xdpe12284.
Symbol: SENSORS_XDPE122 [=n]
Type : tristate
Prompt: Infineon XDPE122 family
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
Defined at drivers/hwmon/pmbus/Kconfig:240
Depends on: HWMON [=y] && PMBUS [=m]
---
Cc: Dean Nelson <dnelson@redhat.com>
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_RANDOM:
Random number generation (part of the ARMv8.5 Extensions)
provides a high bandwidth, cryptographically secure
hardware random number generator.
Symbol: ARCH_RANDOM [=y]
Type : bool
Prompt: Enable support for random number generation
Location:
-> Kernel Features
-> ARMv8.5 architectural features
Defined at arch/arm64/Kconfig:1533
---
CONFIG_ARM64_E0PD:
E0PD (part of the ARMv8.5 extensions) allows us to ensure
that EL0 accesses made via TTBR1 always fault in constant time,
providing similar benefits to KASLR as those provided by KPTI, but
with lower overhead and without disrupting legitimate access to
kernel memory such as SPE.
This option enables E0PD for TTBR1 where available.
Symbol: ARM64_E0PD [=y]
Type : bool
Prompt: Enable support for E0PD
Location:
-> Kernel Features
-> ARMv8.5 architectural features
Defined at arch/arm64/Kconfig:1521
---
CONFIG_ARM64_ERRATUM_1530923:
This option adds a workaround for ARM Cortex-A55 erratum 1530923.
Affected Cortex-A55 cores (r0p0, r0p1, r1p0, r2p0) could end-up with
corrupted TLBs by speculating an AT instruction during a guest
context switch.
If unsure, say Y.
Symbol: ARM64_ERRATUM_1530923 [=y]
Type : bool
Prompt: Cortex-A55: Speculative AT instruction using out-of-context translation regime could cause subsequent request to generate an incorrect translation
Location:
-> Kernel Features
-> ARM errata workarounds via the alternatives framework
Defined at arch/arm64/Kconfig:539
Selects: ARM64_WORKAROUND_SPECULATIVE_AT_VHE [=y]
---
CONFIG_ARM64_USE_LSE_ATOMICS:
As part of the Large System Extensions, ARMv8.1 introduces new
atomic instructions that are designed specifically to scale in
very large systems.
Say Y here to make use of these instructions for the in-kernel
atomic routines. This incurs a small overhead on CPUs that do
not support these instructions and requires the kernel to be
built with binutils >= 2.25 in order for the new instructions
to be used.
Symbol: ARM64_USE_LSE_ATOMICS [=y]
Type : bool
Prompt: Atomic instructions
Location:
-> Kernel Features
-> ARMv8.1 architectural features
Defined at arch/arm64/Kconfig:1397
Depends on: JUMP_LABEL [=y]
---
Cc: Mark Salter <msalter@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Several configurations in ARK and Fedora have changed type (tristate <->
bool) or have started being required by other configured modules. Adjust
the Fedora configurations to match the current Rawhide settings and move
ARK settings that have changed back to pending for review.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
RHEL-8 inherited distgit changelog script from RHEL7-alt, which had a bug that
wouldn't pick all bugzilla numbers from a patch in kernel.spec changelog
section in case it was solving multiple ones, but only the first. With that,
many BZs where not being included in distgit's commit "Resolves:" line checked
by distgit server rules.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
It seems rpmbuild started to complain (warn) about any inline comment in
kernel.spec.template file in new versions, like used in Fedora 31:
warning: extra tokens at the end of %else directive in line 439: %else # released_kernel
...
Place this commentaries before rpmspec real token in a single line, muting the
warnings.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
New versions of awk (i.e. those present in Fedora) started warning about "\ "
not being a regex pattern for whitespaces. Although it still works fine,
upstream may get rid of it soon.
awk: cmd. line:72: warning: regexp escape sequence `\ ' is not a known regexp operator
awk is used in redhat/genspec.sh to generate rpm's changelogs from kernel
source git commits, and the specific file line is responsible to handle
multiline subjects, where it's bigger than 78 chars. Without it working
properly we'll see cropped subjects as changelog lines.
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
This performs a number of refactors to the script that should not impact
behavior. It:
* Resolves all ShellCheck errors and warnings
* Moves cleanup into a function registered with trap
* Simplifies a few expressions to more idiomatic equivalents
* Moves temporary working files out of /tmp/ and into a dedicated
directory created by mktemp.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
This refactors the awk script that sorts new configuration symbols by
subsystem. There were two awkward edge cases.
The first was in the handling of the drivers/{net,net/ethernet} that
failed to strip the trailing ":<linenumber>" from new configuration
symbols in drivers/net/{Kconfig,ethernet/Kconfig}. This led to branch
names that included the ":<linenumber>" which aren't valid branch names
and caused the script to create commits in incorrect branches.
The second edge case was that it replaced "/" with "_" in the filename
it created. The problem with this is that some subsystem directories
have "_" in the name (e.g. net/vmw_vsock) When it turned the filename
back into a kernel tree path it would mangle the name and fail to find
any maintainers for it. The new placeholder character is ":" which is
not currently in any kernel directory name and seems unlikely to appear
in one.
Additionally, there are some changes for readability.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
It was reported that ARK started to fail to build in some build
environments starting with v5.5-rc5 because CONFIG_GCC_PLUGINS was being
changed from unset to y. This is likely due to upstream commit
a5b0dc5a46 ("gcc-plugins: make it possible to disable
CONFIG_GCC_PLUGINS again"), but regardless we want to explicitly set
GGC_PLUGINS one way or the other because it's one of those annoying
Kconfig symbols that depends on the environment you prepare the
configuration in.
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
ARK plans to merge with Fedora and has therefore begun building the
Fedora configuration files.
The current ARK process generates defaults for new configuration options
in the redhat/configs/pending/ directory, and then generates commits
moving these configs to the redhat/configs/common/ directory which are
sent out for review. This is necessary because rebases are largely
automated, there needs to be a place to set defaults for new
configuration options that indicate they need human review.
This is problematic for Fedora because it enables a super-set of
ARK options, which in turn lead to options being exposed during rebases
that are not exposed for ARK. Thus, this adds a
redhat/configs/pending-fedora/ configuration directory where new options
for Fedora rebases are stored. This also renames the current pending/
directory to be pending-common/ in order to make the final destination
of configuration options clearer. Fedora still inherits configuration
options from common/ and pending-common/ so only settings specific to
Fedora are placed here.
There is no pending-ark/ directory at the moment because if, during
review, ARK needs a setting that differs from Fedora, the setting is
changed and manually moved into the ark/ directory.
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_PPC_UV:
This option paravirtualizes the kernel to run in POWER platforms that
supports the Protected Execution Facility (PEF). On such platforms,
the ultravisor firmware runs at a privilege level above the
hypervisor.
If unsure, say "N".
Symbol: PPC_UV [=n]
Type : bool
Prompt: Ultravisor support
Location:
-> Kernel options
Defined at arch/powerpc/Kconfig:455
Depends on: KVM_BOOK3S_HV_POSSIBLE [=y]
Selects: ZONE_DEVICE [=y] && DEV_PAGEMAP_OPS [=y] && DEVICE_PRIVATE [=y] && MEMORY_HOTPLUG [=y] && MEMORY_HOTREMOVE [=y]
---
Cc: Thomas Huth <thuth@redhat.com>
Cc: David Gibson <dgibson@redhat.com>
Cc: Laurent Vivier <lvivier@redhat.com>
In the never-ending slow-motion train wreck that is the Python
ecosystem, we need to explicitly specify Python 3 because the build root
does not have /usr/bin/python which causes the documentation build to
fail. Even if it did, the Python 3 version of Sphinx is being used to
build the documentation so unless /usr/bin/python was Python 3 it'd
still break.
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_FW_CACHE:
Because firmware caching generates uevent messages that are sent
over a netlink socket, it can prevent suspend on many platforms.
It is also not always useful, so on such platforms we have the
option.
If unsure, say Y.
Symbol: FW_CACHE [=y]
Type : bool
Prompt: Enable firmware caching during suspend
Location:
-> Device Drivers
-> Generic Driver Options
-> Firmware loader
-> Firmware loading facility (FW_LOADER [=y])
Defined at drivers/base/firmware_loader/Kconfig:172
Depends on: FW_LOADER [=y] && PM_SLEEP [=y]
---
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
We weren't building with these flags because thing were broken for a while.
It's now fixed so let's pick it up.
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
Add the intel-speed-select utility to the x86 kernel-tools rpm.
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
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_PINCTRL_EQUILIBRIUM:
Equilibrium pinctrl driver is a pinctrl & GPIO driver for Intel Lightning
Mountain network processor SoC that supports both the linux GPIO and pin
control frameworks. It provides interfaces to setup pinmux, assign desired
pin functions, configure GPIO attributes for LGM SoC pins. Pinmux and
pinconf settings are retrieved from device tree.
Symbol: PINCTRL_EQUILIBRIUM [=n]
Type : tristate
Prompt: Generic pinctrl and GPIO driver for Intel Lightning Mountain SoC
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Defined at drivers/pinctrl/Kconfig:423
Depends on: PINCTRL [=y]
Selects: PINMUX [=y] && PINCONF [=y] && GPIOLIB [=y] && GPIO_GENERIC [=m] && GPIOLIB_IRQCHIP [=y] && GENERIC_PINCONF [=y] && GENERIC_PINCTRL_GROUPS [=n] && GENERIC_PINMUX_FUNCTIONS [=n]
---
CONFIG_PINCTRL_MSM8976:
This is the pinctrl, pinmux, pinconf and gpiolib driver for the
Qualcomm TLMM block found on the Qualcomm MSM8976 platform.
The Qualcomm MSM8956, APQ8056, APQ8076 platforms are also
supported by this driver.
Symbol: PINCTRL_MSM8976 [=n]
Type : tristate
Prompt: Qualcomm 8976 pin controller driver
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Defined at drivers/pinctrl/qcom/Kconfig:93
Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
Selects: PINCTRL_MSM [=y]
---
CONFIG_PINCTRL_TIGERLAKE:
This pinctrl driver provides an interface that allows configuring
of Intel Tiger Lake PCH pins and using them as GPIOs.
Symbol: PINCTRL_TIGERLAKE [=n]
Type : tristate
Prompt: Intel Tiger Lake pinctrl and GPIO driver
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Defined at drivers/pinctrl/intel/Kconfig:118
Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
Selects: PINCTRL_INTEL [=m]
---
Cc: John W. Linville <linville@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
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_KASAN_VMALLOC:
By default, the shadow region for vmalloc space is the read-only
zero page. This means that KASAN cannot detect errors involving
vmalloc space.
Enabling this option will hook in to vmap/vmalloc and back those
mappings with real shadow memory allocated on demand. This allows
for KASAN to detect more sorts of errors (and to support vmapped
stacks), but at the cost of higher memory usage.
Symbol: KASAN_VMALLOC [=n]
Type : bool
Prompt: Back mappings in vmalloc space with real shadow memory
Location:
-> Kernel hacking
-> Memory Debugging
Defined at lib/Kconfig.kasan:148
Depends on: KASAN [=y] && HAVE_ARCH_KASAN_VMALLOC [=y]
---
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Laura Abbott <labbott@redhat.com>
Cc: Marcelo Ricardo Leitner <mleitner@redhat.com>
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_S390_UNWIND_SELFTEST:
This option enables s390 specific stack unwinder testing kernel
module. This option is not useful for distributions or general
kernels, but only for kernel developers working on architecture code.
Say N if you are unsure.
Symbol: S390_UNWIND_SELFTEST [=n]
Type : tristate
Prompt: Test unwind functions
Location:
-> Selftests
Defined at arch/s390/Kconfig:1022
---
Cc: Thomas Huth <thuth@redhat.com>
Bugzilla: INTERNAL
Upstream: RHEL only
When I introduced rh-srpm-gcov target I missed that with_gcov macro
will pass extra white space to make:
make -s ARCH=x86_64 V=1 -j8 KCFLAGS= 'WITH_GCOV= 1 ' bzImage
which can break ifeq/ifneq conditions.
ARK is currently not making use of this flag, but for sake of consistency,
mirror the change from RHEL.
Signed-off-by: Jan Stancek <jstancek@redhat.com>
This is a manual import of a patch that got horribly mangled in
Patchwork. The original commit message is below:
Message-id: <20191115130108.257757-1-omosnace@redhat.com>
Patchwork-id: 287415
O-Subject: [ARK INTERNAL PATCH] configs: Enable CONFIG_KEY_DH_OPERATIONS on ARK
Bugzilla:
RH-Acked-by: Herbert Xu <herbert.xu@redhat.com>
RH-Acked-by: Neil Horman <nhorman@redhat.com>
Bugzilla: INTERNAL
Upstream status: RHEL only
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=24725630
Tested: booted on x86_64 and selinux-testuite "keys" subtest now passes
We need CONFIG_KEY_DH_OPERATIONS enabled on ARK for testing SELinux.
Fedora already enables it, so just move the config to common.
We also need to make CONFIG_CRYPTO_DH builtin now on all arches. Again
just adopt the config from Fedora.
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_AD7292:
Say yes here to build support for Analog Devices AD7292
8 Channel ADC with temperature sensor.
To compile this driver as a module, choose M here: the
module will be called ad7292.
Symbol: AD7292 [=n]
Type : tristate
Prompt: Analog Devices AD7292 ADC driver
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Analog to digital converters
Defined at drivers/iio/adc/Kconfig:58
Depends on: IIO [=m] && SPI [=y]
---
CONFIG_ADUX1020:
Say Y here if you want to build a driver for the Analog Devices
ADUX1020 photometric sensor.
To compile this driver as a module, choose M here: the
module will be called adux1020.
Symbol: ADUX1020 [=n]
Type : tristate
Prompt: ADUX1020 photometric sensor
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Light sensors
Defined at drivers/iio/light/Kconfig:35
Depends on: IIO [=m] && I2C [=y]
Selects: REGMAP_I2C [=y]
---
CONFIG_FXOS8700_I2C:
Say yes here to build support for the NXP FXOS8700 m+g combo
sensor on I2C.
This driver can also be built as a module. If so, the module will be
called fxos8700_i2c.
Symbol: FXOS8700_I2C [=n]
Type : tristate
Prompt: NXP FXOS8700 I2C driver
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Inertial measurement units
Defined at drivers/iio/imu/Kconfig:46
Depends on: IIO [=m] && I2C [=y]
Selects: FXOS8700 [=n] && REGMAP_I2C [=y]
---
CONFIG_FXOS8700_SPI:
Say yes here to build support for the NXP FXOS8700 m+g combo
sensor on SPI.
This driver can also be built as a module. If so, the module will be
called fxos8700_spi.
Symbol: FXOS8700_SPI [=n]
Type : tristate
Prompt: NXP FXOS8700 SPI driver
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Inertial measurement units
Defined at drivers/iio/imu/Kconfig:58
Depends on: IIO [=m] && SPI [=y]
Selects: FXOS8700 [=n] && REGMAP_SPI [=y]
---
CONFIG_LTC2983:
Say yes here to build support for the LTC2983 Multi-Sensor
high accuracy digital temperature measurement system.
To compile this driver as a module, choose M here: the module
will be called ltc2983.
Symbol: LTC2983 [=n]
Type : tristate
Prompt: Analog Devices Multi-Sensor Digital Temperature Measurement System
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Temperature sensors
Defined at drivers/iio/temperature/Kconfig:7
Depends on: IIO [=m] && SPI [=y]
Selects: REGMAP_SPI [=y]
---
CONFIG_VEML6030:
Say Y here if you want to build a driver for the Vishay VEML6030
ambient light sensor (ALS).
To compile this driver as a module, choose M here: the
module will be called veml6030.
Symbol: VEML6030 [=n]
Type : tristate
Prompt: VEML6030 ambient light sensor
Location:
-> Device Drivers
-> Industrial I/O support (IIO [=m])
-> Light sensors
Defined at drivers/iio/light/Kconfig:510
Depends on: IIO [=m] && I2C [=y]
Selects: REGMAP_I2C [=y]
---
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_GPIO_BCM_XGS_IPROC:
Say yes here to enable GPIO support for Broadcom XGS iProc SoCs.
Symbol: GPIO_BCM_XGS_IPROC [=y]
Type : tristate
Prompt: BRCM XGS iProc GPIO support
Location:
-> Device Drivers
-> GPIO Support (GPIOLIB [=y])
-> Memory mapped GPIO drivers
Defined at drivers/gpio/Kconfig:158
Depends on: GPIOLIB [=y] && HAS_IOMEM [=y] && OF_GPIO [=y] && (ARCH_BCM_IPROC [=y] || COMPILE_TEST [=n])
Selects: GPIO_GENERIC [=y] && GPIOLIB_IRQCHIP [=y]
---
Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
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_CRYPTO_LIB_BLAKE2S:
Enable the Blake2s library interface. This interface may be fulfilled
by either the generic implementation or an arch-specific one, if one
is available and enabled.
Symbol: CRYPTO_LIB_BLAKE2S [=n]
Type : tristate
Prompt: BLAKE2s hash function library
Location:
-> Cryptographic API (CRYPTO [=y])
Defined at lib/crypto/Kconfig:27
Depends on: CRYPTO [=y] && (CRYPTO_ARCH_HAVE_LIB_BLAKE2S [=n] || !CRYPTO_ARCH_HAVE_LIB_BLAKE2S [=n])
Selects: CRYPTO_LIB_BLAKE2S_GENERIC [=n]
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_HW_RANDOM_HISI_V2:
This driver provides kernel-side support for the True Random Number
Generator V2 hardware found on HiSilicon Hi1620 SoC.
To compile this driver as a module, choose M here: the
module will be called hisi-trng-v2.
If unsure, say Y.
Symbol: HW_RANDOM_HISI_V2 [=y]
Type : tristate
Prompt: HiSilicon True Random Number Generator V2 support
Location:
-> Device Drivers
-> Character devices
-> Hardware Random Number Generator Core support (HW_RANDOM [=y])
Defined at drivers/char/hw_random/Kconfig:311
Depends on: HW_RANDOM [=y] && ARM64 [=y] && ACPI [=y]
Fedora Rawhide has this turned on as a module and it is being
automatically selected based on the current Fedora configuration. This
fixes the build failure CI detected.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
The various header testing options (e.g. CONFIG_KERNEL_HEADER_TEST)
generate stray *.s files as part of the testing. We want to be
running these tests but we don't actually care about the files.
Make sure these files get cleaned up so they don't end up packaged
and causing an excessively big kernel-devel.
Signed-off-by: Laura Abbott <labbott@redhat.com>
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_COMPAT_32BIT_TIME:
This enables 32 bit time_t support in addition to 64 bit time_t support.
This is relevant on all 32-bit architectures, and 64-bit architectures
as part of compat syscall handling.
Symbol: COMPAT_32BIT_TIME [=y]
Type : bool
Prompt: Provide system calls for 32-bit time_t
Location:
-> General architecture-dependent options
Defined at arch/Kconfig:799
---
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_S32:
This enables support for the NXP S32 family of processors.
Symbol: ARCH_S32 [=n]
Type : bool
Prompt: NXP S32 SoC Family
Location:
-> Platform selection
Defined at arch/arm64/Kconfig.platforms:217
---
Cc: Mark Salter <msalter@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
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_X86_IOPL_IOPERM:
This enables the ioperm() and iopl() syscalls which are necessary
for legacy applications.
Legacy IOPL support is an overbroad mechanism which allows user
space aside of accessing all 65536 I/O ports also to disable
interrupts. To gain this access the caller needs CAP_SYS_RAWIO
capabilities and permission from potentially active security
modules.
The emulation restricts the functionality of the syscall to
only allowing the full range I/O port access, but prevents the
ability to disable interrupts from user space which would be
granted if the hardware IOPL mechanism would be used.
Symbol: X86_IOPL_IOPERM [=y]
Type : bool
Prompt: IOPERM and IOPL Emulation
Location:
-> Processor type and features
Defined at arch/x86/Kconfig:1227
---
Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
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_DEV_DAX_HMEM:
EFI 2.8 platforms, and others, may advertise 'specific purpose'
memory. For example, a high bandwidth memory pool. The
indication from platform firmware is meant to reserve the
memory from typical usage by default. This driver creates
device-dax instances for these memory ranges, and that also
enables the possibility to assign them to the DEV_DAX_KMEM
driver to override the reservation and add them to kernel
"System RAM" pool.
Say M if unsure.
Symbol: DEV_DAX_HMEM [=m]
Type : tristate
Prompt: HMEM DAX: direct access to 'specific purpose' memory
Location:
-> Device Drivers
-> DAX: direct access to differentiated memory (DAX [=y])
Defined at drivers/dax/Kconfig:35
Depends on: DAX [=y] && EFI_SOFT_RESERVE [=y]
---
Cc: Jeff Moyer <jmoyer@redhat.com>
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_SF_PDMA:
Support the SiFive PDMA controller.
Symbol: SF_PDMA [=n]
Type : tristate
Prompt: Sifive PDMA controller driver
Location:
-> Device Drivers
-> DMA Engine support (DMADEVICES [=y])
Defined at drivers/dma/sf-pdma/Kconfig:1
Depends on: DMADEVICES [=y]
Selects: DMA_ENGINE [=y] && DMA_VIRTUAL_CHANNELS [=y]
---
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_EFI_SOFT_RESERVE:
On systems that have mixed performance classes of memory EFI
may indicate specific purpose memory with an attribute (See
EFI_MEMORY_SP in UEFI 2.8). A memory range tagged with this
attribute may have unique performance characteristics compared
to the system's general purpose "System RAM" pool. On the
expectation that such memory has application specific usage,
and its base EFI memory type is "conventional" answer Y to
arrange for the kernel to reserve it as a "Soft Reserved"
resource, and set aside for direct-access (device-dax) by
default. The memory range can later be optionally assigned to
the page allocator by system administrator policy via the
device-dax kmem facility. Say N to have the kernel treat this
memory as "System RAM" by default.
If unsure, say Y.
Symbol: EFI_SOFT_RESERVE [=y]
Type : bool
Prompt: Reserve EFI Specific Purpose Memory
Location:
-> Firmware Drivers
-> EFI (Extensible Firmware Interface) Support
Defined at drivers/firmware/efi/Kconfig:78
Depends on: EFI [=y] && EFI_STUB [=y] && ACPI_HMAT [=y]
---
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_DRM_AMD_DC_HDCP:
Choose this option
if you want to support
HDCP authentication
Symbol: DRM_AMD_DC_HDCP [=n]
Type : bool
Prompt: Enable HDCP support in DC
Location:
-> Device Drivers
-> Graphics support
-> Display Engine Configuration
Defined at drivers/gpu/drm/amd/display/Kconfig:47
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_AMDGPU [=m] && DRM_AMD_DC [=y]
---
Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Rob Clark <rclark@redhat.com>
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_SENSORS_BEL_PFE:
If you say yes here you get hardware monitoring support for BEL
PFE1100 and PFE3000 Power Supplies.
This driver can also be built as a module. If so, the module will
be called bel-pfe.
Symbol: SENSORS_BEL_PFE [=n]
Type : tristate
Prompt: Bel PFE Compatible Power Supplies
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
Defined at drivers/hwmon/pmbus/Kconfig:39
Depends on: HWMON [=y] && PMBUS [=m]
---
CONFIG_SENSORS_LTC2947_I2C:
If you say yes here you get support for Linear Technology LTC2947
I2C High Precision Power and Energy Monitor
This driver can also be built as a module. If so, the module will
be called ltc2947-i2c.
Symbol: SENSORS_LTC2947_I2C [=n]
Type : tristate
Prompt: Analog Devices LTC2947 High Precision Power and Energy Monitor over I2C
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
Defined at drivers/hwmon/Kconfig:733
Depends on: HWMON [=y] && I2C [=y]
Selects: REGMAP_I2C [=y] && SENSORS_LTC2947 [=n]
---
CONFIG_SENSORS_LTC2947_SPI:
If you say yes here you get support for Linear Technology LTC2947
SPI High Precision Power and Energy Monitor
This driver can also be built as a module. If so, the module will
be called ltc2947-spi.
Symbol: SENSORS_LTC2947_SPI [=n]
Type : tristate
Prompt: Analog Devices LTC2947 High Precision Power and Energy Monitor over SPI
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
Defined at drivers/hwmon/Kconfig:745
Depends on: HWMON [=y] && SPI_MASTER [=y]
Selects: REGMAP_SPI [=y] && SENSORS_LTC2947 [=n]
---
CONFIG_SENSORS_TMP513:
If you say yes here you get support for Texas Instruments TMP512,
and TMP513 temperature and power supply sensor chips.
This driver can also be built as a module. If so, the module
will be called tmp513.
Symbol: SENSORS_TMP513 [=n]
Type : tristate
Prompt: Texas Instruments TMP513 and compatibles
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
Defined at drivers/hwmon/Kconfig:1739
Depends on: HWMON [=y] && I2C [=y]
---
Cc: Dean Nelson <dnelson@redhat.com>
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_LEDS_EL15203000:
This option enables support for EL15203000 LED Board
(aka RED LED board) which is widely used in coffee vending
machines produced by Crane Merchandising Systems.
To compile this driver as a module, choose M here: the module
will be called leds-el15203000.
Symbol: LEDS_EL15203000 [=n]
Type : tristate
Prompt: LED Support for Crane EL15203000
Location:
-> Device Drivers
-> LED Support (NEW_LEDS [=y])
Defined at drivers/leds/Kconfig:135
Depends on: NEW_LEDS [=y] && LEDS_CLASS [=y] && SPI [=y] && OF [=y]
---
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_MMC_SDHCI_MILBEAUT:
This selects the Secure Digital Host Controller Interface (SDHCI)
Needed by Milbeaut SoC for MMC / SD / SDIO support.
If you have a controller with this interface, say Y or M here.
If unsure, say N.
Symbol: MMC_SDHCI_MILBEAUT [=n]
Type : tristate
Prompt: SDHCI support for Socionext Milbeaut Serieas using F_SDH30
Location:
-> Device Drivers
-> MMC/SD/SDIO card support (MMC [=m])
Defined at drivers/mmc/host/Kconfig:372
Depends on: MMC [=m] && MMC_SDHCI_PLTFM [=m] && OF [=y]
---
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_PCIE_CADENCE_PLAT_HOST:
Say Y here if you want to support the Cadence PCIe platform controller in
host mode. This PCIe controller may be embedded into many different
vendors SoCs.
Symbol: PCIE_CADENCE_PLAT_HOST [=n]
Type : bool
Prompt: Cadence PCIe platform host controller
Location:
-> Device Drivers
-> PCI support (PCI [=y])
-> PCI controller drivers
-> Cadence PCIe controllers support
Defined at drivers/pci/controller/cadence/Kconfig:24
Depends on: PCI [=y] && OF [=y]
Selects: PCIE_CADENCE_HOST [=n] && PCIE_CADENCE_PLAT [=n]
---
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
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_MLXBF_BOOTCTL:
The Mellanox BlueField firmware implements functionality to
request swapping the primary and alternate eMMC boot partition,
and to set up a watchdog that can undo that swap if the system
does not boot up correctly. This driver provides sysfs access
to the userspace tools, to be used in conjunction with the eMMC
device driver to do necessary initial swap of the boot partition.
Symbol: MLXBF_BOOTCTL [=n]
Type : tristate
Prompt: Mellanox BlueField Firmware Boot Control driver
Location:
-> Device Drivers
-> Platform support for Mellanox hardware (MELLANOX_PLATFORM [=y])
Defined at drivers/platform/mellanox/Kconfig:47
Depends on: MELLANOX_PLATFORM [=y] && ARM64 [=y] && ACPI [=y]
---
CONFIG_SYSTEM76_ACPI:
This is a driver for System76 laptops running open firmware. It adds
support for Fn-Fx key combinations, keyboard backlight, and airplane mode
LEDs.
If you have a System76 laptop running open firmware, say Y or M here.
Symbol: SYSTEM76_ACPI [=n]
Type : tristate
Prompt: System76 ACPI Driver
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
Defined at drivers/platform/x86/Kconfig:1342
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y]
Selects: NEW_LEDS [=y] && LEDS_CLASS [=y] && LEDS_TRIGGERS [=y]
---
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_FSL_RCPM:
The NXP QorIQ Processors based on ARM Core have RCPM module
(Run Control and Power Management), which performs all device-level
tasks associated with power management, such as wakeup source control.
Note that currently this driver will not support PowerPC based
QorIQ processor.
Symbol: FSL_RCPM [=n]
Type : bool
Prompt: Freescale RCPM support
Location:
-> Device Drivers
-> SOC (System On Chip) specific Drivers
-> NXP/Freescale QorIQ SoC drivers
Defined at drivers/soc/fsl/Kconfig:44
Depends on: PM_SLEEP [=y] && (ARM || ARM64 [=y])
---
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_TYPEC_HD3SS3220:
Say Y or M here if your system has TI HD3SS3220 Type-C DRP Port
controller driver.
If you choose to build this driver as a dynamically linked module, the
module will be called hd3ss3220.ko.
Symbol: TYPEC_HD3SS3220 [=n]
Type : tristate
Prompt: TI HD3SS3220 Type-C DRP Port controller driver
Location:
-> Device Drivers
-> USB support (USB_SUPPORT [=y])
-> USB Type-C Support (TYPEC [=y])
Defined at drivers/usb/typec/Kconfig:53
Depends on: USB_SUPPORT [=y] && TYPEC [=y] && I2C [=y] && USB_ROLE_SWITCH [=m]
---
Cc: Torez Smith <torez@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
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_BACKLIGHT_QCOM_WLED:
If you have the Qualcomm PMIC, say Y to enable a driver for the
WLED block. Currently it supports PM8941 and PMI8998.
Symbol: BACKLIGHT_QCOM_WLED [=n]
Type : tristate
Prompt: Qualcomm PMIC WLED Driver
Location:
-> Device Drivers
-> Graphics support
-> Backlight & LCD device support
-> Lowlevel Backlight controls (BACKLIGHT_CLASS_DEVICE [=y])
Defined at drivers/video/backlight/Kconfig:285
Depends on: HAS_IOMEM [=y] && BACKLIGHT_CLASS_DEVICE [=y]
Selects: REGMAP [=y]
---
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_HYPERV_TESTING:
Select this option to enable Hyper-V vmbus testing.
Symbol: HYPERV_TESTING [=n]
Type : bool
Prompt: Microsoft Hyper-V driver testing
Location:
-> Kernel hacking
Defined at lib/Kconfig.debug:2159
Depends on: HYPERV [=m] && DEBUG_FS [=y]
---
Building the SRPM finds more errors than just building the configs
(which finds unset values) such as configurations that switch values,
missing files, etc.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_TLS_TOE:
Enable kernel support for legacy HW offload of the TLS protocol,
which is incompatible with the Linux networking stack semantics.
If unsure, say N.
Symbol: TLS_TOE [=n]
Type : bool
Prompt: Transport Layer Security TCP stack bypass
Location:
-> Networking support (NET [=y])
-> Networking options
-> Transport Layer Security support (TLS [=m])
Defined at net/tls/Kconfig:30
Depends on: NET [=y] && TLS [=m]
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_TIPC_CRYPTO:
Saying Y here will enable support for TIPC encryption.
All TIPC messages will be encrypted/decrypted by using the currently most
advanced algorithm: AEAD AES-GCM (like IPSec or TLS) before leaving/
entering the TIPC stack.
Key setting from user-space is performed via netlink by a user program
(e.g. the iproute2 'tipc' tool).
Symbol: TIPC_CRYPTO [=y]
Type : bool
Prompt: TIPC encryption support
Location:
-> Networking support (NET [=y])
-> Networking options
-> The TIPC Protocol (TIPC [=m])
Defined at net/tipc/Kconfig:38
Depends on: NET [=y] && TIPC [=m]
Selects: CRYPTO [=y] && CRYPTO_AES [=y] && CRYPTO_GCM [=y]
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_KUNIT:
Enables support for kernel unit tests (KUnit), a lightweight unit
testing and mocking framework for the Linux kernel. These tests are
able to be run locally on a developer's workstation without a VM or
special hardware when using UML. Can also be used on most other
architectures. For more information, please see
Documentation/dev-tools/kunit/.
Symbol: KUNIT [=n]
Type : bool
Prompt: KUnit - Enable support for unit tests
Location:
-> Kernel hacking
Defined at lib/kunit/Kconfig:5
We missed adding the release keys for a the released_kernel case.
Add them as well as fixing up a duplicate Source numbering.
Signed-off-by: Laura Abbott <labbott@redhat.com>
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_SYMBOLIC_ERRNAME:
If you say Y here, the kernel's printf implementation will
be able to print symbolic error names such as ENOSPC instead
of the number 28. It makes the kernel image slightly larger
(about 3KB), but can make the kernel logs easier to read.
Symbol: SYMBOLIC_ERRNAME [=y]
Type : bool
Prompt: Support symbolic error names in printf
Location:
-> Kernel hacking
-> printk and dmesg options
Defined at lib/Kconfig.debug:167
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_X86_INTEL_TSX_MODE_OFF:
TSX is disabled if possible - equals to tsx=off command line parameter.
Symbol: X86_INTEL_TSX_MODE_OFF [=y]
Type : bool
Prompt: off
Location:
-> Processor type and features
-> TSX enable mode (<choice> [=y])
Defined at arch/x86/Kconfig:1970
Depends on: <choice>
---
CONFIG_X86_INTEL_TSX_MODE_ON:
TSX is always enabled on TSX capable HW - equals the tsx=on command
line parameter.
Symbol: X86_INTEL_TSX_MODE_ON [=n]
Type : bool
Prompt: on
Location:
-> Processor type and features
-> TSX enable mode (<choice> [=y])
Defined at arch/x86/Kconfig:1975
Depends on: <choice>
---
CONFIG_X86_INTEL_TSX_MODE_AUTO:
TSX is enabled on TSX capable HW that is believed to be safe against
side channel attacks- equals the tsx=auto command line parameter.
Symbol: X86_INTEL_TSX_MODE_AUTO [=n]
Type : bool
Prompt: auto
Location:
-> Processor type and features
-> TSX enable mode (<choice> [=y])
Defined at arch/x86/Kconfig:1981
Depends on: <choice>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
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_PTP_1588_CLOCK_IDTCM:
This driver adds support for using IDT CLOCKMATRIX(TM) as a PTP
clock. This clock is only useful if your time stamping MAC
is connected to the IDT chip.
To compile this driver as a module, choose M here: the module
will be called ptp_clockmatrix.
Symbol: PTP_1588_CLOCK_IDTCM [=n]
Type : tristate
Prompt: IDT CLOCKMATRIX as PTP clock
Location:
-> Device Drivers
-> PTP clock support
Defined at drivers/ptp/Kconfig:122
Depends on: PTP_1588_CLOCK [=y]
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_NVME_HWMON:
This provides support for NVMe hardware monitoring. If enabled,
a hardware monitoring device will be created for each NVMe drive
in the system.
If unsure, say N.
Symbol: NVME_HWMON [=n]
Type : bool
Prompt: NVMe hardware monitoring
Location:
-> Device Drivers
-> NVME Support
Defined at drivers/nvme/host/Kconfig:26
Depends on: NVME_CORE [=m]=y && HWMON [=y]=y || NVME_CORE [=m]=m && HWMON [=y]
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_DP83869_PHY:
Currently supports the DP83869 PHY. This PHY supports copper and
fiber connections.
Symbol: DP83869_PHY [=n]
Type : tristate
Prompt: Texas Instruments DP83869 Gigabit PHY
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> PHY Device support and infrastructure (PHYLIB [=y])
Defined at drivers/net/phy/Kconfig:362
Depends on: NETDEVICES [=y] && PHYLIB [=y]
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_ARM64_ERRATUM_1319367:
This option adds work arounds for ARM Cortex-A57 erratum 1319537
and A72 erratum 1319367
Cortex-A57 and A72 cores could end-up with corrupted TLBs by
speculating an AT instruction during a guest context switch.
If unsure, say Y.
Symbol: ARM64_ERRATUM_1319367 [=y]
Type : bool
Prompt: Cortex-A57/A72: Speculative AT instruction using out-of-context translation regime could cause subsequent request to generate an incorrect translation
Location:
-> Kernel Features
-> ARM errata workarounds via the alternatives framework
Defined at arch/arm64/Kconfig:547
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_CRYPTO_DEV_AMLOGIC_GXL:
Select y here to have support for the cryptographic offloader
available on Amlogic GXL SoC.
This hardware handles AES ciphers in ECB/CBC mode.
To compile this driver as a module, choose M here: the module
will be called amlogic-gxl-crypto.
Symbol: CRYPTO_DEV_AMLOGIC_GXL [=n]
Type : tristate
Prompt: Support for amlogic cryptographic offloader
Location:
-> Cryptographic API (CRYPTO [=y])
-> Hardware crypto devices (CRYPTO_HW [=y])
Defined at drivers/crypto/amlogic/Kconfig:1
Depends on: CRYPTO [=y] && CRYPTO_HW [=y]
Selects: CRYPTO_SKCIPHER [=y] && CRYPTO_ENGINE [=n] && CRYPTO_ECB [=y] && CRYPTO_CBC [=y] && CRYPTO_AES [=y]
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_CRYPTO_BLAKE2B:
Implementation of cryptographic hash function BLAKE2b (or just BLAKE2),
optimized for 64bit platforms and can produce digests of any size
between 1 to 64. The keyed hash is also implemented.
This module provides the following algorithms:
- blake2b-160
- blake2b-256
- blake2b-384
- blake2b-512
See https://blake2.net for further information.
Symbol: CRYPTO_BLAKE2B [=n]
Type : tristate
Prompt: BLAKE2b digest algorithm
Location:
-> Cryptographic API (CRYPTO [=y])
Defined at crypto/Kconfig:653
Depends on: CRYPTO [=y]
Selects: CRYPTO_HASH [=y]
Emailing the automated changelog generation patch to a list would be
pointless so mark the merge request as ignored.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Upstream added a dependency on an s390x compiler in the configuration
environment. Adjust the config to not break when prepped on x86 until
upstream discusses what to do.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
This alters the CI job that checks that the configuration is valid to
only trigger when a merge request is made or a push to
internal occurs.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190917154218.29293-1-prarit@redhat.com>
Patchwork-id: 272312
O-Subject: [ARK INTERNAL] redhat/scripts: Remove redhat/scripts/rh_get_maintainer.pl
Bugzilla:
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
rh_get_maintainer.pl is a lightly modified version of get_maintainer.pl
from 3.10.0-ish. The script should be dropped in favor of using
the upstream version, and also dropped from being forward ported.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Laura Abbott <labbott@redhat.com>
Cc: Jeremy Cline <jcline@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Phillip Lougher <plougher@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: "Bruno E. O. Meneguele" <bmeneg@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191121190831.8942-1-labbott@redhat.com>
Patchwork-id: 287873
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: Take CONFIG_DEFAULT_MMAP_MIN_ADDR from Fedra
Bugzilla:
RH-Acked-by: Rafael Aquini <aquini@redhat.com>
Fedora has had a bigger CONFIG_DEFAULT_MMAP_MIN_ADDR value for
a number of years now. Use the suggested values in the help text
for arm and x86_64.
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
Cc: Larry Woodman <lwoodman@redhat.com>
Cc: Rafael Aquini <aquini@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
---
This is exactly what Fedora was using although I realize this doesn't
include powerpc or s390x.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191121191829.30226-1-labbott@redhat.com>
Patchwork-id: 287874
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: Turn off ISDN
Bugzilla:
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: John Linville <linville@redhat.com>
This is slowly going away upstream. Nobody seems to want it so just
turn it off.
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: John W. Linville <linville@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
---
I know we're still waiting to hear back from the BU but if there's
general agreement this is what we want let's just turn it off. It's
really cheap to turn it back on later.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
After generating an initial set of commits in the pending directory,
we need to split that out into individual commits for review. Add
a script to do so. This script is designed to be run from the
root of the kernel tree so we can run get_maintainers.pl if the
appropriate maintainers file is available.
Signed-off-by: Laura Abbott <labbott@redhat.com>
One of the tasks that comes with maintaining ARK is dealing with new
configuration options that come in. We need to set an initial value
for building a kernel and then allow for a final review of the options.
This has been managed by out of tree scripts for a while but to make
automation easier, bring part of this in tree.
Introduce the rh-configs-commit make target. This runs 'make helpnewconfig'
(like listnewconfig execpt it shows the help text) and puts all
the new configuration options in the pending directory. Moving those
options out of the pending directory will be a separate step.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Message-id: <20191120193123.19432-1-labbott@redhat.com>
Patchwork-id: 287796
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: Enable CONFIG_DEBUG_WX
Bugzilla:
RH-Acked-by: Rafael Aquini <aquini@redhat.com>
The purpose of CONFIG_DEBUG_WX is to check for pages that are both
writable and executable. This is a one time check that happens at
bootup. Given this is an important check to catch either bad patches
or occasionally bad firmware, enable this on all arches.
Signed-off-by: Laura Abbott <labbott@redhat.com>
---
This is an option that's been on in Fedora without a problem. It
has definitely caught problems in the past. Given it's a onetime
cost, I think it would be safe to keep on but I also don't know
if it's been evaluated on large memory systems since it does
walk all mapped pages.
As a counter proposal, it might be appropriate for the debug
kernel.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191120162742.14094-1-labbott@redhat.com>
Patchwork-id: 287792
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: Disable wireless USB
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>
Fedora disabled this earlier this year because it's being
deprecated (and hardware doesn't actually exist):
commit 559debe56a8b286d8484b0b45e910ca5592ce6ad
Author: Peter Robinson <pbrobinson@gmail.com>
Date: Sun Jun 16 11:59:22 2019 +0100
disable WUSB (Wireless USB) as HW doesn't exist
It's soon to move to staging in preparation for removal:
https://www.spinics.net/lists/linux-crypto/msg39327.html
Upstream is still telling people not to bother fixing issues
so let's just turn it off.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191119210034.4019-1-labbott@redhat.com>
Patchwork-id: 287761
O-Subject: [ARK INTERNAL PATCHv2] [redhat] Clean up some temporary config files
Bugzilla:
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Don Zickus <dzickus@redhat.com>
As part of running process_configs.sh, we generate some temporary files
for processing. If we find an error somewhere (unset configs, mismatch),
the temporary files don't get cleaned up. Make sure these do get removed.
Signed-off-by: Laura Abbott <labbott@redhat.com>
---
v2: Use a single rm call instead of multiple
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191113152525.107866-1-jcline@redhat.com>
Patchwork-id: 286082
O-Subject: [ARK INTERNAL PATCHv2] configs: New config in drivers/gpu for v5.4-rc1
Bugzilla:
RH-Acked-by: Dave Airlie <airlied@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/gpu/drm/amd/display/Kconfig (help): DRM_AMD_DC_DCN2_1 (bool)
Choose this option if you want to have
Renoir support for display engine
* drivers/gpu/drm/tiny/Kconfig (help): DRM_GM12U320 (tristate)
This is a KMS driver for projectors which use the GM12U320 chipset
for video transfer over USB2/3, such as the Acer C120 mini projector.
* drivers/gpu/drm/panel/Kconfig (help): DRM_PANEL_LG_LB035Q02 (tristate)
Say Y here if you want to enable support for the LB035Q02 RGB panel
(found on the Gumstix Overo Palo35 board). To compile this driver as
a module, choose M here.
* drivers/gpu/drm/panel/Kconfig (help): DRM_PANEL_NEC_NL8048HL11 (tristate)
Say Y here if you want to enable support for the NEC NL8048HL11 RGB
panel (found on the Zoom2/3/3630 SDP boards). To compile this driver
as a module, choose M here.
* drivers/gpu/drm/panel/Kconfig (help): DRM_PANEL_NOVATEK_NT39016 (tristate)
Say Y here if you want to enable support for the panels built
around the Novatek NT39016 display controller.
* drivers/gpu/drm/panel/Kconfig (help): DRM_PANEL_SONY_ACX565AKM (tristate)
Say Y here if you want to enable support for the Sony ACX565AKM
800x600 3.5" panel (found on the Nokia N900).
* drivers/gpu/drm/panel/Kconfig (help): DRM_PANEL_TPO_TD028TTEC1 (tristate)
Say Y here if you want to enable support for TPO TD028TTEC1 480x640
2.8" panel (found on the OpenMoko Neo FreeRunner and Neo 1973).
* drivers/gpu/drm/tiny/Kconfig (help): TINYDRM_HX8357D (tristate)
DRM driver for the following HX8357D panels:
* YX350HV15-T 3.5" 340x350 TFT (Adafruit 3.5")
If M is selected the module will be called hx8357d.
* drivers/gpu/drm/tiny/Kconfig (help): TINYDRM_ILI9225 (tristate)
DRM driver for the following Ilitek ILI9225 panels:
* No-name 2.2" color screen module
If M is selected the module will be called ili9225.
* drivers/gpu/drm/tiny/Kconfig (help): TINYDRM_ILI9341 (tristate)
DRM driver for the following Ilitek ILI9341 panels:
* YX240QV29-T 2.4" 240x320 TFT (Adafruit 2.4")
If M is selected the module will be called ili9341.
* drivers/gpu/drm/tiny/Kconfig (help): TINYDRM_MI0283QT (tristate)
DRM driver for the Multi-Inno MI0283QT display panel
If M is selected the module will be called mi0283qt.
* drivers/gpu/drm/tiny/Kconfig (help): TINYDRM_REPAPER (tristate)
DRM driver for the following Pervasive Displays panels:
1.44" TFT EPD Panel (E1144CS021)
1.90" TFT EPD Panel (E1190CS021)
2.00" TFT EPD Panel (E2200CS021)
2.71" TFT EPD Panel (E2271CS021)
If M is selected the module will be called repaper.
* drivers/gpu/drm/tiny/Kconfig (help): TINYDRM_ST7586 (tristate)
DRM driver for the following Sitronix ST7586 panels:
* LEGO MINDSTORMS EV3
If M is selected the module will be called st7586.
* drivers/gpu/drm/tiny/Kconfig (help): TINYDRM_ST7735R (tristate)
DRM driver Sitronix ST7735R with one of the following LCDs:
* JD-T18003-T01 1.8" 128x160 TFT
If M is selected the module will be called st7735r.
Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
---
Changes in v2:
- DRM_GM12U320 is now m
- DRM_AMD_DC_DCN2_1 is y for x86
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191021163940.28422-1-jcline@redhat.com>
Patchwork-id: 280558
O-Subject: [ARK INTERNAL PATCHv2] configs: New config in arch/powerpc for v5.4-rc1
Bugzilla:
RH-Acked-by: Steve Best <sbest@redhat.com>
RH-Acked-by: Laurent Vivier <lvivier@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* arch/powerpc/platforms/pseries/Kconfig (help): PPC_SVM (bool)
There are certain POWER platforms which support secure guests using
the Protected Execution Facility, with the help of an Ultravisor
executing below the hypervisor layer. This enables support for
those guests.
If unsure, say "N".
* arch/powerpc/Kconfig (help): OPAL_CORE (bool)
This option uses the MPIPL support in firmware to provide an
ELF core of OPAL memory after a crash. The ELF core is exported
as /sys/firmware/opal/core file which is helpful in debugging
OPAL crashes using GDB.
Cc: David Gibson <dgibson@redhat.com>
Cc: Laurent Vivier <lvivier@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014162300.16308-3-jcline@redhat.com>
Patchwork-id: 278876
O-Subject: [ARK INTERNAL PATCH] configs: New config in crypto for v5.4-rc1
Bugzilla:
RH-Acked-by: Ondrej Mosnacek <omosnace@redhat.com>
RH-Acked-by: Herbert Xu <herbert.xu@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* crypto/Kconfig (help): CRYPTO_ESSIV (tristate)
Encrypted salt-sector initialization vector (ESSIV) is an IV
generation method that is used in some cases by fscrypt and/or
dm-crypt. It uses the hash of the block encryption key as the
symmetric key for a block encryption pass applied to the input
IV, making low entropy IV sources more suitable for block
encryption.
This driver implements a crypto API template that can be
instantiated either as a skcipher or as a aead (depending on the
type of the first template argument), and which defers encryption
and decryption requests to the encapsulated cipher after applying
ESSIV to the input IV. Note that in the aead case, it is assumed
that the keys are presented in the same format used by the authenc
template, and that the IV appears at the end of the authenticated
associated data (AAD) region (which is how dm-crypt uses it.)
Note that the use of ESSIV is not recommended for new deployments,
and so this only needs to be enabled when interoperability with
existing encrypted volumes of filesystems is required, or when
building for a particular system that requires it (e.g., when
the SoC in question has accelerated CBC but not XTS, making CBC
combined with ESSIV the only feasible mode for h/w accelerated
block encryption)
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190918194258.8325-1-jcline@redhat.com>
Patchwork-id: 272492
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in drivers/usb for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/usb/cdns3/Kconfig (help): USB_CDNS3 (tristate)
Say Y here if your system has a Cadence USB3 dual-role controller.
It supports: dual-role switch, Host-only, and Peripheral-only.
If you choose to build this driver is a dynamically linked
as module, the module will be called cdns3.ko.
* drivers/usb/common/Kconfig (help): USB_CONN_GPIO (tristate)
The driver supports USB role switch between host and device via GPIO
based USB cable detection, used typically if an input GPIO is used
to detect USB ID pin, and another input GPIO may be also used to detect
Vbus pin at the same time, it also can be used to enable/disable
device if an input GPIO is only used to detect Vbus pin.
To compile the driver as a module, choose M here: the module will
be called usb-conn-gpio.ko
Cc: Torez Smith <torez@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Because of the nature of keeping two sets of configs, the
Fedora configs in this tree are out of sync with work
that's happening in the official Fedora dist-git repo.
Bring this back in sync.
As part of this work, prune a bunch of dead configuration
options. None of the changes meaningfully affect the generated
config output for ARK as compared against the full configs in the
srpms.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Message-id: <20190918194309.8503-1-jcline@redhat.com>
Patchwork-id: 272491
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in fs/erofs for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* fs/erofs/Kconfig (help): EROFS_FS (tristate)
EROFS (Enhanced Read-Only File System) is a lightweight
read-only file system with modern designs (eg. page-sized
blocks, inline xattrs/data, etc.) for scenarios which need
high-performance read-only requirements, e.g. Android OS
for mobile phones and LIVECDs.
It also provides fixed-sized output compression support,
which improves storage density, keeps relatively higher
compression ratios, which is more useful to achieve high
performance for embedded devices with limited memory.
If unsure, say N.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014162300.16308-21-jcline@redhat.com>
Patchwork-id: 278886
O-Subject: [ARK INTERNAL PATCH] configs: New config in mm for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* mm/Kconfig (help): READ_ONLY_THP_FOR_FS (bool)
Allow khugepaged to put read-only file-backed pages in THP.
This is marked experimental because it is a new feature. Write
support of file THPs will be developed in the next few release
cycles.
Cc: Larry Woodman <lwoodman@redhat.com>
Cc: Michael S. Tsirkin <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: Dean Nelson <dnelson@redhat.com>
Cc: Steve Best <sbest@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191111151627.73663-1-jcline@redhat.com>
Patchwork-id: 285197
O-Subject: [ARK INTERNAL PATCHv2] configs: New config in drivers/md for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/md/Kconfig (help): DM_CLONE (tristate)
dm-clone produces a one-to-one copy of an existing, read-only source
device into a writable destination device. The cloned device is
visible/mountable immediately and the copy of the source device to the
destination device happens in the background, in parallel with user
I/O.
If unsure, say N.
* drivers/md/Kconfig (help): DM_VERITY_VERIFY_ROOTHASH_SIG (bool)
Add ability for dm-verity device to be validated if the
pre-generated tree of cryptographic checksums passed has a pkcs#7
signature file that can validate the roothash of the tree.
If unsure, say N.
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: Mike Snitzer <snitzer@redhat.com>
Cc: Jonathan Brassow <jbrassow@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014162300.16308-19-jcline@redhat.com>
Patchwork-id: 278894
O-Subject: [ARK INTERNAL PATCH] configs: New config in init for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* init/Kconfig (help): MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS (bool)
Symbols exported with EXPORT_SYMBOL_NS*() are considered exported in
a namespace. A module that makes use of a symbol exported with such a
namespace is required to import the namespace via MODULE_IMPORT_NS().
There is no technical reason to enforce correct namespace imports,
but it creates consistency between symbols defining namespaces and
users importing namespaces they make use of. This option relaxes this
requirement and lifts the enforcement when loading a module.
If unsure, say N.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191113144431.9403-3-labbott@redhat.com>
Patchwork-id: 286077
O-Subject: [ARK INTERNAL PATCHv2 2/4] [redhat] configs: Set appropriate values for CONFIG_RH_DISABLE_DEPRECATED
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
Allow ARK to use the various deprecation interace but let Fedora
work as normal.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Message-id: <20191104195711.611286-1-jcline@redhat.com>
RH-Acked-by: Vivek Goyal <vgoyal@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* fs/fuse/Kconfig (help): VIRTIO_FS (tristate)
The Virtio Filesystem allows guests to mount file systems from the
host.
If you want to share files between guests or with the host, answer Y
or M.
Cc: Brian Foster <bfoster@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
In RHEL-8, we needed to handle a config comment that had a config name inside
the comment. For example:
# Please do not use CONFIG_FOO=y because it breaks things
This comment caused merge.pl to set CONFIG_FOO equal to 'y' in the output
accidentally. To avoid this, the easy solution was to skip all comments
in the merged output. However, this breaks Fedora's trick to apply last
minute configs with kernel-local.
By dropping the comments, the '# <arch>' header goes missing, confusing the
tools about which arch to apply the configs for.
Modify the original solution from dropping comments to avoiding the
accidental processing of the CONFIG_FOO=y line. This is accomplished by
checking for a comment and falling through thus avoiding the '=' check
in the next else statement (and the source of the problem).
Tested by building a srpm using a kernel-local file.
Acked-by: Prarit Bhargava <prarit@redhat.com>
Acked-by: Laura Abbott <labbott@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/net/ethernet/pensando/Kconfig (help): IONIC (tristate)
This enables the support for the Pensando family of Ethernet
adapters. More specific information on this driver can be
found in
<file:Documentation/networking/device_drivers/pensando/ionic.rst>.
To compile this driver as a module, choose M here. The module
will be called ionic.
* drivers/net/ethernet/pensando/Kconfig (help): NET_VENDOR_PENSANDO (bool)
If you have a network (Ethernet) card belonging to this class, say Y.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Pensando cards. If you say Y, you will be asked
for your specific card in the following questions.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Acked-by: Neil Horman <nhorman@redhat.com>
Currently, we've been switching between copying Fedora and RHEL files
based on dist-tag. Long term, we want to have a single tree to manage
both Fedora and RHEL. Move towards this by shipping both RHEL and
Fedora files in a single RPM. The choice of which set of files to use
gets decided at build time based on the buildroot.
This series is a big large but it's not easy to break up simply because
making one change requires making all the other changes to avoid breaking
anything. The big changes:
- Move some files and scripts to have the .fedora or .rhel extension
- Tweak some of the config scripts to accont for a fedora/rhel extension
- spec file changes to account for these changes
Signed-off-by: Laura Abbott <labbott@redhat.com>
As per the Fedora commit:
The CI build currently adds the full git commit hash to the release of
the RPM it builds. This breaks the kernel build as the EXTRAVERSION
cannot exceed 64 characters.
This sets the EXTRAVERSION to whatever the release was minus
".pr.<hash>".
Signed-off-by: Laura Abbott <labbott@redhat.com>
For various reasons usually releated to architectures, Fedora builds
some things slightly differently. Adjust accordingly.
Signed-off-by: Laura Abbott <labbott@redhat.com>
In the interest of making things easier to read, consolodate all the
make options into a single location in the file. Also switch to
using the standard cflags and ldflags options.
Signed-off-by: Laura Abbott <labbott@redhat.com>
The original design for the common set of configs had Fedora
not using the pending directory. The goal now is to have both
Fedora + RHEL configs in the same tree. With that goal in mind,
let Fedora use the pending directory as well. At the same time,
fixup some other Fedora configuration options that are broken
(once we build for both Fedora and RHEL this will stop being
broken so much)
Signed-off-by: Laura Abbott <labbott@redhat.com>
>From the people on the OSTree side:
OSTree is a far, far more sophisticated wrapper around the `link()`
system call than the `hardlink` package - it supports using
as a mechanism for transactional offline updates, fetching over
HTTP with GPG signatures and deltas, etc. rpm-ostree uses it
for everything.
Having the `kernel-devel` package run `hardlink` just adds
latency to `rpm-ostree compose tree` unnecessarily.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Acked-by: Don Zickus <dzickus@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* net/can/j1939/Kconfig (help): CAN_J1939 (tristate)
SAE J1939
Say Y to have in-kernel support for j1939 socket type. This
allows communication according to SAE j1939.
The relevant parts in kernel are
SAE j1939-21 (datalink & transport protocol)
& SAE j1939-81 (network management).
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Acked-by: Jiri Benc <jbenc@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/net/phy/Kconfig (help): ADIN_PHY (tristate)
Adds support for the Analog Devices Industrial Ethernet PHYs.
Currently supports the:
- ADIN1200 - Robust,Industrial, Low Power 10/100 Ethernet PHY
- ADIN1300 - Robust,Industrial, Low Latency 10/100/1000 Gigabit
Ethernet PHY
Cc: Petr Oros <poros@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Acked-by: Jiri Benc <jbenc@redhat.com>
Bugzilla: http://bugzilla.redhat.com/1730649
Upstream Status: RHEL only
We have a long time customer that requires 64 UARTS.
Increase the number of UARTS to 64 on x86_64, and add a comment to the
config file.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Because of the way ARK flows, the changelog only gets committed
to the master branch. Since master gets overwritten each rebase,
we lose the history we need. Automate bringing the information
for the changelog back to internal.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Message-id: <20191001181211.19739-1-jcline@redhat.com>
Patchwork-id: 275497
O-Subject: [ARK INTERNAL PATCH] configs: turn on ARM64_FORCE_52BIT for debug builds
Bugzilla:
RH-Acked-by: Mark Salter <msalter@redhat.com>
Turn on ARM64_FORCE_52BIT on the debug kernel in order to turn up 52-bit
bugs.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Acked-by: Mark Salter <msalter@redhat.com>
Message-id: <20191022125201.32538-3-labbott@redhat.com>
Patchwork-id: 280638
O-Subject: [ARK INTERNAL PATCH 2/8] [redhat] kernel.spec.template: Tweak the python3 mangling
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
Tweak the python3 mangling message to be a bit clearer about what
exactly we are doing and remove referneces to RHEL8. Also pick up
other python3 environment flags.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191022125201.32538-9-labbott@redhat.com>
Patchwork-id: 280635
O-Subject: [ARK INTERNAL PATCH 8/8] [redhat] kernel.spec.template: Add --with verbose option
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
By default the kernel builds are silent because otherwise there
would be too much noise. Sometimes it's useful to see the full
output. Add a --with verbose option to build without -s.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191022125201.32538-8-labbott@redhat.com>
Patchwork-id: 280634
O-Subject: [ARK INTERNAL PATCH 7/8] [redhat] kernel.spec.template: Switch to using %install instead of %__install
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
This matches what Fedora has and there's no reason to use the
internal one.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191022125201.32538-7-labbott@redhat.com>
Patchwork-id: 280637
O-Subject: [ARK INTERNAL PATCH 6/8] [redhat] kernel.spec.template: Make the kernel.org URL https
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
It's 2019 and everyone should be running https. Match what Fedora uses
and use the https URL.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191022125201.32538-6-labbott@redhat.com>
Patchwork-id: 280636
O-Subject: [ARK INTERNAL PATCH 5/8] [redhat] kernel.spec.template: Update message about secure boot signing
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
We now sign on multiple arches besides x86_64. Update the message to
be agnostic.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191022125201.32538-2-labbott@redhat.com>
Patchwork-id: 280631
O-Subject: [ARK INTERNAL PATCH 1/8] [redhat] kernel.spec.template: Move some with flags definitions up
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
Move gcov and ipaclones to be with the reset of the with flag
defintions for ease of review.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191022125201.32538-5-labbott@redhat.com>
Patchwork-id: 280633
O-Subject: [ARK INTERNAL PATCH 4/8] [redhat] kernel.spec.template: Update some BuildRequires
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
Re-arrange a few build requires to sync up with Fedora. The only
real change is git -> git-core.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191022125201.32538-4-labbott@redhat.com>
Patchwork-id: 280632
O-Subject: [ARK INTERNAL PATCH 3/8] [redhat] kernel.spec.template: Get rid of %clean
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
The basic clean is already defined so there's no need to redefine it
again. Just remove it.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190918194048.6650-1-jcline@redhat.com>
Patchwork-id: 272483
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in drivers/char for v5.4-rc1
Bugzilla:
RH-Acked-by: Jerry Snitselaar <jsnitsel@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/char/Kconfig (help): RANDOM_TRUST_BOOTLOADER (bool)
Some bootloaders can provide entropy to increase the kernel's initial
device randomness. Say Y here to assume the entropy provided by the
booloader is trustworthy so it will be added to the kernel's entropy
pool. Otherwise, say N here so it will be regarded as device input that
only mixes the entropy pool.
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: George Beshers <gbeshers@redhat.com>
Cc: Frank Ramsay <framsay@redhat.com>
Cc: Russ Anderson <randerso@redhat.com>
Cc: Michael S. Tsirkin <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191021170608.8971-1-jcline@redhat.com>
Patchwork-id: 280561
O-Subject: [ARK INTERNAL PATCHv2] configs: New config in net/sched for v5.4-rc1
Bugzilla:
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* net/sched/Kconfig (help): NET_TC_SKB_EXT (bool)
Say Y here to allow tc chain misses to continue in OvS datapath in
the correct recirc_id, and hardware chain misses to continue in
the correct chain in tc software datapath.
Say N here if you won't be using tc<->ovs offload or tc chains offload.
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191021170136.3374-1-jcline@redhat.com>
Patchwork-id: 280560
O-Subject: [ARK INTERNAL PATCHv2] configs: New config in lib for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* lib/Kconfig.debug (help): DEBUG_KMEMLEAK_MEM_POOL_SIZE (int)
Kmemleak must track all the memory allocations to avoid
reporting false positives. Since memory may be allocated or
freed before kmemleak is fully initialised, use a static pool
of metadata objects to track such callbacks. After kmemleak is
fully initialised, this memory pool acts as an emergency one
if slab allocations fail.
Note: this configuration is a rename of DEBUG_KMEMLEAK_EARLY_LOG_SIZE
done in commit c566586818 ("mm: kmemleak: use the memory pool for
early allocations")
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014162300.16308-18-jcline@redhat.com>
Patchwork-id: 278893
O-Subject: [ARK INTERNAL PATCH] configs: New config in fs/verity for v5.4-rc1
Bugzilla:
RH-Acked-by: Eric Sandeen <esandeen@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* fs/verity/Kconfig (help): FS_VERITY (bool)
This option enables fs-verity. fs-verity is the dm-verity
mechanism implemented at the file level. On supported
filesystems (currently EXT4 and F2FS), userspace can use an
ioctl to enable verity for a file, which causes the filesystem
to build a Merkle tree for the file. The filesystem will then
transparently verify any data read from the file against the
Merkle tree. The file is also made read-only.
This serves as an integrity check, but the availability of the
Merkle tree root hash also allows efficiently supporting
various use cases where normally the whole file would need to
be hashed at once, such as: (a) auditing (logging the file's
hash), or (b) authenticity verification (comparing the hash
against a known good value, e.g. from a digital signature).
fs-verity is especially useful on large files where not all
the contents may actually be needed. Also, fs-verity verifies
data each time it is paged back in, which provides better
protection against malicious disks vs. an ahead-of-time hash.
If unsure, say N.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191021163129.22377-1-jcline@redhat.com>
Patchwork-id: 280557
O-Subject: [ARK INTERNAL PATCH] configs: New config in arch/aarch64 for v5.4-rc4
Bugzilla:
RH-Acked-by: Mark Salter <msalter@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc4, New config option(s) were
exposed. Please review the options below.
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 CAVIUM_TX2_ERRATUM_219
bool "Cavium ThunderX2 erratum 219: PRFM between TTBR change and ISB fails"
default y
help
On Cavium ThunderX2, a load, store or prefetch instruction between a
TTBR update and the corresponding context synchronizing operation can
cause a spurious Data Abort to be delivered to any hardware thread in
the CPU core.
Work around the issue by avoiding the problematic code sequence and
trapping KVM guest TTBRx_EL1 writes to EL2 when SMT is enabled. The
trap handler performs the corresponding register access, skips the
instruction and ensures context synchronization by virtue of the
exception return.
If unsure, say Y.
Cc: Mark Salter <msalter@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190923141122.1264-1-jcline@redhat.com>
Patchwork-id: 272788
O-Subject: [ARK INTERNAL PATCHv2] [redhat] configs: New config in arch/arm64 for v5.4-rc1
Bugzilla:
RH-Acked-by: Jeremy Linton <jlinton@redhat.com>
RH-Acked-by: Mark Salter <msalter@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* arch/arm64/Kconfig (help): ARM64_TAGGED_ADDR_ABI (bool)
When this option is enabled, user applications can opt in to a
relaxed ABI via prctl() allowing tagged addresses to be passed
to system calls as pointer arguments. For details, see
Documentation/arm64/tagged-address-abi.txt.
* arch/arm64/Kconfig (help): ARM64_VA_BITS_52 (bool)
Enable 52-bit virtual addressing for userspace when explicitly
requested via a hint to mmap(). The kernel will also use 52-bit
virtual addresses for its own mappings (provided HW support for
this feature is available, otherwise it reverts to 48-bit).
NOTE: Enabling 52-bit virtual addressing in conjunction with
ARMv8.3 Pointer Authentication will result in the PAC being
reduced from 7 bits to 3 bits, which may have a significant
impact on its susceptibility to brute-force attacks.
If unsure, select 48-bit virtual addressing instead.
Cc: Mark Salter <msalter@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>
Cc: Wei Huang <wei@redhat.com>
Cc: Eric Auger <eric.auger@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191015212339.32515-1-labbott@redhat.com>
Patchwork-id: 279322
O-Subject: [ARK INTERNAL PATCH] [redhat] Correctly name tarball for single tarball builds
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
The intention with single tarball builds is to have a separation
between upstream sources and introduced changes. This means the name
of the tarball that's generated should roughly match upstream. Adjust
the generation of this appropriately.
Signed-off-by: Laura Abbott <labbott@redhat.com>
---
After this change, Source0 is now named linux-5.3-rc2.tar.xz and the
folder is also named appropriately. I think this better represents
something like what Fedora is looking for sources.
Note this is based on top of my change for the changelog scine this
conflicts.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014162300.16308-14-jcline@redhat.com>
Patchwork-id: 278875
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/pci for v5.4-rc1
Bugzilla:
RH-Acked-by: Myron Stowe <mstowe@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/pci/controller/dwc/Kconfig (help): PCIE_AL (bool)
Say Y here to enable support of the Amazon's Annapurna Labs PCIe
controller IP on Amazon SoCs. The PCIe controller uses the DesignWare
core plus Annapurna Labs proprietary hardware wrappers. This is
required only for DT-based platforms. ACPI platforms with the
Annapurna Labs PCIe controller don't need to enable this.
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191011183603.21725-4-labbott@redhat.com>
Patchwork-id: 278729
O-Subject: [ARK INTERNAL PATCH 3/3] [redhat] Allow overriding the dist tag on the command line
Bugzilla:
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Herton R. Krzesinski <herton@redhat.com>
Similar to the branch target for building, only set the
dist tag if it's not already been set on the command line.
This allows for easier creation of rpms intended for
other buildroots.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191011183603.21725-3-labbott@redhat.com>
Patchwork-id: 278728
O-Subject: [ARK INTERNAL PATCH 2/3] [redhat] Allow scratch branch target to be overridden
Bugzilla:
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Herton R. Krzesinski <herton@redhat.com>
The scratch branch target is currently hard coded to what's
expected (i.e. the branch for the particular release). It's
useful to be able to change branches easily though. Allow
the scratch target to be overridden on the command line to
make it easy to do tasks like 'BUILD_SCRATCH_TARGET=f32 make rh-koji'.
Do this by only setting the branch target if it's not already
set (?=). While we're doing this, move the default
BUILD_SCRATCH_TARGET into Makefile.common which is where
most of the other per branch settings are.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191011183603.21725-2-labbott@redhat.com>
Patchwork-id: 278727
O-Subject: [ARK INTERNAL PATCH 1/3] [redhat] Remove long dead BUILD_DEFAULT_TARGET
Bugzilla:
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Herton R. Krzesinski <herton@redhat.com>
This variable seems to have been commented out since at least
RHEL6. Let's assume it's not coming back and just remove it.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014215001.22274-1-labbott@redhat.com>
Patchwork-id: 278907
O-Subject: [ARK INTERNAL PATCH] [redhat] Amend the changelog when rebasing
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
Currently for ARK, we don't generate an incremental changelog. Each
release dumps the same patch information into the rpm changelog. Make
this more useful by generating a running rpm changelog when rebasing.
Use the same trick we do to generate a changelog with the marker we
use to generate a base for patches. This lets us detect a rebase and
handle that case separately.
Signed-off-by: Laura Abbott <labbott@redhat.com>
---
This has been a long running quirk of ARK. This is also necessary for us
to get closer to Fedora + ARK. We could potentially run into problems if
there are identical subject lines across patches but that should be
fixable.
Because we're bootstrapping, this needs to be properly synced up to be
used with the next release. I talked to Jeremy and this should be picked
up for -rc3 but if something needs to be fixed I'll get it set up to be
used with -rc4.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014162300.16308-16-jcline@redhat.com>
Patchwork-id: 278883
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/platform for v5.4-rc1
Bugzilla:
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Laura Abbott <labbott@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/platform/chrome/Kconfig (help): CROS_EC (tristate)
If you say Y here you get support for the ChromeOS Embedded
Controller (EC) providing keyboard, battery and power services.
You also need to enable the driver for the bus you are using. The
protocol for talking to the EC is defined by the bus driver.
To compile this driver as a module, choose M here: the
module will be called cros_ec.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014162300.16308-15-jcline@redhat.com>
Patchwork-id: 278885
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/pinctrl for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/pinctrl/qcom/Kconfig (help): PINCTRL_SC7180 (tristate)
This is the pinctrl, pinmux, pinconf and gpiolib driver for the
Qualcomm Technologies Inc TLMM block found on the Qualcomm
Technologies Inc SC7180 platform.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014162300.16308-13-jcline@redhat.com>
Patchwork-id: 278880
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/net/wireless for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/net/wireless/ath/ath9k/Kconfig (help): ATH9K_PCI_NO_EEPROM (tristate)
This separate driver provides a loader in order to support the
AR500X to AR92XX-generation of ath9k PCI(e) WiFi chips, which have
their initialization data (which contains the real PCI Device ID
that ath9k will need) stored together with the calibration data out
of reach for the ath9k chip.
These devices are usually various network appliances, routers or
access Points and such.
If unsure say N.
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: John Linville <linville@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014162300.16308-10-jcline@redhat.com>
Patchwork-id: 278881
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/net/ethernet/mellanox for v5.4-rc1
Bugzilla:
RH-Acked-by: Marcelo Leitner <mleitner@redhat.com>
RH-Acked-by: Neil Horman <nhorman@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/net/ethernet/mellanox/mlx5/core/Kconfig (help): MLX5_SW_STEERING (bool)
Build support for software-managed steering in the NIC.
Cc: Erez Alfasi <ealfasi@redhat.com>
Cc: Alaa Hleihel <ahleihel@redhat.com>
Cc: Slava Shwartsman <sshwarts@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014162300.16308-9-jcline@redhat.com>
Patchwork-id: 278874
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/net/can for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/net/can/sja1000/Kconfig (help): CAN_F81601 (tristate)
This driver adds support for Fintek F81601 PCIE to 2 CAN
Controller. It had internal 24MHz clock source, but it can
be changed by manufacturer. Use modinfo to get usage for
parameters. Visit http://www.fintek.com.tw to get more
information.
* drivers/net/can/Kconfig (help): CAN_KVASER_PCIEFD (tristate)
This is a driver for the Kvaser PCI Express CAN FD family.
Supported devices:
Kvaser PCIEcan 4xHS
Kvaser PCIEcan 2xHS v2
Kvaser PCIEcan HS v2
Kvaser Mini PCI Express HS v2
Kvaser Mini PCI Express 2xHS v2
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014162300.16308-7-jcline@redhat.com>
Patchwork-id: 278891
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/hid for v5.4-rc1
Bugzilla:
RH-Acked-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/hid/Kconfig (help): HID_CREATIVE_SB0540 (tristate)
Support for Creative infrared SB0540-compatible remote controls, such
as the RM-1500 and RM-1800 remotes.
Say Y here if you want support for Creative SB0540 infrared receiver.
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Cathy Avery <cavery@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014162300.16308-5-jcline@redhat.com>
Patchwork-id: 278884
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/dma-buf for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/dma-buf/Kconfig (help): DMABUF_SELFTESTS (tristate)
(no helpstring found)
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014162300.16308-4-jcline@redhat.com>
Patchwork-id: 278888
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/crypto for v5.4-rc1
Bugzilla:
RH-Acked-by: Neil Horman <nhorman@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/crypto/ccp/Kconfig (help): CRYPTO_DEV_CCP_DEBUGFS (bool)
Expose CCP device information such as operation statistics, feature
information, and descriptor queue contents.
* drivers/crypto/hisilicon/Kconfig (help): CRYPTO_DEV_HISI_ZIP (tristate)
Support for HiSilicon ZIP Driver
* drivers/crypto/Kconfig (help): CRYPTO_DEV_SAFEXCEL (tristate)
This driver interfaces with the SafeXcel EIP-97 and EIP-197 cryptographic
engines designed by Inside Secure. It currently accelerates DES, 3DES and
AES block ciphers in ECB and CBC mode, as well as SHA1, SHA224, SHA256,
SHA384 and SHA512 hash algorithms for both basic hash and HMAC.
Additionally, it accelerates combined AES-CBC/HMAC-SHA AEAD operations.
Cc: Neil Horman <nhorman@redhat.com>
Cc: Michael S. Tsirkin <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191014162300.16308-2-jcline@redhat.com>
Patchwork-id: 278872
O-Subject: [ARK INTERNAL PATCH] configs: New config in arch/s390 for v5.4-rc1
Bugzilla:
RH-Acked-by: Cornelia Huck <cohuck@redhat.com>
RH-Acked-by: Thomas Huth <thuth@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* arch/s390/Kconfig (help): KEXEC_SIG (bool)
This option makes kernel signature verification mandatory for
the kexec_file_load() syscall.
In addition to that option, you need to enable signature
verification for the corresponding kernel image type being
loaded in order for this to work.
Cc: Thomas Huth <thuth@redhat.com>
Cc: Cornelia Huck <cohuck@redhat.com>
Cc: David Hildenbrand <david@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190918194018.6258-1-jcline@redhat.com>
Patchwork-id: 272479
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in block for v5.4-rc1
Bugzilla:
RH-Acked-by: Jeff Moyer <jmoyer@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* block/Kconfig (help): BLK_CGROUP_IOCOST (bool)
Enabling this option enables the .weight interface for cost
model based proportional IO control. The IO controller
distributes IO capacity between different groups based on
their share of the overall weight distribution.
Cc: Ming Lei <minlei@redhat.com>
Cc: Jeff Moyer <jmoyer@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190923140215.26145-1-jcline@redhat.com>
Patchwork-id: 272761
O-Subject: [ARK INTERNAL PATCHv2] [redhat] configs: New config in drivers/cpuidle for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>
RH-Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/cpuidle/Kconfig.arm (help): ARM_PSCI_CPUIDLE (bool)
Select this to enable PSCI firmware based CPUidle driver for ARM.
It provides an idle driver that is capable of detecting and
managing idle states through the PSCI firmware interface.
* drivers/cpuidle/Kconfig (help): CPU_IDLE_GOV_HALTPOLL (bool)
This governor implements haltpoll idle state selection, to be
used in conjunction with the haltpoll cpuidle driver, allowing
for polling for a certain amount of time before entering idle
state.
Some virtualized workloads benefit from using it.
* drivers/cpuidle/Kconfig (help): HALTPOLL_CPUIDLE (tristate)
This option enables halt poll cpuidle driver, which allows to poll
before halting in the guest (more efficient than polling in the
host via halt_poll_ns for some scenarios).
Cc: John Linville <linville@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Due to some encryption options Fedora enables, this now needs
to be built in. Split it out to Fedora and ARK separately.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Message-id: <20191001153139.14526-1-jcline@redhat.com>
Patchwork-id: 275492
O-Subject: [ARK INTERNAL PATCHv2] [redhat] configs: New config in drivers/edac for v5.4-rc1
Bugzilla:
RH-Acked-by: Aristeu Rozanski <aris@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/edac/Kconfig (help): EDAC_BLUEFIELD (tristate)
Support for error detection and correction on the
Mellanox BlueField SoCs.
Cc: Aristeu Rozanski <aris@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20191001174534.14040-1-jcline@redhat.com>
Patchwork-id: 275495
O-Subject: [ARK INTERNAL PATCHv3] [redhat] configs: New config in drivers/firmware for v5.4-rc1
Bugzilla:
RH-Acked-by: Al Stone <ahs3@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/firmware/efi/Kconfig (help): EFI_RCI2_TABLE (bool)
Displays the content of the Runtime Configuration Interface
Table version 2 on Dell EMC PowerEdge systems as a binary
attribute 'rci2' under /sys/firmware/efi/tables directory.
RCI2 table contains BIOS HII in XML format and is used to populate
BIOS setup page in Dell EMC OpenManage Server Administrator tool.
The BIOS setup page contains BIOS tokens which can be configured.
Say Y here for Dell EMC PowerEdge systems.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190918194207.7637-1-jcline@redhat.com>
Patchwork-id: 272487
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in drivers/hwmon for v5.4-rc1
Bugzilla:
RH-Acked-by: Dean Nelson <dnelson@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/hwmon/Kconfig (help): SENSORS_AS370 (tristate)
If you say yes here you get support for the PVT sensors of
the Synaptics AS370 SoC
This driver can also be built as a module. If so, the module
will be called as370-hwmon.
* drivers/hwmon/pmbus/Kconfig (help): SENSORS_INSPUR_IPSPS (tristate)
If you say yes here you get hardware monitoring support for the INSPUR
Power System power supply.
This driver can also be built as a module. If so, the module will
be called inspur-ipsps.
Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190918194220.7803-1-jcline@redhat.com>
Patchwork-id: 272488
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in drivers/iio for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/iio/imu/Kconfig (help): ADIS16460 (tristate)
Say yes here to build support for Analog Devices ADIS16460 inertial
sensor.
To compile this driver as a module, choose M here: the module will be
called adis16460.
* drivers/iio/potentiometer/Kconfig (help): MAX5432 (tristate)
Say yes here to build support for the Maxim
MAX5432, MAX5433, MAX5434 and MAX5435 digital
potentiometer chips.
To compile this driver as a module, choose M here: the
module will be called max5432.
* drivers/iio/light/Kconfig (help): NOA1305 (tristate)
Say Y here if you want to build support for the ON Semiconductor
NOA1305 ambient light sensor.
To compile this driver as a module, choose M here:
The module will be called noa1305.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190918194237.7993-1-jcline@redhat.com>
Patchwork-id: 272489
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in drivers/mmc for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/mmc/host/Kconfig (help): MMC_SDHCI_OF_ASPEED (tristate)
This selects the ASPEED Secure Digital Host Controller Interface.
If you have a controller with this interface, say Y or M here. You
also need to enable an appropriate bus interface.
If unsure, say N.
Cc: John Linville <linville@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190918194246.8171-1-jcline@redhat.com>
Patchwork-id: 272490
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in drivers/tty for v5.4-rc1
Bugzilla:
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Laura Abbott <labbott@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/tty/serial/Kconfig (help): SERIAL_FSL_LINFLEXUART (tristate)
Support for the on-chip linflexuart on some Freescale SOCs.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190923135800.25646-1-jcline@redhat.com>
Patchwork-id: 272760
O-Subject: [ARK INTERNAL PATCHv2] [redhat] configs: New config in arch/s390 for v5.4-rc1
Bugzilla:
RH-Acked-by: Thomas Huth <thuth@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* arch/s390/Kconfig (help): MARCH_Z15 (bool)
Select this to enable optimizations for IBM z15 (8562
and 8561 series). The kernel will be slightly faster but will not
work on older machines.
* arch/s390/Kconfig (help): TUNE_Z15 (bool)
(no helpstring found)
Cc: Neil Horman <nhorman@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>
Cc: Cornelia Huck <cohuck@redhat.com>
Cc: David Hildenbrand <david@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190918194030.6474-1-jcline@redhat.com>
Patchwork-id: 272480
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in drivers/bus for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/bus/Kconfig (help): MOXTET (tristate)
Say yes here to add support for the module configuration bus found
on CZ.NIC's Turris Mox. This is needed for the ability to discover
the order in which the modules are connected and to get/set some of
their settings. For example the GPIOs on Mox SFP module are
configured through this bus.
Cc: John Linville <linville@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190919183528.15814-1-labbott@redhat.com>
Patchwork-id: 272583
O-Subject: [ARK INTERNAL PATCH] [redhat] Add option to allow mismatched configs on the command line
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
We added checks for configuration options to make sure everything
gets set properly and reviewed. Sometimes for testing it's useful to
just be able to ignore those warnings for development or other testing.
Add an option to ignore the checks on the command line
(NO_CONFIGCHECKS=1 make rh-srpm) so developers don't have to
hack this out manually.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190923140408.26331-1-jcline@redhat.com>
Patchwork-id: 272762
O-Subject: [ARK INTERNAL PATCHv2] [redhat] configs: New config in drivers/crypto for v5.4-rc1
Bugzilla:
RH-Acked-by: Neil Horman <nhorman@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* drivers/crypto/Kconfig (help): CRYPTO_SHA3_256_S390 (tristate)
This is the s390 hardware accelerated implementation of the
SHA3_256 secure hash standard.
It is available as of z14.
* drivers/crypto/Kconfig (help): CRYPTO_SHA3_512_S390 (tristate)
This is the s390 hardware accelerated implementation of the
SHA3_512 secure hash standard.
It is available as of z14.
Cc: Neil Horman <nhorman@redhat.com>
Cc: Michael S. Tsirkin <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190923144238.420-1-jcline@redhat.com>
Patchwork-id: 272831
O-Subject: [ARK INTERNAL PATCHv2] [redhat] configs: New config in sound/pci for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>
RH-Acked-by: Jaroslav Kysela <jkysela@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* sound/pci/hda/Kconfig (help): SND_HDA_INTEL_DETECT_DMIC (bool)
Say Y to detect digital microphones on SKL+ devices. DMICs
cannot be handled by the HDaudio legacy driver and are
currently only supported by the SOF driver.
If unsure say N.
Cc: John Linville <linville@redhat.com>
Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190918194331.8835-1-jcline@redhat.com>
Patchwork-id: 272493
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in sound/soc for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>
Upstream Status: RHEL only.
Hi,
As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.
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.
* sound/soc/codecs/Kconfig (help): SND_SOC_UDA1334 (tristate)
The UDA1334 is an NXP audio codec, supports the I2S-bus data format
and has basic features such as de-emphasis (at 44.1 kHz sampling
rate) and mute.
Cc: John Linville <linville@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Message-id: <20190920180802.27752-1-major@redhat.com>
Patchwork-id: 272742
O-Subject: [ARK INTERNAL PATCH] [redhat] gitlab: Add CI job for packaging scripts
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>
This job runs each time the `internal` branch is updated. It gathers
the packaging-related files from the repo and artifacts them inside
GitLab. This allows CI jobs to quickly download packaging scripts to
use with other upstream repositories.
Signed-off-by: Major Hayden <major@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
We tried to disable this driver in RHEL8, but the dev experience team
pushed back because virtbox only supports this driver. We shouldn't
allow that to go on forever though, as the driver isn't being maintained
upstream anymore. So lets turn it off in ARK and at least have the
conversation again in RHEL 9
Signed-off-by: Neil Horman <nhorman@redhat.com>
The current setting results in an invalid configuration so while the
patch is under review, adjust the default.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Upstream required this in commit ac7c3e4ff4 ("compiler: enable
CONFIG_OPTIMIZE_INLINING forcibly") so move the setting back into
pending for review.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Fedora has been carrying an out of tree to change the max zone order
for a while. Until we figure out what we want to do with this patch,
just set it to the expected default.
Signed-off-by: Laura Abbott <labbott@redhat.com>
This brings Fedora in sync for 5.3 for new configs. This also includes
adjusting a few options based on dropping a few patches in Fedora.
Signed-off-by: Laura Abbott <labbott@redhat.com>
pr_crit("ACPI has been disabled or is not available on this hardware. This may result in a single cpu boot, incorrect PCI IRQ routing, or boot failure.\n");
pr_crit("Warning: %s - this hardware has not undergone testing by Red Hat and might not be certified. Please consult https://catalog.redhat.com for certified hardware.\n",msg);
pr_crit("Warning: %s - this hardware is not recommended for new deployments. It continues to be supported in this RHEL release, but it is likely to be removed in the next major release. Driver updates and fixes for this device will be limited to critical issues. Please contact Red Hat Support or your device's hardware vendor for additional information.\n",msg);
pr_crit("Warning: %s - This driver has not undergone sufficient testing by Red Hat for this release and therefore cannot be used in production systems.\n",
pr_crit("Warning: %s - this driver is not recommended for new deployments. It continues to be supported in this RHEL release, but it is likely to be removed in the next major release. Driver updates and fixes will be limited to critical issues. Please contact Red Hat Support for additional information.\n",
echo"WARNING: There are uncommitted changes in your tree or the changes are not in sync with linux-kernel-test.patch. Either commit the changes or run 'make dist-test-patch'"