mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: ncmike@us.ibm.com
Cc: xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org,
	gregkh@suse.de
Subject: Re: [PATCH 2.6.16-rc6-xen] export Xen Hypervisor attributes to sysfs
Date: Tue, 21 Mar 2006 08:14:29 +0100	[thread overview]
Message-ID: <1142925269.3077.10.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200603202335.k2KNZEjo005673@mdday.raleigh.ibm.com>

On Mon, 2006-03-20 at 18:35 -0500, Mike D. Day wrote:
> Creates a module that exports Xen Hypervisor attributes to sysfs. The
> module has a tri-state configuration so it can be a loadable module.
> 
> Views the hypervisor as hardware device, uses sysfs as  a scripting
> interface for user space tools that need these attributes.
> 
> Some user space apps, particularly for systems management, need to
> know if their kernel is running in a virtual machine and if so in
> what type of virtual machine. This property is contained in the
> file /sys/hypervisor/type.
> 
> The file hypervisor_sysfs.c creates a generic  hypervisor subsystem
> that can be linked to by any hypervisor. The file xen_sysfs.c exports
> the xen-specific attributes.
> 
> signed-off-by: Mike D. Day <ncmike@us.ibm.com>
> 
> ---
> Initial directory = /sys/hypervisor
> +---compilation
> |   >---compile_date
> |   >---compiled_by
> |   >---compiler
> +---properties
> |   >---capabilities
> |   >---changeset

how is this a property and not part of version?

> |   >---virtual_start
> |   >---writable_pt
> >---type
> +---version
> |   >---extra
> |   >---major
> |   >---minor
> 


again what is the justification of putting this in the kernel? I though
everyone here was agreed that since the management tools that need this
talk to the hypervisor ANYWAY, they might as well just ask this
information as well....




  reply	other threads:[~2006-03-21  7:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20 23:35 Mike D. Day
2006-03-21  7:14 ` Arjan van de Ven [this message]
2006-03-21 10:44   ` Mike D. Day
2006-03-21 11:10     ` Arjan van de Ven
2006-03-21 11:32       ` Mike D. Day
2006-03-24 21:42 ` Greg KH

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=1142925269.3077.10.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=gregkh@suse.de \
    --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®