From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Michal Januszewski <spock@gentoo.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [announce 7/7] fbsplash - documentation
Date: Fri, 11 Mar 2005 23:27:47 +1100 [thread overview]
Message-ID: <1110544067.5810.100.camel@gaston> (raw)
In-Reply-To: <200503090117.12755.arnd@arndb.de>
>
> I don't understand. Does the kernel code need to wait for the helper
> to finish while holding the semaphore? AFAICS, the helper is completely
> asynchronous, so it can simply do its job when the kernel has given
> up the semaphore.
It should be totally async witout any sem. there is no guarantee that
userspace is even available at the time you do the call.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-11 12:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 2:17 [announce 7/7] fbsplash - documentation Michal Januszewski
2005-03-08 3:18 ` Arnd Bergmann
2005-03-08 5:00 ` Matan Peled
2005-03-08 17:39 ` Jesse Barnes
2005-03-08 6:12 ` Jon Smirl
2005-03-08 22:37 ` Michal Januszewski
2005-03-09 0:17 ` Arnd Bergmann
2005-03-09 2:05 ` Michal Januszewski
2005-03-09 15:40 ` Arnd Bergmann
2005-03-10 0:16 ` Michal Januszewski
2005-03-11 12:27 ` Benjamin Herrenschmidt [this message]
2005-03-09 16:54 ` Jon Smirl
2005-03-09 17:29 ` [Linux-fbdev-devel] " Arnd Bergmann
2005-03-09 19:11 ` Pavel Machek
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=1110544067.5810.100.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spock@gentoo.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).