From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: Neeraj Upadhyay <neeraju@codeaurora.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: Query regarding ERRATUM_1418040
Date: Mon, 06 Jul 2020 17:05:52 +0100 [thread overview]
Message-ID: <33f5d0c2348dc4bd78f442cb92de9715@kernel.org> (raw)
In-Reply-To: <20200706151651.GA23622@willie-the-truck>
On 2020-07-06 16:16, Will Deacon wrote:
> On Mon, Jul 06, 2020 at 01:27:16PM +0100, Marc Zyngier wrote:
>> On 2020-07-06 13:09, Will Deacon wrote:
>> > On Thu, Jul 02, 2020 at 09:19:04AM +0100, Marc Zyngier wrote:
>> > > + mrs x1, cntkctl_el1
>> > > + bfi x1, xzr, #1, #1 // ARCH_TIMER_USR_VCT_ACCESS_EN
>> >
>> > Can you use BIC here?
>>
>> You wish. Turns out that BIC is labelled as a v8.2 instruction, even
>> if is just yet another alias for BFM, and gas sends me packing
>> if I dare using it.
>>
>> So the above BFI is a poor man's version of BIC. Which objdump happily
>> disassembles as... BIC! Yes, this is all braindead.
>
> Wha.. really? What about all our other uses of the BIC alias? Are you
> sure
> you're not mixing it up with BFC?
Of course I am. BIC is absolutely fine. I blame the lack of coffee,
or something else.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-07-06 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 8:55 Query regarding ERRATUM_1418040 Neeraj Upadhyay
2020-06-17 11:19 ` Marc Zyngier
2020-06-17 11:25 ` Will Deacon
2020-06-17 13:00 ` Neeraj Upadhyay
2020-06-17 14:29 ` Marc Zyngier
2020-07-01 16:27 ` Will Deacon
2020-07-02 8:19 ` Marc Zyngier
2020-07-06 12:09 ` Will Deacon
2020-07-06 12:27 ` Marc Zyngier
2020-07-06 15:16 ` Will Deacon
2020-07-06 16:05 ` Marc Zyngier [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=33f5d0c2348dc4bd78f442cb92de9715@kernel.org \
--to=maz@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=neeraju@codeaurora.org \
--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 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.