From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Hsung-Pin Chang <hpchang@cs.nchu.edu.tw>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Upcall implementation in Linux
Date: Fri, 11 Aug 2006 11:41:19 +0100 [thread overview]
Message-ID: <1155292879.24077.44.camel@localhost.localdomain> (raw)
In-Reply-To: <20060811041650.A0C2C3993@flute.cs.nchu.edu.tw>
Ar Gwe, 2006-08-11 am 12:13 +0800, ysgrifennodd Hsung-Pin Chang:
> Dear all,
>
> Recently, I need to use upcalls in Linux to actively and
> promptly inform
> the user applications once an kernel event is occurred.
> However, I have some questions about upcall implementation.
> First, the user handler must be "pinned" into memory to
> prevent paging out.
Linux intentionally and deliberately does not support kernel calls into
user space. It leads to very difficult locking problems amongst other
things.
Instead we either send asynchronous events (signal/netlink/..) or we
arrange that a system call returns when the event happens so the user
process resumes.
next prev parent reply other threads:[~2006-08-11 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 4:13 Upcall implementation in Linux Hsung-Pin Chang
2006-08-11 10:41 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-08 18:04 Steve French
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=1155292879.24077.44.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=hpchang@cs.nchu.edu.tw \
--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