From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,T_DKIMWL_WL_HIGH,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 71639C04AB5 for ; Thu, 6 Jun 2019 17:42:31 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 4CE7120868 for ; Thu, 6 Jun 2019 17:42:31 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="Cj7RToGa" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4CE7120868 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Mime-Version:References:In-Reply-To: Date:To:From:Subject:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=Ix6Qy8KiPyhPWm+aNvb1bAROz/oXbjQqAiMHr6Rj4ic=; b=Cj7RToGaRZrZgL 9n/p1+U2CSQ8lTo/Mg/eOKCxmtxTQT+mT7R+uynDmCEudygI0/S1Qm5gxubeWyRtyK3mO1/10NPyA rKmSAO4Ki+HaU1JPCtcESoQCEhWekFmldmgh5iVs2jyoZ3ZVM0LUQcDlCbbfBLA3HEnBFn4Pc+ZoN nRqePuVx8ksc9fvt0PPWOfq7nUjzDdzYPhqD1Ft9VTu+xzwYOujGpHww8TYVUfqjQDWP9aP8E+Vt4 O7CKCbQjHVzE7vVEjk89nxbnBxs9xsT7RlmNeBEVb84HDsKHdZH1LCUbd5sY0C3JAHGGW7e6ig3Yg ou0fN495oBguzWKStoFw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hYwPG-0007oX-2R; Thu, 06 Jun 2019 17:42:30 +0000 Received: from mga02.intel.com ([134.134.136.20]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hYwPA-0007ge-SU for linux-arm-kernel@lists.infradead.org; Thu, 06 Jun 2019 17:42:26 +0000 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Jun 2019 10:42:23 -0700 X-ExtLoop1: 1 Received: from yyu32-desk1.sc.intel.com ([143.183.136.147]) by orsmga001.jf.intel.com with ESMTP; 06 Jun 2019 10:42:22 -0700 Message-ID: <5f92e89a5823a3265fa0b389a19452ba995e9406.camel@intel.com> Subject: Re: [PATCH 4/8] arm64: Basic Branch Target Identification support From: Yu-cheng Yu To: Dave Martin , Catalin Marinas Date: Thu, 06 Jun 2019 10:34:22 -0700 In-Reply-To: <20190606172345.GD28398@e103592.cambridge.arm.com> References: <1558693533-13465-1-git-send-email-Dave.Martin@arm.com> <1558693533-13465-5-git-send-email-Dave.Martin@arm.com> <20190524130217.GA15566@lakrids.cambridge.arm.com> <20190524145306.GZ28398@e103592.cambridge.arm.com> <20190606171155.GI56860@arrakis.emea.arm.com> <20190606172345.GD28398@e103592.cambridge.arm.com> X-Mailer: Evolution 3.28.1-2 Mime-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190606_104225_148469_FD2AA4CD X-CRM114-Status: GOOD ( 20.80 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , linux-arch@vger.kernel.org, Andrew Jones , Arnd Bergmann , Paul Elliott , "H.J. Lu" , Szabolcs Nagy , Will Deacon , Richard Henderson , linux-kernel@vger.kernel.org, Kristina =?UTF-8?Q?Mart=C5=A1enko?= , Sudakshina Das , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, 2019-06-06 at 18:23 +0100, Dave Martin wrote: > On Thu, Jun 06, 2019 at 06:11:56PM +0100, Catalin Marinas wrote: > > On Fri, May 24, 2019 at 03:53:06PM +0100, Dave P Martin wrote: > > > On Fri, May 24, 2019 at 02:02:17PM +0100, Mark Rutland wrote: > > > > On Fri, May 24, 2019 at 11:25:29AM +0100, Dave Martin wrote: > > > > > #endif /* _UAPI__ASM_HWCAP_H */ > > > > > diff --git a/arch/arm64/include/uapi/asm/mman.h > > > > > b/arch/arm64/include/uapi/asm/mman.h > > > > > new file mode 100644 > > > > > index 0000000..4776b43 > > > > > --- /dev/null > > > > > +++ b/arch/arm64/include/uapi/asm/mman.h > > > > > @@ -0,0 +1,9 @@ > > > > > +/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */ > > > > > +#ifndef _UAPI__ASM_MMAN_H > > > > > +#define _UAPI__ASM_MMAN_H > > > > > + > > > > > +#include > > > > > + > > > > > +#define PROT_BTI_GUARDED 0x10 /* BTI guarded > > > > > page */ > > > > > > > > From prior discussions, I thought this would be PROT_BTI, without the > > > > _GUARDED suffix. Do we really need that? > > > > > > > > AFAICT, all other PROT_* definitions only have a single underscore, and > > > > the existing arch-specific flags are PROT_ADI on sparc, and PROT_SAO on > > > > powerpc. > > > > > > No strong opinon. I was trying to make the name less obscure, but I'm > > > equally happy with PROT_BTI if people prefer that. > > > > I prefer PROT_BTI as well. We are going to add a PROT_MTE at some point > > (and a VM_ARM64_MTE in the high VMA flag bits). > > Ack. > > Some things need attention, so I need to respin this series anyway. > > skip_faulting_instruction() and kprobes/uprobes may need looking at, > plus I want to simply the ELF parsing (at least to skip some cost for > arm64). Can we add a case in the 'consistency checks for the interpreter' (right above where you add arch_parse_property()) for PT_NOTE? That way you can still use part of the same parser. Yu-cheng _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel