All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: "Santos, Jose Renato G" <joserenato.santos@hp.com>
Cc: xen-devel@lists.xensource.com, oprofile-list@lists.sourceforge.net
Subject: Re: [Xen-devel] xenoprof support patch issue for oprofile 0.9.3
Date: Fri, 20 Jul 2007 10:44:14 -0400	[thread overview]
Message-ID: <46A0CA3E.5020708@redhat.com> (raw)
In-Reply-To: <08CA2245AFCF444DB3AC415E47CC40AFD37A7A@G3W0072.americas.hpqcorp.net>

Santos, Jose Renato G wrote:
> Will,
> 
> Thanks for pointing this out.
> I will work on a patch to fix this
> By the way, it would be nice to have the xenoprof patches merged into
> Oprofile CVS tree.
> John Levon is not happy with the way passive domain samples are stored
> now and I don't have the bandwidth (and knowdledge of user level
> Oprofile code) to do the right fixes. This has prevented the patches to
> be merged. It would be nice if we can find a volunteer to do the right
> fixes and have the code merged. I would be happy to assist anyone who
> volunteers for the task. What we need is a way of separating samples
> from different domains and change to the tools to understand this new
> information.
> 
> Thanks
> 
> Renato 

Hi Renato,

Definitely want to avoid having separate patches to avoid just this type of 
problem. Getting patches upstream is the way to go on that.

Do you have a pointer to the email discussion about the passive domain sample 
storage? Passive means that the domain is not taking the samples and storing 
them in the domain, right?

One of the things that I have noticed on my previous experiments with the 
xenoprof is there are quite a few steps to setup xenoprof. The user has to do 
setup on each domain. Ideally it would be nice to be able to just do one setup 
in the host domain and then have that information be propagated to the guest 
domains. Similarly the analysis would be nice to get one over all picture of all 
the domains. Clusters have a similar issue; one doesn't want to manage machine 
individually. However clusters may have different hardware for the various nodes 
in the cluster. With xen the only difference could be the software.

-Will

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2007-07-20 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 18:46 xenoprof support patch issue for oprofile 0.9.3 William Cohen
2007-07-19 19:02 ` [Xen-devel] " Santos, Jose Renato G
2007-07-20 14:44   ` William Cohen [this message]
2007-07-20 16:42     ` Santos, Jose Renato G
2007-07-26 14:29       ` [Xen-devel] " William Cohen
2007-07-30 23:11         ` Santos, Jose Renato G

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=46A0CA3E.5020708@redhat.com \
    --to=wcohen@redhat.com \
    --cc=joserenato.santos@hp.com \
    --cc=oprofile-list@lists.sourceforge.net \
    --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.