From: "Liu, Yujie" <yujie.liu@intel.com>
To: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"anshuman.khandual@arm.com" <anshuman.khandual@arm.com>,
lkp <lkp@intel.com>
Cc: "maz@kernel.org" <maz@kernel.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"will@kernel.org" <will@kernel.org>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: Disable EL2 traps for BRBE instructions executed in EL1
Date: Wed, 29 Mar 2023 05:52:06 +0000 [thread overview]
Message-ID: <1aed64aff49b74bfe2e7295c0ae7e40fe6d68055.camel@intel.com> (raw)
In-Reply-To: <4feeae36-f6fe-1422-9f0f-081b9106e91c@arm.com>
On Mon, 2023-03-27 at 11:38 +0530, Anshuman Khandual wrote:
> 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/
Thanks for the information.
We noticed that the base and prerequisite patches are mentioned in the
commit message:
---
This patch applies on v6.3-rc3, after the following patch series from Mark
https://lore.kernel.org/all/20230306-arm64-fgt-reg-gen-v3-0-decba93cbaab@kernel.org/
The robot couldn't understand above description, and it is recommended
to use `git format-patch --base` to generate base info.
Please refer to the documents in:
https://git-scm.com/docs/git-format-patch#_base_tree_information
For this case, the correct order of patches would be:
arm64: Disable EL2 traps for BRBE instructions executed in EL1
arm64/sysreg: Convert HFGITR_EL2 to automatic generation
arm64/sysreg: Convert HFG[RW]TR_EL2 to automatic generation
e8d018dd0257 Linux 6.3-rc3
Please checkout to the patch and do `git format-patch --base
e8d018dd0257 -1`, it will generate base info in the footer of the
patch:
base-commit: e8d018dd0257f744ca50a729e3d042cf2ec9da65
prerequisite-patch-id: 6f448444c7a40a44146d4ecbfa57190ae30a257f
prerequisite-patch-id: 484c605fa9d35d776eda3c47ab95a24841712885
Then the robot can parse this info to select base and apply
prerequisite patches as expected.
--
Best Regards,
Yujie
prev parent reply other threads:[~2023-03-29 5:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230324055127.2228330-1-anshuman.khandual@arm.com>
2023-03-25 0:37 ` [PATCH] arm64: Disable EL2 traps for BRBE instructions executed in EL1 kernel test robot
2023-03-27 6:08 ` Anshuman Khandual
2023-03-29 5:52 ` Liu, Yujie [this message]
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=1aed64aff49b74bfe2e7295c0ae7e40fe6d68055.camel@intel.com \
--to=yujie.liu@intel.com \
--cc=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