linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: John Garry <john.garry@huawei.com>
Cc: will@kernel.org, dwmw2@infradead.org, baolu.lu@linux.intel.com,
	robin.murphy@arm.com, linux-kernel@vger.kernel.org,
	iommu@lists.linux-foundation.org, linuxarm@huawei.com,
	thunder.leizhen@huawei.com, chenxiang66@hisilicon.com,
	rdunlap@infradead.org
Subject: Re: [PATCH v11 0/3] Enhance IOMMU default DMA mode build options
Date: Wed, 9 Jun 2021 10:15:48 +0200	[thread overview]
Message-ID: <YMB4tCrkZv1b44qM@8bytes.org> (raw)
In-Reply-To: <1623158308-180604-1-git-send-email-john.garry@huawei.com>

Hi John,

On Tue, Jun 08, 2021 at 09:18:25PM +0800, John Garry wrote:
> Zhen Lei (3):
>   iommu: Enhance IOMMU default DMA mode build options
>   iommu/vt-d: Add support for IOMMU default DMA mode build options
>   iommu/amd: Add support for IOMMU default DMA mode build options

So I like the idea, but can we go a step further and get (mostly) rid of
the driver-specific setup code for lazy/non-lazy mode? This can happen
in the dma-iommu code and the drivers only need to keep the support for
their legacy command line options.

Regards,

	Joerg

  parent reply	other threads:[~2021-06-09  8:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 13:18 [PATCH v11 0/3] Enhance IOMMU default DMA mode build options John Garry
2021-06-08 13:18 ` [PATCH v11 1/3] iommu: " John Garry
2021-06-09 15:03   ` Robin Murphy
2021-06-09 15:24     ` John Garry
2021-06-08 13:18 ` [PATCH v11 2/3] iommu/vt-d: Add support for " John Garry
2021-06-08 13:18 ` [PATCH v11 3/3] iommu/amd: " John Garry
2021-06-09  8:15 ` Joerg Roedel [this message]
2021-06-10 16:25   ` [PATCH v11 0/3] Enhance " John Garry

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=YMB4tCrkZv1b44qM@8bytes.org \
    --to=joro@8bytes.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=chenxiang66@hisilicon.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=john.garry@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=rdunlap@infradead.org \
    --cc=robin.murphy@arm.com \
    --cc=thunder.leizhen@huawei.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).