linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Guillaume Tucker <guillaume.tucker@collabora.com>,
	kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [kbuild-all] Re: [linux-next:master 8922/11208] lib/x86_64/processor.c:636:25: error: 'KVM_X86_XCOMP_GUEST_SUPP' undeclared
Date: Wed, 20 Jul 2022 13:23:41 +0800	[thread overview]
Message-ID: <b575bf56-ac59-129e-5d83-4531d039c019@intel.com> (raw)
In-Reply-To: <85e57715-09b2-7f49-71bc-d08957b90d68@collabora.com>



On 7/19/2022 3:49 PM, Guillaume Tucker wrote:
> On 19/07/2022 03:28, kernel test robot wrote:
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> head:   036ad6daa8f0fd357af7f50f9da58539eaa6f68c
>> commit: 3bb267a36185b64949ea9c8bbfe93eb01986f6cb [8922/11208] selftests: drop khdr make target
>> reproduce: make O=/tmp/kselftest -C tools/testing/selftests
>>
>> If you fix the issue, kindly add following tag where applicable
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> Note: the linux-next/master HEAD 036ad6daa8f0fd357af7f50f9da58539eaa6f68c builds fine.
>>        It may have been fixed somewhere.
>>
>> All errors (new ones prefixed by >>):
>>
>>     lib/x86_64/processor.c: In function 'vm_xsave_req_perm':
>>>> lib/x86_64/processor.c:636:25: error: 'KVM_X86_XCOMP_GUEST_SUPP' undeclared (first use in this function)
>>       636 |                 .attr = KVM_X86_XCOMP_GUEST_SUPP,
>>           |
> 
> This is because the kernel headers have to be installed first
> now.  So this command needs to be added:

Hi Guillaume,

Thanks for your guidance, we have added the command to the CI.

Best Regards,
Rong Chen

> 
>      make O=/tmp/kselftest headers
> 
> before running this one:
> 
>      make O=/tmp/kselftest -C tools/testing/selftests
> 
> See the email thread for more details:
> 
>      https://lore.kernel.org/lkml/b39b9e0b-45f3-1818-39fe-58921182d957@linuxfoundation.org/
> 
> Thanks,
> Guillaume


      reply	other threads:[~2022-07-20  5:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19  1:28 kernel test robot
2022-07-19  7:49 ` Guillaume Tucker
2022-07-20  5:23   ` Chen, Rong A [this message]

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=b575bf56-ac59-129e-5d83-4531d039c019@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=guillaume.tucker@collabora.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=skhan@linuxfoundation.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