Messages in this thread | | | From | Arnd Bergmann <> | Subject | Re: [PATCH/RFC] s390: Hypervisor File System | Date | Fri, 21 Apr 2006 16:55:46 +0200 |
| |
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 <>< - 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/
| |