Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp415818ybl; Thu, 5 Dec 2019 23:21:46 -0800 (PST) X-Google-Smtp-Source: APXvYqzJjWiaWm+9HIutmyJupM66QeldWQipWiP3nF2XquuPCfwjbGQCXpg2x78lPF2XOBY6KSN+ X-Received: by 2002:aca:48cf:: with SMTP id v198mr11298226oia.35.1575616906024; Thu, 05 Dec 2019 23:21:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575616906; cv=none; d=google.com; s=arc-20160816; b=tKklHFvVJv2qxhHlR7ScazNUNfgHQ3DlP4lkaQV3eZDUsb62qfagZdO6mcUB/v3LZW Ruy0Gi+YiBkw/dCp7aS6qOAXmPdkDej8ITh3Ta7QaVQ+qvsTy4eEqu64VHsV0JIjRHUN V3AxFy8QMwOhnRGXXtLZlXKojNrIfUVEKCCjBCUsm6FcPtImlnjLLTSRiziygjtatH32 3t/ApTTfc4wTti7qz/lxA5L+CYmFR8KhiWFhM2fKZsp+8fkM2sQeaqn3f+ARb7TWeSGa 6g7aASmp/J3lX8k4bHQcYa8MK/SejUbmtdx/MFkJnQlYXSQaphOSslPpMhxXqnqNBAwY n67A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:user-agent:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version:dkim-filter:dkim-signature:dkim-filter; bh=YBcb2XIhpGvQl1++v0zJOJ1RxMw2N0RI5FMDXHCH0qA=; b=knTicw5JqH0Nj+e78Q17Qlpa6bMBWpYyEuTrhq4+ru+8g1nepSRLOWb0+lHMxbP8AU C/TYiehZaVEjwREYtoQAZcFW8W/XJdar4W5HLWJrZ5ZnnFBNUoBtF03Htwv7h6TjG2lP G+6Yf6n/GVCV+IjQIpnwA9QXSTcbMFL1X82538JN973zd8QjRDs//DETrFgOB6jJj115 ajlwpzYWqVVDZW2klfmZu//y1CFq+A7gDvarbcl548PpVB8zoN0W82CRZIVCVa36sPPf mwlytfL5ZDcn7l0CuP/7rKCSNEyxc1iouCv8Nu7TsJBBG2cV3nx8hu75mzwo7xfyiEPg n+ag== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@dlink.ru header.s=mail header.b=p5R61v4R; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s14si6055222otq.37.2019.12.05.23.21.31; Thu, 05 Dec 2019 23:21:46 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@dlink.ru header.s=mail header.b=p5R61v4R; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726370AbfLFHU6 (ORCPT + 99 others); Fri, 6 Dec 2019 02:20:58 -0500 Received: from mail.dlink.ru ([178.170.168.18]:39462 "EHLO fd.dlink.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725858AbfLFHU6 (ORCPT ); Fri, 6 Dec 2019 02:20:58 -0500 Received: by fd.dlink.ru (Postfix, from userid 5000) id 6F7E41B21545; Fri, 6 Dec 2019 10:20:53 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 fd.dlink.ru 6F7E41B21545 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dlink.ru; s=mail; t=1575616853; bh=YBcb2XIhpGvQl1++v0zJOJ1RxMw2N0RI5FMDXHCH0qA=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=p5R61v4RR88Ijn3tXZdHEevK2Wg/cSQTyAZgPSNpcQ9ZAvQmfxseTgq5xYQXBhl40 TWLwSh4S8Y88vlPq2CK2Qi++JDSCaWwH6hp1WBL7rC6JP3CZ5KuyLLouRt/QBD2meU GNSDYdNkkDLsOHOAAP7MeEF/Rp2uODW7Q4XXdYK0= X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.dlink.ru X-Spam-Level: X-Spam-Status: No, score=-99.2 required=7.5 tests=BAYES_50,USER_IN_WHITELIST autolearn=disabled version=3.4.2 Received: from mail.rzn.dlink.ru (mail.rzn.dlink.ru [178.170.168.13]) by fd.dlink.ru (Postfix) with ESMTP id 54F6E1B21308; Fri, 6 Dec 2019 10:20:41 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 fd.dlink.ru 54F6E1B21308 Received: from mail.rzn.dlink.ru (localhost [127.0.0.1]) by mail.rzn.dlink.ru (Postfix) with ESMTP id 0DBDB1B226AC; Fri, 6 Dec 2019 10:20:41 +0300 (MSK) Received: from mail.rzn.dlink.ru (localhost [127.0.0.1]) by mail.rzn.dlink.ru (Postfix) with ESMTPA; Fri, 6 Dec 2019 10:20:41 +0300 (MSK) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Fri, 06 Dec 2019 10:20:40 +0300 From: Alexander Lobakin To: Paul Burton Cc: Paul Burton , Hassan Naveed , Ralf Baechle , James Hogan , Alexei Starovoitov , Daniel Borkmann , Martin KaFai Lau , Song Liu , Yonghong Song , Andrii Nakryiko , netdev@vger.kernel.org, bpf@vger.kernel.org, linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: MIPS eBPF JIT support on pre-32R2 In-Reply-To: <20191205184450.lbrkenmursz4zpdm@lantea.localdomain> References: <09d713a59665d745e21d021deeaebe0a@dlink.ru> <20191205184450.lbrkenmursz4zpdm@lantea.localdomain> User-Agent: Roundcube Webmail/1.4.0 Message-ID: <647fa62c7111a27a2cc217cf06cbe355@dlink.ru> X-Sender: alobakin@dlink.ru Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Paul Burton wrote 05.12.2019 21:44: > Hi Alexander, Hi Paul! > On Thu, Dec 05, 2019 at 03:45:27PM +0300, Alexander Lobakin wrote: >> Hey all, >> >> I'm writing about lines arch/mips/net/ebpf_jit.c:1806-1807: >> >> if (!prog->jit_requested || MIPS_ISA_REV < 2) >> return prog; >> >> Do pre-32R2 architectures (32R1, maybe even R3000-like) actually >> support >> this eBPF JIT code? > > No, they don't; the eBPF JIT makes unconditional use of at least the > (d)ins & (d)ext instructions which were added in MIPSr2, so it would > result in reserved instruction exceptions & panics if enabled on > pre-MIPSr2 CPUs. > >> If they do, then the condition 'MIPS_ISA_REV < 2' >> should be removed as it is always true for them and tells CC to remove >> JIT completely. >> >> If they don't support instructions from this JIT, then the line >> arch/mips/Kconfig:50: >> >> select HAVE_EBPF_JIT if (!CPU_MICROMIPS) >> >> should be changed to something like: >> >> select HAVE_EBPF_JIT if !CPU_MICROMIPS && TARGET_ISA_REV >= 2 >> >> (and then the mentioned 'if' condition would become redundant) > > Good spot; I agree entirely, this dependency should be reflected in > Kconfig. > >> At the moment it is possible to build a kernel without both JIT and >> interpreter, but with CONFIG_BPF_SYSCALL=y (what should not be allowed >> I suppose?) within the following configuration: >> >> - select any pre-32R2 CPU (e.g. CONFIG_CPU_MIPS32_R1); >> - enable CONFIG_BPF_JIT (CONFIG_MIPS_EBPF_JIT will be autoselected); >> - enable CONFIG_BPF_JIT_ALWAYS_ON (this removes BPF interpreter from >> the system). >> >> I may prepare a proper patch by myself if needed (after >> clarification). > > That would be great, thanks! Great, I'll send it in about ~2-3 hours. > One thing to note is that I hope we'll restore the cBPF JIT with this > patch: > > https://lore.kernel.org/linux-mips/20191205182318.2761605-1-paulburton@kernel.org/T/#u > > The cBPF JIT looks like it should work on older pre-MIPSr2 CPUs, so the > only way this is relevant is that your patch might have a minor > conflict. But I thought I'd mention it anyway :) Yes, I thought about this too. If pre-32R2 CPUs don't support our eBPF JIT, we'd better restore cBPF for them, so they could speed-up at least "classic" instructions. Glad you've decided to do that. > Thanks, > Paul Regards, ᚷ ᛖ ᚢ ᚦ ᚠ ᚱ