Thread (28 messages) 28 messages, 3 authors, 2025-01-06

Re: [PATCH v3 06/14] iommufd: Add IOMMUFD_OBJ_VIRQ and IOMMUFD_CMD_VIRQ_ALLOC

From: Jason Gunthorpe <jgg@nvidia.com>
Date: 2025-01-02 20:45:16
Also in: linux-doc, linux-iommu, linux-kselftest, linux-patches, lkml

On Tue, Dec 17, 2024 at 09:00:19PM -0800, Nicolin Chen wrote:
Allow a vIOMMU object to allocate vIRQ Event Queues, with a condition that
each vIOMMU can only have one single vIRQ event queue per type.
I suggest you should tend to use the eventq as the primary naming not
vIRQ, I think that will be a bit clearer.

The virq in the VM is edge triggered by an event queue FD becoming
readable, but the event queue is the file descriptor that reports a
batch of events on read().

The virq name evokes similarities to the virq in vfio which is purely
about conveying if an IRQ edge has happened through an eventfd and has
no event queue associated with it.

Jason
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help