From: "gguevel" <gguevel@interfaceconcept.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Blocking functions and interrupt protection
Date: Mon, 28 Jan 2002 19:29:37 +0100 [thread overview]
Message-ID: <000001c1a829$be44f400$3101a8c0@DOMAIN> (raw)
Hi,
I works on an embedded linux ppc pci target board in a linux PC.
I have a process on the PC which sends ioctl commands to the target via a
write
in a pci doorbell register then sleeps on. The target must reply with a pci
interrupt.
The problem is that the target replies so fast that if the process is
interrupted between the
doorbell write function and the sleep function, the interrupt event from the
target may try to
awake a process which is not sleeping. The event is lost and the ioctl
command is locked
forever.
How can I protect the process to be interrupted between the start of the
doorbell write
function and the end of the sleep function.
This problem is a general case, not specific to my driver. It may happen in
all drivers wich
communicates with fast board which generates asynchronous interrupt events.
Any help would be welcome.
Thanks
Sorry for my poor english language.
Gérard Guével
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2002-01-28 18:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000001c1a829$be44f400$3101a8c0@DOMAIN' \
--to=gguevel@interfaceconcept.com \
--cc=linuxppc-embedded@lists.linuxppc.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).