public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mike D. Day" <ncmike@us.ibm.com>
To: xen-devel@lists.xensource.com
Cc: lkml <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>,
	Dave Hansen <haveblue@us.ibm.com>
Subject: [ PATCH 2.6.16-rc3-xen 1/3] sysfs: export Xen hypervisor attributes to sysfs
Date: Tue, 21 Feb 2006 09:36:35 -0500	[thread overview]
Message-ID: <43FB2573.3070909@us.ibm.com> (raw)

This series of patches is a module that exports Xen Hypervisor attributes
to sysfs. The directory structure created is: 

+---sys
	+---hypervisor
		+---xen
			+---version
			+---major
			+---minor
			+---extra
		+---compilation
			+---by
			+---date
			+---compiler 
		+---properties
			+---changeset
			+---capabilities
			+---virt_start
			+---translated_pm
			+---writable_dt
			+---writable_pt

The xen_sysfs module has a tri-state Kconfig so it can be built-in or
loaded as a module.

The module is in three patches: 

Patch 1 (this patch) is a Xen file that is used by all OS kernels that run
on Xen. This includes linux, NetBSD, FreeBSD, Solaris, and others. Patch 1
adds #defined constants so that linux users of this file can avoid typedefs. 

Patch 2 (follows) contains the Kconfig changes necessary to add this module
to the kernel build. 

Patch 3 (follows) contains the source for the xen_sysfs module itself. 

# HG changeset patch
# User mdday@dual.silverwood.home
# Node ID d296aaf07bcb4141c6dc2a1bfa7d183f919c2167
# Parent  a05e56904e7e5e86aae5a2e022621caaf7b3a6f5
define constants for array sizes. Allows linux users of this file 
to avoid #typedefs. Existing typedefs work as before. 

signed-off-by: Mike D. Day <ncmike@us.ibm.com>

diff -r a05e56904e7e -r d296aaf07bcb xen/include/public/version.h
--- a/xen/include/public/version.h	Mon Feb 20 23:01:50 2006 +0000
+++ b/xen/include/public/version.h	Tue Feb 21 08:11:03 2006 -0500
@@ -1,8 +1,8 @@
/******************************************************************************
 * version.h
- * 
+ *
 * Xen version, type, and compile information.
- * 
+ *
 * Copyright (c) 2005, Nguyen Anh Quynh <aquynh@gmail.com>
 * Copyright (c) 2005, Keir Fraser <keir@xensource.com>
 */
@@ -17,6 +17,7 @@

/* arg == xen_extraversion_t. */
#define XENVER_extraversion 1
+#define XENVER_EXTRAVERSION_LEN 16
typedef char xen_extraversion_t[16];

/* arg == xen_compile_info_t. */
@@ -29,9 +30,11 @@ typedef struct xen_compile_info {
} xen_compile_info_t;

#define XENVER_capabilities 3
+#define XENVER_CAPABILITIES_INFO_LEN 1024
typedef char xen_capabilities_info_t[1024];

#define XENVER_changeset 4
+#define XENVER_CSET_INFO_LEN 64
typedef char xen_changeset_info_t[64];

#define XENVER_platform_parameters 5



             reply	other threads:[~2006-02-21 14:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 14:36 Mike D. Day [this message]
2006-02-21 15:21 ` [ PATCH 2.6.16-rc3-xen 1/3] sysfs: export Xen hypervisor attributes to sysfs Arjan van de Ven
2006-02-21 17:37 ` [Xen-devel] " Keir Fraser
2006-02-21 17:42 ` Christoph Hellwig
2006-02-21 17:56 ` 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=43FB2573.3070909@us.ibm.com \
    --to=ncmike@us.ibm.com \
    --cc=greg@kroah.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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