[AUTOPATCHER-kernel] Kernel upgrade to version 6.6.76.1 - branch 3.0-dev

[CBL-Mariner-Bot]

[AUTOPATCHER-kernel] Kernel upgrade to version 6.6.76.1 - branch 3.0-dev
Upgrade pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=732782&view=results

Updated Builds
BB - in progress
full build- (in progress)
[BVT tests] (in progress)

AMD

*** Smoke Testing Kernel 6.6.76.1-1.azl3 (est. < 1 min) ***
PASS: Kernel version matches the running kernel version.
PASS: eth0 interface is up.
PASS: iptables service is running.
Boot times:
Startup finished in 1.595s (kernel) + 1.442s (initrd) + 9.407s (userspace) = 12.445s 
graphical.target reached after 9.033s in userspace.
Kernel size:
-rw------- 1 root root 15036416 Feb 13 06:29 /boot/vmlinuz-6.6.76.1-1.azl3
30916	/lib/modules/6.6.76.1-1.azl3
kernel memory:
MemTotal:       32874296 kB
MemFree:        32507756 kB
MemAvailable:   32330144 kB
Total memory:
               total        used        free      shared  buff/cache   available
Mem:           32103         531       31745           8         122       31572
Swap:              0           0           0

ARM

*** Smoke Testing Kernel 6.6.76.1-1.azl3 (est. < 1 min) ***
PASS: Kernel version matches the running kernel version.
PASS: eth0 interface is up.
PASS: iptables service is running.
Boot times:
Startup finished in 2.246s (kernel) + 1.360s (initrd) + 4.853s (userspace) = 8.460s 
graphical.target reached after 4.593s in userspace.
Kernel size:
-rw------- 1 root root 48718336 Feb 13 07:02 /boot/vmlinuz-6.6.76.1-1.azl3
49196	/lib/modules/6.6.76.1-1.azl3
kernel memory:
MemTotal:       395447196 kB
MemFree:        392638160 kB
MemAvailable:   391086032 kB
Total memory:
               total        used        free      shared  buff/cache   available
Mem:          386178        4258      383435           1         173      381919
Swap:              0           0           0

[rlmenge]

Result of microsoft/CBL-Mariner-Linux-Kernel@b7c3fd6

This is a new option seperates out ZRAM access time tracking or "ac-time tracking" which was previously a part of the memory tracking option. It is selected if ZRAM_MEMORY_TRACKING is enabled which is on in ARM64 but not in x86_64

[rlmenge]

Keeping off to stay inline with what was previously present for x86_64

[rlmenge]

Moved as a result of microsoft/CBL-Mariner-Linux-Kernel@5cfadda

[rlmenge]

Same as in config
Result of microsoft/CBL-Mariner-Linux-Kernel@b7c3fd6

This is a new option seperates out ZRAM access time tracking or "ac-time tracking" which was previously a part of the memory tracking option. It is selected if ZRAM_MEMORY_TRACKING is enabled which is on in ARM64 but not in x86_64.

[rlmenge]

Keeping on to stay inline with what was previously present for aarch64

[rlmenge]

Result of microsoft/CBL-Mariner-Linux-Kernel@acefaa6

The config_aarch64 sets DRM_MEDIATEK which previously selected MTK_SMI . MTK_SMI is still available at https://github.com/microsoft/CBL-Mariner-Linux-Kernel/blob/rolling-lts/mariner-3/6.6.76.1/drivers/memory/Kconfig#L183

[rlmenge]

This only selectable now by

  │   - MTK_IOMMU [=n] && IOMMU_SUPPORT [=y] && (ARCH_MEDIATEK [=y] || COMPILE_TEST [=n])                                                                                                                                  
  │   - MTK_IOMMU_V1 [=n] && IOMMU_SUPPORT [=y] && ARM && (ARCH_MEDIATEK [=y] || COMPILE_TEST [=n]) 

Which would require turning on MTK_IOMMU or MTK_IOMMU_V1 .

[rlmenge]

In order to keep CONFIG_MTK_SMI we need to enable

CONFIG_MTK_IOMMU=m 
CONFIG_IOMMU_IO_PGTABLE_ARMV7S=y
# CONFIG_IOMMU_IO_PGTABLE_ARMV7S_SELFTEST is not set

I tested the kernel modules' size using du -s /lib/modules/$(uname -r) (default unit appears to be KB) and vmlinuz size difference and saw ~64KB increase

Without CONFIG_MTK_SMI

49164   /lib/modules/6.6.76.1-1.azl3
-rw------- 1 root root 48718336 Feb 11 02:38 /boot/vmlinuz-6.6.76.1-1.azl3

With CONFIG_MTK_SMI

49228  /lib/modules/6.6.76.1-1001.azl3
-rw------- 1 root root 48718336 Feb 12 18:55 /boot/vmlinuz-6.6.76.1-1001.azl3

[rlmenge]

Keeping CONFIG_MTK_SMI to stay inline with previous offerings