From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] ARM: Manage the pl310 erratas in a dynamic way
Date: Tue, 29 Jan 2013 11:29:17 +0000 [thread overview]
Message-ID: <20130129112917.GF2637@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130129101026.GA1063@bnru10>
On Tue, Jan 29, 2013 at 03:40:38PM +0530, srinidhi kasagar wrote:
> - Added l2x0_quirks to manage the errata in cpu_idle path. Tried to address
> Russell's comment on this, but could not completely. Because, neither I can
> keep the #ifdef CONFIG_PL310_ERRATA_769419 nor remove it entirely since
> the platform A suffers from this bug, whereas B do not but shares the same
> defconfig.
Yes you can and I covered this situation in my email. In that case,
you _define_ CONFIG_PL310_ERRATA_769419 such that the barrier _always_
gets included both both platforms.
As I already said, there is _no_ point making the barrier conditional;
it's probably more expensive to make it conditional than just to execute
it every time. But we still might as well optimize it away if we are
running _only_ on platforms which _do_ _not_ have that errata.
prev parent reply other threads:[~2013-01-29 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 10:10 [PATCH v2 0/5] ARM: Manage the pl310 erratas in a dynamic way srinidhi kasagar
2013-01-29 11:29 ` Russell King - ARM Linux [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=20130129112917.GF2637@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).