[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175033652435.3069576.5168060744496766238.b4-ty@kernel.org>
Date: Thu, 19 Jun 2025 13:36:02 +0100
From: Marc Zyngier <maz@...nel.org>
To: Oliver Upton <oliver.upton@...ux.dev>,
Paolo Bonzini <pbonzini@...hat.com>,
Joerg Roedel <joro@...tes.org>,
David Woodhouse <dwmw2@...radead.org>,
Lu Baolu <baolu.lu@...ux.intel.com>,
Sean Christopherson <seanjc@...gle.com>
Cc: linux-arm-kernel@...ts.infradead.org,
kvmarm@...ts.linux.dev,
kvm@...r.kernel.org,
iommu@...ts.linux.dev,
linux-kernel@...r.kernel.org,
Sairaj Kodilkar <sarunkod@....com>,
Vasant Hegde <vasant.hegde@....com>,
Maxim Levitsky <mlevitsk@...hat.com>,
Joao Martins <joao.m.martins@...cle.com>,
Francesco Lavra <francescolavra.fl@...il.com>,
David Matlack <dmatlack@...gle.com>
Subject: Re: (subset) [PATCH v3 01/62] KVM: arm64: Explicitly treat routing entry type changes as changes
On Wed, 11 Jun 2025 15:45:04 -0700, Sean Christopherson wrote:
> Explicitly treat type differences as GSI routing changes, as comparing MSI
> data between two entries could get a false negative, e.g. if userspace
> changed the type but left the type-specific data as-
>
> Note, the same bug was fixed in x86 by commit bcda70c56f3e ("KVM: x86:
> Explicitly treat routing entry type changes as changes").
>
> [...]
Applied to fixes, thanks!
[01/62] KVM: arm64: Explicitly treat routing entry type changes as changes
commit: 1fbe6861a6d9a942fb8ab8677ddf1ecb86b1af60
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists