public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Michael Holzheu <HOLZHEU@de.ibm.com>
Cc: "Pekka Enberg" <penberg@cs.helsinki.fi>,
	linux-kernel@vger.kernel.org, mschwid2@de.ibm.com,
	penberg@gmail.com
Subject: Re: [PATCH/RFC] s390: Hypervisor File System
Date: Fri, 21 Apr 2006 16:55:46 +0200	[thread overview]
Message-ID: <200604211655.46993.arnd@arndb.de> (raw)
In-Reply-To: <OF88396E73.9225D435-ON42257157.004BB28F-42257157.004C9411@de.ibm.com>

On Friday 21 April 2006 15:56, Michael Holzheu wrote:
> > This filesystem makes no sense for anything but s390 so please put it
> > under arch/s390/ (following the convention set by cell specific
> > spufs). Thanks.
> 
> Agreed! As long as the filesystem is s390 specifc, we probably should put
> it put it under arch/s390/hypfs. But in general one could imagine, that
> also other hypervisor platforms want to have such a filesystem in the
> future. In that case, we could make the filesystem more generic. E.g. we
> could split it into the filesystem part and an architecture specific
> backend which provides the hypervisor data. But you are right, until no
> other platform supports it, we should keep it simple, leave it s390
> specific and move it to arch/s390.
> 
There was some discussion about a sysfs hierarchy for hypervisor data
some time ago, see also http://lwn.net/Articles/176365/.
The idea was rather similar, just for other attributes. Maybe this
can be consolidated in some way.

Is there a strong reason why you made your own file system instead of
using subsystem_register to add /sys/hypervisor?

	Arnd <><

  reply	other threads:[~2006-04-21 14:55 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21 11:35 [PATCH/RFC] s390: Hypervisor File System Michael Holzheu
2006-04-21 11:53 ` Pekka Enberg
2006-04-21 13:56   ` Michael Holzheu
2006-04-21 14:55     ` Arnd Bergmann [this message]
2006-04-21 15:31       ` Michael Holzheu
2006-04-21 13:32 ` Pekka Enberg
2006-04-21 14:08   ` Michael Holzheu
2006-04-21 15:38     ` Pekka Enberg
2006-04-21 16:40       ` Martin Schwidefsky
2006-04-25 14:04         ` Pekka Enberg
2006-04-21 14:42 ` Pekka Enberg
2006-04-21 14:59   ` Michael Holzheu
2006-04-21 15:41     ` Pekka Enberg
2006-04-21 15:18   ` Jörn Engel
2006-04-21 15:36     ` Michael Holzheu
2006-04-21 15:46       ` Jörn Engel
2006-04-21 22:30   ` Ingo Oeser
2006-04-24 17:17     ` Michael Holzheu
2006-04-24 19:57       ` Ingo Oeser
2006-04-25  6:27       ` Pekka Enberg
2006-04-24 17:19   ` Michael Holzheu
  -- strict thread matches above, loose matches on Subject: below --
2006-04-24 17:19 Michael Holzheu
2006-04-25  6:58 ` Pekka Enberg
2006-04-25  7:32   ` Pekka Enberg
2006-04-25  7:47     ` Andrew Morton
2006-04-25  8:01       ` Pekka Enberg
2006-04-25  8:52     ` Jörn Engel
2006-04-25  9:00       ` Pekka Enberg
2006-04-25 12:22     ` Michael Holzheu
2006-04-25 14:33 ` Pekka Enberg
2006-04-25 14:45   ` Jörn Engel
2006-04-26  9:30   ` Michael Holzheu

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=200604211655.46993.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=HOLZHEU@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mschwid2@de.ibm.com \
    --cc=penberg@cs.helsinki.fi \
    --cc=penberg@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox