From: Sean Christopherson <seanjc@google.com>
To: kernel test robot <lkp@intel.com>
Cc: Aaron Lewis <aaronlewis@google.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Alexander Graf <graf@amazon.com>
Subject: Re: lib/x86_64/handlers.S:20: Error: unrecognized instruction `call route_exception'
Date: Tue, 27 Jul 2021 16:07:48 +0000 [thread overview]
Message-ID: <YQAvVGwJqUak1E0l@google.com> (raw)
In-Reply-To: <202107270520.DIJjv4ia-lkp@intel.com>
On Tue, Jul 27, 2021, kernel test robot wrote:
> Hi Aaron,
>
> First bad commit (maybe != root cause):
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: ff1176468d368232b684f75e82563369208bc371
> commit: 29faeb9632012d6c3fa4aa33c3d589b9ff18b206 selftests: kvm: Add exception handling to selftests
> date: 9 months ago
> config: openrisc-randconfig-s031-20210726 (attached as .config)
> compiler: or1k-linux-gcc (GCC) 10.3.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # apt-get install sparse
> # sparse version: v0.6.3-341-g8af24329-dirty
> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=29faeb9632012d6c3fa4aa33c3d589b9ff18b206
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout 29faeb9632012d6c3fa4aa33c3d589b9ff18b206
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross C=1
> CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=openrisc
> SHELL=/bin/bash -C tools/testing/selftests install
KVM's selftests don't play nice with cross-compiles for unsupported architectures.
arm64 and s390 have expilict x86_64 -> {arm64,s390} support from commit 66d69e081b52
("selftests: fix kvm relocatable native/cross builds and installs"), but for
anything else the Makefile assumes an x86_64 target.
Realistically, only test bots are going to run afoul of our laziness. Do we care
enough to fix this up properly?
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <seanjc@google.com>
To: kbuild-all@lists.01.org
Subject: Re: lib/x86_64/handlers.S:20: Error: unrecognized instruction `call route_exception'
Date: Tue, 27 Jul 2021 16:07:48 +0000 [thread overview]
Message-ID: <YQAvVGwJqUak1E0l@google.com> (raw)
In-Reply-To: <202107270520.DIJjv4ia-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]
On Tue, Jul 27, 2021, kernel test robot wrote:
> Hi Aaron,
>
> First bad commit (maybe != root cause):
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: ff1176468d368232b684f75e82563369208bc371
> commit: 29faeb9632012d6c3fa4aa33c3d589b9ff18b206 selftests: kvm: Add exception handling to selftests
> date: 9 months ago
> config: openrisc-randconfig-s031-20210726 (attached as .config)
> compiler: or1k-linux-gcc (GCC) 10.3.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # apt-get install sparse
> # sparse version: v0.6.3-341-g8af24329-dirty
> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=29faeb9632012d6c3fa4aa33c3d589b9ff18b206
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout 29faeb9632012d6c3fa4aa33c3d589b9ff18b206
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross C=1
> CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=openrisc
> SHELL=/bin/bash -C tools/testing/selftests install
KVM's selftests don't play nice with cross-compiles for unsupported architectures.
arm64 and s390 have expilict x86_64 -> {arm64,s390} support from commit 66d69e081b52
("selftests: fix kvm relocatable native/cross builds and installs"), but for
anything else the Makefile assumes an x86_64 target.
Realistically, only test bots are going to run afoul of our laziness. Do we care
enough to fix this up properly?
next prev parent reply other threads:[~2021-07-27 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 21:10 lib/x86_64/handlers.S:20: Error: unrecognized instruction `call route_exception' kernel test robot
2021-07-26 21:10 ` kernel test robot
2021-07-27 16:07 ` Sean Christopherson [this message]
2021-07-27 16:07 ` Sean Christopherson
2021-07-27 18:51 ` Paolo Bonzini
2021-07-27 18:51 ` Paolo Bonzini
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=YQAvVGwJqUak1E0l@google.com \
--to=seanjc@google.com \
--cc=aaronlewis@google.com \
--cc=graf@amazon.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--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 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.