From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=209.85.221.46 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1792505275; b=DHBsp854wiUXP6VxIsh/4+/e2UobC3dQ8gI6v1aggIO5HTxvhen9+O6aFN4XFOvfG097 AHuG6P1HrI2niTpSjeDKP04NfY/lIVGSyrZKEBBNofxEn3zdLa/I6J9e9kwZe6+4JTnRu AqTNfQed9qRbHwIqnGqltDkQ8Vdcy2yb315/TsMxgQLBWfsOeMimNiGwOnGgC9MWSa+FQ maDsGo0m/kzBbfUuTThgXgzcZvFeV7A6BTIiw872jv0/ca1jV20aobX3or3v7TzrI/r/x 45Z34JU7XyuPEsvJtEh5X8iLfOtJ6oasR4pcOIHWj7mSO6wZgHBIofiNGhVr8CUc3wQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1792505275; h=DMARC-Filter:Received:DKIM-Signature:X-Google-DKIM-Signature: X-Forwarded-Encrypted:X-Gm-Message-State:X-Gm-Gg:X-Received:Received: Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; bh=o+EfFrr6u+uTNXFgvPFyR21Dr/tevP4cbAxZ6qNFw/g=; b=RydIAVxtQ14wzDAGolD6XBvJhMvQwyR04rAuwN3rdeiXDIaib8nJcQPayI0zS0Yy6LcC fsLIZKq6tLaEwtOC5fN5bzqkqcsFPC6mh7nKfEKuYAaBTB6q/xDJW8L/4cq8peyuehz2N Cfia+TCXHFkXgMUj/PHUgMIB8X+Sz2H58eRhu8WNc0+RV6WBGWJp/pEI0pkGHcBBwakXv QIwpl3Qhd3q8iPMOyKr/PkJ9vR0DyquIjqAodnxEsPuwIx1ej0UTt05n7wJH5l7yl9dAq rZVBfklncs6yaa/vrzsHmXPx3kiNIQXp2ENcvPMmg4BqbaNb8OfNEaZErvY7q7nEyyA== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none header.from=resnulli.us; spf=none smtp.mailfrom=resnulli.us; dkim=pass header.d=resnulli-us.20251104.gappssmtp.com header.i=@resnulli-us.20251104.gappssmtp.com header.a=rsa-sha256 header.s=20251104 header.b=bYnh9Nzy; arc=none smtp.remote-ip=209.85.221.46 Received: from mail-wr1-f46.google.com (mail-wr1-f46.google.com [209.85.221.46]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AF267606A324 for ; Tue, 20 Oct 2026 14:07:54 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org AF267606A324 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=resnulli.us Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=resnulli.us Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=resnulli-us.20251104.gappssmtp.com header.i=@resnulli-us.20251104.gappssmtp.com header.a=rsa-sha256 header.s=20251104 header.b=bYnh9Nzy Received: by mail-wr1-f46.google.com with SMTP id ffacd0b85a97d-48e0d1da913so696560f8f.1 for ; Tue, 20 Oct 2026 07:07:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=resnulli-us.20251104.gappssmtp.com; s=20251104; t=1792505273; x=1793110073; darn=vger.kernel.org; h=in-reply-to:content-disposition:content-type:mime-version :references:message-id:subject:cc:to:from:date:from:to:cc:subject :date:message-id:reply-to:content-type; bh=o+EfFrr6u+uTNXFgvPFyR21Dr/tevP4cbAxZ6qNFw/g=; b=bYnh9Nzyqli4bkwECf7KhQVk8jCjNLNbQzkaT8LJHZiv4XJM7PfFIFcY1VCEzrtknq 9EylpBWwbFBk22NvshQ2OoXHOhzxu/mCg2UQjEaPPH3fdtURPoKV2hoB08DUuAj5Os8W +/K5zFQrhC+iQ3fhAmcYbzV5P7yr99fEu30Z6/tsRqQxJtfen76pOCtrQVqNGfsiSEy5 HecTgNN2hp2lUa7et+pqZCg9b7fzBeyXrvZw2748bTxfZcptj0i7lobluoX0Gwi5I65C 3uRJs3KotsJzoFHlAh0kUpxPPodcH6LntlsfMsLNQZZKDzy2ukRTDU9cu0Ukxqmfaeih 3MVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1792505273; x=1793110073; h=in-reply-to:content-disposition:content-type:mime-version :references:message-id:subject:cc:to:from:date:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=o+EfFrr6u+uTNXFgvPFyR21Dr/tevP4cbAxZ6qNFw/g=; b=eFzxFy9rYr3IQnR/0v/L74vvb3BzYm2MqGjzvpP7IafwyAT/bWDUlhA2KFb1A+recX KGV+Qpw8T3STWcaCSWH35eO0lMlEoMSama5Q29iM3xpx21HKk6eyV9aLIZKFUgUhFKYe BCsFfg/p0kB2H+vL2RI6aI6mouwpshpy+6VuqTB9vML/+XWhLILC54aX1RABBxAhzHsA bqiifh+8hrvN0paS0uPX48QYdDX9t7Q4iYDljSC98o1Botdpr356csHLE1bBO5hsrrss F0plI49lCIPnpFFy1myZ29nOpJR7DuLJ/Sl1IHGY5VlSMeDhubqk5v1TJVaCK/RmayhK Nrzw== X-Forwarded-Encrypted: i=1; AKwUvBweAaIAo1vIdLQkINVjPbLqilkcdA1eqcdbBjt2gmDwpxvtor0SyKS9V48lLISphIZlccw=@vger.kernel.org X-Gm-Message-State: AFq9FYJIagppvtehmR4nW9hZ0acOHkoFteNCVDws/Ji+OT4Q2WAuQODP yGdX0/b547pDrQ1zjFBhRTMK8EbZNTvrYc+JEWE25oicDeAkp5EglTVWlfbI1X8gRTw= X-Gm-Gg: AYBFou3TFPQpN1W2pj/c7I0LX6qG1OpJ+IxV2sC0CGs3gXYmTUGNIxws9JegXK/ufam 8avLfVBrxw1cdEf431HxkKFfltT47LUtAcaWV1LyR3V9mS1xnhQy4ESSif9HPDiURSPUy08bGVV AgS1oy4y55RsXsQOUuzqrXEBosSHfjLz48UKPlHm5YuxgbGBsjK88g0II6jwdfLKO50VBoMPG0J 7f5yjySS9vxW9P871g3EbZlyHOzxpbczENdKz1BcdH9F5KYMxC1DbpoJLawufOkrOPPD8Qa+nJn 9Hbw0ad4/Oc6h15MnAKiwWLyPhgi5sTsKDhyVqcs5aoDLgH6almJ3fI4Rzata8OHwpEe+v3lM9w cD0ZBk/dyru8OjW09kZdUqi5zHzBpobe1CPfr1WlrWtRwN1/+xuMHkalVv7aqIcBhqZKVUoytMN 8EL6YLOdijapjejUvVVUdDr0PyLmTkFVqFOhAfxvMyOhoedxg4W6XgZPzrkOemKwaHjsP19Irob l3u X-Received: by 2002:a05:6000:188b:b0:48d:eac6:5c2c with SMTP id ffacd0b85a97d-48e1e7bdaffmr4987751f8f.15.1792505272557; Tue, 20 Oct 2026 07:07:52 -0700 (PDT) Received: from localhost ([85.163.81.98]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-48e1d8208e0sm6913917f8f.36.2026.10.20.07.07.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 Oct 2026 07:07:52 -0700 (PDT) Date: Tue, 20 Oct 2026 16:07:48 +0200 From: Jiri Pirko To: Jason Gunthorpe Cc: linux-coco@lists.linux.dev, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, x86@kernel.org, kvm@vger.kernel.org, linux-doc@vger.kernel.org, david.quigley@intel.com, lukas@wunner.de, ksinyuk@kernel.org, rodrigo.vivi@intel.com, cedric.xing@intel.com, sameo@meta.com, drdeeglaze@gmail.com, James.Bottomley@hansenpartnership.com, aik@amd.com, jpiotrowski@nvidia.com, qinkun@google.com, pgonda@google.com, jic23@kernel.org, alistair.francis@wdc.com, ankita@nvidia.com, suzuki.poulose@arm.com, kas@kernel.org, rick.p.edgecombe@intel.com, elena.reshetova@intel.com, dave.hansen@linux.intel.com, sathyanarayanan.kuppuswamy@linux.intel.com, peter.fang@intel.com Subject: Re: [PATCH RFC 03/20] ctlv: Add the root family specification and generated files Message-ID: References: <20261015145053.3664509-1-jiri@resnulli.us> <20261015145053.3664509-4-jiri@resnulli.us> <179245258505.58760.6060356114682279013.b4-review@b4> <20261020125520.GN14213@ziepe.ca> X-Mailing-List: kvm@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20261020125520.GN14213@ziepe.ca> Tue, Oct 20, 2026 at 02:55:20PM +0200, jgg@ziepe.ca wrote: >On Tue, Oct 20, 2026 at 02:28:55PM +0200, Jiri Pirko wrote: >> Tue, Oct 20, 2026 at 01:29:45AM +0200, jgg@nvidia.com wrote: >> >> [ ... 238 lines skipped ... ] >> >> --- /dev/null >> >> +++ b/Documentation/ctlv/families.yaml >> >> @@ -0,0 +1,13 @@ >> >> +# SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) >> >> +%YAML 1.2 >> >> +--- >> >> +# Append-only registry of CTLV family names, indexed by family ID: the entry at >> >> +# index N has family ID N, up to 65535. The root family owns ID 0 and heads the >> >> +# list, and every other entry comes after the entry of the family it inherits. >> >> +# An entry may be marked deprecated, but never reordered, removed, renamed or >> >> +# reused, its position being its wire identity. Every entry must have a >> >> +# specification in specs/.yaml, and is added by the change that adds the >> >> +# implementation. Fixtures under tools/ctlv/tests/ are not registered. >> >> + >> >> +families: >> >> + - ctlv >> > >> >I see where you are coming from with this, but it is going to be >> >problematic from a global kernel perspective. Given CTLV is imagined >> >as a general tool for any subsystem we cannot control the tree that >> >things merge through. It will not be like netdev where there is one >> >authoritative tree with a linear history. >> > >> >So if Bob and Jane maintainers both add their own subsystems by the >> >time it gets to Linus the IDs will get scrambled, and bisection will >> >be lost. >> > >> >Either changes to this file must be strictly done in a single tree >> >with shared branches (which is going to be a bit hard process wise) >> > >> >Or we need to put the ID #s here and have some simple process to >> >coordinate them during the development process. Since new families are >> >probably rare it shouldn't be a big deal >> >> Exactly. Collision is not very likely. Explicit ID or implicit, scramble >> would still happen. And in that case it is resolvable. > >I think because of process if it is kept like this we will have to >merge 'dead code' to reserve spots for people doing new work.. > >But at a minimum this comment above needs a big fat warning not to >change this file without consulting with XYZ to coordinate merging. Agreed.