Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp287725pxb; Wed, 4 Nov 2020 23:11:12 -0800 (PST) X-Google-Smtp-Source: ABdhPJxGeF1srazctjsU14vvC2AmGdRb2pgQVyH+gS7egcf8MafDQCGJE5rqjTrINLdXyloNLIsW X-Received: by 2002:a17:906:c41:: with SMTP id t1mr978903ejf.19.1604560272193; Wed, 04 Nov 2020 23:11:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1604560272; cv=none; d=google.com; s=arc-20160816; b=m3R+Z/d36Dh7DVsrx45lM+WE74uiH5Tv1XDRkQKBnm9/X2d5WwwLmbKHEPrOGOyG27 l4AERtOpejqWc+tLRZEwx/ZdgLkFtt5UQQvecPsi8ntMGvRYj8/NHR7Qn5+kHME/lQc7 dXN0BkBx8v/7T8EmK9EsR9t2csvyoeKxzwSCsaLnv592TmOT5s2mhomNbFg38K0b0xLa qMqmx8jxQtDj4SH65gDC74qWQBz8XQh9OC+i7GguII49WSA7JP2IrCGtrzvXagXJDKXe gOQ7mSAxcGJbNJe9dA/sEuCth+8OiYMbf+p2JZ1EQRa+R0qwi06P/OfnbL08Yn0QERE5 4AeQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:dkim-signature; bh=jvkuQPSDCN6FYaBMhi9QfR8XY+glajAyMRxV78sAHp8=; b=hMbyUlyGFuE0VDW9y0Cy5xnRehmfjuWXRPRSpFGybC8TvYeicNjrHK2eGMclv3j5nE OihQ2YZoTVx56YCYI2G+TY1T/tSAhdyWgZ5HAcC8wZyutSLRl8EMSYl9fWWfROTHGlrj pTVIIk+moB0ecv9/nIPmmG1VlFyOySRiFSfm7gLjkQf6Rng6NMFgg7NAxf80S7GxYN+M k8rkh9w0OV3iKz+7q1Ik9Kr3LYMQl1ut5NEP0wZFBIT2Azu2Wl1fb53mSp24X62R6x8u e7aIFWK8QZaMPWucMlLANQCZLjcvEZ5yCxv0n1AMl8FI9ixOPayXG5JmkZo1le+oIo6s Ym8w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="DaKOFf/i"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j6si512626edr.531.2020.11.04.23.10.49; Wed, 04 Nov 2020 23:11:12 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="DaKOFf/i"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726371AbgKEHIS (ORCPT + 99 others); Thu, 5 Nov 2020 02:08:18 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:41927 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726428AbgKEHIR (ORCPT ); Thu, 5 Nov 2020 02:08:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1604560096; 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=jvkuQPSDCN6FYaBMhi9QfR8XY+glajAyMRxV78sAHp8=; b=DaKOFf/ijQf8tLGf897YVM1E5qQM49mFvGFdaxuZVb4eSLtS12c41I3PXaHqqIh4YkA9FG yzg4Jtu7Rw+8d2F36f0P4HxxnatQk3FCC53nYF22BMxg9majPOO5JAgXuJsb8HVvxdVRHO NGPVEItEMhlz4VWEF2DmEfeCwlUjK7Q= 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-309-24oP9kIaO0WULtCF9hmyQw-1; Thu, 05 Nov 2020 02:08:12 -0500 X-MC-Unique: 24oP9kIaO0WULtCF9hmyQw-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 1552A804762; Thu, 5 Nov 2020 07:08:11 +0000 (UTC) Received: from x1.home (ovpn-112-213.phx2.redhat.com [10.3.112.213]) by smtp.corp.redhat.com (Postfix) with ESMTP id 0BA3D5DA33; Thu, 5 Nov 2020 07:08:06 +0000 (UTC) Date: Thu, 5 Nov 2020 00:08:06 -0700 From: Alex Williamson To: Vikas Gupta Cc: eric.auger@redhat.com, cohuck@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, vikram.prakash@broadcom.com Subject: Re: [RFC, v0 1/3] vfio/platform: add support for msi Message-ID: <20201105000806.1df16656@x1.home> In-Reply-To: <20201105060257.35269-2-vikas.gupta@broadcom.com> References: <20201105060257.35269-1-vikas.gupta@broadcom.com> <20201105060257.35269-2-vikas.gupta@broadcom.com> Organization: Red Hat MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 5 Nov 2020 11:32:55 +0530 Vikas Gupta wrote: > diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h > index 2f313a238a8f..aab051e8338d 100644 > --- a/include/uapi/linux/vfio.h > +++ b/include/uapi/linux/vfio.h > @@ -203,6 +203,7 @@ struct vfio_device_info { > #define VFIO_DEVICE_FLAGS_AP (1 << 5) /* vfio-ap device */ > #define VFIO_DEVICE_FLAGS_FSL_MC (1 << 6) /* vfio-fsl-mc device */ > #define VFIO_DEVICE_FLAGS_CAPS (1 << 7) /* Info supports caps */ > +#define VFIO_DEVICE_FLAGS_MSI (1 << 8) /* Device supports msi */ > __u32 num_regions; /* Max region index + 1 */ > __u32 num_irqs; /* Max IRQ index + 1 */ > __u32 cap_offset; /* Offset within info struct of first cap */ This doesn't make any sense to me, MSIs are just edge triggered interrupts to userspace, so why isn't this fully described via VFIO_DEVICE_GET_IRQ_INFO? If we do need something new to describe it, this seems incomplete, which indexes are MSI (IRQ_INFO can describe that)? We also already support MSI with vfio-pci, so a global flag for the device advertising this still seems wrong. Thanks, Alex