Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3019565pxj; Sun, 6 Jun 2021 23:22:38 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyGeGW2nf6zGBmwk8r9KFbJal1fTYdrr8I2BgH31asbQBoQdYZDNQkSbIsguP+osODchOpO X-Received: by 2002:a50:9549:: with SMTP id v9mr18364933eda.312.1623046958604; Sun, 06 Jun 2021 23:22:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623046958; cv=none; d=google.com; s=arc-20160816; b=o0uxaMLrwEPxtToeLiQVhRzI5neFKbKKbjclCnzXtozTaXgkN6oQPtOxP/dpvTfCND XivoXbynfmcHdGPje8nTHenz3KQT5toFjytmwC4HFFwZMfUJB9zPtUQWXm1GBTUPNUsj C7qaX5aHMPSRDmnnR5FXpHJ2s0cFWb4oVzbdPttWZ1yL9WtoPuzQ18k9my0PhfAy7GwI pFesVPWXU9JsvleMKw10q+7OnHQs2E7Jn1R/MvWXILWRrddlPPhva0qGItM0TuT8N2RQ 5pRviZiiM0MDBAbw6wKZXJY/9D6je9spMr9hdheOEUVOXWOScb+8F7XPJZx5MKirFiFW uTjg== 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-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=etAYp70Qbjpm5kdJfVKLEI1h5ZLaCLoHU8H9E+czoGM=; b=Lj0Tfd4rxkPwJ+clTZ9mgNmOzxtTGvATQe/qqWpSEzMvcYLSN4M9wPwvnkSH3jFFos iTaZDiNNdYiLB+cfAYvIh2M0KF6Y5+aN532sgoRjpoFZXOjakIcIOtxX7Uy04faTXq9b tBwuxNli6RGUjRnVpozqyYbrK/uct5/4xxVXp7VU4M1oR5b8UtqdO/kFOc8HRyQo6GVQ 65WRZ5jUGEMr2J1RLcj92qXI8R1hpK+TsoN8tIcLgulEncGJTAmi4kDPkv0BOp03FU/n 2Kt3+kTtnU19qX17wI1tAdS1pY2Vv0NNwg1rZx+LcoD2Cl7ricHR3qPZrBbMT10TKiAx 2OcQ== 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 c11si13634332edw.275.2021.06.06.23.22.16; Sun, 06 Jun 2021 23:22:38 -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 S230169AbhFGGVN (ORCPT + 99 others); Mon, 7 Jun 2021 02:21:13 -0400 Received: from verein.lst.de ([213.95.11.211]:44476 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229436AbhFGGVN (ORCPT ); Mon, 7 Jun 2021 02:21:13 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id BD91467373; Mon, 7 Jun 2021 08:19:18 +0200 (CEST) Date: Mon, 7 Jun 2021 08:19:18 +0200 From: Christoph Hellwig To: Nick Kossifidis Cc: guoren@kernel.org, anup.patel@wdc.com, palmerdabbelt@google.com, arnd@arndb.de, wens@csie.org, maxime@cerno.tech, drew@beagleboard.org, liush@allwinnertech.com, lazyparser@gmail.com, wefu@redhat.com, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, linux-sunxi@lists.linux.dev, Guo Ren , Christoph Hellwig Subject: Re: [RFC PATCH v2 06/11] riscv: pgtable: Add DMA_COHERENT with custom PTE attributes Message-ID: <20210607061918.GA24060@lst.de> References: <1622970249-50770-1-git-send-email-guoren@kernel.org> <1622970249-50770-10-git-send-email-guoren@kernel.org> <610849b6f66e8d5a9653c9f62f46c48d@mailhost.ics.forth.gr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <610849b6f66e8d5a9653c9f62f46c48d@mailhost.ics.forth.gr> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jun 06, 2021 at 08:22:14PM +0300, Nick Kossifidis wrote: > This patch violates the Privilege Spec section 4.4.1 that clearly states: > > "Bits63–54 are reserved for future standard use and must be zeroed by > software for forward compatibility" > > Standard use means that valid values can only be defined by the Priv. Spec, > not by the vendor (otherwise they'd be marked as "custom use" or "platform > use"), and since they "must" be zeroed by software we 'll be violating the > Privilege Spec if we do otherwise. Yes, that is why I think it is a no-go.