From: Dave.Martin@arm.com (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mcpm: remove redundant dsb instructions prior to sev
Date: Fri, 6 Dec 2013 16:44:49 +0000 [thread overview]
Message-ID: <20131206164449.GC4897@e103592.cambridge.arm.com> (raw)
In-Reply-To: <1386347645-16570-1-git-send-email-will.deacon@arm.com>
On Fri, Dec 06, 2013 at 04:34:05PM +0000, Will Deacon wrote:
> sync_cache_w already includes a dsb, so we can just use sev() directly
> then following a cache-sync.
>
> Cc: Dave Martin <Dave.Martin@arm.com>
> Cc: Nicolas Pitre <nico@fluxnic.net>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
This makes sense. I have a feeling the dsb_sev() calls originated
during my original attempt to use dedicated uncached memory for the
synchronisation buffer -- i.e., there was no cache flush.
The extra dsbs do indeed look redundant now.
Acked-by: Dave Martin <Dave.Martin@arm.com>
Cheers
---Dave
> ---
>
> Hi guys,
>
> I was auditing our uses of wfe (they're all fine) but noticed these
> extra dsbs in the process.
>
> Will
>
> arch/arm/common/mcpm_entry.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/common/mcpm_entry.c b/arch/arm/common/mcpm_entry.c
> index 26020a03f659..74140ed9922f 100644
> --- a/arch/arm/common/mcpm_entry.c
> +++ b/arch/arm/common/mcpm_entry.c
> @@ -167,7 +167,7 @@ void __mcpm_cpu_down(unsigned int cpu, unsigned int cluster)
> dmb();
> mcpm_sync.clusters[cluster].cpus[cpu].cpu = CPU_DOWN;
> sync_cache_w(&mcpm_sync.clusters[cluster].cpus[cpu].cpu);
> - dsb_sev();
> + sev();
> }
>
> /*
> @@ -183,7 +183,7 @@ void __mcpm_outbound_leave_critical(unsigned int cluster, int state)
> dmb();
> mcpm_sync.clusters[cluster].cluster = state;
> sync_cache_w(&mcpm_sync.clusters[cluster].cluster);
> - dsb_sev();
> + sev();
> }
>
> /*
> --
> 1.8.2.2
>
next prev parent reply other threads:[~2013-12-06 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 16:34 [PATCH] ARM: mcpm: remove redundant dsb instructions prior to sev Will Deacon
2013-12-06 16:44 ` Dave Martin [this message]
2013-12-06 16:45 ` Nicolas Pitre
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=20131206164449.GC4897@e103592.cambridge.arm.com \
--to=dave.martin@arm.com \
--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