Date: Thu, 4 May 2006 08:34:11 -0700
From: Greg KH <greg@kroah.com>
To: Michael Holzheu <HOLZHEU@de.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, ioe-lkml@rameria.de,
       joern@wohnheim.fh-wedel.de, linux-kernel@vger.kernel.org,
       mschwid2@de.ibm.com, penberg@cs.helsinki.fi
Subject: Re: [PATCH] s390: Hypervisor File System
Message-ID: <20060504153411.GA27485@kroah.com>
References: <20060504144259.GA26668@kroah.com> <OF99AF266B.81368F01-ON42257164.00523E52-42257164.0052802A@de.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <OF99AF266B.81368F01-ON42257164.00523E52-42257164.0052802A@de.ibm.com>
User-Agent: Mutt/1.5.11
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1251
Lines: 38

On Thu, May 04, 2006 at 05:01:07PM +0200, Michael Holzheu wrote:
> Hi Greg,
> 
> Greg KH <greg@kroah.com> wrote on 05/04/2006 04:42:59 PM:
> > > I would suggest do do it like /sys/kernel and put the code
> > > into kernel/ksysfs.c and include/linux/kobject.h
> >
> > No, if you do that then every kernel gets that mount point, when almost
> > no one really wants it :)
> >
> > If you leave it as a separate file, then the build system can just
> > include the file as needed.
> >
> 
> So you want a new config option CONFIG_HYPERVISOR?

Sure.  But don't make it a user selectable config option, but rather,
one your S390 option sets.

That way the Xen and other groups can also set it when they need it.

> When no one except for us wants it, wouldn't it be best
> then to create /sys/hypervisor first in the hypfs code?
> 
> If someone else needs it in the future, we still can move
> it common code.

The Xen people need it too.  Now who knows when their code will ever hit
mainline...

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/