From: John Levon <levon@movementarian.org>
To: Satoshi Uchida <s-uchida@ap.jp.nec.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Sysfs Interface for balloon driver
Date: Wed, 20 Sep 2006 16:20:06 +0100 [thread overview]
Message-ID: <20060920152006.GA32328@totally.trollied.org> (raw)
In-Reply-To: <00c401c6dc60$f22303f0$4c87380a@ad.spf.cl.nec.co.jp>
On Wed, Sep 20, 2006 at 12:00:36PM +0900, Satoshi Uchida wrote:
> In this time, it locate by following reason.
> A balloon driver is similar to front-end driver.
Not really. Front-end drivers are real drivers, thus it makes sense for
them to appear to be attached to a bus, even if that bus is virtual.
> I feel that the term "hypervisor" means VMM in general.
> And a balloon exists for VM, and not for VMM.
I don't understand what you mean here.
> Therefore, I think that such information should not be located to /sys/hypervisor.
Anyone else have an opinion?
> Should new location make for storing such (VM's) information ?
> For example, as following.
> /sys/virtualization -+--- domain
> +--- hypervisor
Why would we need this? We already have xenstore for representing other
domain's information, and /sys/ is always specific to that particular
operating system instantiation.
regards
john
next prev parent reply other threads:[~2006-09-20 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 0:26 [PATCH] Sysfs Interface for balloon driver Satoshi Uchida
2006-09-20 1:12 ` John Levon
2006-09-20 3:00 ` Satoshi Uchida
2006-09-20 15:20 ` John Levon [this message]
2006-09-20 18:26 ` Anthony Liguori
2006-09-20 23:23 ` Ian Pratt
2006-09-20 23:29 ` John Levon
2006-09-20 23:40 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2006-09-22 2:15 Satoshi Uchida
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=20060920152006.GA32328@totally.trollied.org \
--to=levon@movementarian.org \
--cc=s-uchida@ap.jp.nec.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 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.