[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180521160328.02bc9414@jacob-builder>
Date: Mon, 21 May 2018 16:03:28 -0700
From: Jacob Pan <jacob.jun.pan@...ux.intel.com>
To: "Liu, Yi L" <yi.l.liu@...el.com>
Cc: "iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Joerg Roedel <joro@...tes.org>,
"David Woodhouse" <dwmw2@...radead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alex Williamson <alex.williamson@...hat.com>,
Jean-Philippe Brucker <jean-philippe.brucker@....com>,
"Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
"Tian, Kevin" <kevin.tian@...el.com>,
"Raj, Ashok" <ashok.raj@...el.com>,
Jean Delvare <khali@...ux-fr.org>,
"Christoph Hellwig" <hch@...radead.org>,
Lu Baolu <baolu.lu@...ux.intel.com>,
jacob.jun.pan@...ux.intel.com
Subject: Re: [PATCH v5 13/23] iommu: introduce device fault report API
On Thu, 17 May 2018 23:22:43 +0000
"Liu, Yi L" <yi.l.liu@...el.com> wrote:
> > So as long as in-kernel PRQ handling can do queuing, there is no
> > need for queuing in the host reporting path.
>
> Will it affect current interface? Here the handler only get an "evt"
> per a PRQ IRQ. And I suppose vfio needs not rely on host iommu
> queuing?
I don't think it needs iommu driver queuing.
Powered by blists - more mailing lists