All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike D. Day" <ncmike@us.ibm.com>
To: Arjan van de Ven <arjan@infradead.org>
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 05:44:03 -0500	[thread overview]
Message-ID: <441FD8F3.208@us.ibm.com> (raw)
In-Reply-To: <1142925269.3077.10.camel@laptopd505.fenrus.org>

Arjan van de Ven wrote:

>> +---properties
>> |   >---capabilities
>> |   >---changeset
> 
> how is this a property and not part of version?
Agree, changeset should be part of version

> 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....

I think we had a good discussion but short of agreement. Some tools want to 
read a file from /sys/hypervisor/ rather than call a c lib. (In other words, 
not all tools will talk to the hypervisor.) It is appropriate to view the 
hypervisor as a hardware device so it is appropriate to have some information 
in sysfs. 

I appreciate the counter argument as well, but think this should be a 
configurable option. 

thanks, 

Mike

  reply	other threads:[~2006-03-21 10:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20 23:35 [PATCH 2.6.16-rc6-xen] export Xen Hypervisor attributes to sysfs Mike D. Day
2006-03-21  7:14 ` Arjan van de Ven
2006-03-21 10:44   ` Mike D. Day [this message]
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=441FD8F3.208@us.ibm.com \
    --to=ncmike@us.ibm.com \
    --cc=arjan@infradead.org \
    --cc=gregkh@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.