From: kbuild test robot <lkp@intel.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Bandan Das <bsd@redhat.com>, Nadav Amit <nadav.amit@gmail.com>
Subject: Re: [PATCH v2 4/4] KVM: x86: emulate FXSAVE and FXRSTOR
Date: Thu, 3 Nov 2016 07:58:34 +0800 [thread overview]
Message-ID: <201611030741.7Je7TG1V%fengguang.wu@intel.com> (raw)
In-Reply-To: <20161102184537.29039-5-rkrcmar@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]
Hi Radim,
[auto build test ERROR on kvm/linux-next]
[also build test ERROR on v4.9-rc3 next-20161028]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/Radim-Kr-m/KVM-x86-emulate-FXSAVE-and-FXRSTOR/20161103-025333
base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git linux-next
config: x86_64-randconfig-s2-11030650 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
arch/x86/kvm/emulate.c: In function 'em_fxsave':
>> arch/x86/kvm/emulate.c:3931: error: expected string literal before ')' token
arch/x86/kvm/emulate.c:3934: error: expected string literal before ')' token
arch/x86/kvm/emulate.c: In function 'fx_load_64bit_xmm':
arch/x86/kvm/emulate.c:3953: error: expected string literal before ')' token
arch/x86/kvm/emulate.c: In function 'em_fxrstor':
arch/x86/kvm/emulate.c:3990: error: expected string literal before ')' token
arch/x86/kvm/emulate.c:3994: error: expected string literal before ')' token
vim +3931 arch/x86/kvm/emulate.c
3925 return rc;
3926
3927 ctxt->ops->get_fpu(ctxt);
3928
3929 #ifdef CONFIG_X86_64
3930 if (ctxt->rex_prefix & (1 << 3))
> 3931 rc = asm_safe("fxsave64 %[fx]", , [fx] "+m"(fx_state) ::);
3932 else
3933 #endif
3934 rc = asm_safe("fxsave %[fx]", , [fx] "+m"(fx_state) ::);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27618 bytes --]
next prev parent reply other threads:[~2016-11-02 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 18:45 [PATCH v2 0/4] " Radim Krčmář
2016-11-02 18:45 ` [PATCH v2 1/4] KVM: x86: add Align16 instruction flag Radim Krčmář
2016-11-02 18:45 ` [PATCH v2 2/4] KVM: x86: save one bit in ctxt->d Radim Krčmář
2016-11-02 18:45 ` [PATCH v2 3/4] KVM: x86: add asm_safe wrapper Radim Krčmář
2016-11-02 18:45 ` [PATCH v2 4/4] KVM: x86: emulate FXSAVE and FXRSTOR Radim Krčmář
2016-11-02 23:58 ` kbuild test robot [this message]
2016-11-03 13:58 ` Radim Krčmář
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=201611030741.7Je7TG1V%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=bsd@redhat.com \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nadav.amit@gmail.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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
all inboxes | Powered by JetHome®