From: Vignesh Raman <vignesh.raman@collabora.com>
To: Maxime Ripard <mripard@kernel.org>,
Helen Koike <helen.fornazier@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v2] drm/ci: Add CI pipeline for drm-misc branches
Date: Mon, 19 Oct 2026 15:30:54 +0530 [thread overview]
Message-ID: <9e1fc5c6-53ff-4a4d-9744-77bcf6a0325e@collabora.com> (raw)
In-Reply-To: <20260911-drm-drm-misc-ci-v2-1-1847f89585cb@kernel.org>
Hi,
On 11/09/26 17:48, Maxime Ripard wrote:
> The DRM CI infrastructure builds upon Mesa's CI to run IGT tests on
> hardware. Its focus is on functional testing on a selected number of
> targets.
>
> The concern for drm-misc is different: it merges a large number of
> patches across many platforms, and build or unit test breakages happen
> on a regular basis. Adding build and unit testing for drm-misc has been
> on the back of our minds, and a first attempt was made last year. The
> feedback was to rely more on the existing infrastructure.
>
> Introduce a CI entry point that runs on pushes to drm-misc-next,
> drm-misc-fixes, and drm-misc-next-fixes. It reuses kunit.yml,
> check-devicetrees.yml, and the freedesktop ci-templates, while defining
> build templates inline to avoid pulling in the Mesa pipeline.
>
> A single Debian container with LLVM handles cross-compilation to all
> three architectures. The pipeline compiles the kernel using defconfigs
> from the drm/tip rerere-cache branch, runs the DRM KUnit tests, and
> checks device tree bindings.
>
> Link: https://lore.kernel.org/all/20250319-greedy-sturgeon-from-avalon-ac758f@houat/
> Acked-by: Vignesh Raman <vignesh.raman@collabora.com>
> Signed-off-by: Maxime Ripard <mripard@kernel.org>
> ---
> Changes in v2:
> - Run dt_bindings_check
> - Run on push instead of MR after some discussions with Dave and Sima
> - Test run here: https://gitlab.freedesktop.org/mripard/kernel/-/pipelines/1744733
> - Link to v1: https://lore.kernel.org/r/20260902-drm-drm-misc-ci-v1-1-49d05e228eab@kernel.org
Acked-by: Vignesh Raman <vignesh.raman@collabora.com>
Regards,
Vignesh
> ---
> drivers/gpu/drm/ci/drm-misc-ci.yml | 147 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 147 insertions(+)
>
> diff --git a/drivers/gpu/drm/ci/drm-misc-ci.yml b/drivers/gpu/drm/ci/drm-misc-ci.yml
> new file mode 100644
> index 000000000000..4ab87547794e
> --- /dev/null
> +++ b/drivers/gpu/drm/ci/drm-misc-ci.yml
> @@ -0,0 +1,147 @@
> +# CI pipeline for drm-misc-next, drm-misc-fixes, and drm-misc-next-fixes.
> +#
> +# Runs on pushes to drm-misc-next, drm-misc-fixes, and
> +# drm-misc-next-fixes. Compiles the kernel for arm, arm64, and
> +# x86_64, runs the DRM KUnit tests, and checks device tree bindings.
> +#
> +# A single container image is built using freedesktop ci-templates with
> +# the packages needed for kernel compilation and LLVM for
> +# cross-compilation. QEMU is installed at runtime by the KUnit jobs.
> +#
> +# check-devicetrees.yml and kunit.yml are included directly. build.yml
> +# and the Mesa container/build pipelines are not:
> +# they pull in hundreds of Mesa-specific jobs and templates that would
> +# each need to be individually stubbed or disabled. The build templates
> +# (.build:arm32, .build:arm64, .build:x86_64) are defined inline.
> +
> +variables:
> + CI_TEMPLATES_COMMIT: &ci-templates-commit aec7a6ce7bb38902c70641526f6611e27141784a
> + # Project whose container registry stores the built images
> + FDO_UPSTREAM_REPO: mripard/kernel
> + KERNEL_BUILD_CONTAINER_TAG: "2026-09-11-01"
> + LLVM_VERSION: "19"
> +
> +default:
> + before_script: []
> +
> +include:
> + - project: 'freedesktop/ci-templates'
> + ref: *ci-templates-commit
> + file:
> + - '/templates/debian.yml'
> + - local: drivers/gpu/drm/ci/check-devicetrees.yml
> + - local: drivers/gpu/drm/ci/kunit.yml
> +
> +stages:
> + - container
> + - build
> + - static-checks
> + - kunit
> +
> +# --- Pipeline rules ---
> +workflow:
> + rules:
> + - if: $CI_PIPELINE_SOURCE == "push" && $CI_COMMIT_BRANCH =~ /^drm-misc-(next|fixes|next-fixes)$/
> + when: always
> +
> +# kunit.yml's jobs inherit .build-rules through the .build:* chain.
> +# Pass everything through since the pipeline is already gated by
> +# workflow:rules.
> +.build-rules:
> + rules:
> + - when: on_success
> +
> +# --- Container build job ---
> +# Single container with all build tools. LLVM handles cross-compilation
> +# to arm and arm64, so no architecture-specific containers are needed.
> +debian/kernel-build:
> + extends: .fdo.container-build@debian
> + stage: container
> + variables:
> + FDO_DISTRIBUTION_VERSION: trixie
> + FDO_DISTRIBUTION_TAG: "${KERNEL_BUILD_CONTAINER_TAG}"
> + FDO_DISTRIBUTION_PACKAGES: >-
> + bc bison ca-certificates cpio curl
> + clang-${LLVM_VERSION} flex gcc gzip
> + lld-${LLVM_VERSION} llvm-${LLVM_VERSION}
> + libelf-dev libssl-dev
> + make perl pkg-config
> + python3 python3-dev python3-pip python3-venv
> + swig xz-utils yamllint
> +
> +# --- Build templates ---
> +# Stubs for templates referenced by check-devicetrees.yml. The
> +# originals live in build.yml and container.yml which we do not
> +# include.
> +.build:
> + extends: .build-rules
> +
> +.use-debian/x86_64_build:
> + extends: .build-base
> +
> +.build-base:
> + image: "${CI_REGISTRY}/${FDO_UPSTREAM_REPO}/debian/trixie:${KERNEL_BUILD_CONTAINER_TAG}"
> + needs: ["debian/kernel-build"]
> +
> +.build:arm32:
> + extends: .build-base
> + variables:
> + KERNEL_ARCH: "arm"
> + DEFCONFIG_ARCH: "arm"
> +
> +.build:arm64:
> + extends: .build-base
> + variables:
> + KERNEL_ARCH: "arm64"
> + DEFCONFIG_ARCH: "arm64"
> +
> +.build:x86_64:
> + extends: .build-base
> + variables:
> + KERNEL_ARCH: "x86_64"
> + DEFCONFIG_ARCH: "x86"
> +
> +# --- Kernel-wide build jobs (LLVM) ---
> +.kernel-build:
> + stage: build
> + timeout: 45m
> + variables:
> + GIT_DEPTH: 1
> + DEFCONFIG_URL: https://gitlab.freedesktop.org/drm/tip/-/raw/rerere-cache/drm-misc-${DEFCONFIG_ARCH}_defconfig
> + artifacts: {}
> + before_script:
> + - drivers/gpu/drm/ci/setup-llvm-links.sh
> + - curl -L --retry 4 -f --retry-all-errors --retry-delay 60 -o .config "${DEFCONFIG_URL}"
> +
> +kernel-build:arm32:
> + extends: [.build:arm32, .kernel-build]
> + script:
> + - make ARCH=arm LLVM=1 olddefconfig
> + - make ARCH=arm LLVM=1 -j$(nproc)
> +
> +kernel-build:arm64:
> + extends: [.build:arm64, .kernel-build]
> + script:
> + - make ARCH=arm64 LLVM=1 olddefconfig
> + - make ARCH=arm64 LLVM=1 -j$(nproc)
> +
> +kernel-build:x86_64:
> + extends: [.build:x86_64, .kernel-build]
> + script:
> + - make ARCH=x86 LLVM=1 olddefconfig
> + - make ARCH=x86 LLVM=1 -j$(nproc)
> +
> +# --- Disable dtbs-check jobs ---
> +# dtbs-check validates compiled DTBs which may produce warnings from
> +# code we are not responsible for. Keep dt-binding-check only.
> +dtbs-check:arm32:
> + rules:
> + - when: never
> +
> +dtbs-check:arm64:
> + rules:
> + - when: never
> +
> +# --- KUnit jobs ---
> +# kunit:arm32, kunit:arm64, and kunit:x86_64 are defined in kunit.yml
> +# and implicitly enabled here through the .build:* templates above.
>
> ---
> base-commit: 99c95ce1b07081d7944d637ba7d72d835c0d520a
> change-id: 20260902-drm-drm-misc-ci-ec6c69506609
>
> Best regards,
next prev parent reply other threads:[~2026-10-19 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 12:18 Maxime Ripard
2026-10-19 10:00 ` Vignesh Raman [this message]
2026-10-19 14:26 ` Maxime Ripard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e1fc5c6-53ff-4a4d-9744-77bcf6a0325e@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=helen.fornazier@gmail.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=maarten.lankhorst@linux.intel.com \
--cc=morbo@google.com \
--cc=mripard@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®