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=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,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 D0C64C433E1 for ; Wed, 3 Jun 2020 11:00:49 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (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 977F420738 for ; Wed, 3 Jun 2020 11:00:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="RSLF/pj9" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 977F420738 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender:Content-Type: Content-Transfer-Encoding:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date:Message-ID:From: References:To:Subject:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=p2PQrsjCbs5kkwYmwxVu3QYF0XEgHBmAAu0mes73DC4=; b=RSLF/pj9E7iUV2132TNRSlSOF 0+GVuVDiRSrzFWqHvVxHcxgpui+bUbEHvGDmrwPtvUGqjNApuhYOWs3AeWUEEgyTnp8vxhHRw5C1V S0O9N/WzBDGkygM6bU/1hYCPIP2cuCHmoIXtolYiBcZLX3mOvoHHhAY9GDd5csBgRwxLv7WL3zkMR xTbXj3iFhvHX8zbLNdqsgXfw+U/4Z88jq9BbcXgV0z9vt/4DE4Jv/ydcHQz6n5BLTIxe1kM7WoIkj caC9InT6lJPWf51CuBS0wIPOLXS83px7IF1ra1JmTGWw2xWM3DBjsrz/Uy6k/+33vU4yfIoRqDb5z dtWlmy5tw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jgR8a-0002JI-Hd; Wed, 03 Jun 2020 11:00:48 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jgR8W-0002Ie-Ul for linux-arm-kernel@lists.infradead.org; Wed, 03 Jun 2020 11:00:46 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id E435B31B; Wed, 3 Jun 2020 04:00:41 -0700 (PDT) Received: from [10.57.0.45] (unknown [10.57.0.45]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 2DD503F305; Wed, 3 Jun 2020 04:00:40 -0700 (PDT) Subject: Re: [RFC 0/2] iommu: arm-smmu: Add support for early direct mappings To: Bjorn Andersson , Will Deacon References: <20191209150748.2471814-1-thierry.reding@gmail.com> <20200228025700.GA856087@builder> <20200514193249.GE279327@builder.lan> <20200527110343.GD11111@willie-the-truck> <20200602063210.GT11847@yoga> From: Robin Murphy Message-ID: Date: Wed, 3 Jun 2020 12:00:37 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <20200602063210.GT11847@yoga> Content-Language: en-GB X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200603_040045_078460_293B0919 X-CRM114-Status: GOOD ( 26.50 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-arm-msm , iommu@lists.linux-foundation.org, Thierry Reding , John Stultz , linux-tegra@vger.kernel.org, linux-arm-kernel Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 2020-06-02 07:32, Bjorn Andersson wrote: > On Wed 27 May 04:03 PDT 2020, Will Deacon wrote: > >> Hi John, Bjorn, >> >> On Tue, May 26, 2020 at 01:34:45PM -0700, John Stultz wrote: >>> On Thu, May 14, 2020 at 12:34 PM wrote: >>>> >>>> On Thu 27 Feb 18:57 PST 2020, Bjorn Andersson wrote: >>>> >>>> Rob, Will, we're reaching the point where upstream has enough >>>> functionality that this is becoming a critical issue for us. >>>> >>>> E.g. Lenovo Yoga C630 is lacking this and a single dts patch to boot >>>> mainline with display, GPU, WiFi and audio working and the story is >>>> similar on several devboards. >>>> >>>> As previously described, the only thing I want is the stream mapping >>>> related to the display controller in place, either with the CB with >>>> translation disabled or possibly with a way to specify the framebuffer >>>> region (although this turns out to mess things up in the display >>>> driver...) >>>> >>>> I did pick this up again recently and concluded that by omitting the >>>> streams for the USB controllers causes an instability issue seen on one >>>> of the controller to disappear. So I would prefer if we somehow could >>>> have a mechanism to only pick the display streams and the context >>>> allocation for this. >>>> >>>> >>>> Can you please share some pointers/insights/wishes for how we can >>>> conclude on this subject? >>> >>> Ping? I just wanted to follow up on this discussion as this small >>> series is crucial for booting mainline on the Dragonboard 845c >>> devboard. It would be really valuable to be able to get some solution >>> upstream so we can test mainline w/o adding additional patches. >> >> Sorry, it's been insanely busy recently and I haven't had a chance to think >> about this on top of everything else. We're also carrying a hack in Android >> for you :) >> > > Thanks for taking the time to get back to us on this! > >>> The rest of the db845c series has been moving forward smoothly, but >>> this set seems to be very stuck with no visible progress since Dec. >>> >>> Are there any pointers for what folks would prefer to see? >> >> I've had a chat with Robin about this. Originally, I was hoping that >> people would all work together towards an idyllic future where firmware >> would be able to describe arbitrary pre-existing mappings for devices, >> irrespective of the IOMMU through which they master and Linux could >> inherit this configuration. However, that hasn't materialised (there was >> supposed to be an IORT update, but I don't know what happened to that) >> and, in actual fact, the problem that you have on db845 is /far/ more >> restricted than the general problem. >> >> Could you please try hacking something along the following lines and see >> how you get on? You may need my for-joerg/arm-smmu/updates branch for >> all the pieces: >> >> 1. Use the ->cfg_probe() callback to reserve the SMR/S2CRs you need >> "pinning" and configure for bypass. >> >> 2. Use the ->def_domain_type() callback to return IOMMU_DOMAIN_IDENTITY >> for the display controller >> >> I /think/ that's sufficient, but note that it differs from the current >> approach because we don't end up reserving a CB -- bypass is configured >> in the S2CR instead. Some invalidation might therefore be needed in >> ->cfg_probe() after unhooking the CB. >> >> Thanks, and please yell if you run into problems with this approach. >> > > This sounded straight forward and cleaner, so I implemented it... > > Unfortunately the hypervisor is playing tricks on me when writing to > S2CR registers: > - TRANS writes lands as requested > - BYPASS writes ends up in the register as requested, with type FAULT > - FAULT writes are ignored > > In other words, the Qualcomm firmware prevents us from relying on > marking the relevant streams as BYPASS type. Sigh... at that point I'm inclined to suggest we give up and stop trying to drive these things with arm-smmu. The XZR thing was bad enough, but if they're not even going to pretend to implement the architecture correctly then I'm not massively keen to continue tying the architectural driver in further knots if innocent things like CONFIG_IOMMU_DEFAULT_PASSTHROUGH are going to unexpectedly and catastrophically fail. We have qcom-iommu for hypervisor-mediated SMMUs, and this new hypervisor behaviour sounds to me more like "qcom-iommu++" with reassignable stream-to-context mappings, rather than a proper Arm SMMU emulation. > Instead Qualcomm seems to implement "bypass" by setting up stream > mapping, of TRANS type, pointing to a context bank without > ARM_SMMU_SCTLR_M set. ...which arm-smmu specifically does not do because it's a silly waste of resources - typically context banks are even scarcer than S2CRs. Robin. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel