From: Arjan van de Ven <arjan@infradead.org>
To: "Mike D. Day" <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 12:10:44 +0100 [thread overview]
Message-ID: <1142939444.3077.55.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <441FD8F3.208@us.ibm.com>
On Tue, 2006-03-21 at 05:44 -0500, Mike D. Day wrote:
> 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.
then make a simple tool that gives the info to stdout
> I appreciate the counter argument as well, but think this should be a
> configurable option.
"a config option" is a cop-out. By proposing a config option you even
admit it's not essential for userspace. The last thing this should be is
a config option; it either is needed and important, and should be there
always, or it's redundant and should be done in userspace. "A config
option" is just admitting that it is the later, but that you need to
justify the time you spent on the kernel patch somewhere ;-)
next prev parent reply other threads:[~2006-03-21 11:10 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
2006-03-21 10:44 ` Mike D. Day
2006-03-21 11:10 ` Arjan van de Ven [this message]
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=1142939444.3077.55.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®