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 6E501C4332F for ; Fri, 23 Dec 2022 15:51:48 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id D3DD7900003; Fri, 23 Dec 2022 10:51:47 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id CEDC7900002; Fri, 23 Dec 2022 10:51:47 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id BDC86900003; Fri, 23 Dec 2022 10:51:47 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) by kanga.kvack.org (Postfix) with ESMTP id AC310900002 for ; Fri, 23 Dec 2022 10:51:47 -0500 (EST) Received: from smtpin17.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id 6F2D31C5E3E for ; Fri, 23 Dec 2022 15:51:47 +0000 (UTC) X-FDA: 80274011454.17.12F9738 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by imf22.hostedemail.com (Postfix) with ESMTP id 8A1F6C000E for ; Fri, 23 Dec 2022 15:51:45 +0000 (UTC) Authentication-Results: imf22.hostedemail.com; dkim=none; dmarc=none; spf=none (imf22.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=1671810705; 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=VjREvly6v4iW5WBKji5Z/MtShQpHvS42fC2jzQZHNEI=; b=Bj188lbgb3hGc8KMAgUwJfWTFqtY64iPFoJVfcoSd0A2CjIZ7boZi4V7yhW0pjqT1rS/7G QoJAU92+ClBDQ1K9NbwkMG3nWsScsJNB1fDbNTD89UhgXvZcb9/fOGzSoz4lL9l0w6DcHE TL2saUZtEnemkMwjE+uh3hIdC3FV3hw= ARC-Authentication-Results: i=1; imf22.hostedemail.com; dkim=none; dmarc=none; spf=none (imf22.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=1671810705; a=rsa-sha256; cv=none; b=ISkCpANQ2yitoiMj89hvphGFgrhxQXyXX66TwxqkzdD1/oBzdtJKyKqC3s06yfSCSDZRvw OT3JCR4bwyozOarXl8cluTL4uPyQja50TaUQliYO7F/KdWi24TbMyXDBQl7jpim5BqwX2m 1OsVUOJcpplbVdpQKwag9Lora7qGSmo= Received: by verein.lst.de (Postfix, from userid 2407) id 85B4668AA6; Fri, 23 Dec 2022 16:51:41 +0100 (CET) Date: Fri, 23 Dec 2022 16:51:41 +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: <20221223155141.GB30339@lst.de> References: <20221223092703.61927-1-hch@lst.de> <20221223092703.61927-2-hch@lst.de> <20221223144731.GA4587@thinkpad> <20221223145722.GA29401@lst.de> <20221223154039.GD4587@thinkpad> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221223154039.GD4587@thinkpad> User-Agent: Mutt/1.5.17 (2007-11-01) X-Rspamd-Server: rspam07 X-Rspamd-Queue-Id: 8A1F6C000E X-Rspam-User: X-Stat-Signature: k7m1xgiyugpkuz5p4hdqs83dz3h7g7hf X-HE-Tag: 1671810705-669017 X-HE-Meta: U2FsdGVkX1+yh/LNCY9eF7KYI1zcE5OlcU7IOO00w+FmHkRt9B7QiuU6bwixrdnSq7OvLrLnzq2QvQaBOHScOfAAzB1XHxBbSL0NMIXs0iaiyZ1vcq/pMzH2emP7r21HPov4lrRdW01mQYMcIPT1MSPVJqvyGwIn3l8Bm9ZNORp8OypAyHvlqZS7ZDJIryURVPEBaIJXoXt1z1mGO1stDxmI5h0tGw/W6z7w80rY8WJyWqEf3hkQKFiZ61X0l0StsnCFFKjihOy9J4Vnw7O0Dm4xSXwjqjc2mdGpFrpGx4QvFmS8lCgtt7kolFJSigovzWm7Al0wsCEjPCeNpKbWLQD8Bx+XzTR7bgT+Ll5dNKlXp1w1nsWXBYv9dRFTszN0JsYC0kU/pL0rxoDA/sUkgSwl0B/zjIIpyj1fyDKwSsHwUSIVdKbexpdxHBvmhEuWQdHwvQ9z5tEsN2YqoSGxKu0OuXbDVu51GCVGIqbr3wlM/KxeOm5PnXvwEPJQFtpsKZ2t98yoqOp2Cs+De0vEpUzR8vD5HfCHwCDr2BMgIMnEY2Z/eveJtLtCiUlDj/oumh/UPZGlGb7fzQRIyb4wYQPdqeiYs5xhuqAQ24euMuxLDw0ujkmxXDMZ+p/DI4lDL9sCfPB/xSNETKBX1Vd2rUOp4h84brP5pBC3j5QALq+11Bz1JCtcEk24ejuOTujlNW5xY6FuY+10l6pQ1dgbD8CMvpvurpPhT4UJMVAwUnklt4QJfPLlsTr2OL2hqM77EgnplYlB3SDWKE8x/ePZQUWRBH2qtaCeBCAElVrw4jHm9p5Ef6SU2la+XhwzVIwl 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 09:10:39PM +0530, Manivannan Sadhasivam wrote: > On Fri, Dec 23, 2022 at 03:57:22PM +0100, Christoph Hellwig wrote: > > 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. > > Sibi posted a series that uses a separate no-map carveout for this usecase: > https://lore.kernel.org/lkml/20221213140724.8612-1-quic_sibis@quicinc.com/ Oh, I've missed that entire thread. I actually stumbled over this today while finding it during a vmap audit..