From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastian Blank <waldi@debian.org>
Subject: xenfs aka /proc/xen
Date: Fri, 28 May 2010 00:54:40 +0200
Message-ID: <20100527225440.GC25018@wavehammer.waldi.eu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Hi

The current tree includes a xenfs to be used on /proc/xen. This always
looked wrong to me as it merges arbitrary information and access to Xen
infrastructure. Also it is the only hypervisor support that needs such
filesystem while everyone else and even several part of the Xen support
uses the traditional ways, devices and sysfs.

One of the entries (capabilities) provides information about the
proviledge level to the hypervisor and belongs more likely into
/sys/hypervisor. The four other are plain old devices and belongs into
/dev.

Bastian

-- 
There's coffee in that nebula!
		-- Capt. Kathryn Janeway, Star Trek: Voyager, "The Cloud"