From: timur@codeaurora.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: mm: Add workaround for Qualcomm Technologies Falkor erratum E1029
Date: Wed, 8 Mar 2017 10:50:03 -0600 [thread overview]
Message-ID: <646fee0b-13b4-85d7-63d5-26e450bd2e2d@codeaurora.org> (raw)
In-Reply-To: <20170303122703.GA12945@leverpostej>
On 03/03/2017 06:27 AM, Mark Rutland wrote:
> The idle loop is not the only place where WFI can occur.
>
> Notably, firmware is within its rights to use WFI, as is userspace given
> that SCTLR_EL1.nTWI is set at boot time. So IIUC, userspace can deadlock
> a core, which makes this sound very serious.
>
> Can this *only* happen for the PMU interrupt?
>
> I assume that as mentioned for other Falkor workarounds "the affected
> chips are pre-production and are only available to select customers for
> a limited time"?
>
> Given that we're having to a fair amount of the arm64 core code, for
> parts that QC don't even intend to support long term, it's increasingly
> difficult to care about this upstream.
>
> Are additional workarounds necessary for these parts?
We are withdrawing this patch. We acknowledge your concerns.
There are other errata affected by this patch that we have submitted, but
this is the only one that is unacceptable. The affected chips are
pre-production, and so we'll just keep this work-around internally until
those chips have been replaced.
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc. Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
prev parent reply other threads:[~2017-03-08 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 0:19 [PATCH] arm64: mm: Add workaround for Qualcomm Technologies Falkor erratum E1029 Timur Tabi
2017-03-03 12:27 ` Mark Rutland
2017-03-08 16:50 ` Timur Tabi [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=646fee0b-13b4-85d7-63d5-26e450bd2e2d@codeaurora.org \
--to=timur@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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.