From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EEF22C2BA1A for ; Fri, 24 Apr 2020 06:32:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id BAE682074F for ; Fri, 24 Apr 2020 06:32:12 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="KJe2frUx" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726072AbgDXGcM (ORCPT ); Fri, 24 Apr 2020 02:32:12 -0400 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:58096 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725889AbgDXGcM (ORCPT ); Fri, 24 Apr 2020 02:32:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1587709930; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Br99cdVjmyMMmE/vnpE4Kpx523ywPgMa8SOIrrQl4mQ=; b=KJe2frUxZz5wysffWwDZtlt04cNIMSxzV5NTejiRBfha0R7BJ2yW8ymNvLG0nSr0qaIoqv 9Z4nmWmqMM/OkvxbRzPlsC8xh6bo1cO/LqrGhgPE0DOh12CfsFnwOZQwHhSOPN2rrYV7dN 8hpeD2AJthDFKmBLsIB6d/65N971vHs= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-16-3lI3ysjhOsOdV7hKIARvLQ-1; Fri, 24 Apr 2020 02:32:06 -0400 X-MC-Unique: 3lI3ysjhOsOdV7hKIARvLQ-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 633C880B70A; Fri, 24 Apr 2020 06:32:02 +0000 (UTC) Received: from [10.72.13.62] (ovpn-13-62.pek2.redhat.com [10.72.13.62]) by smtp.corp.redhat.com (Postfix) with ESMTP id BF0DD60605; Fri, 24 Apr 2020 06:31:42 +0000 (UTC) Subject: Re: [PATCH RFC 00/15] Add VFIO mediated device support and IMS support for the idxd driver. To: Jason Gunthorpe , Dave Jiang Cc: vkoul@kernel.org, megha.dey@linux.intel.com, maz@kernel.org, bhelgaas@google.com, rafael@kernel.org, gregkh@linuxfoundation.org, tglx@linutronix.de, hpa@zytor.com, alex.williamson@redhat.com, jacob.jun.pan@intel.com, ashok.raj@intel.com, yi.l.liu@intel.com, baolu.lu@intel.com, kevin.tian@intel.com, sanjay.k.kumar@intel.com, tony.luck@intel.com, jing.lin@intel.com, dan.j.williams@intel.com, kwankhede@nvidia.com, eric.auger@redhat.com, parav@mellanox.com, dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org, linux-pci@vger.kernel.org, kvm@vger.kernel.org, "Michael S. Tsirkin" , Zha Bin , "Liu, Jing2" References: <158751095889.36773.6009825070990637468.stgit@djiang5-desk3.ch.intel.com> <20200421235442.GO11945@mellanox.com> From: Jason Wang Message-ID: Date: Fri, 24 Apr 2020 14:31:40 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20200421235442.GO11945@mellanox.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Content-Transfer-Encoding: quoted-printable Sender: dmaengine-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: dmaengine@vger.kernel.org On 2020/4/22 =E4=B8=8A=E5=8D=887:54, Jason Gunthorpe wrote: >> The mdev utilizes Interrupt Message Store or IMS[3] instead of MSIX fo= r >> interrupts for the guest. This preserves MSIX for host usages and also= allows a >> significantly larger number of interrupt vectors for guest usage. > I never did get a reply to my earlier remarks on the IMS patches. > > The concept of a device specific addr/data table format for MSI is not > Intel specific. This should be general code. We have a device that can > use this kind of kernel capability today. > > Jason > +1. Another example is to extend virtio MMIO to support MSI[1]. Thanks [1] https://lkml.org/lkml/2020/2/10/127