From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753917AbcGVMo2 (ORCPT ); Fri, 22 Jul 2016 08:44:28 -0400 Received: from mga11.intel.com ([192.55.52.93]:10008 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753444AbcGVMo1 (ORCPT ); Fri, 22 Jul 2016 08:44:27 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,404,1464678000"; d="scan'208";a="738248537" Date: Fri, 22 Jul 2016 20:44:11 +0800 From: Fengguang Wu To: Max Filippov , Chris Zankel , kbuild-all@01.org, linux-kernel@vger.kernel.org Subject: Re: [kbuild-all] arch/xtensa/include/asm/initialize_mmu.h:55: Error: invalid register 'atomctl' for 'wsr' instruction Message-ID: <20160722124411.GC32690@wfg-t540p.sh.intel.com> References: <201607221826.7SNz0708%fengguang.wu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <201607221826.7SNz0708%fengguang.wu@intel.com> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Max, On Fri, Jul 22, 2016 at 06:32:28PM +0800, kbuild test robot wrote: >Hi, > >FYI, the error/warning still remains. > >tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master >head: 47ef4ad2684d380dd6d596140fb79395115c3950 >commit: 9da8320bb97768e35f2e64fa7642015271d672eb xtensa: add test_kc705_hifi variant >date: 4 months ago >config: xtensa-audio_kc705_defconfig (attached as .config) >compiler: xtensa-linux-gcc (GCC) 4.9.0 >All errors (new ones prefixed by >>): > > arch/xtensa/include/asm/initialize_mmu.h: Assembler messages: >>> arch/xtensa/include/asm/initialize_mmu.h:55: Error: invalid register 'atomctl' for 'wsr' instruction >-- > arch/xtensa/kernel/coprocessor.S: Assembler messages: >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_ovf_sar' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_bithead' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_ts_fts_bu_bp' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_cw_sd_no' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_cbegin0' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_cend0' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i' Are they really matter? Or I can shut these errors up. Thanks, Fengguang >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i' >>> arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'ae_s64.i' > >vim +55 arch/xtensa/include/asm/initialize_mmu.h > >6cb97111 Baruch Siach 2013-12-29 39 >c622b29d Max Filippov 2012-11-19 40 #ifdef __ASSEMBLY__ >c622b29d Max Filippov 2012-11-19 41 >c622b29d Max Filippov 2012-11-19 42 #define XTENSA_HWVERSION_RC_2009_0 230000 >c622b29d Max Filippov 2012-11-19 43 >c622b29d Max Filippov 2012-11-19 44 .macro initialize_mmu >c622b29d Max Filippov 2012-11-19 45 >c622b29d Max Filippov 2012-11-19 46 #if XCHAL_HAVE_S32C1I && (XCHAL_HW_MIN_VERSION >= XTENSA_HWVERSION_RC_2009_0) >c622b29d Max Filippov 2012-11-19 47 /* >c622b29d Max Filippov 2012-11-19 48 * We Have Atomic Operation Control (ATOMCTL) Register; Initialize it. >c622b29d Max Filippov 2012-11-19 49 * For details see Documentation/xtensa/atomctl.txt >c622b29d Max Filippov 2012-11-19 50 */ >c622b29d Max Filippov 2012-11-19 51 #if XCHAL_DCACHE_IS_COHERENT >c622b29d Max Filippov 2012-11-19 52 movi a3, 0x25 /* For SMP/MX -- internal for writeback, >c622b29d Max Filippov 2012-11-19 53 * RCW otherwise >c622b29d Max Filippov 2012-11-19 54 */ >c622b29d Max Filippov 2012-11-19 @55 #else >c622b29d Max Filippov 2012-11-19 56 movi a3, 0x29 /* non-MX -- Most cores use Std Memory >c622b29d Max Filippov 2012-11-19 57 * Controlers which usually can't use RCW >c622b29d Max Filippov 2012-11-19 58 */ >c622b29d Max Filippov 2012-11-19 59 #endif >c622b29d Max Filippov 2012-11-19 60 wsr a3, atomctl >c622b29d Max Filippov 2012-11-19 61 #endif /* XCHAL_HAVE_S32C1I && >c622b29d Max Filippov 2012-11-19 62 * (XCHAL_HW_MIN_VERSION >= XTENSA_HWVERSION_RC_2009_0) >c622b29d Max Filippov 2012-11-19 63 */ > >:::::: The code at line 55 was first introduced by commit >:::::: c622b29d1f38021411965b7e0170ab055551b257 xtensa: initialize atomctl SR > >:::::: TO: Max Filippov >:::::: CC: Chris Zankel > >--- >0-DAY kernel test infrastructure Open Source Technology Center >https://lists.01.org/pipermail/kbuild-all Intel Corporation >_______________________________________________ >kbuild-all mailing list >kbuild-all@lists.01.org >https://lists.01.org/mailman/listinfo/kbuild-all