WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [ PATCH 2.6.16-rc3-xen 3/3] sysfs: export Xen hypervisor

To: Dave Hansen <haveblue@xxxxxxxxxx>
Subject: [Xen-devel] Re: [ PATCH 2.6.16-rc3-xen 3/3] sysfs: export Xen hypervisor attributes to sysfs
From: Heiko Carstens <heiko.carstens@xxxxxxxxxx>
Date: Wed, 22 Feb 2006 13:32:50 +0100
Cc: "Mike D. Day" <ncmike@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, lkml <linux-kernel@xxxxxxxxxxxxxxx>, Greg KH <greg@xxxxxxxxx>
Delivery-date: Thu, 23 Feb 2006 10:55:15 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1140542130.8693.18.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <43FB2642.7020109@xxxxxxxxxx> <1140542130.8693.18.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: mutt-ng/devel-r781 (Linux)
> I'm wondering if this information couldn't be laid out in a slightly
> more generic way so that other hypervisors could use the same layout.
> Instead of:
> 
> +---sys
>         +---hypervisor
>                 +---xen
>                         +---version
>                         +---major
>                         +---minor
>                         +---extra
> 
> It could be:
> 
> +---sys
>         +---hypervisor
>                 +---type
>               +---version
>                         +---major
>                         +---minor
>                         +---extra
> 
> Where cat /sys/hypervisor/type is 'xen'.  That way, if there are generic
> things about hypervisors to export here, any generic tools can find them
> without having to know exactly which hypervisor is running.
> 
> You can also set the standard that any other hypervisor has to
> follow! :)

I doubt that there is much that different hypervisors can share.
Why should all this be visible for user space anyway? What's the purpose?

Heiko

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>