From: kernel test robot <lkp@intel.com>
To: Gavin Shan <gshan@redhat.com>, kvmarm@lists.cs.columbia.edu
Cc: maz@kernel.org, drjones@redhat.com, kbuild-all@lists.01.org,
shan.gavin@gmail.com, kvm@vger.kernel.org,
linux-doc@vger.kernel.org, catalin.marinas@arm.com,
corbet@lwn.net, linux-kernel@vger.kernel.org,
zhenyzha@redhat.com, will@kernel.org,
linux-kselftest@vger.kernel.org, bgardon@google.com,
dmatlack@google.com, pbonzini@redhat.com, shuah@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/5] KVM: arm64: Enable ring-based dirty memory tracking
Date: Sat, 17 Sep 2022 23:10:14 +0800 [thread overview]
Message-ID: <202209180726.FLL69aKA-lkp@intel.com> (raw)
In-Reply-To: <20220916045135.154505-3-gshan@redhat.com>
Hi Gavin,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on kvm/queue]
[also build test WARNING on kvmarm/next linus/master v6.0-rc5 next-20220916]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Gavin-Shan/KVM-arm64-Enable-ring-based-dirty-memory-tracking/20220916-125417
base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
config: arm64-allyesconfig (https://download.01.org/0day-ci/archive/20220918/202209180726.FLL69aKA-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/a1a4cd8f6a5e8927f800baff7d965870a1b7d7ba
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Gavin-Shan/KVM-arm64-Enable-ring-based-dirty-memory-tracking/20220916-125417
git checkout a1a4cd8f6a5e8927f800baff7d965870a1b7d7ba
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/arm64/kvm/../../../virt/kvm/dirty_ring.c:14:12: warning: no previous prototype for 'kvm_cpu_dirty_log_size' [-Wmissing-prototypes]
14 | int __weak kvm_cpu_dirty_log_size(void)
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/kvm_cpu_dirty_log_size +14 arch/arm64/kvm/../../../virt/kvm/dirty_ring.c
fb04a1eddb1a65 Peter Xu 2020-09-30 13
fb04a1eddb1a65 Peter Xu 2020-09-30 @14 int __weak kvm_cpu_dirty_log_size(void)
fb04a1eddb1a65 Peter Xu 2020-09-30 15 {
fb04a1eddb1a65 Peter Xu 2020-09-30 16 return 0;
fb04a1eddb1a65 Peter Xu 2020-09-30 17 }
fb04a1eddb1a65 Peter Xu 2020-09-30 18
--
0-DAY CI Kernel Test Service
https://01.org/lkp
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Gavin Shan <gshan@redhat.com>, kvmarm@lists.cs.columbia.edu
Cc: kbuild-all@lists.01.org, kvm@vger.kernel.org,
linux-doc@vger.kernel.org, catalin.marinas@arm.com,
linux-kselftest@vger.kernel.org, bgardon@google.com,
shuah@kernel.org, corbet@lwn.net, maz@kernel.org,
drjones@redhat.com, will@kernel.org, zhenyzha@redhat.com,
dmatlack@google.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, pbonzini@redhat.com,
peterx@redhat.com, oliver.upton@linux.dev, shan.gavin@gmail.com
Subject: Re: [PATCH v2 2/5] KVM: arm64: Enable ring-based dirty memory tracking
Date: Sat, 17 Sep 2022 23:10:14 +0800 [thread overview]
Message-ID: <202209180726.FLL69aKA-lkp@intel.com> (raw)
In-Reply-To: <20220916045135.154505-3-gshan@redhat.com>
Hi Gavin,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on kvm/queue]
[also build test WARNING on kvmarm/next linus/master v6.0-rc5 next-20220916]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Gavin-Shan/KVM-arm64-Enable-ring-based-dirty-memory-tracking/20220916-125417
base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
config: arm64-allyesconfig (https://download.01.org/0day-ci/archive/20220918/202209180726.FLL69aKA-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/a1a4cd8f6a5e8927f800baff7d965870a1b7d7ba
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Gavin-Shan/KVM-arm64-Enable-ring-based-dirty-memory-tracking/20220916-125417
git checkout a1a4cd8f6a5e8927f800baff7d965870a1b7d7ba
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/arm64/kvm/../../../virt/kvm/dirty_ring.c:14:12: warning: no previous prototype for 'kvm_cpu_dirty_log_size' [-Wmissing-prototypes]
14 | int __weak kvm_cpu_dirty_log_size(void)
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/kvm_cpu_dirty_log_size +14 arch/arm64/kvm/../../../virt/kvm/dirty_ring.c
fb04a1eddb1a65 Peter Xu 2020-09-30 13
fb04a1eddb1a65 Peter Xu 2020-09-30 @14 int __weak kvm_cpu_dirty_log_size(void)
fb04a1eddb1a65 Peter Xu 2020-09-30 15 {
fb04a1eddb1a65 Peter Xu 2020-09-30 16 return 0;
fb04a1eddb1a65 Peter Xu 2020-09-30 17 }
fb04a1eddb1a65 Peter Xu 2020-09-30 18
--
0-DAY CI Kernel Test Service
https://01.org/lkp
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Gavin Shan <gshan@redhat.com>, kvmarm@lists.cs.columbia.edu
Cc: kbuild-all@lists.01.org, kvm@vger.kernel.org,
linux-doc@vger.kernel.org, catalin.marinas@arm.com,
linux-kselftest@vger.kernel.org, bgardon@google.com,
shuah@kernel.org, corbet@lwn.net, maz@kernel.org,
drjones@redhat.com, will@kernel.org, zhenyzha@redhat.com,
dmatlack@google.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, pbonzini@redhat.com,
peterx@redhat.com, oliver.upton@linux.dev, shan.gavin@gmail.com
Subject: Re: [PATCH v2 2/5] KVM: arm64: Enable ring-based dirty memory tracking
Date: Sat, 17 Sep 2022 23:10:14 +0800 [thread overview]
Message-ID: <202209180726.FLL69aKA-lkp@intel.com> (raw)
In-Reply-To: <20220916045135.154505-3-gshan@redhat.com>
Hi Gavin,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on kvm/queue]
[also build test WARNING on kvmarm/next linus/master v6.0-rc5 next-20220916]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Gavin-Shan/KVM-arm64-Enable-ring-based-dirty-memory-tracking/20220916-125417
base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
config: arm64-allyesconfig (https://download.01.org/0day-ci/archive/20220918/202209180726.FLL69aKA-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/a1a4cd8f6a5e8927f800baff7d965870a1b7d7ba
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Gavin-Shan/KVM-arm64-Enable-ring-based-dirty-memory-tracking/20220916-125417
git checkout a1a4cd8f6a5e8927f800baff7d965870a1b7d7ba
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/arm64/kvm/../../../virt/kvm/dirty_ring.c:14:12: warning: no previous prototype for 'kvm_cpu_dirty_log_size' [-Wmissing-prototypes]
14 | int __weak kvm_cpu_dirty_log_size(void)
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/kvm_cpu_dirty_log_size +14 arch/arm64/kvm/../../../virt/kvm/dirty_ring.c
fb04a1eddb1a65 Peter Xu 2020-09-30 13
fb04a1eddb1a65 Peter Xu 2020-09-30 @14 int __weak kvm_cpu_dirty_log_size(void)
fb04a1eddb1a65 Peter Xu 2020-09-30 15 {
fb04a1eddb1a65 Peter Xu 2020-09-30 16 return 0;
fb04a1eddb1a65 Peter Xu 2020-09-30 17 }
fb04a1eddb1a65 Peter Xu 2020-09-30 18
--
0-DAY CI Kernel Test Service
https://01.org/lkp
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-17 15:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 4:51 [PATCH v2 0/5] KVM: arm64: Enable ring-based dirty memory tracking Gavin Shan
2022-09-16 4:51 ` Gavin Shan
2022-09-16 4:51 ` Gavin Shan
2022-09-16 4:51 ` [PATCH v2 1/5] KVM: x86: Introduce KVM_REQ_RING_SOFT_FULL Gavin Shan
2022-09-16 4:51 ` Gavin Shan
2022-09-16 4:51 ` Gavin Shan
2022-09-16 18:09 ` Peter Xu
2022-09-16 18:09 ` Peter Xu
2022-09-16 18:09 ` Peter Xu
2022-09-18 9:00 ` Marc Zyngier
2022-09-18 9:00 ` Marc Zyngier
2022-09-18 9:00 ` Marc Zyngier
2022-09-18 23:58 ` Gavin Shan
2022-09-18 23:58 ` Gavin Shan
2022-09-18 23:58 ` Gavin Shan
2022-09-19 9:22 ` Marc Zyngier
2022-09-19 9:22 ` Marc Zyngier
2022-09-19 9:22 ` Marc Zyngier
2022-09-19 16:17 ` Peter Xu
2022-09-19 16:17 ` Peter Xu
2022-09-19 16:17 ` Peter Xu
2022-09-16 4:51 ` [PATCH v2 2/5] KVM: arm64: Enable ring-based dirty memory tracking Gavin Shan
2022-09-16 4:51 ` Gavin Shan
2022-09-16 4:51 ` Gavin Shan
2022-09-17 15:10 ` kernel test robot [this message]
2022-09-17 15:10 ` kernel test robot
2022-09-17 15:10 ` kernel test robot
2022-09-19 1:27 ` Gavin Shan
2022-09-19 1:27 ` Gavin Shan
2022-09-19 1:27 ` Gavin Shan
2022-09-19 1:27 ` Gavin Shan
2022-09-16 4:51 ` [PATCH v2 3/5] KVM: selftests: Use host page size to map ring buffer in dirty_log_test Gavin Shan
2022-09-16 4:51 ` Gavin Shan
2022-09-16 4:51 ` Gavin Shan
2022-09-16 4:51 ` [PATCH v2 4/5] KVM: selftests: Clear dirty ring states between two modes " Gavin Shan
2022-09-16 4:51 ` Gavin Shan
2022-09-16 4:51 ` Gavin Shan
2022-09-16 4:51 ` [PATCH v2 5/5] KVM: selftests: Automate choosing dirty ring size " Gavin Shan
2022-09-16 4:51 ` Gavin Shan
2022-09-16 4:51 ` Gavin Shan
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=202209180726.FLL69aKA-lkp@intel.com \
--to=lkp@intel.com \
--cc=bgardon@google.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dmatlack@google.com \
--cc=drjones@redhat.com \
--cc=gshan@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=shan.gavin@gmail.com \
--cc=shuah@kernel.org \
--cc=will@kernel.org \
--cc=zhenyzha@redhat.com \
/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.