From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Name of event-channel and other devices vs. udev Date: Thu, 27 May 2010 15:05:10 -0700 Message-ID: <4BFEEC96.3010207@goop.org> References: <20100526105144.GA28280@wavehammer.waldi.eu.org> <20100527073512.GA17135@wavehammer.waldi.eu.org> <20100527143104.GB6040@wavehammer.waldi.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100527143104.GB6040@wavehammer.waldi.eu.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Bastian Blank , xen-devel@lists.xensource.com, Keir Fraser List-Id: xen-devel@lists.xenproject.org On 05/27/2010 07:31 AM, Bastian Blank wrote: > On Thu, May 27, 2010 at 09:35:12AM +0200, Bastian Blank wrote: > >> On Wed, May 26, 2010 at 12:51:44PM +0200, Bastian Blank wrote: >> >>> - Make the kernel name the device "xen/evtchn". >>> >> This approach somewhat reliable failed for me[1]. Also nothing else in >> the kernel uses it. So I assume this is not really supported. >> > Xen themself is responsible for this behaviour. > You presumably don't mean the hypervisor. Do you mean the toolstack is doing something bad when the misc device has a '/' in it? I noticed when I applied your change it does things like look in /sys/class/xen/evtchn (or something). What other changes are needed to keep things working after this change? J