On Wed, May 13, 2026 at 03:15:52AM +0000, Michael Kelley wrote: > From: Jacob Pan <[email protected]> Sent: Tuesday, May 12, 2026 > 4:46 PM > > > > Hi Mukesh, > > > > On Mon, 11 May 2026 19:02:49 -0700 > > Mukesh R <[email protected]> wrote: > > > > > This file actually implements irq remapping, so rename to more > > > appropriate hyperv-irq.c. A new file to implement hyperv iommu will > > > be introduced later. Also, it should not be tied to HYPERV_IOMMU, > > > but to CONFIG_HYPERV and IRQ_REMAP. The file already has #ifdef > > > CONFIG_IRQ_REMAP. > > > > > > Reviewed-by: Anirudh Rayabharam (Microsoft) <[email protected]> > > > Signed-off-by: Mukesh R <[email protected]> > > > --- > > > MAINTAINERS | 2 +- > > > drivers/iommu/Makefile | 2 +- > > > drivers/iommu/{hyperv-iommu.c => hyperv-irq.c} | 6 +++--- > > > > Given that we have multiple Hyper-V IOMMU-related files — this renamed > > hyperv-irq.c, the existing hyperv-iommu code, iommu-root (this > > series) and the recently posted guest pvIOMMU driver — should we create > > a drivers/iommu/hyperv/ directory to consolidate them? > > Patch 1/4 in the guest pvIOMMU driver [1] that was recently posted by > Yu Zhang does as you suggest. > > Michael > > [1] > https://lore.kernel.org/linux-hyperv/[email protected]/ >
Maybe we can send a standalone patch and get it merged first (move it to drivers/iommu/hyperv/irq_remapping.c)? The rename itself is a meaningful cleanup regardless of either series, and in the future, both Mukesh and I can can then build on top of it without conflicts. :) B.R. Yu
