[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250507123103.GC90261@nvidia.com>
Date: Wed, 7 May 2025 09:31:03 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Vasant Hegde <vasant.hegde@....com>
Cc: Nicolin Chen <nicolinc@...dia.com>, kevin.tian@...el.com,
corbet@....net, will@...nel.org, bagasdotme@...il.com,
robin.murphy@....com, joro@...tes.org, thierry.reding@...il.com,
vdumpa@...dia.com, jonathanh@...dia.com, shuah@...nel.org,
jsnitsel@...hat.com, nathan@...nel.org, peterz@...radead.org,
yi.l.liu@...el.com, mshavit@...gle.com, praan@...gle.com,
zhangzekun11@...wei.com, iommu@...ts.linux.dev,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-tegra@...r.kernel.org,
linux-kselftest@...r.kernel.org, patches@...ts.linux.dev,
mochs@...dia.com, alok.a.tiwari@...cle.com,
Suravee Suthikulpanit <suravee.suthikulpanit@....com>
Subject: Re: [PATCH v3 11/23] iommufd/viommu: Add IOMMUFD_CMD_VQUEUE_ALLOC
ioctl
On Wed, May 07, 2025 at 01:11:43PM +0530, Vasant Hegde wrote:
> - MMIO Offset 0018h IOMMU Control Register
> EventLogEn: Event log enable
> * When guest sets this bit, qemu will trap and will send queue_alloc
> * When guest disables this bit, qemu will trap and send vqueue_destroy
>
> This part is fine.
Ok
> EventIntEn: Event log interrupt enable
> * When guest sets this bit, qemu will trap
> * this needs to be communicated to Host so that we can program VF Control
> BAR and enable the interrupt
This sounds like modifying the vqueue? Or maybe on the viommu?
> - There is other bit "Completion wait interrupt enable"
> This doesn't related to any buffer. Instead if we configure this for
> completion wait command it will generate interrupt.
This sounds like a modify on the VIOMMU object?
Jason
Powered by blists - more mailing lists