WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] xc: deal with xen/evtchn and xen/gntdev device n

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xc: deal with xen/evtchn and xen/gntdev device names
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 01 Jun 2010 09:35:11 -0700
Cc: Bastian Blank <waldi@xxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 01 Jun 2010 10:50:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1275379012.24218.20337.camel@xxxxxxxxxxxxxxxxxxxxxx>
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: <4C00690B.2020303@xxxxxxxx> <1275379012.24218.20337.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc12 Lightning/1.0b2pre Thunderbird/3.0.4
On 06/01/2010 12:56 AM, Ian Campbell wrote:
> Does any of this logic really belong in libxc in the first place? 
>   

No.  It's a relic of a simpler time.

> Can we not just rip it all out and make it the distro/platform's
> responsibility to ensure these devices exist and are correct? Perhaps
> that might involve shipping some default/example udev rules instead.
>   

I only kept it because I didn't want to break any existing installs, but
updating the kernel's name is going to do that anyway.  Unfortunately
the current libxc code is broken in the worst possible way - it will
unlink an existing correct device and then fail to replace it - so even
if the system has set it up correctly it will still screw things up.

I think we're just going to have to have a flag day and fix kernel,
libxc and udev (assuming it needs it) all at once...

    J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel