Arena/019f954b android kernel xiaomi sm6150

.github/workflows/build-kernel.yml

@@ -0,0 +1,164 @@
+name: Build SM6150 Kernel (ARM64, Manual)
+
+# ------------------------------------------------------------------
+# MANUAL TRIGGER ONLY. No push/pull_request/schedule triggers exist,
+# so this workflow will never run automatically. Trigger it from:
+# Repo -> Actions tab -> "Build SM6150 Kernel (ARM64, Manual)" -> "Run workflow"
+# ------------------------------------------------------------------
+on:
+  workflow_dispatch:
+    inputs:
+      clean_build:
+        description: "Run a clean build (sh build.sh clean)"
+        required: true
+        type: boolean
+        default: true
+
+jobs:
+  build:
+    # Native ARM64 hosted runner (no QEMU emulation).
+    runs-on: ubuntu-24.04-arm
+
+    steps:
+      - name: Checkout kernel source
+        uses: actions/checkout@v4
+        with:
+          ref: arena/019f954b-android-kernel-xiaomi-sm6150
+          fetch-depth: 1  # shallow clone, we don't need full git history
+
+      - name: Free up disk space on runner
+        run: |
+          echo "Disk usage before cleanup:"
+          df -h /
+          sudo rm -rf /usr/share/dotnet /usr/local/lib/android /opt/ghc \
+                      /opt/hostedtoolcache/CodeQL /usr/local/.ghcup \
+                      /usr/local/share/boost "$AGENT_TOOLSDIRECTORY" 2>/dev/null || true
+          sudo docker image prune --all --force 2>/dev/null || true
+          echo "Disk usage after cleanup:"
+          df -h /
+
+      - name: Restore ccache
+        uses: actions/cache@v4
+        with:
+          path: ~/.ccache
+          # Exact key almost never hits (tied to this commit), so it falls back
+          # to the newest restore-key below and reuses the last successful cache.
+          # A fresh cache entry is saved under the exact key at the end of the job.
+          key: ccache-${{ runner.os }}-arm64-${{ github.sha }}
+          restore-keys: |
+            ccache-${{ runner.os }}-arm64-
+
+      - name: Install build dependencies
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y --no-install-recommends \
+            build-essential bc bison flex libssl-dev libelf-dev \
+            python3 zip unzip git curl kmod cpio rsync ccache \
+            device-tree-compiler gcc-aarch64-linux-gnu gcc-arm-linux-gnueabi
+
+      - name: Configure ccache
+        run: |
+          ccache --max-size=3G
+          ccache --zero-stats
+          echo "CCACHE_DIR=$HOME/.ccache" >> "$GITHUB_ENV"
+
+      - name: Patch build.sh (nproc for JOBS, wrap compiler calls with ccache)
+        run: |
+          # JOBS=1 is hardcoded in the script -> single-threaded build. Use all cores instead.
+          sed -i 's/^JOBS=1$/JOBS=$(nproc --all)/' build.sh
+
+          # Route CC / HOSTCC through ccache so repeated builds reuse cached objects.
+          sed -i 's|CC=\${CLANG_PATH}/clang \\|CC="ccache ${CLANG_PATH}/clang" \\|g' build.sh
+          sed -i 's|HOSTCC=\${CLANG_PATH}/clang \\|HOSTCC="ccache ${CLANG_PATH}/clang" \\|g' build.sh
+
+          echo "----- JOBS line -----"
+          grep -n '^JOBS=' build.sh
+          echo "----- CC / HOSTCC lines -----"
+          grep -n 'CC=' build.sh
+          echo "Runner has $(nproc --all) cores available"
+          chmod +x build.sh
+
+      - name: Run kernel build
+        id: build
+        run: |
+          set -o pipefail
+          if [ "${{ github.event.inputs.clean_build }}" = "true" ]; then
+            ./build.sh clean 2>&1 | tee build.log
+          else
+            ./build.sh 2>&1 | tee build.log
+          fi
+
+      - name: Show ccache stats
+        if: always()
+        run: ccache --show-stats
+
+      - name: Show output directory contents
+        if: always()
+        run: |
+          echo "----- out/ directory -----"
+          find out -maxdepth 2 -type f -name "*.zip" 2>/dev/null || echo "No zip found"
+          ls -la out/ 2>/dev/null || echo "out/ directory not found"
+
+      - name: Notify Telegram
+        if: always()
+        env:
+          BOT_TOKEN: ${{ secrets.TELEGRAM_BOT_TOKEN }}
+          CHAT_ID: ${{ secrets.TELEGRAM_CHAT_ID }}
+        run: |
+          set +e
+
+          if [ "${{ steps.build.outcome }}" = "success" ]; then
+            STATUS_EMOJI="✅"
+            STATUS_TEXT="BUILD PASSED"
+          else
+            STATUS_EMOJI="❌"
+            STATUS_TEXT="BUILD FAILED"
+          fi
+
+          RUN_URL="${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}"
+
+          MESSAGE="$(printf '%s\n%s\n%s\n%s\n%s' \
+            "${STATUS_EMOJI} ${STATUS_TEXT}" \
+            "Repo: ${{ github.repository }}" \
+            "Branch: ${{ github.ref_name }}" \
+            "Triggered by: ${{ github.actor }}" \
+            "Run: ${RUN_URL}")"
+
+          # 1) Status message
+          curl -s -X POST "https://api.telegram.org/bot${BOT_TOKEN}/sendMessage" \
+            -d chat_id="${CHAT_ID}" \
+            --data-urlencode text="${MESSAGE}"
+
+          # 2) Build log (always, if it exists)
+          if [ -f build.log ]; then
+            curl -s -X POST "https://api.telegram.org/bot${BOT_TOKEN}/sendDocument" \
+              -F chat_id="${CHAT_ID}" \
+              -F document=@build.log \
+              -F caption="Build log — ${STATUS_TEXT}"
+          fi
+
+          # 3) Kernel zip (only when the build actually succeeded and the file exists)
+          if [ "${{ steps.build.outcome }}" = "success" ] && [ -f out/Mahashunya-Kernel-Phoenix.zip ]; then
+            curl -s -X POST "https://api.telegram.org/bot${BOT_TOKEN}/sendDocument" \
+              -F chat_id="${CHAT_ID}" \
+              -F document=@out/Mahashunya-Kernel-Phoenix.zip \
+              -F caption="Mahashunya-Kernel-Phoenix.zip"
+          fi
+
+      - name: Upload build log (always, even on failure)
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: build-log
+          path: build.log
+          if-no-files-found: warn
+          retention-days: 14
+
+      - name: Upload final kernel zip
+        if: success()
+        uses: actions/upload-artifact@v4
+        with:
+          name: Mahashunya-Kernel-Phoenix
+          path: out/Mahashunya-Kernel-Phoenix.zip
+          if-no-files-found: error
+          retention-days: 30

