IETF Logo Mail Archive

Re: [Bpf] BPF ISA conformance groups

Watson Ladd <watsonbladd@gmail.com> Sun, 10 December 2023 21:14 UTC

Return-Path: <watsonbladd@gmail.com>
X-Original-To: bpf@ietfa.amsl.com
Delivered-To: bpf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73DB0C14F5F5 for <bpf@ietfa.amsl.com>; Sun, 10 Dec 2023 13:14:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HBjtbYTI-Z0u for <bpf@ietfa.amsl.com>; Sun, 10 Dec 2023 13:14:04 -0800 (PST)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3A80C14F5E4 for <bpf@ietf.org>; Sun, 10 Dec 2023 13:14:04 -0800 (PST)
Received: by mail-pg1-x535.google.com with SMTP id 41be03b00d2f7-517ab9a4a13so3190279a12.1 for <bpf@ietf.org>; Sun, 10 Dec 2023 13:14:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1702242844; x=1702847644; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=GXDK4NPT8AOsFRt9zx3A0m9grq81nXyLEQqGa/oegKE=; b=NhYYoNQjk7Whyj5nHYuh+EZMVy4+/Cc0iOOruuDatqKLzXrylmi7R8MPVrrP/CUQnH 5f+yzF0G9SrJprpvcrnXruxVeKkDzz0TAn3Y16aFerlI6pTBg9viwAM8ui1S5e5ZWq7p r7OgPmi/PdkzianfD2RQIK6LKIpGkO157XntjMRkV+Olp5Vmpp4kZTojLfNmSK1sGOhz QgLDu8A5XTEBq0/AD/D3RiVA7FJ2LMaCr1GFrEBVQbBbm2Pg3TSwH8Z+AsAqll+YCNuJ nePMNxwjLv8Cyv8oz96qfH/JXiqZNQYbdrpW/DwLJR88Hw/27rOUiaujjlBh04qexXBi Kk6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702242844; x=1702847644; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=GXDK4NPT8AOsFRt9zx3A0m9grq81nXyLEQqGa/oegKE=; b=XQrGbOhFpOT0pAEDR4OmMG7erb582/kxIpuzL1kMQKiRvolbiBD4W07SQ0yDuq1AHR OPnBbyUoUX+yoftAhAqKBrZjE2wOjMOq8vGjZPLpz6KvBzZd8+6M8vrthVNIa+G22qdH xGlP1Rnimn7dAkvez3lF2DampLvqfLES6ynhH9SLzmJd1yUQOI4cQ7FFz4JGrTNv3JX9 pkTBp2O8qkcpVERQhxUVAMZ9RqXMltB9eHPLvb4Uc3HhQxLYk/bDpNwMApmRpevUrIVy 5/HXs8hI5qK+L1TKFeX14kjoPbU58ZzqCD0/Dzb8EGagfOpbdkPzXOFRovB0NZ5rXjmt cZMg==
X-Gm-Message-State: AOJu0YyD5+SbvW4D2AqtF9dWWqHR3M6PoOj4Y9Vsb5IDa5RnUWh+aEKF KwEQAiYhcJeiZS9v5oAhbdE9ZBdsTVD4HvwEMQYCDrK7
X-Google-Smtp-Source: AGHT+IGcVi6zf4BkMmnx+BqLx9B6ugGY02+UOdr+AAS259vMUzp3EZhrExK7RFTfcMOmGIm7sBv5mnGewuTZDJ/u36U=
X-Received: by 2002:a05:6a20:3d93:b0:190:5faf:ea71 with SMTP id s19-20020a056a203d9300b001905fafea71mr4604576pzi.49.1702242843686; Sun, 10 Dec 2023 13:14:03 -0800 (PST)
MIME-Version: 1.0
References: <20231127201817.GB5421@maniforge> <072101da2558$fe5f5020$fb1df060$@gmail.com> <20231207215152.GA168514@maniforge> <CAADnVQ+Mhe6ean6J3vH1ugTyrgWNxupLoFfwKu6-U=3R8i1TNQ@mail.gmail.com>
In-Reply-To: <CAADnVQ+Mhe6ean6J3vH1ugTyrgWNxupLoFfwKu6-U=3R8i1TNQ@mail.gmail.com>
From: Watson Ladd <watsonbladd@gmail.com>
Date: Sun, 10 Dec 2023 13:13:52 -0800
Message-ID: <CACsn0c=+H57dx4C17VNkzJaUF2cYeW33Vgq+72uPv60jZ4O8Hw@mail.gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: David Vernet <void@manifault.com>, Dave Thaler <dthaler1968=40googlemail.com@dmarc.ietf.org>, Christoph Hellwig <hch@infradead.org>, bpf@ietf.org, bpf <bpf@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bpf/kQHSOOsxCIl_4lpSuPm6BHEMlIA>
Subject: Re: [Bpf] BPF ISA conformance groups
X-BeenThere: bpf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion of BPF/eBPF standardization efforts within the IETF <bpf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bpf>, <mailto:bpf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bpf/>
List-Post: <mailto:bpf@ietf.org>
List-Help: <mailto:bpf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bpf>, <mailto:bpf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Dec 2023 21:14:08 -0000

>
> Hence my point: legacy and the rest (as of cpu=v4) are the only two categories
> we should have in _this_ version of the standard.
> Rest assured we will add new insn in the coming months.
> I suggest we figure out conformance groups for future insns at that time.
> That would be the time to argue and actually extract value out of discussion.
> Retroactive bike shedding is a bike shedding and nothing else.

If some existing implementations aren't supporting some of these
instructions don't we need a way to make a profile that says that so
that tools can know what they have to generate for things to work?
That to my mind is the reason we would define the profiles.

Sincerely,
Watson
>
> --
> Bpf mailing list
> Bpf@ietf.org
> https://www.ietf.org/mailman/listinfo/bpf



-- 
Astra mortemque praestare gradatim

v2.46.0 | Report a Bug | By Email | System Status