Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Sat, 6 Aug 2022 22:28:55 +0200
From:   Joerg Roedel <joro@8bytes.org>
To:     Linus Torvalds <torvalds@linux-foundation.org>
Cc:     Will Deacon <will@kernel.org>, linux-kernel@vger.kernel.org,
        iommu@lists.linux.dev
Subject: Re: [git pull] IOMMU Updates for Linux v5.20
Message-ID: <Yu7PBwJy8LbI/aTs@8bytes.org>
References: <YuzlAT7RW1U36+ap@8bytes.org>
 <CAHk-=whs5CR5FRZP_HUksrr9wX6=Rai-S_XTUFJN7jwB5wKN-Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHk-=whs5CR5FRZP_HUksrr9wX6=Rai-S_XTUFJN7jwB5wKN-Q@mail.gmail.com>
Precedence: bulk

On Sat, Aug 06, 2022 at 12:39:54PM -0700, Linus Torvalds wrote:
> I'm currently bisecting a boot failure on my desktop, and it's gone
> into the iommu code.
> 
> I'm assuming it's the 64-bit thing, but I'll bisect further to make sure.
> 
> If it is, it will be reverted as hopelessly optimistic.

A faster way to track down whether this change causes the boot failures
on your machine is to boot with iommu.forcedac=0 to disable the new
behavior and see if the issue goes away.

Please let me know if I can help with anything.

Regards,

	Joerg