[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABgObfb5QngpP_DGLx_6Y+wD+-3aSOnYUsdHCpym+V6VxY8krg@mail.gmail.com>
Date: Thu, 17 Apr 2025 19:37:35 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Sairaj Kodilkar <sarunkod@....com>
Cc: Sean Christopherson <seanjc@...gle.com>, Vasant Hegde <vasant.hegde@....com>,
Joerg Roedel <joro@...tes.org>, David Woodhouse <dwmw2@...radead.org>,
Lu Baolu <baolu.lu@...ux.intel.com>, kvm@...r.kernel.org, iommu@...ts.linux.dev,
linux-kernel@...r.kernel.org, Maxim Levitsky <mlevitsk@...hat.com>,
Joao Martins <joao.m.martins@...cle.com>, David Matlack <dmatlack@...gle.com>,
Naveen N Rao <naveen.rao@....com>
Subject: Re: [PATCH 06/67] iommu/amd: WARN if KVM attempts to set vCPU
affinity without posted intrrupts
On Wed, Apr 16, 2025 at 11:47 AM Sairaj Kodilkar <sarunkod@....com> wrote:
> I think it is safe to have this WARN_ON(!dev_data->use_vapic) without
> any false positives. IOMMU driver sets the dev_data->use_vapic only when
> the device is in UNMANAGE_DOMAIN and it is 0 if the device is in any
> other domain (DMA, DMA_FQ, IDENTITY).
>
> We have a bigger problem from the VFIO side if we hit this WARN_ON()
> as device is not in a UNMANGED_DOMAIN.
This does seem safe, but its more of a VFIO/iommu change than a KVM
one so I'm not too comfortable with merging it myself; please submit
it as a separate patch.
Paolo
Powered by blists - more mailing lists