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 <[email protected]>
>
> ---
> 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....
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
