From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kernel test robot <lkp@intel.com>,
Chao Peng <chao.p.peng@linux.intel.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Fuad Tabba <tabba@google.com>,
Xu Yilun <yilun.xu@linux.intel.com>,
Kai Huang <kai.huang@intel.com>,
Tianrui Zhao <zhaotianrui@loongson.cn>,
Bibo Mao <maobibo@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>
Subject: 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'?
Date: Tue, 16 Jan 2024 10:43:23 -0800 [thread overview]
Message-ID: <ZabOS2uWDJ1fAhQi@google.com> (raw)
In-Reply-To: <CABgObfZfjD9RqHOQsZquv7g_u4TRaJyNj315Z05R=piGnFAEvg@mail.gmail.com>
+KVM LoongArch maintainers
On Tue, Jan 16, 2024, Paolo Bonzini wrote:
> On Tue, Jan 16, 2024 at 2:06 PM kernel test robot <lkp@intel.com> 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@intel.com/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@intel.com/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.
next prev parent reply other threads:[~2024-01-16 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 13:05 [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'? kernel test robot
2024-01-16 17:45 ` Paolo Bonzini
2024-01-16 18:43 ` Sean Christopherson [this message]
2024-01-17 2:08 ` Huacai Chen
2024-01-18 9:03 ` Huacai Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZabOS2uWDJ1fAhQi@google.com \
--to=seanjc@google.com \
--cc=chao.p.peng@linux.intel.com \
--cc=chenhuacai@kernel.org \
--cc=kai.huang@intel.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=maobibo@loongson.cn \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=tabba@google.com \
--cc=yilun.xu@linux.intel.com \
--cc=zhaotianrui@loongson.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.