From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev incompatibility with qemu and bochs
Date: Wed, 19 Oct 2005 17:45:55 +0000 [thread overview]
Message-ID: <20051019174555.GA3850@kroah.com> (raw)
In-Reply-To: <43560651.9090802@ums.usu.ru>
On Wed, Oct 19, 2005 at 02:39:45PM +0600, Alexander E. Patrakov wrote:
> 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.
Feel free to provide such a patch, if you need it.
thanks,
greg k-h
-------------------------------------------------------
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 prev parent reply other threads:[~2005-10-19 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 8:39 Udev incompatibility with qemu and bochs Alexander E. Patrakov
2005-10-19 17:45 ` Greg KH [this message]
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=20051019174555.GA3850@kroah.com \
--to=greg@kroah.com \
--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).