From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roland Paterson-Jones Subject: Re: Help/problems with blktap on xen-unstable Date: Wed, 20 Sep 2006 15:44:27 +0200 Message-ID: <451145BB.2010503@rolandpj.com> References: <4510E1C0.7020405@rolandpj.com> <1158747512.32181.7.camel@leto.intern.saout.de> <45112EC5.4010706@rolandpj.com> <1158754236.32181.11.camel@leto.intern.saout.de> <451131DF.1000903@rolandpj.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <451131DF.1000903@rolandpj.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: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Roland Paterson-Jones wrote: > So, I guess I need to recompile with an alternate device major number. I can find the following refs to 254 in the source (some are dups): ./linux-2.6.16.13-xen0/drivers/xen/blktap/blktap.c: major=254, minor numbers begin at 0 */ ./linux-2.6.16.13-xen0/drivers/xen/blktap/blktap.c:#define BLKTAP_DEV_MAJOR 254 /* TODO: Make major number dynamic * ./linux-2.6-xen-sparse/drivers/xen/blktap/blktap.c: major=254, minor numbers begin at 0 */ ./linux-2.6-xen-sparse/drivers/xen/blktap/blktap.c:#define BLKTAP_DEV_MAJOR 254 /* TODO: Make major number dynamic * ./tools/blktap/lib/blktaplib.h:#define BLKTAP_DEV_MAJOR 254 ./tools/blktap/drivers/blktapctrl.c: make_blktap_dev(devname,254,0); ./tools/blktap_user/aiotools/blktapctrl.c: make_blktap_dev(devname,254,0); ./tools/blktap_user/blktaplib.h:#define BLKTAP_DEV_MAJOR 254 I'm guessing it would be good to have one definition, but I'm not too familiar with the code structure. Can a .h file span kernel and user source? Also, any idea what is meant by making major number 'dynamic' - are they proposing walking the major numbers in code until successful, or just a config option somewhere (where?). Regards Roland