xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	ian.jackson@eu.citrix.com, Paul Durrant <paul.durrant@citrix.com>,
	wei.liu2@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] tools: probe for existence of qemu-xen trace backends.
Date: Wed, 10 Feb 2016 15:06:52 +0000	[thread overview]
Message-ID: <1455116812.19857.173.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1602101450570.27008@kaball.uk.xensource.com>

On Wed, 2016-02-10 at 14:51 +0000, Stefano Stabellini wrote:
> On Wed, 10 Feb 2016, Ian Campbell wrote:
> > On Wed, 2016-02-10 at 14:27 +0000, Ian Campbell wrote:
> > > On Wed, 2016-02-10 at 14:18 +0000, Anthony PERARD wrote:
> > > > On Wed, Feb 10, 2016 at 02:14:13PM +0000, Stefano Stabellini wrote:
> > > > > On Wed, 10 Feb 2016, Ian Campbell wrote:
> > > > > > diff --git a/tools/Makefile b/tools/Makefile
> > > > > > index 5688a7c..76a2235 100644
> > > > > > --- a/tools/Makefile
> > > > > > +++ b/tools/Makefile
> > > > > > @@ -228,7 +228,7 @@ qemu-xen-dir-force-update: qemu-xen-dir-
> > > > > > find
> > > > > >  	fi
> > > > > >  
> > > > > >  ifeq ($(debug),y)
> > > > > > -QEMU_XEN_ENABLE_DEBUG := --enable-debug --enable-trace-
> > > > > > backend=stderr
> > > > > > +QEMU_XEN_ENABLE_DEBUG := --enable-debug
> > > > > >  else
> > > > > >  QEMU_XEN_ENABLE_DEBUG :=
> > > > > >  endif
> > > > > > @@ -240,8 +240,16 @@ subdir-all-qemu-xen-dir: qemu-xen-dir-find
> > > > > >  		source=.; \
> > > > > >  	fi; \
> > > > > >  	cd qemu-xen-dir; \
> > > > > > +	if $$source/scripts/tracetool.py --check-backends --
> > > > > > backends 
> > > > > > log ; then \
> > > > > 
> > > > > --check-backends only works on qemu-xen >= 4.6, on the other hand
> > > > > we
> > > > > know that qemu-xen < 4.6 supports stderr.
> > > > 
> > > > But, if you use '--check-backend --backend' (no 's') instead, the
> > > > check
> > > > would works with qemu-xen >= 4.3
> > > 
> > > That would be preferable to the below, IMHO. Any contrary opinions?
> > 
> > Actually, given that the upstream default is now "log", how about:
> > 
> >         if $$source/scripts/tracetool.py --check-backend --backend
> > stderr ; then \
> > 		enable_trace_backend='--enable-trace-backend=stderr'; \
> > 	else \		enable_trace_backend='' ; \
> > 	
> >         fi ; \
> > 
> > IOW just accept the upstream default (be it log or whatever comes next)
> > from this version onwards?
> 
> The risk associated with that is that in the past QEMU recommended
> 'simple', which has a binary output to a separate file.

I can't see any evidence of that in the git log over configure (which has
trace_backend="<thing>" in it. The configure file gained this option in
"trace: Add trace-events file for declaring trace events" with "nop" as the
default (circa QEMU 0.13.50) which it was until the recent switch to "log".

In any case what harm does have some other upstream default enable do? AIUI
you need to also enable specific tracing on the QEMU command line for it to
be useful, surely no version of QEMU was dumping some binary trace file
into $CWD by default?

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-02-10 15:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 12:42 [PATCH] tools: probe for existence of qemu-xen trace backends Ian Campbell
2016-02-10 14:14 ` Stefano Stabellini
2016-02-10 14:18   ` Anthony PERARD
2016-02-10 14:27     ` Ian Campbell
2016-02-10 14:37       ` Ian Campbell
2016-02-10 14:44         ` Stefano Stabellini
2016-02-10 14:59           ` Ian Campbell
2016-02-10 14:37       ` Stefano Stabellini
2016-02-10 14:43       ` Ian Campbell
2016-02-10 14:51         ` Stefano Stabellini
2016-02-10 15:06           ` Ian Campbell [this message]
2016-02-10 15:42             ` Stefano Stabellini
2016-02-10 15:53               ` Ian Campbell

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=1455116812.19857.173.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=paul.durrant@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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;
as well as URLs for NNTP newsgroup(s).