From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: RFC: removing hardcoded "modprobe blktap" in xencommons Date: Mon, 15 Jul 2013 10:34:02 +0100 Message-ID: <51E3DE2A02000078000E4DCC@nat28.tlf.novell.com> References: <20130712161255.GB4409@zion.uk.xensource.com> <51E3AD9C02000078000E4C9D@nat28.tlf.novell.com> <20130715073309.GA25286@zion.uk.xensource.com> <51E3C49502000078000E4D3D@nat28.tlf.novell.com> <20130715082656.GC25286@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130715082656.GC25286@zion.uk.xensource.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: GeorgeDunlap , Ian Jackson , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org >>> On 15.07.13 at 10:26, Wei Liu wrote: > So my point is, if every driver follows the kernel convention > (open(/dev/XYZ) would cause the module to load automatically) there then > would be minimal changes to libxl. It is unmaintained kernel modules > like blktap makes it not feasible to make things simplier. > > (Wild guess below, correct me if I'm wrong) > > Say, if we could make it just like open(blkback_char_dev), the loading > is just a one-liner and doesn't need to be using libxl's AO interface. Once again - most if not all backends don't fit that model - blktap as said doesn't and neither blkback nor netback don't as they don't create any /dev nodes. Backend module loading might be triggerable through xenstore node watches... Jan