Age | Commit message (Collapse) | Author |
|
In commit e2c73a6860bd ("rcu: Remove the RCU_FAST_NO_HZ Kconfig option")
the so named option was removed from the v5.17 kernel.
We should get it out of our active branches to prevent a warning.
Signed-off-by: Paul Gortmaker <paulg@kernel.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
It was removed from mainline in v6.4 in commit f22f9aaf6c3d ("selinux:
remove the runtime disable functionality").
Signed-off-by: Paul Gortmaker <paulg@kernel.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
nftable ptests do create interfaces of veth type and this
feature would be needed to enable those tests
e.g. from tests/shell/testcases/packetpath/vlan_8021ad_tag
ip link add veth0 netns $ns1 type veth peer name veth0 netns $ns2
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
We ended up with two lxc fragments when meta-virtualization
was sync'd to the kernel-cache
We can make our existing feature include the new one and
nothing will break.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
1/1 [
Author: Bruce Ashfield
Email: bruce.ashfield@gmail.com
Subject: aufs: adjust for v6.9+
Date: Wed, 3 Apr 2024 10:15:47 -0400
The following commit drops SLAB_MEM_SPREAD, so we remove it
from aufs.
commit cdeeaaba174886aa6c1ff4c0c5449c5066dbe82f
Author: Vlastimil Babka <vbabka@suse.cz>
Date: Fri Feb 23 19:27:17 2024 +0100
mm, slab: deprecate SLAB_MEM_SPREAD flag
The SLAB_MEM_SPREAD flag used to be implemented in SLAB, which was
removed. SLUB instead relies on the page allocator's NUMA policies.
Change the flag's value to 0 to free up the value it had, and mark it
for full removal once all users are gone.
Reported-by: Steven Rostedt <rostedt@goodmis.org>
Closes: https://lore.kernel.org/all/20240131172027.10f64405@gandalf.local.home/
Reviewed-and-tested-by: Xiongwei Song <xiongwei.song@windriver.com>
Reviewed-by: Chengming Zhou <chengming.zhou@linux.dev>
Reviewed-by: Roman Gushchin <roman.gushchin@linux.dev>
Acked-by: David Rientjes <rientjes@google.com>
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Several nftables ptest testcases failed due to missing features. The
following kernel configuration options are added as part of the missing
features:
- NFT_FIB_INET (tristate "Netfilter nf_tables fib inet support")
This option allows using the FIB expression from the inet table.
The lookup will be delegated to the IPv4 or IPv6 FIB depending
on the protocol of the packet.
- NFT_FIB_IPV4 (tristate "nf_tables fib / ip route lookup support")
This module enables IPv4 FIB lookups, e.g. for reverse path filtering.
It also allows query of the FIB for the route type, e.g. local, unicast,
multicast or blackhole.
- NFT_FIB_IPV6 (tristate "nf_tables fib / ipv6 route lookup support")
This module enables IPv6 FIB lookups, e.g. for reverse path filtering.
It also allows query of the FIB for the route type, e.g. local, unicast,
multicast or blackhole.
Adding those three kernel configuration options above pass the following
ptest testcases:
- tests/shell/testcases/parsing/large_rule_pipe
Previously failed due to using rule:
meta nfproto ipv6 fib saddr . iif oif missing drop
- tests/shell/testcases/nft-f/sample-ruleset
Previously failed due to using rules:
fib saddr . iif oif eq 0 counter drop
fib daddr type { broadcast, multicast, anycast } counter drop
fib daddr type { broadcast, multicast, anycast } counter drop
fib daddr type { broadcast, multicast, anycast } counter drop
- tests/shell/testcases/optimizations/ruleset
Previously failed due to using rule:
fib daddr type broadcast drop
Signed-off-by: William Lyu <William.Lyu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Starting from kernel v6.2 (including all rc versions),
CONFIG_NFT_OBJREF has become builtin and cannot be disabled [1]. So,
this configure option is removed from nf_tables.cfg.
References
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d037abc2414b4539401e0e6aa278bedc4628ad69
Signed-off-by: William Lyu <William.Lyu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Enable the ThunderX EDAC support.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
This is both used as a PCIe card, but is also often the virtual hardware
in VMs.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Add more config options so that the Xilinx KV260 is fully supported.
This work was done by Bill Mills <bill.mills@linaro.org>, I simply
integrated it.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Add the required options so that this BSP works on the Marvell ThunderX2.
Thanks to anton.antonov@arm.com for the config and testing.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Thanks to anton.antonov@arm.com.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Add more hardware enabling so that NXP i.MX8M boards boot successfully.
Thanks to anton.antonov@arm.com for the options and testing.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
SBCs don't tend to use SATA, but larger platforms will.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
If these are kernel modules then there's a WARN_ON triggered when booted
on IMX boards.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
With CONFIG_I2C_DEV=m you must modprobe that module in order to get the
/dev nodes. It is a small module (~8.5K) so just include it in.
Signed-off-by: Bill Mills <bill.mills@linaro.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
A bug in my annotation script meant this item ended up in the wrong place.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Some .cfg files were included accidentally, fix this.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Add MULTIQ and NET_EMATCH config.
Signed-off-by: Xiaolei Wang <xiaolei.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Add xdp feature config.
Signed-off-by: Xiaolei Wang <xiaolei.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
ixgb driver was removed in kernel commit e485f3a6eae0
("ixgb: Remove ixgb driver").
Signed-off-by: Yongxin Liu <yongxin.liu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
CONFIG_VFIO_MDEV wasn't a user choice after kerne commit
8bf8c5ee1f38 ("vfio-mdev: turn VFIO_MDEV into a selectable symbol").
Signed-off-by: Yongxin Liu <yongxin.liu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
CONFIG_VFIO_VIRQFD was changed to bool in kernel commit
e2d55709398e ("vfio: Fold vfio_virqfd.ko into vfio.ko") and
it is not user selectable.
Signed-off-by: Yongxin Liu <yongxin.liu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
intel-x86-64-preempt-rt.cfg was removed in commit bd20a636b044
("config: remove mis-located configuration fragment").
Signed-off-by: Yongxin Liu <yongxin.liu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
This is required to enable the hugetlb cgroup.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Add CONFIG_CGROUP_BPF to ensure docker can be started under cgroup v2,
otherwise it would report the following error:
Error: for ... error setting cgroup config for procHooks process:
bpf_prog_query(BPF_CGROUP_DEVICE) failed: invalid argument: unknown
Cgroup v2 device controller has no interface files and is implemented on top
of cgroup BPF. To control access to device files, a user may create bpf programs
of type BPF_PROG_TYPE_CGROUP_DEVICE and attach them to cgroups with
BPF_CGROUP_DEVICE flag.
Signed-off-by: Xiangyu Chen <xiangyu.chen@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
This brings it closer to other qemu configs in yocto and help to use usb
mouse and keyboard device emulation
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Pull in a large number of drivers and build them as modules. The set of
drivers enabled is based on the current defconfig.
Some chunks are split out into separate files to keep the top-level
cfg file size manageable.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
NO_HZ was obsoleted in 2011[1] and simply selects NO_HZ_IDLE.
[1] linux 3ca277e
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
This will enable kernel options for Intel Sound Open Firmware support,
only fewer Intel platforms use Soundwire audio by default, but when SOF
enabled, this will replace HD audio driver which most of Intel boards
used. So we need enable it carefully only for some specific boards.
Signed-off-by: Liwei Song <liwei.song@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Adjust KARCH to x86_64 and i386 accordingly to avoid condition
check failed in some scc files like features/thermal/coretemp.scc
This will ensure some kernel options be correcly set for intel-x86
bsp.
Signed-off-by: Liwei Song <liwei.song@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Add the skeleton of an initial genericarm64 kernel.
At present this has only been boot tested on a BeaglePlay and is missing
some functionality, but it does boot via EFI from SD card successfully.
Future work will organise the configuration fragments more neatly,
move more options to modules, increase functionality, and add support
for more boards.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Otherwise the audit will notice that "y " was requested but "y" was set.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
This was removed in kernel a9ee6cf (5.14 onwards).
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Consider this 5+ year old commit
commit bcbc7bbc4fb967d8d4ae6333f71b73491a80b94e
Author: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Date: Thu Mar 1 16:00:41 2018 +0200
latencytop: remove recipe
Last commit and release were in 2009; website is down; it's a dead project.
(From OE-Core rev: 36aae56e7f86a4d5ce93e4528e7dcc42f60c705e)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Given that, it seems sensible to drop it from default inclusion across
the BSPs. I've left the feature itself, so anyone who still cares can
easily manually add it still.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
The x86-64 BSP isn't quite the same as the "more specific" BSP like a
Beaglebone Black or the (now deleted) Edgerouter. Where we have exact
hardware specifics for boards like those, the x86-64 BSP is more of a
"generic" thing used as the baseline across an endless sea of boards.
To that end, this is somewhat a revert of commit bd77e1f904f6
("bsp/intel-x86: change the supported maximum number of CPUs to 512 in 64-bit bsp")
It is great that a handful of people out there are using Yocto on these
huge server machines, but that doesn't reflect 99% of the rest of us who
continue to lean towards the original "embedded theme" of Yocto.
That means a whole bunch of extra per-CPU jumping through hoops; some
can be mitigated by booting with "nr_cpus=4" (or whatever the core count
is) but I guarantee largely nobody out there is doing that.
Let those users with the crazy CPU count own that config customization
locally. The default is 64 which still seems way too large IMHO, but
at least we are moving in the right direction.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Similar to the argument of why we shouldn't force NUMA on everyone, the
9 chip registered ECC RAM type stuff also tends to be found mostly on
larger server type stuff and less so on embedded targets.
We already have a skeleton EDAC feature, so move the features over
there. One could argue that we might want to separate into arch
specific config fragments, but to me - that seems overkill at this
point in time.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
A user reported getting NUMA warnings like the ones reported here:
https://www.suse.com/support/kb/doc/?id=000021040
"Fail to get numa node for CPU:0 bus:0 dev:0 fn:1"
...and repeated for every core on the platform. Distracting.
When I asked if it was a crazy big server system with multiple CPU
sockets and localized RAM near each socket - the answer was "no".
Turns out they didn't choose NUMA support - rather we did it for them.
Yocto has been and still remains more "embedded leaning". That is not
to say we can't support NUMA. We just shouldn't be enabling it by
default in the base x86-64 config fragment that everyone uses.
Move the two NUMA settings that were not in our existing numa.cfg
feature out of the BSP and into the feature.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
No functional change - just makes further reorganizations and
refactoring more easy to review/parse.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Add optee config values for inclusion in BSPs that require
support.
We'll extend this in the future via KERNEL_FEATURES and
distro feature coordination.
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
It's required at least in selftest to test read-only file systems.
Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
According to the kernel self protection page[1], add recommended options to
features/security for aarch64/arm64.
Ref:
[1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings#arm64
Signed-off-by: Xiangyu Chen <xiangyu.chen@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
These commits were unlinked by commenting them out back in 2015:
commit d341564a1ff749f87cfc9b2819b2759903c1efba
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Thu Jul 16 15:08:13 2015 -0400
qemuppc: remove old PREP platform patches
We've been using the MAC99 platform for some time now, there's no need
to carry the old PReP platform patches.
We can safely push them off a cliff now, some 9-ish years later.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|