Received: by 2002:a05:6a10:d5a5:0:0:0:0 with SMTP id gn37csp3845838pxb; Mon, 4 Oct 2021 10:51:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzplzniJofmL/ETQY5bNbDDvA1Fa15zLPv96p+9KEjQxiW7VVcNT/ZKjP14yhu3aEXroo8/ X-Received: by 2002:a05:6402:3587:: with SMTP id y7mr493859edc.182.1633369866858; Mon, 04 Oct 2021 10:51:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1633369866; cv=none; d=google.com; s=arc-20160816; b=Hns3eI1BXamLRlzWupvJ520DpyxxvcfGTE3QjEeznIwI67VNjUunNO4SohTHo7I3Ty tXdhldrtBob9ymhvY152w7xG8vWNrPqmKIAopLXq0vESpV5T2ygN9iBfOLMe2b828XPs ry1n1HNTj5DQ1gzIqaQYjf6lWnPYjso/Y6+HtpiRmotBKxOe3CCLl5prG2xTAK0qGseB JEoUpynrf8W9Enf8V28Gn/mtEuD+awxprSnaq8+YnUiXGeRmJtBPSeJ8G6ZXzktRD1JN ReCoyzjqmll6SLDiq7ukfiXHJaj8TmO+LwPYsUgVUGm5Y3uWK/nTdfPZ9DLfmLbhJHMN YoZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=v4FPmS3RZa/xH+ZZYDYX9Gnmvo+kaU3beqNrQd7cnds=; b=TOypYfCSqAYoynGJEghiiRACRqslHFN8IA+zW02zw/CddLqpZGZZxpADmlwA0AJ4PD EOKCsOPLD4IIO8Z9uPNYSJGl6GpV/sCS02T6REt7I3NbwxHvwntwXlx9S0819BbdziAq U9Ax2z5k/YG0pRw/xuGftcJsPbwA1eewaUtSBsPxt/8M72ictf6CUs71EDeZ0xV1Sokg vd1N8beOpYid12ueYk2hOc9j8JrZValfr1p+Lc0gNhn24/iZVvLBGwQ6L5qNUgtUUrLx aSS7C3e3NL4vDSyHxha5ul2bCbMjc1jKTD8DEOY0IwFaX1JpZa3UKVvgOTlYrgU1jd03 yA0w== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 1si16506612ejb.87.2021.10.04.10.50.36; Mon, 04 Oct 2021 10:51:06 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234068AbhJDPSl (ORCPT + 99 others); Mon, 4 Oct 2021 11:18:41 -0400 Received: from foss.arm.com ([217.140.110.172]:49700 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233289AbhJDPSk (ORCPT ); Mon, 4 Oct 2021 11:18:40 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 16716D6E; Mon, 4 Oct 2021 08:16:51 -0700 (PDT) Received: from [192.168.1.131] (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id F21133F70D; Mon, 4 Oct 2021 08:16:47 -0700 (PDT) Subject: Re: [PATCH 0/5] arm64: ARMv8.7-A: MTE: Add asymm mode support To: Will Deacon Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, Andrew Morton , Catalin Marinas , Dmitry Vyukov , Andrey Ryabinin , Alexander Potapenko , Marco Elver , Evgenii Stepanov , Branislav Rankov , Andrey Konovalov , Lorenzo Pieralisi References: <20210913081424.48613-1-vincenzo.frascino@arm.com> <20210929154907.GC22029@willie-the-truck> From: Vincenzo Frascino Message-ID: <90cb5600-44cb-1ed5-de4b-d19919090622@arm.com> Date: Mon, 4 Oct 2021 17:16:49 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20210929154907.GC22029@willie-the-truck> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Will, sorry for the late reply but I am on sabbatical :) On 9/29/21 5:49 PM, Will Deacon wrote: > I'm surprised not to see any update to: > > Documentation/arm64/memory-tagging-extension.rst > > particularly regarding the per-cpu preferred tag checking modes. Is > asymmetric mode not supported there? > The document that you are pointing out covers the userspace support, this series introduces the in-kernel support only for asymmetric MTE. The userspace bits for asymm will be added with a future series. The confusion comes from the fact, as Peter correctly pointed already, that I forgot to mention this vital info in the cover letter. Sorry about that I will make sure that this is addressed in v2. Thanks! > Will -- Regards, Vincenzo