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


[Xen-devel] Re: [PATCH] Fix name of Xen event-channel device

To: Bastian Blank <waldi@xxxxxxxxxx>, Michael Tokarev <mjt@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: [PATCH] Fix name of Xen event-channel device
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Fri, 28 May 2010 16:20:03 -0700
Delivery-date: Fri, 28 May 2010 16:20:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100527171313.GB11358@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> <20100527150251.GD6040@xxxxxxxxxxxxxxxxxxxxxxx> <4BFEA2DF.8080006@xxxxxxxxxxxxxxxx> <20100527171313.GB11358@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 10:13 AM, Bastian Blank wrote:
> The udev rules will just not longer match, as they only rename the
> device, this is no problem. However libxc _will_ break, as it lacks
> proper error check in its own device creation routine.

Yeah, that's really annoying.  I can't change the kernel without also
having a flag day to update libxc.  I guess we could make sure all the
stable Xen branches get a libxc fix backported to them, but I wonder if
it would break other toolstacks?

> However there are not much possibilities here: this support will go away
> and it will annoy every user for some time.

But if we don't make any kernel changes then libxc will muddle on even
if udev stops handling the device name properly?


Xen-devel mailing list