lkml.org 
[lkml]   [2021]   [Mar]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: A problem of Intel IOMMU hardware ?
Date


> -----Original Message-----
> From: Tian, Kevin [mailto:kevin.tian@intel.com]
> Sent: Thursday, March 18, 2021 4:27 PM
> To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
> <longpeng2@huawei.com>; Nadav Amit <nadav.amit@gmail.com>
> Cc: chenjiashang <chenjiashang@huawei.com>; David Woodhouse
> <dwmw2@infradead.org>; iommu@lists.linux-foundation.org; LKML
> <linux-kernel@vger.kernel.org>; alex.williamson@redhat.com; Gonglei (Arei)
> <arei.gonglei@huawei.com>; will@kernel.org
> Subject: RE: A problem of Intel IOMMU hardware ?
>
> > From: iommu <iommu-bounces@lists.linux-foundation.org> On Behalf Of
> > Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
> >
> > > 2. Consider ensuring that the problem is not somehow related to
> > > queued invalidations. Try to use __iommu_flush_iotlb() instead of
> qi_flush_iotlb().
> > >
> >
> > I tried to force to use __iommu_flush_iotlb(), but maybe something
> > wrong, the system crashed, so I prefer to lower the priority of this operation.
> >
>
> The VT-d spec clearly says that register-based invalidation can be used only when
> queued-invalidations are not enabled. Intel-IOMMU driver doesn't provide an
> option to disable queued-invalidation though, when the hardware is capable. If you
> really want to try, tweak the code in intel_iommu_init_qi.
>

Hi Kevin,

Thanks to point out this. Do you have any ideas about this problem ? I tried
to descript the problem much clear in my reply to Alex, hope you could have
a look if you're interested.

> Thanks
> Kevin
\
 
 \ /
  Last update: 2021-03-18 09:40    [W:0.262 / U:0.044 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site