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.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,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 25341C28CBC for ; Sun, 3 May 2020 22:32:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 03E14206B9 for ; Sun, 3 May 2020 22:32:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729266AbgECWcu (ORCPT ); Sun, 3 May 2020 18:32:50 -0400 Received: from mga11.intel.com ([192.55.52.93]:10348 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729171AbgECWct (ORCPT ); Sun, 3 May 2020 18:32:49 -0400 IronPort-SDR: oEh9WLDoccDO1tCqLZu4CS4VGnMUC02EX7t94Lm4cMIol3MuBKAIREdKInEv3/8quIVKkZLzfq ++XZ8yVvvz9g== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 May 2020 15:32:48 -0700 IronPort-SDR: sTeKarLq7jLZgLfv76YD7tgCpaLe5Yi0j4r4MStyBV+Ctlfcl6hxElw52rtfdGWB8S9O5lndBl nMJ5Wq6IjL7A== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.73,349,1583222400"; d="scan'208";a="406300258" Received: from meghadey-mobl1.amr.corp.intel.com (HELO [10.212.197.87]) ([10.212.197.87]) by orsmga004.jf.intel.com with ESMTP; 03 May 2020 15:32:47 -0700 Subject: Re: [PATCH RFC 00/15] Add VFIO mediated device support and IMS support for the idxd driver. To: Jason Gunthorpe Cc: Dan Williams , Dave Jiang , Vinod Koul , maz@kernel.org, Bjorn Helgaas , "Rafael J. Wysocki" , Greg KH , Thomas Gleixner , "H. Peter Anvin" , Alex Williamson , Jacob jun Pan , "Raj, Ashok" , Yi L Liu , Baolu Lu , "Tian, Kevin" , Sanjay K Kumar , "Luck, Tony" , Jing Lin , kwankhede@nvidia.com, eric.auger@redhat.com, parav@mellanox.com, dmaengine@vger.kernel.org, Linux Kernel Mailing List , X86 ML , linux-pci@vger.kernel.org, KVM list References: <158751095889.36773.6009825070990637468.stgit@djiang5-desk3.ch.intel.com> <20200421235442.GO11945@mellanox.com> <20200423194941.GG13640@mellanox.com> <20200503222146.GD19158@mellanox.com> From: "Dey, Megha" Message-ID: Date: Sun, 3 May 2020 15:32:47 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200503222146.GD19158@mellanox.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-pci-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org Hi Jason, On 5/3/2020 3:21 PM, Jason Gunthorpe wrote: > On Fri, May 01, 2020 at 03:31:14PM -0700, Dey, Megha wrote: >> Hi Jason, >> >> On 4/23/2020 12:49 PM, Jason Gunthorpe wrote: >>> On Thu, Apr 23, 2020 at 12:17:50PM -0700, Dan Williams wrote: >>> >>>> Per Megha's follow-up can you send the details about that other device >>>> and help clear a path for a device-specific MSI addr/data table >>>> format. Ever since HMM I've been sensitive, perhaps overly-sensitive, >>>> to claims about future upstream users. The fact that you have an >>>> additional use case is golden for pushing this into a common area and >>>> validating the scope of the proposed API. >>> >>> I think I said it at plumbers, but yes, we are interested in this, and >>> would like dynamic MSI-like interrupts available to the driver (what >>> Intel calls IMS) >>> >> >> So basically you are looking for a way to dynamically allocate the >> platform-msi interrupts, correct? > > The basic high level interface here seems fine, which is bascially a > way for a driver to grab a bunch of platform-msi interrupts for its > own use ok! > >> Since I don't have access to any of the platform-msi devices, it is hard for >> me to test this code for other drivers expect idxd for now. >> Once I submit the next round of patches, after addressing all the comments, >> would it be possible for you to test this code for any of your devices? > > Possibly, need to find time > Sure, thanks! > Jason >