mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: "Mike D. Day" <ncmike@us.ibm.com>,
	xen-devel@lists.xensource.com,
	lkml <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: [ PATCH 2.6.16-rc3-xen 3/3] sysfs: export Xen hypervisor attributes to sysfs
Date: Wed, 22 Feb 2006 13:32:50 +0100	[thread overview]
Message-ID: <20060222123250.GB9295@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <1140542130.8693.18.camel@localhost.localdomain>

> 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

  parent reply	other threads:[~2006-02-22 12:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 14:40 Mike D. Day
2006-02-21 17:15 ` Dave Hansen
2006-02-21 17:48   ` Mike D. Day
2006-02-22 12:32   ` Heiko Carstens [this message]
2006-02-22 12:37     ` Mike D. Day
2006-02-22 12:56       ` Arjan van de Ven
2006-02-22 13:06         ` Mike D. Day
2006-02-22 13:19           ` Heiko Carstens
2006-02-22 13:43             ` Mike D. Day
2006-02-22 14:01               ` Arjan van de Ven
2006-02-22 16:08                 ` Mike D. Day
2006-02-23  4:26                 ` Anthony Liguori
2006-02-23  8:24                   ` Arjan van de Ven
2006-02-21 18:02 ` Alan Cox
2006-02-21 18:10 ` Greg KH
2006-02-22 12:26 ` Heiko Carstens

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=20060222123250.GB9295@osiris.boeblingen.de.ibm.com \
    --to=heiko.carstens@de.ibm.com \
    --cc=greg@kroah.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncmike@us.ibm.com \
    --cc=xen-devel@lists.xensource.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
all inboxes | Powered by JetHome®