Re: [linux-next:master 697/13343] arch/loongarch/kvm/mmu.c:810:13: error: implicit declaration of function 'mmu_invalidate_retry_hva'; did you mean 'mmu_invalidate_retry_gfn'?

[Sean Christopherson <seanjc@xxxxxxxxxx>]

+KVM LoongArch maintainers

On Tue, Jan 16, 2024, Paolo Bonzini wrote:
> On Tue, Jan 16, 2024 at 2:06 PM kernel test robot <lkp@xxxxxxxxx> wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head:   8d04a7e2ee3fd6aabb8096b00c64db0d735bc874
> > commit: 8569992d64b8f750e34b7858eac5d7daaf0f80fd [697/13343] KVM: Use gfn instead of hva for mmu_notifier_retry
> > config: loongarch-allmodconfig (https://download.01.org/0day-ci/archive/20240116/202401162158.2FqwkuiP-lkp@xxxxxxxxx/config)
> > compiler: loongarch64-linux-gcc (GCC) 13.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240116/202401162158.2FqwkuiP-lkp@xxxxxxxxx/reproduce)
> 
> This was fixed-up when merging the KVM tree, but I missed it because
> it was not mentioned in the loongarch pull request. I'll send a fixup
> as soon as Linus gets back online.

And I suspect KVM LooongArch isn't being fed into linux-next, e.g. the tree entry
in MAINTAINERS points at your repo.

Side topic, where can I find a toolchain that can actually build KVM LooongArch?
Clang recognizes the arch, but barfs on a variety of things, and I can't find the
right Debian packages for gcc.