.gitignore

@@ -130,3 +130,6 @@ kernel/configs/android-*.cfg
 #Ignoring Android.bp link file
 #
 Android.bp
+!.github/
+!.github/workflows/
+!.github/workflows/*

Documentation/ABI/testing/procfs-smaps_rollup

@@ -3,18 +3,28 @@ Date:		August 2017
 Contact:	Daniel Colascione <dancol@google.com>
 Description:
 		This file provides pre-summed memory information for a
-		process.  The format is identical to /proc/pid/smaps,
+		process.  The format is almost identical to /proc/pid/smaps,
 		except instead of an entry for each VMA in a process,
 		smaps_rollup has a single entry (tagged "[rollup]")
 		for which each field is the sum of the corresponding
 		fields from all the maps in /proc/pid/smaps.
-		For more details, see the procfs man page.
+		Additionally, the fields Pss_Anon, Pss_File and Pss_Shmem
+		are not present in /proc/pid/smaps.  These fields represent
+		the sum of the Pss field of each type (anon, file, shmem).
+		For more details, see Documentation/filesystems/proc.txt
+		and the procfs man page.
 
 		Typical output looks like this:
 
 		00100000-ff709000 ---p 00000000 00:00 0		 [rollup]
+		Size:               1192 kB
+		KernelPageSize:        4 kB
+		MMUPageSize:           4 kB
 		Rss:		     884 kB
 		Pss:		     385 kB
+		Pss_Anon:	     301 kB
+		Pss_File:	      80 kB
+		Pss_Shmem:	       4 kB
 		Shared_Clean:	     696 kB
 		Shared_Dirty:	       0 kB
 		Private_Clean:	     120 kB

Documentation/filesystems/proc.txt

@@ -147,9 +147,11 @@ Table 1-1: Process specific entries in /proc
 		symbol the task is blocked in - or "0" if not blocked.
  pagemap	Page table
  stack		Report full stack trace, enable via CONFIG_STACKTRACE
- smaps		an extension based on maps, showing the memory consumption of
+ smaps		An extension based on maps, showing the memory consumption of
 		each mapping and flags associated with it
- numa_maps	an extension based on maps, showing the memory locality and
+ smaps_rollup	Accumulated smaps stats for all mappings of the process.  This
+		can be derived from smaps, but is faster and more convenient
+ numa_maps	An extension based on maps, showing the memory locality and
 		binding policy as well as mem usage (in pages) of each mapping.
 ..............................................................................
 
@@ -349,7 +351,7 @@ Table 1-4: Contents of the stat files (as of 2.6.30-rc7)
   exit_code     the thread's exit_code in the form reported by the waitpid system call
 ..............................................................................
 
-The /proc/PID/maps file containing the currently mapped memory regions and
+The /proc/PID/maps file contains the currently mapped memory regions and
 their access permissions.
 
 The format is:
@@ -402,11 +404,14 @@ is not associated with a file:
  or if empty, the mapping is anonymous.
 
 The /proc/PID/smaps is an extension based on maps, showing the memory
-consumption for each of the process's mappings. For each of mappings there
-is a series of lines such as the following:
+consumption for each of the process's mappings. For each mapping (aka Virtual
+Memory Area, or VMA) there is a series of lines such as the following:
 
 08048000-080bc000 r-xp 00000000 03:02 13130      /bin/bash
+
 Size:               1084 kB
+KernelPageSize:        4 kB
+MMUPageSize:           4 kB
 Rss:                 892 kB
 Pss:                 374 kB
 Shared_Clean:        892 kB
@@ -428,11 +433,14 @@ Locked:                0 kB
 VmFlags: rd ex mr mw me dw
 Name:           name from userspace
 
-the first of these lines shows the same information as is displayed for the
-mapping in /proc/PID/maps.  The remaining lines show the size of the mapping
-(size), the amount of the mapping that is currently resident in RAM (RSS), the
-process' proportional share of this mapping (PSS), the number of clean and
-dirty private pages in the mapping.
+The first of these lines shows the same information as is displayed for the
+mapping in /proc/PID/maps.  Following lines show the size of the mapping
+(size); the size of each page allocated when backing a VMA (KernelPageSize),
+which is usually the same as the size in the page table entries; the page size
+used by the MMU when backing a VMA (in most cases, the same as KernelPageSize);
+the amount of the mapping that is currently resident in RAM (RSS); the
+process' proportional share of this mapping (PSS); and the number of clean and
+dirty shared and private pages in the mapping.
 
 The "proportional set size" (PSS) of a process is the count of pages it has
 in memory, where each page is divided by the number of processes sharing it.
@@ -518,6 +526,19 @@ guarantees:
 2) If there is something at a given vaddr during the entirety of the
    life of the smaps/maps walk, there will be some output for it.
 
+The /proc/PID/smaps_rollup file includes the same fields as /proc/PID/smaps,
+but their values are the sums of the corresponding values for all mappings of
+the process.  Additionally, it contains these fields:
+
+Pss_Anon
+Pss_File
+Pss_Shmem
+
+They represent the proportional shares of anonymous, file, and shmem pages, as
+described for smaps above.  These fields are omitted in smaps since each
+mapping identifies the type (anon, file, or shmem) of all pages it contains.
+Thus all information in smaps_rollup can be derived from smaps, but at a
+significantly higher cost.
 
 The /proc/PID/clear_refs is used to reset the PG_Referenced and ACCESSED/YOUNG
 bits on both physical and virtual pages associated with a process, and the

Documentation/sysctl/vm.txt

@@ -19,7 +19,10 @@ files can be found in mm/swap.c.
 Currently, these files are in /proc/sys/vm:
 
 - admin_reserve_kbytes
+- anon_min_kbytes
 - block_dump
+- clean_low_kbytes
+- clean_min_kbytes
 - compact_memory
 - compact_unevictable_allowed
 - dirty_background_bytes
@@ -98,13 +101,68 @@ Changing this takes effect whenever an application requests memory.
 
 ==============================================================
 
+anon_min_kbytes
+
+This knob provides *hard* protection of anonymous pages. The anonymous pages
+on the current node won't be reclaimed under any conditions when their amount
+is below vm.anon_min_kbytes.
+
+This knob may be used to prevent excessive swap thrashing when anonymous
+memory is low (for example, when memory is going to be overfilled by
+compressed data of zram module).
+
+Setting this value too high (close to MemTotal) can result in inability to
+swap and can lead to early OOM under memory pressure.
+
+The default value is defined by CONFIG_ANON_MIN_KBYTES.
+
+==============================================================
+
 block_dump
 
 block_dump enables block I/O debugging when set to a nonzero value. More
 information on block I/O debugging is in Documentation/laptops/laptop-mode.txt.
 
 ==============================================================
 
+clean_low_kbytes
+
+This knob provides *best-effort* protection of clean file pages. The file pages
+on the current node won't be reclaimed under memory pressure when the amount of
+clean file pages is below vm.clean_low_kbytes *unless* we threaten to OOM.
+
+Protection of clean file pages using this knob may be used when swapping is
+still possible to
+  - prevent disk I/O thrashing under memory pressure;
+  - improve performance in disk cache-bound tasks under memory pressure.
+
+Setting it to a high value may result in a early eviction of anonymous pages
+into the swap space by attempting to hold the protected amount of clean file
+pages in memory.
+
+The default value is defined by CONFIG_CLEAN_LOW_KBYTES.
+
+==============================================================
+
+clean_min_kbytes
+
+This knob provides *hard* protection of clean file pages. The file pages on the
+current node won't be reclaimed under memory pressure when the amount of clean
+file pages is below vm.clean_min_kbytes.
+
+Hard protection of clean file pages using this knob may be used to
+  - prevent disk I/O thrashing under memory pressure even with no free swap space;
+  - improve performance in disk cache-bound tasks under memory pressure;
+  - avoid high latency and prevent livelock in near-OOM conditions.
+
+Setting it to a high value may result in a early out-of-memory condition due to
+the inability to reclaim the protected amount of clean file pages when other
+types of pages cannot be reclaimed.
+
+The default value is defined by CONFIG_CLEAN_MIN_KBYTES.
+
+==============================================================
+
 compact_memory
 
 Available only when CONFIG_COMPACTION is set. When 1 is written to the file,
@@ -818,6 +876,14 @@ decrease the amount of swap.  A value of 0 instructs the kernel not to
 initiate swap until the amount of free and file-backed pages is less
 than the high water mark in a zone.
 
+This knob has no effect if the amount of clean file pages on the current
+node is below vm.clean_low_kbytes or vm.clean_min_kbytes. In this case,
+only anonymous pages can be reclaimed.
+
+If the number of anonymous pages on the current node is below
+vm.anon_min_kbytes, then only file pages can be reclaimed with
+any vm.swappiness value.
+
 The default value is 60.
 
 ==============================================================

Makefile

@@ -812,6 +812,20 @@ KBUILD_CFLAGS += $(call cc-option, -Wno-sometimes-uninitialized)
 KBUILD_CFLAGS += $(call cc-option, -Wno-pointer-to-int-cast)
 KBUILD_CFLAGS += $(call cc-option, -Wno-void-pointer-to-int-cast)
 
+# Polly Loop Optimizations
+ifeq ($(cc-name),clang)
+    POLLY_FLAGS := -mllvm -polly \
+                   -mllvm -polly-vectorizer=stripmine \
+                   -mllvm -polly-parallel \
+                   -mllvm -polly-tiling \
+                   -mllvm -polly-invariant-load-hoisting \
+                   -mllvm -polly-run-dce \
+                   -mllvm -polly-matmul-opt \
+                   -mllvm -polly-tc-opt
+
+    KBUILD_CFLAGS += $(POLLY_FLAGS)
+endif
+
 # Quiet clang warning: comparison of unsigned expression < 0 is always false
 
 KBUILD_CFLAGS += $(call cc-disable-warning, tautological-compare)