This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Name of event-channel and other devices vs. udev

To: Bastian Blank <waldi@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Name of event-channel and other devices vs. udev
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Thu, 27 May 2010 15:37:49 -0700
Delivery-date: Thu, 27 May 2010 15:38:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100527222641.GA25018@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20100526105144.GA28280@xxxxxxxxxxxxxxxxxxxxxxx> <20100527073512.GA17135@xxxxxxxxxxxxxxxxxxxxxxx> <20100527143104.GB6040@xxxxxxxxxxxxxxxxxxxxxxx> <4BFEEC96.3010207@xxxxxxxx> <20100527222641.GA25018@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100430 Fedora/3.0.4-2.fc12 Lightning/1.0b2pre Thunderbird/3.0.4
On 05/27/2010 03:26 PM, Bastian Blank wrote:
> It does the following:
> - Search in /sys/**/evtchn for the device number, this fails.
> - Compares the existing /dev/xen/evtchn with the error and unlinks it.
> - Tries to mknod it again with the error value, this fails.

That's unfortunate.

>> What other changes are needed to keep things working after this change?
> To possibilities:
> - Fix the error detection in this crude device creation code.
> - Rip it out and always rely on the system to provide the devices.
> For Debian I already decided to use the later one.

Yes, that seems like the cleanest approach.  Does it need any udev
config to get that right?  In particular, is there a mechanism to
autoload misc device modules?


Xen-devel mailing list