Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3363636yba; Tue, 23 Apr 2019 02:27:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqz9ty72PFZeJu2NuF1d0+ug9p79jB6OBiY4rs+EL1CcYjwrPZ1dcUNUgq9iXM6oyzbuMT8r X-Received: by 2002:a63:d607:: with SMTP id q7mr14307097pgg.213.1556011641644; Tue, 23 Apr 2019 02:27:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556011641; cv=none; d=google.com; s=arc-20160816; b=OWXxI/yA2QR6uLy2vh/KYh4ykLfnYm0HN0nKLHbkFD6ePFJ0AUX9AJLaU538AGOhF5 JFK5PFeok2IwESTGn6zb+3VpCoV9mo+knRjKLPMA+CxF4bYZ3EAazf7NP/7HJutEug0e PbkA2GdcsHx7i27c90osEb6ZSV93KRXsKviITuDbSBAmWF9iklbCY3OunPa5GqZlZP9E l5BHmXT+SzxixR5Xwj5V6ZIl+6rvRWgmbdsBqOzM2Av8nAXEWPIBaGGE70TUeCUGyExx ze9etB9rMavGeqkjHkZmeAEA/LXsq5SacrL6P6J79+02BUTtrQwDfd72YQpSqGe1gZB4 yZQg== 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=V9UdSWNwTpZChrSc7x0IYLvDOmAquEM7Inf9DPcxGJE=; b=CgP//DAftazQi1ZQdh0blG6+NcHpgPW2OxcCzM8t9B8imD5aAQGUUbvAnuU4AFZaYQ DO1Nxa0pmjlU04UGGO0zkWsaR3gjyOP+ghkKA+Hw6s87mE/cUqkhHcRKziFvHBq4sh6w iRjv7+4i7rY1XD+zgZB/pZNM++Pttu0I1SoQ1uoh2oFZmODPdiLfZbLGZM2vkd0uDZto wS4YZdHcW5advOjJyPprfbv7qspE+QvPNOUQk0VH0Lv2Wj89BUeFhI+n8sucb/cyuyy4 u+6cgAFvkHRc1dYJcwa4vAran+ph0W6qJXZcK1xiX3BQ0h8r22pqS0fokRaYlnSR66DT vauQ== 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 d9si15408905pls.12.2019.04.23.02.27.05; Tue, 23 Apr 2019 02:27:21 -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 S1726893AbfDWJ0Q (ORCPT + 99 others); Tue, 23 Apr 2019 05:26:16 -0400 Received: from foss.arm.com ([217.140.101.70]:52386 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725916AbfDWJ0Q (ORCPT ); Tue, 23 Apr 2019 05:26:16 -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 918EB374; Tue, 23 Apr 2019 02:26:15 -0700 (PDT) Received: from [10.37.8.239] (unknown [10.37.8.239]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 4991C3F557; Tue, 23 Apr 2019 02:26:13 -0700 (PDT) Subject: Re: [PATCH 1/7] genirq/msi: Add a new field in msi_desc to store an IOMMU cookie To: Thomas Gleixner Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, logang@deltatee.com, douliyangs@gmail.com, miquel.raynal@bootlin.com, marc.zyngier@arm.com, jason@lakedaemon.net, joro@8bytes.org, robin.murphy@arm.com, bigeasy@linutronix.de, linux-rt-users@vger.kernel.org References: <20190418172611.21561-1-julien.grall@arm.com> <20190418172611.21561-2-julien.grall@arm.com> From: Julien Grall Message-ID: <943b0907-f2ee-63c1-7134-997ffaf6f348@arm.com> Date: Tue, 23 Apr 2019 10:26:11 +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: Content-Type: text/plain; charset=utf-8; format=flowed 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 Hi Thomas, On 4/18/19 8:28 PM, Thomas Gleixner wrote: > On Thu, 18 Apr 2019, Julien Grall wrote: > >> When an MSI doorbell is located downstream of an IOMMU, it is required >> to swizzle the physical address with an appropriately-mapped IOVA for any >> device attached to one of our DMA ops domain. >> >> At the moment, the allocation of the mapping may be done when composing >> the message. However, the composing may be done in non-preemtible >> context while the allocation requires to be called from preemptible >> context. >> >> A follow-up patch will split the current logic in two functions >> requiring to keep an IOMMU cookie per MSI. >> >> This patch introduces a new field in msi_desc to store an IOMMU cookie >> when CONFIG_IOMMU_DMA is selected. > > # git grep 'This patch' Documentation/process/ > > Applied to the whole series. Sorry for that. I will rework all the commit messages and resend the series. Cheers, -- Julien Grall