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

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

> Maybe:
> 
> if $$source/scripts/tracetool.py --check-backends --backends log &>/dev/null
> then
>     enable_trace_backend='--enable-trace-backend=log'
> else
>     enable_trace_backend='--enable-trace-backend=stderr'
> fi
> 
> ?
> 
> 
> > +		enable_trace_backend='--enable-trace-backend=log'; \
> > +	elif $$source/scripts/tracetool.py --check-backends --backends stderr ; then \
> > +		enable_trace_backend='--enable-trace-backend=stderr'; \
> > +	else \
> > +		enable_trace_backend='' ; \
> > +	fi ; \
> >  	$$source/configure --enable-xen --target-list=i386-softmmu \
> >  		$(QEMU_XEN_ENABLE_DEBUG) \
> > +		$$enable_trace_backend \
> >  		--prefix=$(LIBEXEC) \
> >  		--libdir=$(LIBEXEC_LIB) \
> >  		--includedir=$(LIBEXEC_INC) \
> > -- 
> > 2.1.4
> > 

-- 
Anthony PERARD

  reply	other threads:[~2016-02-10 14:18 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 [this message]
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
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=20160210141846.GA28822@perard.uk.xensource.com \
    --to=anthony.perard@citrix.com \
    --cc=ian.campbell@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).