From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
Subject: Re: Automatic loading of xen-evtchn module in Xen 4.0.0?
Date: Sat, 27 Mar 2010 15:18:14 -0700 [thread overview]
Message-ID: <4BAE8426.2050703@goop.org> (raw)
In-Reply-To: <20100327173221.GJ1878@reaktio.net>
On 03/27/2010 10:32 AM, Pasi Kärkkäinen wrote:
> Hello,
>
> xend automatically mounts /proc/xen, but it doesn't try loading evtchn or xen-evtchn modules.
> Should we add automatic loading of these modules?
>
> xend doesn't start if xen event channel functionality is missing.
>
> Fedora Xen rpms do load modules automatically, like this:
>
> # cat /etc/sysconfig/modules/xen.modules
> #!/bin/sh
>
> test -d /proc/xen || exit 0
> test -f /proc/xen/capabilities || mount -t xenfs xen /proc/xen
> test -f /proc/xen/capabilities || exit 0
> grep -q "control_d" /proc/xen/capabilities || exit 0
>
> for module in xen-evtchn evtchn blkbk netbk; do
> modprobe ${module}>/dev/null 2>&1
> done
>
We should be able to make these mount automatically with udev rules, I
think, but I'm not sure whether you can do udev rules to mount misc
devices (which is what /dev/xen/evtchn is).
I think the front/back xenbus and device drivers are still a bit of a
mess with regard to modules; I have to admit I tend to just compile them
all in. It would be nice to get all that properly sorted out so they
can be sensibly modularized and auto-loaded as required. (A good first
step would be to systematically work out what compile combinations
actually work or fail, hint, hint ;)
J
next prev parent reply other threads:[~2010-03-27 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 17:32 Automatic loading of xen-evtchn module in Xen 4.0.0? Pasi Kärkkäinen
2010-03-27 22:18 ` Jeremy Fitzhardinge [this message]
2010-03-30 9:44 ` Ian Campbell
2010-03-30 14:22 ` Konrad Rzeszutek Wilk
2010-03-30 14:26 ` Ian Campbell
2010-03-30 22:47 ` Jeremy Fitzhardinge
2010-03-31 8:40 ` Ian Campbell
2010-03-31 13:39 ` Konrad Rzeszutek Wilk
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=4BAE8426.2050703@goop.org \
--to=jeremy@goop.org \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
/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).