From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Will Deacon <will@kernel.org>
Cc: Ashok Raj <ashok.raj@intel.com>,
Intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Tom Murphy <murphyt7@tcd.ie>,
Christoph Hellwig <hch@infradead.org>,
iommu@lists.linux-foundation.org,
David Woodhouse <dwmw2@infradead.org>,
baolu.lu@linux.intel.com
Subject: Re: [Intel-gfx] [PATCH v4 0/7] Convert the intel iommu driver to the dma-iommu api
Date: Fri, 20 Nov 2020 18:20:09 +0800 [thread overview]
Message-ID: <e3299ef9-99ab-8e5a-027a-608495f5a293@linux.intel.com> (raw)
In-Reply-To: <20201103105442.GD22888@8bytes.org>
On 2020/11/3 18:54, Joerg Roedel wrote:
> Hi,
>
> On Tue, Nov 03, 2020 at 11:58:26AM +0200, Joonas Lahtinen wrote:
>> Would that work for you? We intend to send the feature pull requests
>> to DRM for 5.11 in the upcoming weeks.
>
> For the IOMMU side it is best to include the workaround for now. When
> the DRM fixes are merged into v5.11-rc1 together with this conversion,
> it can be reverted and will not be in 5.11-final.
Okay! So I will keep the workaround and send a new version (mostly
rebase) to Will.
Best regards,
baolu
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Will Deacon <will@kernel.org>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Ashok Raj <ashok.raj@intel.com>,
Intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Tom Murphy <murphyt7@tcd.ie>,
Christoph Hellwig <hch@infradead.org>,
iommu@lists.linux-foundation.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v4 0/7] Convert the intel iommu driver to the dma-iommu api
Date: Fri, 20 Nov 2020 18:20:09 +0800 [thread overview]
Message-ID: <e3299ef9-99ab-8e5a-027a-608495f5a293@linux.intel.com> (raw)
In-Reply-To: <20201103105442.GD22888@8bytes.org>
On 2020/11/3 18:54, Joerg Roedel wrote:
> Hi,
>
> On Tue, Nov 03, 2020 at 11:58:26AM +0200, Joonas Lahtinen wrote:
>> Would that work for you? We intend to send the feature pull requests
>> to DRM for 5.11 in the upcoming weeks.
>
> For the IOMMU side it is best to include the workaround for now. When
> the DRM fixes are merged into v5.11-rc1 together with this conversion,
> it can be reverted and will not be in 5.11-final.
Okay! So I will keep the workaround and send a new version (mostly
rebase) to Will.
Best regards,
baolu
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Will Deacon <will@kernel.org>
Cc: baolu.lu@linux.intel.com, Christoph Hellwig <hch@infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
Tom Murphy <murphyt7@tcd.ie>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Ashok Raj <ashok.raj@intel.com>,
Intel-gfx@lists.freedesktop.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/7] Convert the intel iommu driver to the dma-iommu api
Date: Fri, 20 Nov 2020 18:20:09 +0800 [thread overview]
Message-ID: <e3299ef9-99ab-8e5a-027a-608495f5a293@linux.intel.com> (raw)
In-Reply-To: <20201103105442.GD22888@8bytes.org>
On 2020/11/3 18:54, Joerg Roedel wrote:
> Hi,
>
> On Tue, Nov 03, 2020 at 11:58:26AM +0200, Joonas Lahtinen wrote:
>> Would that work for you? We intend to send the feature pull requests
>> to DRM for 5.11 in the upcoming weeks.
>
> For the IOMMU side it is best to include the workaround for now. When
> the DRM fixes are merged into v5.11-rc1 together with this conversion,
> it can be reverted and will not be in 5.11-final.
Okay! So I will keep the workaround and send a new version (mostly
rebase) to Will.
Best regards,
baolu
next prev parent reply other threads:[~2020-11-20 10:20 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 6:34 [Intel-gfx] [PATCH v4 0/7] Convert the intel iommu driver to the dma-iommu api Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-09-27 6:34 ` [Intel-gfx] [PATCH v4 1/7] iommu: Handle freelists when using deferred flushing in iommu drivers Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-09-27 6:34 ` [Intel-gfx] [PATCH v4 2/7] iommu: Add iommu_dma_free_cpu_cached_iovas() Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-09-27 6:34 ` [Intel-gfx] [PATCH v4 3/7] iommu: Allow the dma-iommu api to use bounce buffers Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-09-27 6:34 ` [Intel-gfx] [PATCH v4 4/7] iommu: Add quirk for Intel graphic devices in map_sg Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-11-03 12:00 ` [Intel-gfx] " Robin Murphy
2020-11-03 12:00 ` Robin Murphy
2020-11-03 12:00 ` Robin Murphy
2020-09-27 6:34 ` [Intel-gfx] [PATCH v4 5/7] iommu/vt-d: Update domain geometry in iommu_ops.at(de)tach_dev Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-09-27 6:34 ` [Intel-gfx] [PATCH v4 6/7] iommu/vt-d: Convert intel iommu driver to the iommu ops Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-09-27 6:34 ` [Intel-gfx] [PATCH v4 7/7] iommu/vt-d: Cleanup after converting to dma-iommu ops Lu Baolu
2020-09-27 6:34 ` Lu Baolu
2020-09-27 6:47 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Convert the intel iommu driver to the dma-iommu api (rev3) Patchwork
2020-09-28 9:44 ` [Intel-gfx] [PATCH v4 0/7] Convert the intel iommu driver to the dma-iommu api Tvrtko Ursulin
2020-09-28 9:44 ` Tvrtko Ursulin
2020-09-28 9:44 ` Tvrtko Ursulin
2020-09-29 0:11 ` [Intel-gfx] " Lu Baolu
2020-09-29 0:11 ` Lu Baolu
2020-09-29 0:11 ` Lu Baolu
2020-10-01 12:17 ` [Intel-gfx] " Joerg Roedel
2020-10-01 12:17 ` Joerg Roedel
2020-10-01 12:17 ` Joerg Roedel
2020-10-02 11:59 ` [Intel-gfx] " Lu Baolu
2020-10-02 11:59 ` Lu Baolu
2020-10-02 11:59 ` Lu Baolu
2020-10-12 8:44 ` [Intel-gfx] " Tvrtko Ursulin
2020-10-12 8:44 ` Tvrtko Ursulin
2020-10-12 8:44 ` Tvrtko Ursulin
2020-10-13 0:32 ` [Intel-gfx] " Lu Baolu
2020-10-13 0:32 ` Lu Baolu
2020-10-13 0:32 ` Lu Baolu
2020-11-02 2:00 ` [Intel-gfx] " Lu Baolu
2020-11-02 2:00 ` Lu Baolu
2020-11-02 2:00 ` Lu Baolu
2020-11-02 11:52 ` [Intel-gfx] " Tvrtko Ursulin
2020-11-02 11:52 ` Tvrtko Ursulin
2020-11-02 11:52 ` Tvrtko Ursulin
2020-11-03 2:53 ` [Intel-gfx] " Lu Baolu
2020-11-03 2:53 ` Lu Baolu
2020-11-03 2:53 ` Lu Baolu
2020-11-03 9:14 ` [Intel-gfx] " Tvrtko Ursulin
2020-11-03 9:14 ` Tvrtko Ursulin
2020-11-03 9:14 ` Tvrtko Ursulin
2020-11-03 9:58 ` [Intel-gfx] " Joonas Lahtinen
2020-11-03 9:58 ` Joonas Lahtinen
2020-11-03 9:58 ` Joonas Lahtinen
2020-11-03 10:54 ` [Intel-gfx] " Joerg Roedel
2020-11-03 10:54 ` Joerg Roedel
2020-11-03 10:54 ` Joerg Roedel
2020-11-20 10:20 ` Lu Baolu [this message]
2020-11-20 10:20 ` Lu Baolu
2020-11-20 10:20 ` Lu Baolu
2020-10-01 21:17 ` [Intel-gfx] " Logan Gunthorpe
2020-10-01 21:17 ` Logan Gunthorpe
2020-10-01 21:17 ` Logan Gunthorpe
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=e3299ef9-99ab-8e5a-027a-608495f5a293@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=ashok.raj@intel.com \
--cc=dwmw2@infradead.org \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=murphyt7@tcd.ie \
--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.