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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id E65D4C46467 for ; Fri, 23 Dec 2022 14:57:29 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 06EF0900003; Fri, 23 Dec 2022 09:57:29 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 01E01900002; Fri, 23 Dec 2022 09:57:28 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id E2843900003; Fri, 23 Dec 2022 09:57:28 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id D15C8900002 for ; Fri, 23 Dec 2022 09:57:28 -0500 (EST) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id A184A80893 for ; Fri, 23 Dec 2022 14:57:28 +0000 (UTC) X-FDA: 80273874576.11.D04B268 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by imf04.hostedemail.com (Postfix) with ESMTP id C444C40006 for ; Fri, 23 Dec 2022 14:57:26 +0000 (UTC) Authentication-Results: imf04.hostedemail.com; dkim=none; dmarc=none; spf=none (imf04.hostedemail.com: domain of hch@lst.de has no SPF policy when checking 213.95.11.211) smtp.mailfrom=hch@lst.de ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1671807447; a=rsa-sha256; cv=none; b=lmDfl/FD1/1PcH1ONsC1lPx7WyXQuGBZtUFWWZbRzsVwu9180851N94/U2HG+BgT/XHl9k y5eb6lxS6C6qVEXToMF/zvl7JnRK49Bgv0Q8lb2vjcZTUSLUT8ZX0mZwQkvEE+trsJDu0t MWUtBpQoFfZm2BQel7knw3nITURQeAs= ARC-Authentication-Results: i=1; imf04.hostedemail.com; dkim=none; dmarc=none; spf=none (imf04.hostedemail.com: domain of hch@lst.de has no SPF policy when checking 213.95.11.211) smtp.mailfrom=hch@lst.de ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1671807447; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=UvKZ99mW/dbwP+gR+tJX29Jf4J4BCodpR2igAdpnq6o=; b=TN0tvOwMhLtQG35mTu3MZMl2qTbCkMqsxgudUlhWEJbbNlTPdPCj9UqKjLSlRfjwc6U73R 0Ah/a+6alnlnE3kC0kweV8bprIi5gODlZiGrH29Zu6jgh/ChukoXAPWxuEWMT7amvV4yEf f/7rq8n5WdydpWTS6xHExYc+TQjwX04= Received: by verein.lst.de (Postfix, from userid 2407) id 6691D68BFE; Fri, 23 Dec 2022 15:57:22 +0100 (CET) Date: Fri, 23 Dec 2022 15:57:22 +0100 From: Christoph Hellwig To: Manivannan Sadhasivam Cc: Christoph Hellwig , Andy Gross , Bjorn Andersson , Konrad Dybcio , Mathieu Poirier , Andrew Morton , Uladzislau Rezki , linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, iommu@lists.linux.dev Subject: Re: [PATCH 1/2] Revert "remoteproc: qcom_q6v5_mss: map/unmap metadata region before/after use" Message-ID: <20221223145722.GA29401@lst.de> References: <20221223092703.61927-1-hch@lst.de> <20221223092703.61927-2-hch@lst.de> <20221223144731.GA4587@thinkpad> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221223144731.GA4587@thinkpad> User-Agent: Mutt/1.5.17 (2007-11-01) X-Rspam-User: X-Rspamd-Server: rspam03 X-Rspamd-Queue-Id: C444C40006 X-Stat-Signature: zntwy4o6zd3ibjmacrw8bw6jfxcbckui X-HE-Tag: 1671807446-978534 X-HE-Meta: U2FsdGVkX1++ufcj4aXFl7K1OZaPxfA6WRovFKtOv4ZFXN7xE3nM7TV1va4FgAypp2aQBf4cjJqCWpdVf9KzPbl28LEqQo/nlfBmb3Cc76ou3FXx9BNfAv5sk3nP94CI1f/ZTh3otOQ4ziD1Ug+Rt/NB22gmC6ngHhND2JjKp6uBQiOndL0XQTRHXVInBpZH1Y4wT/yknCOHrT7O450FQCtXl4Y/RqqRyl11FUBuc5ghNIfojNryzRHqz2D3zOaGue68vyaNCfzrvYfQ1LBQqOh2mmq9HBDwYHx2ZMe1jOWxFoBGTCVZN/ouvJPVvji9v4ETtxus72bk0/Dt+lKt/XsrWmNTugZs+74Bz9TU03qmKyGujzGuACiA90ScrXvswQYYvjGlcSy/sumWGnYwA4j6etZtSbv4lcRF3ee9jqXghjui9o7g9PwKW+qlmt3caocrYWz9fO/I6jTop7nCRTYEy/aVoAvHbevw/2IdSe0GHUShytriCypvNiDEtrnHJEkmC9r7m997y+nGWfsKecZC+cGF0T9pPNVgjQNAWQLIBlb4YxwQJjpt4kECQvhN4WemhwUBPagqNBp84RbMSg67bi4vrr0tGhoHKr2VQn+yReTFJmonJK0fOSG0I5xIAqVozA0nMcAmqdqY8LY9Fe8XhEdQzIk2vSmL3K6RP4SoG48SxiciWgEm3ly5d4c+hYwULfdZrMt+fvk6k9eQ7WJ+hqtnB930UjREhyI4mGutgJWmkEEnCYYzLIe48JUNXiItboTM3J59LRmXIFgIXg== X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Fri, Dec 23, 2022 at 08:17:31PM +0530, Manivannan Sadhasivam wrote: > Acked-by: Manivannan Sadhasivam Btw, if the hardware really does not like a kernel mapping, the right way is to just keep using the normal dma allocator, but make sure that there shared-dma-pool with the no-map property for the device.