linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Joerg Roedel <joro@8bytes.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Christoph Hellwig <hch@lst.de>,
	John Garry <john.garry@huawei.com>
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
Date: Sat, 6 Aug 2022 13:31:28 -0700	[thread overview]
Message-ID: <CAHk-=wiSxEVW78nTumvz+ZYt2MZcmqe6S0nb_-efKYm636VuGA@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=whs5CR5FRZP_HUksrr9wX6=Rai-S_XTUFJN7jwB5wKN-Q@mail.gmail.com>

On Sat, Aug 6, 2022 at 12:39 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> If it is, it will be reverted as hopelessly optimistic.

Indeed. I should just have verified with the kernel command line, but
I started bisecting when it wasn't entirely obvious what was going on,
so I just finished it.

Commit 4bf7fda4dce2 ("iommu/dma: Add config for PCI SAC address
trick") is reverted in my tree. You can try again in a decade or so,
but at least on x86-64, that config option is basically a "stop modern
machines from working", and I don't want to have that even as an
option.

If somebody wants some debug output to figure out which device it is
that cares, send me a patch, but we're not trying this thing as-is
again.

                 Linus

      parent reply	other threads:[~2022-08-06 20:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  9:38 [git pull] IOMMU Updates for Linux v5.20 Joerg Roedel
2022-08-06 18:19 ` pr-tracker-bot
2022-08-06 19:39 ` Linus Torvalds
2022-08-06 20:28   ` Joerg Roedel
2022-08-06 20:31   ` Linus Torvalds [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHk-=wiSxEVW78nTumvz+ZYt2MZcmqe6S0nb_-efKYm636VuGA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux.dev \
    --cc=john.garry@huawei.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).