From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/5] irqchip: gic: use writel instead of dsb + writel_relaxed
Date: Tue, 11 Feb 2014 08:52:22 +0000 [thread overview]
Message-ID: <52F9E4C6.8080600@arm.com> (raw)
In-Reply-To: <1392042159-11603-2-git-send-email-will.deacon@arm.com>
On 10/02/14 14:22, Will Deacon wrote:
> When sending an SGI to another CPU, we require a DSB to ensure that
> any pending stores to normal memory are made visible to the recipient
> before the interrupt arrives.
>
> Rather than use a vanilla dsb() (which will soon cause an assembly error
> on arm64) before the writel_relaxed, we can instead use dsb(ishst),
> since we just need to ensure that any pending normal writes are visible
> within the inner-shareable domain before we poke the GIC.
>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
> ---
>
> v1 => v2: Use dsb ishst instead of writel (which requires an L2 sync)
> since the sync should already have been executed by the caller
> if required. We *might* be able to relax this further to a dmb
> but Catalin and I haven't got to the bottom of that yet.
>
> Marc: I dropped your Ack, so could you take another look please?
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2014-02-11 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 14:22 [PATCH v2 1/5] arm64: barriers: make use of barrier options with explicit barriers Will Deacon
2014-02-10 14:22 ` [PATCH v2 2/5] irqchip: gic: use writel instead of dsb + writel_relaxed Will Deacon
2014-02-10 16:17 ` Catalin Marinas
2014-02-11 8:52 ` Marc Zyngier [this message]
2014-02-10 14:22 ` [PATCH v2 3/5] iommu/arm-smmu: provide option to dsb macro when publishing tables Will Deacon
2014-02-10 14:22 ` [PATCH v2 4/5] arm64: barriers: wire up new barrier options Will Deacon
2014-02-10 14:22 ` [PATCH v2 5/5] arm64: barriers: use barrier() instead of smp_mb() when !SMP Will Deacon
2014-02-10 16:18 ` [PATCH v2 1/5] arm64: barriers: make use of barrier options with explicit barriers Catalin Marinas
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=52F9E4C6.8080600@arm.com \
--to=marc.zyngier@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;
as well as URLs for NNTP newsgroup(s).