From: yangyingliang@huawei.com (Yang Yingliang)
To: linux-arm-kernel@lists.infradead.org
Subject: A gic problem about eoi
Date: Thu, 18 Feb 2016 13:00:58 +0800 [thread overview]
Message-ID: <56C5500A.2060104@huawei.com> (raw)
Hi, Marc
We found if hardware clear pending and active status is slower than
software handling, the new sgi will be merged because of hardware
status. The new sgi will be lost.
If we add a dsb instruction after gic_write_eoir(), it can avoid this
case happening.
Is it a right way to add a dsb instruction after gic_write_eoir()
in current gic driver code ?
Thanks,
Yang
next reply other threads:[~2016-02-18 5:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 5:00 Yang Yingliang [this message]
2016-02-18 9:00 ` A gic problem about eoi Marc Zyngier
2016-02-19 6:39 ` Yang Yingliang
2016-02-19 11:49 ` 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=56C5500A.2060104@huawei.com \
--to=yangyingliang@huawei.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).