Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp259874pxf; Thu, 25 Mar 2021 03:32:36 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzVTIAFcDRGddMnKzn7496Lyr4S3i+xILETICE7qJLJFw432mojEW7gxt4lYOt7DkUzVM67 X-Received: by 2002:a05:6402:4245:: with SMTP id g5mr8362417edb.306.1616668356195; Thu, 25 Mar 2021 03:32:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616668356; cv=none; d=google.com; s=arc-20160816; b=pWN4AQahUlGUW6gOmZ4txiKVluOzaHF1K4YPabUOR1CrwvTRyTqOvxJ+xhuFrk+Acy Ry4kGxCwa5SrISH4UwbUIEemGRxCw4/K8KnkjHQGABRGN0ZXNxC9OAaLQGU0ghLYp0iQ VO5mMKUWuyBVus+C9CMfTymUGj4JF3Vp8SCyaUC1JQiN4XwCGCFQ8GSu+cNN7J4Gke/X dGyow9zbYMPuacfiz7kMbx6xlMYJm7agGrdjQpzsv4TdV+f7Bdjz4GySaQOHducgClic cpReiwWYhtksc/q+ktlCjr1OZ9EhIx8aIGWDOr69ChtWNB1CvKVLzOwNSXPxKi+p0VkD PRkw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=CkXadhkfwoyYBE44aZLSUPSPV+MOMIAGdMPCI7TsiIw=; b=gKp3hDygpaXXORk7bcys7YP1J+q+zETJ/IBwpSmM5dfCP7CXP1dxOWV5pyXXr1nXvv NoKqpwCCLtea1+WJs5NyW0I6ul9p+2OdV6gcjQSQQfixGAFgoMbbGV3tBFQWrxjXGG6+ EE+g+drvpKCy2k/4dhwd5eK7ZAzNWU8N1Av1lnEH8R4UCIjgMrLbKtKd4cnZyGFosQx9 MXv/dUXvn+BVXZsuKEBS6cc992ObnVCOIpvpmTjaSnrg3affgB7apbpDk4BtZrunRqAU LHxAkp5/wz2/aECBVJ9vZf0azflRw5JiLrSkkRKdoN6DmUUW+1Xwo3p9iswVAUJcma8t Cgiw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u6si3731365ejx.73.2021.03.25.03.32.13; Thu, 25 Mar 2021 03:32:36 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229934AbhCYK3D (ORCPT + 99 others); Thu, 25 Mar 2021 06:29:03 -0400 Received: from elvis.franken.de ([193.175.24.41]:58945 "EHLO elvis.franken.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229716AbhCYK2s (ORCPT ); Thu, 25 Mar 2021 06:28:48 -0400 Received: from uucp (helo=alpha) by elvis.franken.de with local-bsmtp (Exim 3.36 #1) id 1lPNEM-0007Ug-00; Thu, 25 Mar 2021 11:28:46 +0100 Received: by alpha.franken.de (Postfix, from userid 1000) id CCBECC1C81; Thu, 25 Mar 2021 11:17:12 +0100 (CET) Date: Thu, 25 Mar 2021 11:17:12 +0100 From: Thomas Bogendoerfer To: Tiezhu Yang Cc: "Maciej W. Rozycki" , linux-mips@vger.kernel.org, bpf@vger.kernel.org, linux-kernel@vger.kernel.org, Xuefeng Li , Christoph Hellwig Subject: Re: [PATCH v2] MIPS/bpf: Enable bpf_probe_read{, str}() on MIPS again Message-ID: <20210325101712.GA6893@alpha.franken.de> References: <1616034557-5844-1-git-send-email-yangtiezhu@loongson.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 22, 2021 at 03:12:59PM +0800, Tiezhu Yang wrote: > On 03/22/2021 12:46 PM, Maciej W. Rozycki wrote: > > On Thu, 18 Mar 2021, Tiezhu Yang wrote: > > > > > diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig > > > index 160b3a8..4b94ec7 100644 > > > --- a/arch/mips/Kconfig > > > +++ b/arch/mips/Kconfig > > > @@ -6,6 +6,7 @@ config MIPS > > > select ARCH_BINFMT_ELF_STATE if MIPS_FP_SUPPORT > > > select ARCH_HAS_FORTIFY_SOURCE > > > select ARCH_HAS_KCOV > > > + select ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE > > Hmm, documentation on ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE seems rather > > scarce, but based on my guess shouldn't this be "if !EVA"? > > > > Maciej > > I do not quite know what the effect if MIPS EVA (Enhanced Virtual > Addressing) > is set, I saw that ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE should be > restricted > to archs with non-overlapping address ranges. > > I wonder whether MIPS EVA will generate overlapping address ranges? they can overlap in EVA mode. > If yes, it is better to make ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE depend > on !EVA on MIPS. Could please add the change ? Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]