mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Natarajan, Janakarajan" <Janakarajan.Natarajan@amd.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, kvm@vger.kernel.org, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Radim Krcmar <rkrcmar@redhat.com>,
	Len Brown <len.brown@intel.com>, Kyle Huey <me@kylehuey.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	Borislav Petkov <bp@suse.de>,
	Grzegorz Andrejczuk <grzegorz.andrejczuk@intel.com>,
	Kan Liang <Kan.liang@intel.com>
Subject: Re: [PATCH v4 3/3] x86/kvm: Expose AMD Core Perf Extension flag to guests
Date: Fri, 2 Feb 2018 17:26:41 -0600	[thread overview]
Message-ID: <49f7c379-87e9-bf01-1590-63dcd7726d7d@amd.com> (raw)
In-Reply-To: <201802030310.MucL4Uiq%fengguang.wu@intel.com>

On 2/2/2018 2:03 PM, kbuild test robot wrote:
> Hi Janakarajan,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on tip/x86/core]
> [also build test WARNING on v4.15]
> [cannot apply to kvm/linux-next next-20180202]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
This patch uses functions defined in commit 
'd6321d493319bfd406c484e8359c6101cbda39d3 KVM: x86: generalize 
guest_cpuid_has_ helpers'.
https://lkml.org/lkml/2017/8/2/811
>
> url:    https://github.com/0day-ci/linux/commits/Janakarajan-Natarajan/Support-Perf-Extensions-on-AMD-KVM-guests/20180202-231344
> reproduce:
>          # apt-get install sparse
>          make ARCH=x86_64 allmodconfig
>          make C=1 CF=-D__CHECK_ENDIAN__
>
>
> sparse warnings: (new ones prefixed by >>)
>
>>> arch/x86/kvm/cpuid.c:58:6: sparse: symbol 'perf_ext_supported' was not declared. Should it be
> Please review and possibly fold the followup patch.
>
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

  reply	other threads:[~2018-02-02 23:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30 17:32 [PATCH v4 0/3] Support Perf Extensions on AMD KVM guests Janakarajan Natarajan
2018-01-30 17:32 ` [PATCH v4 1/3] x86/msr: Add AMD Core Perf Extension MSRs Janakarajan Natarajan
2018-01-30 17:32 ` [PATCH v4 2/3] x86/kvm: Add support for AMD Core Perf Extension in guest Janakarajan Natarajan
2018-01-30 17:32 ` [PATCH v4 3/3] x86/kvm: Expose AMD Core Perf Extension flag to guests Janakarajan Natarajan
2018-02-02 20:03   ` [RFC PATCH] x86/kvm: perf_ext_supported() can be static kbuild test robot
2018-02-02 20:03   ` [PATCH v4 3/3] x86/kvm: Expose AMD Core Perf Extension flag to guests kbuild test robot
2018-02-02 23:26     ` Natarajan, Janakarajan [this message]
2018-02-05 13:43   ` Radim Krcmar
2018-02-05 17:48     ` Natarajan, Janakarajan

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=49f7c379-87e9-bf01-1590-63dcd7726d7d@amd.com \
    --to=janakarajan.natarajan@amd.com \
    --cc=Kan.liang@intel.com \
    --cc=bp@suse.de \
    --cc=grzegorz.andrejczuk@intel.com \
    --cc=hpa@zytor.com \
    --cc=kbuild-all@01.org \
    --cc=kvm@vger.kernel.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=me@kylehuey.com \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=x86@kernel.org \
    /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®