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;
Subject: Re: MSI/MSIX for VFIO platform
To:     Alex Williamson <alex.williamson@redhat.com>,
        Vikas Gupta <vikas.gupta@broadcom.com>
Cc:     Cornelia Huck <cohuck@redhat.com>, kvm@vger.kernel.org,
        linux-kernel@vger.kernel.org,
        Vikram Prakash <vikram.prakash@broadcom.com>,
        Srinath Mannam <srinath.mannam@broadcom.com>
References: <c94c36305980f80674aa699e27b9895b@mail.gmail.com>
 <20200910105735.1e060b95@w520.home>
From:   Auger Eric <eric.auger@redhat.com>
Message-ID: <f9b3c805-cd64-3402-ff73-339c35c4c27a@redhat.com>
Date:   Fri, 11 Sep 2020 15:52:59 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <20200910105735.1e060b95@w520.home>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi Vikas,

On 9/10/20 6:57 PM, Alex Williamson wrote:
> On Thu, 10 Sep 2020 16:15:27 +0530
> Vikas Gupta <vikas.gupta@broadcom.com> wrote:
> 
>> Hi Alex/Cornelia,
>>
>> We are looking for MSI interrupts for platform devices in user-space
>> applications via event/poll mechanism using VFIO.
>>
>> Since there is no support for MSI/MSIX handling in VFIO-platform in kernel,
>> it may not possible to get this feature in user-space.
>>
>> Is there any other way we can get this feature in user-space OR can you
>> please suggest if any patch or feature is in progress for same in VFIO
>> platform?
>>
>> Any suggestions would be helpful.
> 
> Eric (Cc'd) is the maintainer of vfio-platform.
> 
> vfio-platform devices don't have IRQ indexes dedicated to MSI and MSI-X
> like vfio-pci devices do (technically these are PCI concepts, but I
> assume we're referring generically to message signaled interrupts), but
> that's simply due to the lack of standardization in platform devices.
> Logically these are simply collections of edge triggered interrupts,
> which the vfio device API supports generically, it's simply a matter
> that the vfio bus driver exposing a vfio-platform device create an IRQ
> index exposing these vectors.  Thanks,

I have not worked on MSI support and I am not aware of any work
happening in this area.

First I would recommend to look at IRQ related uapis exposed by VFIO:
VFIO_DEVICE_GET_IRQ_INFO
VFIO_DEVICE_SET_IRQS

and try to understand if they can be implemented for MSIs in a generic
way in the vfio_platform driver using platform-msi helpers.

For instance VFIO_DEVICE_GET_IRQ_INFO would need to return the number of
requested vectors. On init I guess we should allocate vectors using
platform_msi_domain_alloc_irqs/ devm_request_irq and in the handler
trigger the eventfd provided through VFIO_DEVICE_SET_IRQS.

On userspace where you have to trap the MSI setup to call the above
functions and setup irqfd injection. This would be device specific as
opposed to PCI. That's just rough ideas at the moment.

Thanks

Eric

> 
> Alex
>