From: kernel test robot <lkp@intel.com>
To: Bibo Mao <maobibo@loongson.cn>,
Tianrui Zhao <zhaotianrui@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, WANG Xuerui <kernel@xen0n.name>,
Sean Christopherson <seanjc@google.com>,
kvm@vger.kernel.org, loongarch@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6/6] LoongArch: KVM: Mark page accessed and dirty with page ref added
Date: Thu, 20 Jun 2024 11:05:19 +0800 [thread overview]
Message-ID: <202406201000.BjivosoH-lkp@intel.com> (raw)
In-Reply-To: <20240619080940.2690756-7-maobibo@loongson.cn>
Hi Bibo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 92e5605a199efbaee59fb19e15d6cc2103a04ec2]
url: https://github.com/intel-lab-lkp/linux/commits/Bibo-Mao/LoongArch-KVM-Delay-secondary-mmu-tlb-flush-until-guest-entry/20240619-161831
base: 92e5605a199efbaee59fb19e15d6cc2103a04ec2
patch link: https://lore.kernel.org/r/20240619080940.2690756-7-maobibo%40loongson.cn
patch subject: [PATCH v2 6/6] LoongArch: KVM: Mark page accessed and dirty with page ref added
config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20240620/202406201000.BjivosoH-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/20240620/202406201000.BjivosoH-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202406201000.BjivosoH-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/loongarch/kvm/mmu.o: warning: objtool: __jump_table+0x0: special: can't find orig instruction
objdump-func vmlinux.o __jump_table:
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-06-20 3:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 8:09 [PATCH v2 0/6] LoongArch: KVM: Fix some issues relative with mmu Bibo Mao
2024-06-19 8:09 ` [PATCH v2 1/6] LoongArch: KVM: Delay secondary mmu tlb flush until guest entry Bibo Mao
2024-06-23 7:54 ` Huacai Chen
2024-06-24 1:22 ` maobibo
2024-06-24 1:58 ` Huacai Chen
2024-06-24 2:35 ` maobibo
2024-06-19 8:09 ` [PATCH v2 2/6] LoongArch: KVM: Select huge page only if secondary mmu supports it Bibo Mao
2024-06-23 7:55 ` Huacai Chen
2024-06-24 1:28 ` maobibo
2024-06-19 8:09 ` [PATCH v2 3/6] LoongArch: KVM: Discard dirty page tracking on readonly memslot Bibo Mao
2024-06-19 8:09 ` [PATCH v2 4/6] LoongArch: KVM: Add memory barrier before update pmd entry Bibo Mao
2024-06-23 10:18 ` Huacai Chen
2024-06-24 1:37 ` maobibo
2024-06-24 1:56 ` Huacai Chen
2024-06-24 2:21 ` maobibo
2024-06-24 4:18 ` Huacai Chen
2024-06-24 6:00 ` WANG Rui
2024-06-19 8:09 ` [PATCH v2 5/6] LoongArch: KVM: Add dirty bitmap initially all set support Bibo Mao
2024-06-19 8:09 ` [PATCH v2 6/6] LoongArch: KVM: Mark page accessed and dirty with page ref added Bibo Mao
2024-06-20 3:05 ` kernel test robot [this message]
2024-06-22 5:21 ` Huacai Chen
2024-06-24 1:12 ` maobibo
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=202406201000.BjivosoH-lkp@intel.com \
--to=lkp@intel.com \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=maobibo@loongson.cn \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=seanjc@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®