Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755018Ab3FPGvd (ORCPT ); Sun, 16 Jun 2013 02:51:33 -0400 Received: from mail-ie0-f174.google.com ([209.85.223.174]:50161 "EHLO mail-ie0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754933Ab3FPGva convert rfc822-to-8bit (ORCPT ); Sun, 16 Jun 2013 02:51:30 -0400 Date: Sun, 16 Jun 2013 01:51:26 -0500 From: Rob Landley Subject: Re: Commit f9afbd45b0d0 broke mips r4k. To: Ralf Baechle Cc: linux-kernel@vger.kernel.org, sanjayl@kymasys.com, kvm@vger.kernel.org, linux-mips@linux-mips.org, Markos Chandras References: <1371090916.2776.104@driftwood> <20130613090002.GD7422@linux-mips.org> In-Reply-To: <20130613090002.GD7422@linux-mips.org> (from ralf@linux-mips.org on Thu Jun 13 04:00:02 2013) X-Mailer: Balsa 2.4.11 Message-Id: <1371365486.2776.113@driftwood> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3012 Lines: 69 On 06/13/2013 04:00:02 AM, Ralf Baechle wrote: > On Wed, Jun 12, 2013 at 09:35:16PM -0500, Rob Landley wrote: > > > My aboriginal linux project builds tiny linux systems to run under > > qemu, producing as close to the same system as possible across a > > bunch of different architectures. The above change broke the mips > > r4k build I've been running under qemu. > > > > Here's a toolchain and reproduction sequence: > > > > wget http://landley.net/aboriginal/bin/cross-compiler-mips.tar.bz2 > > tar xvjf cross-compiler-mips.tar.bz2 > > export PATH=$PWD/cross-compiler-mips/bin:$PATH > > make ARCH=mips allnoconfig KCONFIG_ALLCONFIG=miniconfig.mips > > make CROSS_COMPILE=mips- ARCH=mips > > > > (The file miniconfig.mips is attached.) > > > > It ends: > > > > CC init/version.o > > LD init/built-in.o > > arch/mips/built-in.o: In function `local_r4k_flush_cache_page': > > c-r4k.c:(.text+0xe278): undefined reference to > `kvm_local_flush_tlb_all' > > c-r4k.c:(.text+0xe278): relocation truncated to fit: R_MIPS_26 > > against `kvm_local_flush_tlb_all' > > arch/mips/built-in.o: In function `local_flush_tlb_range': > > (.text+0xe938): undefined reference to `kvm_local_flush_tlb_all' > > arch/mips/built-in.o: In function `local_flush_tlb_range': > > (.text+0xe938): relocation truncated to fit: R_MIPS_26 against > > `kvm_local_flush_tlb_all' > > arch/mips/built-in.o: In function `local_flush_tlb_mm': > > (.text+0xed38): undefined reference to `kvm_local_flush_tlb_all' > > arch/mips/built-in.o: In function `local_flush_tlb_mm': > > (.text+0xed38): relocation truncated to fit: R_MIPS_26 against > > `kvm_local_flush_tlb_all' > > kernel/built-in.o: In function `__schedule': > > core.c:(.sched.text+0x16a0): undefined reference to > > `kvm_local_flush_tlb_all' > > core.c:(.sched.text+0x16a0): relocation truncated to fit: R_MIPS_26 > > against `kvm_local_flush_tlb_all' > > mm/built-in.o: In function `use_mm': > > (.text+0x182c8): undefined reference to `kvm_local_flush_tlb_all' > > mm/built-in.o: In function `use_mm': > > (.text+0x182c8): relocation truncated to fit: R_MIPS_26 against > > `kvm_local_flush_tlb_all' > > fs/built-in.o:(.text+0x7b50): more undefined references to > > `kvm_local_flush_tlb_all' follow > > fs/built-in.o: In function `flush_old_exec': > > (.text+0x7b50): relocation truncated to fit: R_MIPS_26 against > > `kvm_local_flush_tlb_all' > > > > Revert the above commit and it builds to the end. > > Commit d414976d1ca721456f7b7c603a8699d117c2ec07 [MIPS: include: > mmu_context.h: Replace VIRTUALIZATION with KVM] fixes the issue and > was pulled by Linus only yesterday. I cannot reproduce the error > following your receipe using the latest Linux/MIPS tree. Confirmed, that fixed it. Thanks, Rob-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/