All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Michael Holzheu <holzheu@de.ibm.com>,
	schwidefsky@de.ibm.com, penberg@cs.helsinki.fi,
	ioe-lkml@rameria.de, joern@wohnheim.fh-wedel.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390: Hypervisor File System
Date: Sat, 29 Apr 2006 00:51:33 -0700	[thread overview]
Message-ID: <20060429075133.GA1886@kroah.com> (raw)
In-Reply-To: <20060428234441.1407c82f.akpm@osdl.org>

On Fri, Apr 28, 2006 at 11:44:41PM -0700, Andrew Morton wrote:
> Michael Holzheu <holzheu@de.ibm.com> wrote:
> >
> >  As mount point for the filesystem /sys/hypervisor is created.
> 
> What does this mean, btw?  I don't see code there creating a new sysfs
> directory, and userspace cannot do this.

The call to subsystem_register() does this.

> Also, "/sys/hypervisor" is probably insufficiently specific.  In a few
> years time people will be asking "Which hypervisor?  We have eighteen of them!".

I agree, the xen people are already clammering for some kind of sysfs
tree and wanted to create /sys/hypervisor/xen.  How about
/sys/hypervisor/s390?

thanks,

greg k-h

  reply	other threads:[~2006-04-29  7:53 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28  9:22 [PATCH] s390: Hypervisor File System Michael Holzheu
2006-04-28  9:43 ` Jörn Engel
2006-04-28 11:53   ` Michael Holzheu
2006-04-28 15:48     ` Jörn Engel
2006-04-28  9:56 ` Andrew Morton
2006-04-28 17:36   ` Michael Holzheu
2006-04-28 17:43     ` Jörn Engel
2006-05-02  8:06       ` Michael Holzheu
2006-04-28 19:44     ` Andrew Morton
2006-04-28 10:36 ` Pekka J Enberg
2006-04-28 13:14   ` Michael Holzheu
2006-04-29  6:44 ` Andrew Morton
2006-04-29  7:51   ` Greg KH [this message]
2006-04-29  8:14     ` Andrew Morton
2006-05-03  8:48       ` Michael Holzheu
2006-05-03 22:10         ` Greg KH
2006-05-04 10:22           ` Michael Holzheu
2006-05-04 14:42             ` Greg KH
2006-05-04 15:01               ` Michael Holzheu
2006-05-04 15:34                 ` Greg KH
2006-04-29  7:53 ` Greg KH
2006-04-29  8:41   ` Kyle Moffett
2006-04-29 21:55     ` Greg KH
2006-04-30  5:18       ` Kyle Moffett
2006-05-01 20:38         ` Greg KH
2006-05-01 23:29           ` Kyle Moffett
2006-05-02  4:00             ` Greg KH
2006-05-02  5:23               ` Kay Sievers
2006-05-02  5:37                 ` Greg KH
2006-05-02 11:46                   ` Kay Sievers
2006-05-02 21:28                     ` Greg KH
2006-05-02 21:33                       ` Kay Sievers
2006-05-02 21:54                         ` Greg KH
2006-05-02  8:48               ` Kyle Moffett
2006-05-02 21:30                 ` Greg KH
2006-05-02 21:49                   ` Kay Sievers
2006-05-02 23:18                     ` Kyle Moffett
2006-05-03  9:33     ` Michael Holzheu
2006-05-03  9:42       ` Pekka J Enberg
2006-05-03 12:11         ` Michael Holzheu
2006-05-03 12:33           ` Jörn Engel
2006-05-03 12:51             ` Michael Holzheu
2006-05-03 13:00               ` Jörn Engel
2006-05-03 13:18                 ` Michael Holzheu
2006-05-03 13:22                   ` Jörn Engel
2006-05-03 13:38                     ` Michael Holzheu
2006-05-03 14:17                       ` Martin Schwidefsky
2006-05-03 14:23                         ` Michael Holzheu
2006-05-03 14:58                           ` Martin Schwidefsky
2006-05-03 15:22                             ` Michael Holzheu
2006-05-03 15:54                   ` Valdis.Kletnieks
2006-05-03 10:01       ` Jörn Engel
2006-05-02 10:12   ` Michael Holzheu
2006-05-02 13:00   ` Michael Holzheu
2006-05-03  8:45   ` Michael Holzheu
  -- strict thread matches above, loose matches on Subject: below --
2006-04-28 17:37 Michael Holzheu
2006-04-28 17:47 ` Jörn Engel
2006-05-02  7:25   ` Michael Holzheu
2006-05-05 13:22 Michael Holzheu
2006-05-05 21:14 ` Greg KH
2006-05-08 12:24 Michael Holzheu
2006-05-09  5:01 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060429075133.GA1886@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=holzheu@de.ibm.com \
    --cc=ioe-lkml@rameria.de \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=schwidefsky@de.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.