public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mike D. Day" <ncmike@us.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Greg KH <greg@kroah.com>,
	xen-devel@lists.xensource.com,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] Re: [RFC] [PATCH] sysfs support for Xen attributes
Date: Thu, 12 Jan 2006 10:50:39 -0500	[thread overview]
Message-ID: <43C67ACF.5000600@us.ibm.com> (raw)
In-Reply-To: <1137079724.5397.29.camel@localhost.localdomain>

Dave Hansen wrote:

>>Debugging is always a good reason :) but I'm specifically thinking of 
>>systems management tools, deployment of virtual machines, and migration. 
>>All of these attributes are important for tools that manage, deploy, or 
>>migrate.
> 
> 
> -ETOOMANYBUZZWORDS :)

How is this helping to reach consensus?

> One concern I have with this approach is that it is for things for which
> a need is _anticipated_, instead of things that are actually needed.  It
> is awesome that this is being done in advance, but you have to be
> careful not to throw the kitchen sink at the problem from the beginning.

I've got 2 problems with this comment. First, these things are actually 
needed. VMWare has tools that deploy, manage, and migrate virtual 
machines, PHYP does as well (it can't migrate partitions). Xen really 
needs tools that do the same. It would be best if these tools are 
open-source themselves and use GPL'd code to get the necessary 
information from xen. If you try to use xen I think you will agree.

My second problem with this comment the implication that anticipating 
needs is bad. I understand your argument but disagree on the kitchen 
sink comment.

> Would a potential workload manager contact the individual Xen partitions
> in order to get an overview of the entire machine?  Why would it not
> simply contact the controlling partition?

Not sure what you mean by controlling partition. Xen doesn't have a 
hardware management console like PHYP does. Xen management tools need to 
run on a regular linux kernel that is running within a domain. Usually 
this is the first domain created, aka domain 0.

So to answer your question, of course a "workload manager" would contact 
  domain 0. But how does domain 0 obtain an overview of the entire 
machine so it can relay that info back to the "workload manager"? Domain 
0  has to get the attributes from the hypervisor. How does it do that? 
The best way is to read attributes from sysfs.


-- 

Mike D. Day
STSM and Architect, Open Virtualization
IBM Linux Technology Center
ncmike@us.ibm.com

  reply	other threads:[~2006-01-12 15:50 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11 17:17 [RFC] [PATCH] sysfs support for Xen attributes Mike D. Day
2006-01-11 17:19 ` Arjan van de Ven
2006-01-11 17:56 ` Stephen Hemminger
2006-01-11 18:45 ` Dave Hansen
2006-01-11 23:07 ` Greg KH
2006-01-12  0:23   ` Mike D. Day
2006-01-12  0:57     ` Greg KH
2006-01-12  1:49       ` Mike D. Day
2006-01-12  2:17         ` [Xen-devel] " Mark Williamson
2006-01-12  7:10         ` Greg KH
2006-01-12 14:44           ` [Xen-devel] " Mike D. Day
2006-01-12 14:53             ` Mark Williamson
2006-01-12 15:42               ` Anthony Liguori
2006-01-12 15:57             ` Anthony Liguori
2006-01-12 17:34               ` Greg KH
2006-01-12 18:44                 ` Anthony Liguori
2006-01-12 17:43             ` Greg KH
2006-01-12  9:10         ` Dave Hansen
2006-01-12 14:52           ` [Xen-devel] " Mike D. Day
2006-01-12 15:28             ` Dave Hansen
2006-01-12 15:50               ` Mike D. Day [this message]
2006-01-12 12:54         ` Gerd Hoffmann
2006-01-12 13:21           ` Arjan van de Ven
2006-01-12 14:42             ` Gerd Hoffmann
2006-01-12 17:39               ` Greg KH
2006-01-12 18:53                 ` Anthony Liguori
2006-01-12 18:55                   ` Arjan van de Ven
2006-01-12 18:59                     ` Anthony Liguori
2006-01-12 19:11                       ` Mike D. Day
2006-01-12 19:31                         ` Greg KH
2006-01-12 19:08                   ` Greg KH
2006-01-12 19:18                     ` Mike D. Day
2006-01-12 19:30                       ` Greg KH
2006-01-12 17:38           ` Greg KH
2006-01-12  1:32     ` Dave Hansen
2006-01-12 10:04       ` [Xen-devel] " Keir Fraser
2006-01-12 15:14         ` Dave Hansen
2006-01-12 15:06           ` Mark Williamson
2006-01-12 15:26           ` Keir Fraser
2006-01-12 15:37             ` Dave Hansen
2006-01-12 15:49               ` Anthony Liguori
2006-01-11 23:31 ` Pavel Machek
2006-01-12 19:01   ` 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=43C67ACF.5000600@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