From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Udev incompatibility with qemu and bochs
Date: Wed, 19 Oct 2005 08:39:45 +0000 [thread overview]
Message-ID: <43560651.9090802@ums.usu.ru> (raw)
Hello,
udevstart contains the following code:
static void asmlinkage sig_handler(int signum)
{
switch (signum) {
case SIGALRM:
exit(1);
case SIGINT:
case SIGTERM:
exit(20 + signum);
}
}
int main(int argc, char *argv[], char *envp[])
{
/* snip */
sigaction(SIGALRM, &act, NULL);
sigaction(SIGINT, &act, NULL);
sigaction(SIGTERM, &act, NULL);
/* trigger timeout to prevent hanging processes */
alarm(UDEV_ALARM_TIMEOUT);
/* snip */
}
UDEV_ALARM_TIMEOUT is defined to 120 seconds in udev.h. The problem is
that it does take 2 minutes to populate /dev inside slow emulators like
qemu or bochs, especially when the emulated and host CPU types differ
and udev rules include RUN+=/sbin/udev_run_hotplugd. The reason is that
inside those emulators exec() is very expensive (involves
jit-compilation from one sort of machine code to another). Please
provide an option to disable this alarm. The preferred form would be an
environment variable, so that I can type "linux UDEV_NO_ALARM=1" at the
boot prompt inside the emulator and see the system booting normally.
Thanks,
--
Alexander E. Patrakov
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2005-10-19 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 8:39 Alexander E. Patrakov [this message]
2005-10-19 17:45 ` Udev incompatibility with qemu and bochs Greg KH
2005-10-19 18:05 ` Kay Sievers
2005-10-20 1:45 ` Alexander E. Patrakov
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=43560651.9090802@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).