From: Mark Rutland <mark.rutland@arm.com>
To: Bharat Bhushan <bbhushan2@marvell.com>
Cc: catalin.marinas@arm.com, will@kernel.org,
daniel.lezcano@linaro.org, maz@kernel.org,
konrad.dybcio@somainline.org, saiprakash.ranjan@codeaurora.org,
robh@kernel.org, marcan@marcan.st, suzuki.poulose@arm.com,
broonie@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Linu Cherian <lcherian@marvell.com>
Subject: Re: [PATCH] clocksource: Add Marvell Errata-38627 workaround
Date: Mon, 5 Jul 2021 10:14:36 +0100 [thread overview]
Message-ID: <20210705091436.GE38629@C02TD0UTHF1T.local> (raw)
In-Reply-To: <20210705090753.GD38629@C02TD0UTHF1T.local>
On Mon, Jul 05, 2021 at 10:07:53AM +0100, Mark Rutland wrote:
> Hi Bharat,
>
> On Mon, Jul 05, 2021 at 11:38:43AM +0530, Bharat Bhushan wrote:
> > CPU pipeline have unpredicted behavior when timer
> > interrupt appears and then disappears prior to the
> > exception happening. Time interrupt appears on timer
> > expiry and disappears when timer programming or timer
> > disable. This typically can happen when a load
> > instruction misses in the cache, which can take
> > few hundreds of cycles, and an interrupt appears
> > after the load instruction starts executing but
> > disappears before the load instruction completes.
>
> Could you elaborate on the scenario? What sort of unpredictable
> behaviour can occur? e.g:
>
> * Does the CPU lockup?
> * Does the CPU take the exception at all?
> * Does the load behave erroneously?
> * Does any CPU state (e.g. GPRs, PC, PSTATE) become corrupted?
>
> Does the problem manifest when IRQs are masked by DAIF.I, or by
> CNT8_CTL_EL0.{IMASK,ENABLE} ?
Whoops, that was supposed to say:
| CNT*_CTL_EL0.{IMASK,ENABLE}
... i.e. those fields in either CNTP_CTL_EL0 or CNTV_CTL_EL0.
Thanks,
Mark.
next prev parent reply other threads:[~2021-07-05 9:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 6:08 Bharat Bhushan
2021-07-05 9:07 ` Mark Rutland
2021-07-05 9:14 ` Mark Rutland [this message]
2021-07-08 10:47 ` [EXT] " Bharat Bhushan
2021-07-08 11:41 ` Mark Rutland
2021-07-13 2:40 ` Bharat Bhushan
2021-07-13 15:38 ` Marc Zyngier
2021-07-13 16:12 ` Mark Rutland
2021-07-26 4:29 ` Bharat Bhushan
2021-07-26 18:03 ` Marc Zyngier
2021-07-05 9:26 ` Marc Zyngier
2021-07-08 10:48 ` [EXT] " Bharat Bhushan
2021-07-11 9:57 ` Marc Zyngier
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=20210705091436.GE38629@C02TD0UTHF1T.local \
--to=mark.rutland@arm.com \
--cc=bbhushan2@marvell.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=konrad.dybcio@somainline.org \
--cc=lcherian@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=maz@kernel.org \
--cc=robh@kernel.org \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=suzuki.poulose@arm.com \
--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®