From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751253AbeEUXAj (ORCPT ); Mon, 21 May 2018 19:00:39 -0400 Received: from mga07.intel.com ([134.134.136.100]:46351 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751019AbeEUXAi (ORCPT ); Mon, 21 May 2018 19:00:38 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,427,1520924400"; d="scan'208";a="60547644" Date: Mon, 21 May 2018 16:03:28 -0700 From: Jacob Pan To: "Liu, Yi L" Cc: "iommu@lists.linux-foundation.org" , LKML , Joerg Roedel , "David Woodhouse" , Greg Kroah-Hartman , Alex Williamson , Jean-Philippe Brucker , "Wysocki, Rafael J" , "Tian, Kevin" , "Raj, Ashok" , Jean Delvare , "Christoph Hellwig" , Lu Baolu , jacob.jun.pan@linux.intel.com Subject: Re: [PATCH v5 13/23] iommu: introduce device fault report API Message-ID: <20180521160328.02bc9414@jacob-builder> In-Reply-To: References: <1526072055-86990-1-git-send-email-jacob.jun.pan@linux.intel.com> <1526072055-86990-14-git-send-email-jacob.jun.pan@linux.intel.com> <20180517085909.7470dfb5@jacob-builder> Organization: OTC X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 17 May 2018 23:22:43 +0000 "Liu, Yi L" 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.