Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <69a0c6f17b000b54b8333ee42b3124c1d5a869e2.1631105737.git.robin.murphy@arm.com>
In-Reply-To: <69a0c6f17b000b54b8333ee42b3124c1d5a869e2.1631105737.git.robin.murphy@arm.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed, 8 Sep 2021 09:47:03 -0700
Message-ID: <CAHk-=whm5tP-JDnZ=LCr2ZpnPaAZakZyN=wD_tY7pydQJRtJXw@mail.gmail.com>
Subject: Re: [PATCH] iommu: Clarify default domain Kconfig
To:     Robin Murphy <robin.murphy@arm.com>
Cc:     Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
        iommu <iommu@lists.linux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, Sep 8, 2021 at 5:55 AM Robin Murphy <robin.murphy@arm.com> wrote:
>
> Although strictly it is the AMD and Intel drivers which have an existing
> expectation of lazy behaviour by default, it ends up being rather
> unintuitive to describe this literally in Kconfig. Express it instead as
> an architecture dependency, to clarify that it is a valid config-time
> decision.

Thanks, I think this describes the behavior much more naturally, even
if apparently the end result is pretty much identical.

I'm assuming I'll get it through the iommu tree eventually (no need to
expedite this),

           Linus