Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5531830yba; Mon, 13 May 2019 12:31:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqxj2uJxbelRDInYy/sfvTr6o3ORnhzWIJAnKqN4U7SWxkYSWPeMuaq0xERX52uCUyEeB4eB X-Received: by 2002:a62:200f:: with SMTP id g15mr35674616pfg.7.1557775884753; Mon, 13 May 2019 12:31:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557775884; cv=none; d=google.com; s=arc-20160816; b=QnF6JgEivpuM1ZPUpNnuePxZ5EhEf7NytpkykxmgDvZsTeMi+cSfPn1tdEIkqI8QWY 7+ud37LrT0qBqty8gKL53XH2BsQYNGY3BA5sSkTIRBRAllSSE4Lby3eUhPjsLcSxKbel ECFknTwpN9CvehDUhAkLQ1GkvUiDehyhx585FEhUrwh8mqlozVEE+OCOXOdo7urBpQRf +BmHxof395vt0E4nBh2bTf2kSKDqP5eQjVfhhAGkyaeLerOSjAENVFypNk74Kq16VGLu 9k/RV2U666JuQy/sGsJKo9emRtSggYejjYXQ1IBf4giCtxmfdZ1uyPaN/dFOI9yLSXY4 WsjQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=MtYOg/BgtazsCxJypufQp4SBj4S9+Oocu8h/w9bJFf4=; b=Ud6o/ei8LfxbY4muTn8lsvk/vgWThaYSxv/18lVIcyXTOwp1P06c5UtQxZUG081cRT kU/c8EobIEz4MyF7A9qf47Be3ZUX6ys5xTzr7v8TfrGabDPrfr4gZsP7OdPR0DoIYGjw QsDWdpwVka9VyIXv+Lx0jpLllzEuOGyekqG36XLebp8NThEkP7TT5FkwypnENfm2wIcW 6P+jHODpvXgzx8OA0o1U0sJpqi7commenGs1QYL/uWUdOWxcrbzYOi/5tHmJEW14aNqq idbLQApDClxspvqHbtw2w4kFH1h1/PaKrdaVifr2EvkFZymc9n7/2kMZpgY4c8vw3LNq KEGQ== ARC-Authentication-Results: i=1; mx.google.com; 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 d24si18395935pgm.405.2019.05.13.12.31.08; Mon, 13 May 2019 12:31:24 -0700 (PDT) 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; 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 S1731191AbfEMRKM (ORCPT + 99 others); Mon, 13 May 2019 13:10:12 -0400 Received: from foss.arm.com ([217.140.101.70]:33826 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730268AbfEMRKM (ORCPT ); Mon, 13 May 2019 13:10:12 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id B2DEE341; Mon, 13 May 2019 10:10:11 -0700 (PDT) Received: from [10.1.196.129] (ostrya.cambridge.arm.com [10.1.196.129]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id DFA893F71E; Mon, 13 May 2019 10:10:09 -0700 (PDT) Subject: Re: [PATCH v3 02/16] iommu: Introduce cache_invalidate API To: Auger Eric , Jacob Pan , "iommu@lists.linux-foundation.org" , LKML , Joerg Roedel , David Woodhouse , Alex Williamson Cc: "Tian, Kevin" , Raj Ashok , Andriy Shevchenko References: <1556922737-76313-1-git-send-email-jacob.jun.pan@linux.intel.com> <1556922737-76313-3-git-send-email-jacob.jun.pan@linux.intel.com> <44d5ba37-a9e9-cc7a-2a3a-d32b840afa29@arm.com> <7807afe9-efab-9f48-4ca0-2332a7a54950@redhat.com> From: Jean-Philippe Brucker Message-ID: <1a5a5fad-ed21-5c79-9a9e-ff21fadfb95f@arm.com> Date: Mon, 13 May 2019 18:09:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <7807afe9-efab-9f48-4ca0-2332a7a54950@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13/05/2019 17:50, Auger Eric wrote: >> struct iommu_inv_pasid_info { >> #define IOMMU_INV_PASID_FLAGS_PASID (1 << 0) >> #define IOMMU_INV_PASID_FLAGS_ARCHID (1 << 1) >> __u32 flags; >> __u32 archid; >> __u64 pasid; >> }; > I agree it does the job now. However it looks a bit strange to do a > PASID based invalidation in my case - SMMUv3 nested stage - where I > don't have any PASID involved. > > Couldn't we call it context based invalidation then? A context can be > tagged by a PASID or/and an ARCHID. I think calling it "context" would be confusing as well (I shouldn't have used it earlier), since VT-d uses that name for device table entries (=STE on Arm SMMU). Maybe "addr_space"? Thanks, Jean > > Domain invalidation would invalidate all the contexts belonging to that > domain. > > Thanks > > Eric