From: Anshuman Khandual <anshuman.khandual@arm.com>
To: kernel test robot <lkp@intel.com>, linux-arm-kernel@lists.infradead.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Mark Brown <broonie@kernel.org>,
Marc Zyngier <maz@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: Disable EL2 traps for BRBE instructions executed in EL1
Date: Mon, 27 Mar 2023 11:38:36 +0530 [thread overview]
Message-ID: <4feeae36-f6fe-1422-9f0f-081b9106e91c@arm.com> (raw)
In-Reply-To: <202303250802.KytExIHw-lkp@intel.com>
On 3/25/23 06:07, kernel test robot wrote:
> All errors (new ones prefixed by >>):
>
>>> <instantiation>:36:14: error: expected compatible register or logical immediate
> orr x0, x0, #HFGITR_EL2_nBRBIALL
> ^
> <instantiation>:10:2: note: while in macro instantiation
> __init_el2_fgt
> ^
> arch/arm64/kernel/head.S:577:2: note: while in macro instantiation
> init_el2_state
> ^
> <instantiation>:37:14: error: expected compatible register or logical immediate
> orr x0, x0, #HFGITR_EL2_nBRBINJ
> ^
> <instantiation>:10:2: note: while in macro instantiation
> __init_el2_fgt
> ^
> arch/arm64/kernel/head.S:577:2: note: while in macro instantiation
> init_el2_state
> ^
I guess these build errors are caused by unavailability of the pre-requisite
patches from Mark Brown, in this test environment ?
https://lore.kernel.org/all/20230306-arm64-fgt-reg-gen-v3-0-decba93cbaab@kernel.org/
next prev parent reply other threads:[~2023-03-27 6:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 5:51 Anshuman Khandual
2023-03-24 11:55 ` Mark Brown
2023-03-27 6:05 ` Anshuman Khandual
2023-03-24 19:39 ` kernel test robot
2023-03-25 0:37 ` kernel test robot
2023-03-27 6:08 ` Anshuman Khandual [this message]
2023-03-29 5:52 ` Liu, Yujie
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=4feeae36-f6fe-1422-9f0f-081b9106e91c@arm.com \
--to=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=will@kernel.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
all inboxes | Powered by JetHome®