From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Gardner Subject: Re: xentrace_setmask badly broken? Date: Wed, 02 Jan 2008 20:42:56 -0700 Message-ID: <477C59C0.6000104@hp.com> References: <20080102151826296.00000000500@djm-pc> <200801030151.05435.mark.williamson@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200801030151.05435.mark.williamson@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Mark Williamson Cc: "dan.magenheimer@oracle.com" , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Mark Williamson wrote: > 1) Command line arguments to set the xentrace mask are completely ignored, > > > It looks like the tool just sets things up the way Xenmon needs them... This > is fine but I wonder if it couldn't just be rolled into the xenbaked? If > it's a necessary special-purpose tool for xenmon, it should probably be > stashed away off the user's path somewhere. As far as I can recall, Xenmon doesn't explicitly rely on the trace mask. Its only use to xenmon is if too many trace events are generated, then you can use the trace mask to reduce the volume. But I think the xenmon related trace events are numbered more-or-less sequentially, so a mask isn't very useful for picking which ones you'd like to see. But you can use the trace mask to turn off xenmon related events if you are just interested in vmx events, for instance. Rob