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 X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4428AFA372C for ; Fri, 8 Nov 2019 17:32:54 +0000 (UTC) Received: from mail.linuxfoundation.org (mail.linuxfoundation.org [140.211.169.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 18761214DA for ; Fri, 8 Nov 2019 17:32:54 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="yHvB28Fn" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 18761214DA Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=iommu-bounces@lists.linux-foundation.org Received: from mail.linux-foundation.org (localhost [127.0.0.1]) by mail.linuxfoundation.org (Postfix) with ESMTP id 025BCDDF; Fri, 8 Nov 2019 17:32:54 +0000 (UTC) Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 93B6EB4B for ; Fri, 8 Nov 2019 17:32:53 +0000 (UTC) Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 3EFFCEC for ; Fri, 8 Nov 2019 17:32:53 +0000 (UTC) Received: from willie-the-truck (236.31.169.217.in-addr.arpa [217.169.31.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A10052084D; Fri, 8 Nov 2019 17:32:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1573234373; bh=Ofx8YKmDV57qHEAkebxJT8e1dJRj7IJxPAc/SX4NHqQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=yHvB28FnuDMkdkXpBFbiPqmmjVjHBkk/mH3QgZbyhcBUq8OGIK/5vOdid6UGunG86 wzf3WuaIySpscgorqrGjICHsKndEi4DHC1CWzmxJwiN/kal8TNome5GAuXSy9abhIl Cjm6d7g4WxIIlP92SSH/7+5zrvjuAj9La75WILvs= Date: Fri, 8 Nov 2019 17:32:48 +0000 From: Will Deacon To: John Garry Subject: Re: [PATCH v2 6/9] Revert "iommu/arm-smmu: Make arm-smmu-v3 explicitly non-modular" Message-ID: <20191108173248.GA22448@willie-the-truck> References: <20191108151608.20932-1-will@kernel.org> <20191108151608.20932-7-will@kernel.org> <06dfd385-1af0-3106-4cc5-6a5b8e864759@huawei.com> <7e906ed1-ab85-7e25-9b29-5497e98da8d8@huawei.com> <20191108164728.GB20866@willie-the-truck> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Cc: "Isaac J. Manjarres" , Jean-Philippe Brucker , Saravana Kannan , linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, Bjorn Helgaas , Robin Murphy X-BeenThere: iommu@lists.linux-foundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Development issues for Linux IOMMU support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: iommu-bounces@lists.linux-foundation.org Errors-To: iommu-bounces@lists.linux-foundation.org On Fri, Nov 08, 2019 at 05:25:09PM +0000, John Garry wrote: > On 08/11/2019 16:47, Will Deacon wrote: > > On Fri, Nov 08, 2019 at 04:44:25PM +0000, John Garry wrote: > > > BTW, it now looks like it was your v1 series I was testing there, on your > > > branch iommu/module. It would be helpful to update for ease of testing. > > > > Yes, sorry about that. I'll update it now (although I'm not sure it will > > help with this -- I was going to see what happens with other devices such > > as the intel-iommu or storage controllers) > > So I tried your v2 series for this - it has the same issue, as I > anticipated. Right, I'm just not sure how resilient drivers are expected to be to force unbinding like this. You can break lots of stuff with root... > It seems that some iommu drivers do call iommu_device_register(), so maybe a > decent reference. Or simply stop the driver being unbound. I'm not sure what you mean about iommu_device_register() (we call that already), but I guess we can keep the '.suppress_bind_attrs = true' if necessary. I'll have a play on my laptop and see how well that works if you start unbinding stuff. Will _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu