From: Logan Gunthorpe <logang@deltatee.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>, Tom Murphy <murphyt7@tcd.ie>,
David Woodhouse <dwmw2@infradead.org>,
Christoph Hellwig <hch@infradead.org>
Cc: Ashok Raj <ashok.raj@intel.com>,
Intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org
Subject: Re: [Intel-gfx] [PATCH v3 0/6] Convert the intel iommu driver to the dma-iommu api
Date: Mon, 21 Sep 2020 09:48:06 -0600 [thread overview]
Message-ID: <e95a55ea-b03f-4b3c-327a-b48d364577e9@deltatee.com> (raw)
In-Reply-To: <fe94760f-3c10-4222-ec87-291c01325fef@linux.intel.com>
On 2020-09-20 12:36 a.m., Lu Baolu wrote:
> Hi Logan,
>
> On 2020/9/19 4:47, Logan Gunthorpe wrote:
>> Hi Lu,
>>
>> On 2020-09-11 9:21 p.m., Lu Baolu wrote:
>>> Tom Murphy has almost done all the work. His latest patch series was
>>> posted here.
>>>
>>> https://lore.kernel.org/linux-iommu/20200903201839.7327-1-murphyt7@tcd.ie/
>>>
>>> Thanks a lot!
>>>
>>> This series is a follow-up with below changes:
>>>
>>> 1. Add a quirk for the i915 driver issue described in Tom's cover
>>> letter.
>>> 2. Fix several bugs in patch "iommu: Allow the dma-iommu api to use
>>> bounce buffers" to make the bounce buffer work for untrusted devices.
>>> 3. Several cleanups in iommu/vt-d driver after the conversion.
>>>
>>
>> I'm trying to test this on an old Sandy Bridge, but found that I get
>> spammed with warnings on boot. I've put a sample of a few of them below.
>> They all seem to be related to ioat.
>>
>> I had the same issue with Tom's v2 but never saw this on his v1.
>
> Have you verified whether this could be reproduced with the lasted
> upstream kernel (without this patch series)?
Yes. Also, it's hitting a warning in the dma-iommu code which would not
be hit without this patch set.
Thanks,
Logan
WARNING: multiple messages have this Message-ID (diff)
From: Logan Gunthorpe <logang@deltatee.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>, Tom Murphy <murphyt7@tcd.ie>,
David Woodhouse <dwmw2@infradead.org>,
Christoph Hellwig <hch@infradead.org>
Cc: Intel-gfx@lists.freedesktop.org, Ashok Raj <ashok.raj@intel.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v3 0/6] Convert the intel iommu driver to the dma-iommu api
Date: Mon, 21 Sep 2020 09:48:06 -0600 [thread overview]
Message-ID: <e95a55ea-b03f-4b3c-327a-b48d364577e9@deltatee.com> (raw)
In-Reply-To: <fe94760f-3c10-4222-ec87-291c01325fef@linux.intel.com>
On 2020-09-20 12:36 a.m., Lu Baolu wrote:
> Hi Logan,
>
> On 2020/9/19 4:47, Logan Gunthorpe wrote:
>> Hi Lu,
>>
>> On 2020-09-11 9:21 p.m., Lu Baolu wrote:
>>> Tom Murphy has almost done all the work. His latest patch series was
>>> posted here.
>>>
>>> https://lore.kernel.org/linux-iommu/20200903201839.7327-1-murphyt7@tcd.ie/
>>>
>>> Thanks a lot!
>>>
>>> This series is a follow-up with below changes:
>>>
>>> 1. Add a quirk for the i915 driver issue described in Tom's cover
>>> letter.
>>> 2. Fix several bugs in patch "iommu: Allow the dma-iommu api to use
>>> bounce buffers" to make the bounce buffer work for untrusted devices.
>>> 3. Several cleanups in iommu/vt-d driver after the conversion.
>>>
>>
>> I'm trying to test this on an old Sandy Bridge, but found that I get
>> spammed with warnings on boot. I've put a sample of a few of them below.
>> They all seem to be related to ioat.
>>
>> I had the same issue with Tom's v2 but never saw this on his v1.
>
> Have you verified whether this could be reproduced with the lasted
> upstream kernel (without this patch series)?
Yes. Also, it's hitting a warning in the dma-iommu code which would not
be hit without this patch set.
Thanks,
Logan
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Logan Gunthorpe <logang@deltatee.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>, Tom Murphy <murphyt7@tcd.ie>,
David Woodhouse <dwmw2@infradead.org>,
Christoph Hellwig <hch@infradead.org>
Cc: Intel-gfx@lists.freedesktop.org, Ashok Raj <ashok.raj@intel.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v3 0/6] Convert the intel iommu driver to the dma-iommu api
Date: Mon, 21 Sep 2020 09:48:06 -0600 [thread overview]
Message-ID: <e95a55ea-b03f-4b3c-327a-b48d364577e9@deltatee.com> (raw)
In-Reply-To: <fe94760f-3c10-4222-ec87-291c01325fef@linux.intel.com>
On 2020-09-20 12:36 a.m., Lu Baolu wrote:
> Hi Logan,
>
> On 2020/9/19 4:47, Logan Gunthorpe wrote:
>> Hi Lu,
>>
>> On 2020-09-11 9:21 p.m., Lu Baolu wrote:
>>> Tom Murphy has almost done all the work. His latest patch series was
>>> posted here.
>>>
>>> https://lore.kernel.org/linux-iommu/20200903201839.7327-1-murphyt7@tcd.ie/
>>>
>>> Thanks a lot!
>>>
>>> This series is a follow-up with below changes:
>>>
>>> 1. Add a quirk for the i915 driver issue described in Tom's cover
>>> letter.
>>> 2. Fix several bugs in patch "iommu: Allow the dma-iommu api to use
>>> bounce buffers" to make the bounce buffer work for untrusted devices.
>>> 3. Several cleanups in iommu/vt-d driver after the conversion.
>>>
>>
>> I'm trying to test this on an old Sandy Bridge, but found that I get
>> spammed with warnings on boot. I've put a sample of a few of them below.
>> They all seem to be related to ioat.
>>
>> I had the same issue with Tom's v2 but never saw this on his v1.
>
> Have you verified whether this could be reproduced with the lasted
> upstream kernel (without this patch series)?
Yes. Also, it's hitting a warning in the dma-iommu code which would not
be hit without this patch set.
Thanks,
Logan
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-09-21 15:48 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 3:21 [PATCH v3 0/6] Convert the intel iommu driver to the dma-iommu api Lu Baolu
2020-09-12 3:21 ` [Intel-gfx] " Lu Baolu
2020-09-12 3:21 ` Lu Baolu
2020-09-12 3:21 ` [PATCH v3 1/6] iommu: Handle freelists when using deferred flushing in iommu drivers Lu Baolu
2020-09-12 3:21 ` [Intel-gfx] " Lu Baolu
2020-09-12 3:21 ` Lu Baolu
2020-09-12 3:21 ` [PATCH v3 2/6] iommu: Add iommu_dma_free_cpu_cached_iovas() Lu Baolu
2020-09-12 3:21 ` [Intel-gfx] " Lu Baolu
2020-09-12 3:21 ` Lu Baolu
2020-09-12 3:21 ` [PATCH v3 3/6] iommu: Allow the dma-iommu api to use bounce buffers Lu Baolu
2020-09-12 3:21 ` [Intel-gfx] " Lu Baolu
2020-09-12 3:21 ` Lu Baolu
2020-09-12 3:21 ` [PATCH v3 4/6] iommu: Add quirk for Intel graphic devices in map_sg Lu Baolu
2020-09-12 3:21 ` [Intel-gfx] " Lu Baolu
2020-09-12 3:21 ` Lu Baolu
2020-09-12 3:21 ` [PATCH v3 5/6] iommu/vt-d: Convert intel iommu driver to the iommu ops Lu Baolu
2020-09-12 3:21 ` [Intel-gfx] " Lu Baolu
2020-09-12 3:21 ` Lu Baolu
2020-09-12 3:22 ` [PATCH v3 6/6] iommu/vt-d: Cleanup after converting to dma-iommu ops Lu Baolu
2020-09-12 3:22 ` [Intel-gfx] " Lu Baolu
2020-09-12 3:22 ` Lu Baolu
2020-09-12 3:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Convert the intel iommu driver to the dma-iommu api (rev2) Patchwork
2020-09-12 3:56 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-09-12 4:19 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-09-14 8:04 ` [PATCH v3 0/6] Convert the intel iommu driver to the dma-iommu api Tvrtko Ursulin
2020-09-14 8:04 ` [Intel-gfx] " Tvrtko Ursulin
2020-09-15 1:47 ` Lu Baolu
2020-09-15 1:47 ` [Intel-gfx] " Lu Baolu
2020-09-15 1:47 ` Lu Baolu
2020-09-15 8:31 ` Tvrtko Ursulin
2020-09-15 8:31 ` [Intel-gfx] " Tvrtko Ursulin
2020-09-22 11:05 ` Robin Murphy
2020-09-22 11:05 ` [Intel-gfx] " Robin Murphy
2020-09-22 11:05 ` Robin Murphy
2020-09-23 5:38 ` Lu Baolu
2020-09-23 5:38 ` [Intel-gfx] " Lu Baolu
2020-09-23 5:38 ` Lu Baolu
2020-09-24 2:35 ` Lu Baolu
2020-09-24 2:35 ` [Intel-gfx] " Lu Baolu
2020-09-18 20:47 ` Logan Gunthorpe
2020-09-18 20:47 ` Logan Gunthorpe
2020-09-18 20:47 ` Logan Gunthorpe
2020-09-20 6:36 ` Lu Baolu
2020-09-20 6:36 ` Lu Baolu
2020-09-20 6:36 ` Lu Baolu
2020-09-21 15:48 ` Logan Gunthorpe [this message]
2020-09-21 15:48 ` Logan Gunthorpe
2020-09-21 15:48 ` Logan Gunthorpe
2020-09-22 0:24 ` Lu Baolu
2020-09-22 0:24 ` Lu Baolu
2020-09-22 0:24 ` Lu Baolu
2020-09-22 15:38 ` Logan Gunthorpe
2020-09-22 15:38 ` Logan Gunthorpe
2020-09-22 15:38 ` Logan Gunthorpe
2020-09-22 9:51 ` Robin Murphy
2020-09-22 9:51 ` Robin Murphy
2020-09-22 9:51 ` Robin Murphy
2020-09-22 18:45 ` Logan Gunthorpe
2020-09-22 18:45 ` Logan Gunthorpe
2020-09-22 18:45 ` 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=e95a55ea-b03f-4b3c-327a-b48d364577e9@deltatee.com \
--to=logang@deltatee.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=murphyt7@tcd.ie \
/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.