linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jing Zhang <jingzhangos@google.com>, KVM <kvm@vger.kernel.org>,
	KVMARM <kvmarm@lists.cs.columbia.edu>,
	LinuxMIPS <linux-mips@vger.kernel.org>,
	KVMPPC <kvm-ppc@vger.kernel.org>,
	LinuxS390 <linux-s390@vger.kernel.org>,
	Linuxkselftest <linux-kselftest@vger.kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
	Julien Thierry <julien.thierry.kdev@gmail.com>
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH 2/4] KVM: stats: Add fd-based API to read binary stats data
Date: Sat, 3 Apr 2021 13:24:18 +0800	[thread overview]
Message-ID: <202104031344.oNE1vaQq-lkp@intel.com> (raw)
In-Reply-To: <20210402224359.2297157-3-jingzhangos@google.com>

[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]

Hi Jing,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on f96be2deac9bca3ef5a2b0b66b71fcef8bad586d]

url:    https://github.com/0day-ci/linux/commits/Jing-Zhang/KVM-statistics-data-fd-based-binary-interface/20210403-064555
base:   f96be2deac9bca3ef5a2b0b66b71fcef8bad586d
config: i386-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


cocci warnings: (new ones prefixed by >>)
>> arch/x86/kvm/x86.c:270:36-37: WARNING: Use ARRAY_SIZE
   arch/x86/kvm/x86.c:235:34-35: WARNING: Use ARRAY_SIZE

vim +270 arch/x86/kvm/x86.c

   267	
   268	struct _kvm_stats_header kvm_vcpu_stats_header = {
   269		.name_size = KVM_STATS_NAME_LEN,
 > 270		.count = sizeof(kvm_vcpu_stats_desc) / sizeof(struct _kvm_stats_desc),
   271		.desc_offset = sizeof(struct kvm_stats_header),
   272		.data_offset = sizeof(struct kvm_stats_header) +
   273			sizeof(kvm_vcpu_stats_desc),
   274	};
   275	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 65059 bytes --]

  reply	other threads:[~2021-04-03  5:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02 22:43 [PATCH 0/4] KVM statistics data fd-based binary interface Jing Zhang
2021-04-02 22:43 ` [PATCH 1/4] KVM: stats: Separate common stats from architecture specific ones Jing Zhang
2021-04-02 22:43 ` [PATCH 2/4] KVM: stats: Add fd-based API to read binary stats data Jing Zhang
2021-04-03  5:24   ` kernel test robot [this message]
2021-04-03 17:42     ` Jing Zhang
2021-04-03 17:35   ` Jing Zhang
2021-04-02 22:43 ` [PATCH 3/4] KVM: stats: Add documentation for statistics data binary interface Jing Zhang
2021-04-02 22:43 ` [PATCH 4/4] KVM: selftests: Add selftest for KVM " Jing Zhang

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=202104031344.oNE1vaQq-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=james.morse@arm.com \
    --cc=jingzhangos@google.com \
    --cc=julien.thierry.kdev@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).