From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: mechanism to syncronise device access from user and kernel
Date: Fri, 05 Dec 2008 19:08:39 -0600 [thread overview]
Message-ID: <4939D097.5030305@shaw.ca> (raw)
In-Reply-To: <377462.57009.qm@web30107.mail.mud.yahoo.com>
Parav Pandit wrote:
> Hi,
>
> I have a device whose registers are accessed by driver as well as user space application via mmap() area.
>
> How to synchronize the access (avoid race condition) between user space driver and kernel mode driver, in single CPU and multi-CPU systems?
This doesn't seem like the best idea in the first place.. certainly not
if unprivileged processes can get access to the registers, as there's no
way to require them to follow the synchronization process. Generally a
given set of registers should be driven by a kernel driver or a
userspace process, not both.
next prev parent reply other threads:[~2008-12-06 1:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 18:28 mechanism to syncronise device access from user and kernel Parav Pandit
2008-12-06 1:08 ` Robert Hancock [this message]
2008-12-06 12:40 ` Matthew Garrett
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=4939D097.5030305@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.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