From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [PATCH] xc: deal with xen/evtchn and xen/gntdev device names Date: Thu, 03 Jun 2010 12:32:57 -0700 Message-ID: <4C080369.3090801@goop.org> References: <4C00690B.2020303@goop.org> <1275379012.24218.20337.camel@zakaz.uk.xensource.com> <4C0536BF.7070605@goop.org> <1275470944.24218.23601.camel@zakaz.uk.xensource.com> <4C06822A.8000702@goop.org> <1275553876.24218.28795.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1275553876.24218.28795.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: Bastian Blank , Xen-devel List-Id: xen-devel@lists.xenproject.org On 06/03/2010 01:31 AM, Ian Campbell wrote: > On Wed, 2010-06-02 at 17:09 +0100, Jeremy Fitzhardinge wrote: > >> On 06/02/2010 02:29 AM, Ian Campbell wrote: >> >>> On Tue, 2010-06-01 at 17:35 +0100, Jeremy Fitzhardinge wrote: >>> I don't think we need a flag day. It seems like we already ship a udev >>> rule (in tools/hotplug/Linux/xen-backend.rules) which correctly >>> created /dev/xen/evtchn with the current kernel and which is apparently >>> unnecessary (but harmless) with the proposed kernel change. >>> >>> >> My main concern is that an old libxc will screw anyone with new kernel >> and udev. >> > Is it any more likely to screw them with a new kernel than with an old > one? > Yeah, because libxc's rummage around in sysfs will actually work. If we rename the devices to be correct, it won't find them and it just ends up deleting the old device and either failing to create a new one, or creating it with a bogus major/minor. > If so I think that's an argument for propagating the removal of this > functionality into stable trees sooner rather than later rather than > papering over the craziness for even longer. > Yep. J