> -----Original Message----- > From: Sean Christopherson <seanjc@xxxxxxxxxx> > Sent: Monday, June 24, 2024 4:32 PM > To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@xxxxxxxxxx> > Cc: Catalin Marinas <catalin.marinas@xxxxxxx>; Will Deacon > <will@xxxxxxxxxx>; Marc Zyngier <maz@xxxxxxxxxx>; Oliver Upton > <oliver.upton@xxxxxxxxx>; Huacai Chen <chenhuacai@xxxxxxxxxx>; Michael > Ellerman <mpe@xxxxxxxxxxxxxx>; Anup Patel <anup@xxxxxxxxxxxxxx>; Paul > Walmsley <paul.walmsley@xxxxxxxxxx>; Palmer Dabbelt > <palmer@xxxxxxxxxxx>; Albert Ou <aou@xxxxxxxxxxxxxxxxx>; Heiko > Carstens <hca@xxxxxxxxxxxxx>; Vasily Gorbik <gor@xxxxxxxxxxxxx>; > Alexander Gordeev <agordeev@xxxxxxxxxxxxx>; Christian Borntraeger > <borntraeger@xxxxxxxxxxxxx>; Janosch Frank <frankja@xxxxxxxxxxxxx>; > Claudio Imbrenda <imbrenda@xxxxxxxxxxxxx>; Thomas Gleixner > <tglx@xxxxxxxxxxxxx>; Ingo Molnar <mingo@xxxxxxxxxx>; Borislav Petkov > <bp@xxxxxxxxx>; Dave Hansen <dave.hansen@xxxxxxxxxxxxxxx>; > x86@xxxxxxxxxx; Peter Zijlstra <peterz@xxxxxxxxxxxxx>; Arnaldo Carvalho de > Melo <acme@xxxxxxxxxx>; Paolo Bonzini <pbonzini@xxxxxxxxxx>; Tony > Krowiak <akrowiak@xxxxxxxxxxxxx>; Halil Pasic <pasic@xxxxxxxxxxxxx>; > Jason Herne <jjherne@xxxxxxxxxxxxx>; Harald Freudenberger > <freude@xxxxxxxxxxxxx>; Alex Williamson <alex.williamson@xxxxxxxxxx>; > Andy Lutomirski <luto@xxxxxxxxxx>; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; > kvmarm@xxxxxxxxxxxxxxx; linux-mips@xxxxxxxxxxxxxxx; kvm@xxxxxxxxxxxxxxx; > linuxppc-dev@xxxxxxxxxxxxxxxx; kvm-riscv@xxxxxxxxxxxxxxxxxxx; linux- > riscv@xxxxxxxxxxxxxxxxxxx; linux-s390@xxxxxxxxxxxxxxx; linux- > kernel@xxxxxxxxxxxxxxx; linux-perf-users@xxxxxxxxxxxxxxx; Anish Ghulati > <aghulati@xxxxxxxxxx>; Venkatesh Srinivas <venkateshs@xxxxxxxxxxxx>; > Andrew Thornton <andrewth@xxxxxxxxxx> > Subject: Re: [PATCH 00/26] KVM: vfio: Hide KVM internals from others > > On Thu, Jun 20, 2024, Shameerali Kolothum Thodi wrote: > > > This is a borderline RFC series to hide KVM's internals from the rest of > > > the kernel, where "internals" means data structures, enums, #defines, > > > APIs, etc. that are intended to be KVM-only, but are exposed > everywhere > > > due to kvm_host.h (and other headers) living in the global include paths. > > > > Hi Sean, > > > > Just thought of checking with you on this series. Do you have plans to > revive this > > series? > > Yep! > > > The reason I am asking is, on ARM64/KVM side we do have a requirement > > to share the KVM VMID with SMMUV3. Please see the RFC I sent out > earlier this > > year[1]. The series basically provides a way for KVM to pin a VMID and also > > associates an iommufd ctx with a struct kvm * to retrieve that VMID. > > > > As mentioned above, some of the patches in this series(especially 1-4 & 6) > that > > does the VFIO cleanups and dropping CONFIG_KVM_VFIO looks very > straightforward > > and useful. I am thinking of including those when I re-spin my RFC series, if > > that’s ok. > > Please don't include them, as the patch they build towards (patch 5) is > buggy[*], > and I am fairly certain that at least some of the patches will change > significantly. Ok. Got it. Thanks for taking a look at the KVM pinned VMID series and comments there. Shameer
