From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2413E2D239D for ; Fri, 19 Sep 2025 08:41:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758271317; cv=none; b=t0P5PJ/hWsUUT4VFbBbZtzuF26zCKvclQpCX53EUph+jO5N8zHFQdOAveP0wJKW2t+zne+C/CWrFWTFLGfhl8+ribDMrtK/ND7p/nG1E5TC9sPkOOLIX6ujEZDuTWeXf9Rdp/fLGi4AHWqs7UYxz43auWgBXWwr0dF4h22kb//A= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758271317; c=relaxed/simple; bh=RS1EOgFBBuh/sAvZIPvDgqQGS4+zn5Ue4VpcLSZzKk4=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=HK/5gwXTt2BKniCFsRLRW2T9sacls6EWsdtpMeBVQGBLOeqxNLQ744TxVpHN3d8Vl1Ad3XIhFsTLJh2oqYSIDg1kjPy9KxfCPTWzsqN9MZfMXBPbUjCAVedux3EOJRzy/J83FSxSjHLE/wKlRcMJMWvHJsBm/1b1nKr5fW8cVpw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=eZWIhIsl; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="eZWIhIsl" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C9194C4CEF0; Fri, 19 Sep 2025 08:41:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1758271316; bh=RS1EOgFBBuh/sAvZIPvDgqQGS4+zn5Ue4VpcLSZzKk4=; h=Date:Reply-To:Subject:To:Cc:References:From:In-Reply-To:From; b=eZWIhIslFzec5N2/FAzZFICtnMN/PX4EaXUUEUjr0BhiDTHL8i7HC+QO/mStrOr9k KLlgsFNbfKcX/gvICntqZAAPwF0IpaGKBNkmqJpG0qb3zjMCcB06fAo/p15XIlwYie 2MP3ST+1KEZMhR0kHI0j2Jf53JB9jwSaj7/PJtxUIYKBbecgu2obpXbCABTqQINKcA E65AMMBs4BA0mPGMRKoTEzLSvSmZ75iJLaZA/ZHVUXg5vcO+jn+u2N8aAADS5JxBe9 zdbu0eHF9m8+QzQ6V7EDwMX3FOFhJZ4KgR8mYvfw6R21VcjvEYR4i8THXmGXtprH1N jIAkeW/CBD67w== Message-ID: Date: Fri, 19 Sep 2025 10:41:53 +0200 Precedence: bulk X-Mailing-List: kdevops@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Reply-To: Daniel Gomez Subject: Re: [PATCH 0/3] Add configuration fragment support to kdevops To: Luis Chamberlain Cc: Chuck Lever , kdevops@lists.linux.dev, Daniel Gomez References: <20250917-kdevops-fragment-support-v1-0-72cb56bc12b6@samsung.com> Content-Language: en-US From: Daniel Gomez Organization: kernel.org In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 18/09/2025 23.19, Luis Chamberlain wrote: > On Wed, Sep 17, 2025 at 02:29:17PM +0200, Daniel Gomez wrote: >> This series introduces Linux kernel-style configuration fragment support >> to kdevops, enabling flexible configuration composition and better >> maintainability. >> >> * Import merge_config.sh from Linux kernel for fragment merging >> * Update scripts/config with latest upstream fixes (v5.11 -> v6.15) >> * Add practical VM configuration fragments for guest scaling >> >> Benefits: >> - Modular configuration: Compose complex configs from reusable fragments >> - Better maintainability: Separate concerns (VM sizing, features, workflows) >> - Flexible deployment: Mix and match fragments for different scenarios >> - Upstream compatibility: Uses standard Linux kernel tooling >> >> Usage example: >> >> * Minimal development VM + diy enablement: >> make dynamic_pcipassthrough_kconfig KDEVOPS_ENABLE_PCIE_KCONFIG=1 >> make defconfig-sysbench-mysql-atomic-tps-variability >> ./scripts/kconfig/merge_config.sh -n .config \ >> ./defconfigs/configs/vm2g2c.config >> ./defconfigs/configs/diy.config \ >> >> This builds on the kconfig environment discussion [1] and provides an >> alternative to the SAT solver solution. >> >> Link: https://lore.kernel.org/kdevops/20250704-b4-params-v1-1-42dd4ff478b3@samsung.com/ [1] >> >> Signed-off-by: Daniel Gomez > > This is nice, but does it scale? I don't think so. 100%. That said, there isn't much difference between our defconfigs/* and fragments. A fragment is simply a reusable piece of configuration that we repeat across all defconfigs. For example, this allows users to combine xfs defconfigs + vm configuration. > So my ask would be to > see if you can integrate the pico SAT patches to our shared kconfig tree > tree first under a new branch which branches out of the origin/yamlconfig > branch. Then merge that to kdevops and evaluate what a true SAT solver > can do. This let's us essentially lead the way forward for Linux. I already have higher priority tasks on my plate right now (CI). Let's make a plan instead. I believe Chuck was putting together a task list for terraform. Would it help to have a global backlog for tasks to do? > > The experiences we learn can be brought back to Linux. > > Luis