From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net [23.128.96.19]) (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 3B1CE17C2 for ; Thu, 19 Oct 2023 06:02:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="FYYMs1iO" Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 82F51FE for ; Wed, 18 Oct 2023 23:02:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=iy7K0NNvOe9ObcQHxgus7YO71fkHVQ1hLDFILqCrRlk=; b=FYYMs1iOBBa1lnCFpe7XgPKhET 4f7q4R7cHZsa4FEqNt9f7YyF65jFwK+d/fHXBi9tB04/hGA0UtLPYEjiFYbBFA9gaOq678/levoCb TLCPvkpJ/lbmRFzgcGffSLBD/qrB0EZ2sgQQIAyiML3EN0rZS/ASTwoGIh1mQdTXbMTgt4pKElSak Sxm0+1bdh1qaMCF8UkQeFjWl0mcDHVOwx+DiOUC6QA9vAOLdST3c1qgTv7i9GI0Cnok7zWqEwLa71 6n5DMUZXAdCDiv1RTS5rJjzkcwHIVMTUI87Qu+nHYPrjuqRJYCov/CLcn0vt5XlzfzLzvGXSFViyn vhNw1+Qw==; Received: from hch by bombadil.infradead.org with local (Exim 4.96 #2 (Red Hat Linux)) id 1qtM7C-00GSIN-1D; Thu, 19 Oct 2023 06:02:38 +0000 Date: Wed, 18 Oct 2023 23:02:38 -0700 From: Christoph Hellwig To: Dave Thaler Cc: "bpf@ietf.org" , bpf Subject: Re: [Bpf] ISA RFC compliance question Message-ID: References: Precedence: bulk X-Mailing-List: bpf@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html On Fri, Sep 29, 2023 at 08:14:12PM +0000, Dave Thaler wrote: > Now that we have some new "v4" instructions, it seems a good time to ask about > what it means to support (or comply with) the ISA RFC once published. Does > it mean that a verifier/disassembler/JIT compiler/etc. MUST support *all* the > non-deprecated instructions in the document? That is any runtime or tool that > doesn't support the new instructions is considered non-compliant with the BPF ISA? Unless we clearly designate optional extensions that that can clearly be marked supported or not supported that is the only way to get interoperability. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net [23.128.96.19]) (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 CDCDA186C for ; Thu, 19 Oct 2023 06:04:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ietf.org header.i=@ietf.org header.b="fw1v313b"; dkim=pass (1024-bit key) header.d=ietf.org header.i=@ietf.org header.b="ApU8FJjX"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="FYYMs1iO" Received: from mail.ietf.org (mail.ietf.org [50.223.129.194]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4B8BF12D for ; Wed, 18 Oct 2023 23:04:01 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 153D8C1519AE for ; Wed, 18 Oct 2023 23:04:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1697695441; bh=9jIfV+ccN/3jTighuIXILj3np/VaR5HZMkVR8iGWtvM=; h=Date:From:To:Cc:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=fw1v313bk4Ux2SIkGJUOzexDJdBaNEBHs3yzNpn853aGvzXiPsrTc/cC2LxDKGNHr pBr8HnyBQEab2q0Igs6U1uTC7gBxXhAnoNGTyWCNQDANrgjjdIFd8PgMh+L7y6BSwT B0xBV5stG563gwAruKMH8IektRDh1t+F6+VbKDqU= X-Mailbox-Line: From bpf-bounces@ietf.org Wed Oct 18 23:04:01 2023 Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D71F7C151997; Wed, 18 Oct 2023 23:04:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1697695440; bh=9jIfV+ccN/3jTighuIXILj3np/VaR5HZMkVR8iGWtvM=; h=Date:From:To:Cc:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=ApU8FJjX28C3ggQVElti3DYGWmacll26Hgsn9VGe5vNtFlJdm4esDlDxs+sp3U2RT euFqm8UZbhVNLztzgHXDoBhbJAWoqUXaAmYjzroepdyyycJ8ACbHABimvqeV8z76Oo VD3W5qb0PhXKWY1LLTIoCiKyU5M6MDw2yTEFQ8Gw= Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33085C151997; Wed, 18 Oct 2023 23:02:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Score: -7.105 X-Spam-Level: Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=infradead.org 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 4MTBsuGyGUGa; Wed, 18 Oct 2023 23:02:39 -0700 (PDT) Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 61AFCC15199A; Wed, 18 Oct 2023 23:02:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=iy7K0NNvOe9ObcQHxgus7YO71fkHVQ1hLDFILqCrRlk=; b=FYYMs1iOBBa1lnCFpe7XgPKhET 4f7q4R7cHZsa4FEqNt9f7YyF65jFwK+d/fHXBi9tB04/hGA0UtLPYEjiFYbBFA9gaOq678/levoCb TLCPvkpJ/lbmRFzgcGffSLBD/qrB0EZ2sgQQIAyiML3EN0rZS/ASTwoGIh1mQdTXbMTgt4pKElSak Sxm0+1bdh1qaMCF8UkQeFjWl0mcDHVOwx+DiOUC6QA9vAOLdST3c1qgTv7i9GI0Cnok7zWqEwLa71 6n5DMUZXAdCDiv1RTS5rJjzkcwHIVMTUI87Qu+nHYPrjuqRJYCov/CLcn0vt5XlzfzLzvGXSFViyn vhNw1+Qw==; Received: from hch by bombadil.infradead.org with local (Exim 4.96 #2 (Red Hat Linux)) id 1qtM7C-00GSIN-1D; Thu, 19 Oct 2023 06:02:38 +0000 Date: Wed, 18 Oct 2023 23:02:38 -0700 From: Christoph Hellwig To: Dave Thaler Cc: "bpf@ietf.org" , bpf Message-ID: References: Precedence: bulk X-Mailing-List: bpf@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html Archived-At: Subject: Re: [Bpf] ISA RFC compliance question X-BeenThere: bpf@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: Discussion of BPF/eBPF standardization efforts within the IETF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: bpf-bounces@ietf.org Sender: "Bpf" Message-ID: <20231019060238.LLWINnMHqvRiDA-oQKCIrtISwvHPd7yQhkc9Q1bwyzk@z> On Fri, Sep 29, 2023 at 08:14:12PM +0000, Dave Thaler wrote: > Now that we have some new "v4" instructions, it seems a good time to ask about > what it means to support (or comply with) the ISA RFC once published. Does > it mean that a verifier/disassembler/JIT compiler/etc. MUST support *all* the > non-deprecated instructions in the document? That is any runtime or tool that > doesn't support the new instructions is considered non-compliant with the BPF ISA? Unless we clearly designate optional extensions that that can clearly be marked supported or not supported that is the only way to get interoperability. -- Bpf mailing list Bpf@ietf.org https://www.ietf.org/mailman/listinfo/bpf