From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, mingo@elte.hu,
avi@redhat.com, akataria@vmware.com
Subject: Re: [PATCH 2/2] show hypervisor information on sysfs
Date: Tue, 10 Feb 2009 14:31:58 +0100 [thread overview]
Message-ID: <20090210143158.056bbd43@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20090210132023.GB13577@poweredge.glommer>
On Tue, 10 Feb 2009 11:20:23 -0200
Glauber Costa <glommer@redhat.com> wrote:
> > Anyway, just wanted to make you aware of what might come next.
>
> Why wouldn't it be extensible? So far, I've only added an attribute. But we
> can easily add others, and directories with even more attributes if we must.
Oh, sure it's easily extensible, the question is if the first attribute
you now add will be at the right place. That is: is all information
about the 1st level hypervisor supposed to be found in /sys/hypervisor
or should it be in a subdirectory? E.g. /sys/hypervisor/level1 or
something like that.
But adding your attribute won't hurt. The worst case is that it gets
duplicated.
prev parent reply other threads:[~2009-02-10 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 15:46 [PATCH 0/2] Show hypervisor information on sysfs Glauber Costa
2009-02-06 15:46 ` [PATCH 1/2] tell cpuinfo if we're running on top of KVM Glauber Costa
2009-02-06 15:46 ` [PATCH 2/2] show hypervisor information on sysfs Glauber Costa
2009-02-07 10:43 ` Heiko Carstens
2009-02-10 13:20 ` Glauber Costa
2009-02-10 13:31 ` Heiko Carstens [this message]
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=20090210143158.056bbd43@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=akataria@vmware.com \
--cc=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).