From: Robin Murphy <robin.murphy@arm.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org, will@kernel.org,
linux-kernel@vger.kernel.org, hch@lst.de
Subject: Re: [PATCH v2] iommu/dma: Add config for PCI SAC address trick
Date: Wed, 22 Jun 2022 14:12:39 +0100 [thread overview]
Message-ID: <b9439692-c72b-b856-c7c0-e60a863f3e74@arm.com> (raw)
In-Reply-To: <YrMSJ6AGwn3PxSIH@8bytes.org>
On 2022-06-22 13:59, Joerg Roedel wrote:
> On Thu, Jun 09, 2022 at 04:12:10PM +0100, Robin Murphy wrote:
>> firmware bindings by now. Let's be brave and default it to off in the
>
> I don't have an overall good feeling about this, but as you said, let's
> be brave. This is applied now to the core branch.
>
> If it causes too much trouble we can still revert it (and re-revert it
> later, ...)
Even easier, we can just bring back "default X86", or "default y", if
too many folks object to configuring it manually :)
Thanks for your bravery!
Robin.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Robin Murphy <robin.murphy@arm.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: will@kernel.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, hch@lst.de, john.garry@huawei.com
Subject: Re: [PATCH v2] iommu/dma: Add config for PCI SAC address trick
Date: Wed, 22 Jun 2022 14:12:39 +0100 [thread overview]
Message-ID: <b9439692-c72b-b856-c7c0-e60a863f3e74@arm.com> (raw)
In-Reply-To: <YrMSJ6AGwn3PxSIH@8bytes.org>
On 2022-06-22 13:59, Joerg Roedel wrote:
> On Thu, Jun 09, 2022 at 04:12:10PM +0100, Robin Murphy wrote:
>> firmware bindings by now. Let's be brave and default it to off in the
>
> I don't have an overall good feeling about this, but as you said, let's
> be brave. This is applied now to the core branch.
>
> If it causes too much trouble we can still revert it (and re-revert it
> later, ...)
Even easier, we can just bring back "default X86", or "default y", if
too many folks object to configuring it manually :)
Thanks for your bravery!
Robin.
next prev parent reply other threads:[~2022-06-22 13:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 15:12 [PATCH v2] iommu/dma: Add config for PCI SAC address trick Robin Murphy
2022-06-09 15:12 ` Robin Murphy
2022-06-09 18:09 ` John Garry via iommu
2022-06-09 18:09 ` John Garry
2022-06-10 6:01 ` Christoph Hellwig
2022-06-10 6:01 ` Christoph Hellwig
2022-06-22 12:59 ` Joerg Roedel
2022-06-22 12:59 ` Joerg Roedel
2022-06-22 13:12 ` Robin Murphy [this message]
2022-06-22 13:12 ` Robin Murphy
2022-06-23 11:33 ` Joerg Roedel
2022-06-23 11:33 ` Joerg Roedel
2022-06-23 11:41 ` Robin Murphy
2022-06-23 11:41 ` Robin Murphy
2022-06-24 13:28 ` Joerg Roedel
2022-06-24 13:28 ` Joerg Roedel
2022-06-24 14:49 ` Robin Murphy
2022-06-24 14:49 ` Robin Murphy
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=b9439692-c72b-b856-c7c0-e60a863f3e74@arm.com \
--to=robin.murphy@arm.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.