RE: [Xen-devel] [PATCH] xenoprof (linux-sparse)

["Santos, Jose Renato G" <joserenato.santos@xxxxxx>]

  John,

  Thanks for your comments and suggetions.

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of John Levon
> Sent: Sunday, November 13, 2005 4:41 AM
> To: Santos, Jose Renato G
> Cc: Ian Pratt; xen-devel@xxxxxxxxxxxxxxxxxxx; Turner, Yoshio; 
> Jose Renato Santos; G John Janakiraman
> Subject: Re: [Xen-devel] [PATCH] xenoprof (linux-sparse)
> 
> On Sat, Nov 12, 2005 at 08:00:38PM -0800, Santos, Jose Renato G wrote:
> 
> > The patch for Oprofile user level tools could go to a 
> "tools/oprofile"
> > directory or something equivalent as you suggested.
> 
> I'd much rather you send this patch to us and get it included 
> rather than putting it somewhere else.
> 

  Ok John. I will work on the changes you suggested in the next
  days and send you the user level tools patch.

> Also, I don't think the kernel bits should be applied until 
> you've resolved the issues I had with the escape codes I 
> mentioned a few months ago... it shouldn't be hard to rework, right?
> 

  Right now we don't need the escape codes. Those are used for
supporting
  delivery of passive domain samples, ie. including an event sample from
  a domain without oprofile to another domain that has oprofile running.
  The escape codes are used to indicate a sample belongs to a different
  domain. The current version does not support passive domains, so we
  really don't need the escape codes at the moment. I am planning to
change the
  way passive samples are handled, so we won't need escape code for that
  either, but this will require some more time (I am planning to use
  separate buffers for different domains, but I will have to discuss
this
  in more detail with you later).  Would you be happy if for now I
remove 
  the escape code completely? This should be easy to do.

  Thanks for your support

  Renato




> regards,
> john
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel