<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-virtualization.git/recipes-kernel, branch master-test</title>
<subtitle>Mirror of git.yoctoproject.org/meta-virtualization</subtitle>
<id>https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=master-test</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=master-test'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/'/>
<updated>2021-07-23T13:09:56+00:00</updated>
<entry>
<title>virtualization/config: allow conditional use of yocto-cfg-fragments</title>
<updated>2021-07-23T13:09:56+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-06-17T03:10:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=8db75f2809318cfb4dbe1c6873c5a6bcfefc4d8c'/>
<id>urn:sha1:8db75f2809318cfb4dbe1c6873c5a6bcfefc4d8c</id>
<content type='text'>
To help enforce/guide consistent configuration and to avoid duplicating
configuration fragments into the meta-virt layer, we leverage a native
provider of the yocto-kernel-cache fragment repository.

To allow support for kernels that support fragments, but don't have the
yocto-kernel-cache in the kernel's SRC_URI, we create two conditional
parts of the virtualization configuration.

If virtualization is enabled in the distro features, the kernel
version matches one of our supported ones, and the kernel inherits
kernel-yocto, we add a depedency on the yocto-cfg-fragments-native
recipe.

That recipe will install the fragment collection to the kernel recipe's
native sysroot.

We can then check for the kernel-cache on the SRC_URI. If it is present,
we use the feature at the standard location. If it is not present, we
add the fragment from the native sysroot.

While we could always use the native sysroot variant, we want to allow
a kernel with a kernel-cache to be the first choice, and provide their
own fragments.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>yocto-cfg-fragments: introduce native provider of configuration fragments</title>
<updated>2021-07-23T13:09:56+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-06-17T03:10:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=44db8ee6ddf7c9eb1b5ffb22e9b83b3840997da9'/>
<id>urn:sha1:44db8ee6ddf7c9eb1b5ffb22e9b83b3840997da9</id>
<content type='text'>
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>k8s/k3s: add kernel configuration features</title>
<updated>2021-03-16T03:15:42+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2020-11-06T16:03:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=ba3ece52b3f05ff1abb0fa340a4ea0c92e59507f'/>
<id>urn:sha1:ba3ece52b3f05ff1abb0fa340a4ea0c92e59507f</id>
<content type='text'>
We already have docker and some other fragments that are relevant to
k3s/k8s, but the addition of ipset as a depends for k3s highlights
that we should have a reference configuration that sets all the options
for proper opration and runtime dependencies.

When k8s or k3s are distro features, we'll apply the new fragment to
any kernel that supports fragments (and matches the supported
versions).

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>kernel: drop 5.8 configs</title>
<updated>2021-01-16T03:50:49+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-01-16T03:50:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=eabacfd2486bf4cc3cd6adf80e8ef8733f599f02'/>
<id>urn:sha1:eabacfd2486bf4cc3cd6adf80e8ef8733f599f02</id>
<content type='text'>
The 5.8 kernel is being dropped in oe-core, which means we don't
test the 5.8 integration any more .. so we drop the .inc for the
configs.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>kernel: add 5.10 include file</title>
<updated>2021-01-05T21:34:32+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2021-01-05T21:33:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=29a8122f479c7ae1a7200f4f0e692b5af8283209'/>
<id>urn:sha1:29a8122f479c7ae1a7200f4f0e692b5af8283209</id>
<content type='text'>
oe-core now has a 5.10 reference kernel, so we need a 5.10 include
file to pick up our configurations.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>linux-yocto: add cgroup-hugetlb config</title>
<updated>2020-11-19T16:07:33+00:00</updated>
<author>
<name>Tim Orling</name>
<email>ticotimo@gmail.com</email>
</author>
<published>2020-11-15T03:49:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=fbfced367daaca778bda733f11c36973577c2456'/>
<id>urn:sha1:fbfced367daaca778bda733f11c36973577c2456</id>
<content type='text'>
Add kernel config fragment for CONFIG_CGROUP_HUGETLB

This is a recommended config for Kubernetes and k8s
will throw a warning if it is not present.

Signed-off-by: Tim Orling &lt;ticotimo@gmail.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>kernel: fix conditional application of fragments</title>
<updated>2020-10-08T22:33:41+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2020-10-08T22:33:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=5be8686e659c42985fb6ee22dd6a6152735f414e'/>
<id>urn:sha1:5be8686e659c42985fb6ee22dd6a6152735f414e</id>
<content type='text'>
using bb.utils.contains wasn't able to match on the substring
"type=kmeta" to enable the conditional inclusion of fragments
and KERNEL_FEATURES.

We switch to a python string only method so we can fix the
fragment application

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>kernel: add 5.8 linux-yocto include file</title>
<updated>2020-10-06T18:20:38+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2020-10-06T18:20:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=9cdcd3ee8d1f65ccd69a1af9ca9e0e03566d95ac'/>
<id>urn:sha1:9cdcd3ee8d1f65ccd69a1af9ca9e0e03566d95ac</id>
<content type='text'>
Adding the version specific include for linux-yocto 5.8.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>config: make kernel meta data include more specific</title>
<updated>2020-10-06T18:16:24+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2020-10-06T18:16:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=47425c21c7314a258752004eb75c72f724c3c2e0'/>
<id>urn:sha1:47425c21c7314a258752004eb75c72f724c3c2e0</id>
<content type='text'>
Rather than only matching on the major/minor version, we should also
check that the SRC_URI contains a "type=kmeta", to indicate that a
kernel-meta data repository is available.

This allows fragment enabled kernels, that don't want to use the
main kernel meta data repository to not throw an error (when their
version matches one of the reference kernels).

This can potentially mask runtime issues (since kernel configuration
options may not be present in the final kernel), but it makes the
layer more usable, so we take the tradeoff.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>lxc: drop RT_GROUP_SCHED</title>
<updated>2020-07-13T12:40:38+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2020-07-06T09:00:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=cc25d8efd8d5ab03e8d0db2bd456ff0060e781ad'/>
<id>urn:sha1:cc25d8efd8d5ab03e8d0db2bd456ff0060e781ad</id>
<content type='text'>
The group scheduling options in the lxc fragment were initially
used to support performance guaranteed systems using containers.

This option now causes issues with systemd runtimes and the
original feature it implemented is no longer relevant

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
</feed>
