From: Timur Tabi <timur@freescale.com>
To: linux-kernel@vger.kernel.org, Kumar Gala <kumar.gala@freescale.com>
Subject: Best method for sending messages to user space?
Date: Tue, 21 Oct 2008 12:54:09 -0500 [thread overview]
Message-ID: <48FE1741.1000502@freescale.com> (raw)
I have a driver that provides services for a hypervisor that my company is
creating. The hypervisor can send notifications to the driver via interrupts.
I want to send a message to user space whenever the driver receives one of the
interrupts. The messages don't have any payload.
Should I be creating kobjects and using kobject_uevent(..., KOBJ_CHANGE) to send
these messages? I want to take advantage of the standard (hotplug?) user-space
interface for this sort of thing, so that I don't need to have a custom-written
daemon running that waits on blocking ioctl calls.
--
Timur Tabi
Linux kernel developer at Freescale
next reply other threads:[~2008-10-21 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 17:54 Timur Tabi [this message]
2008-10-21 18:14 ` Best method for sending messages to user space? Dan Williams
2008-10-21 19:43 ` Timur Tabi
2008-10-21 20:16 ` Dan Williams
2008-10-21 20:23 ` Timur Tabi
2008-10-21 20:42 ` Dan Williams
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=48FE1741.1000502@freescale.com \
--to=timur@freescale.com \
--cc=kumar.gala@freescale.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.