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 14:59:05 +0000 [thread overview]
Message-ID: <1455116345.19857.169.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1602101442340.27008@kaball.uk.xensource.com>
On Wed, 2016-02-10 at 14:44 +0000, Stefano Stabellini wrote:
> > > > But, if you use '--check-backend --backend' (no 's') instead, the
> > > > check
> > > > would works with qemu-xen >= 4.3
> >
> > BTW, I think those correspond to
> >
> > qemu-mainline == QEMU 2.5.50
> > qemu-xen-unstable == QEMU 2.4.1
> > qemu-xen-4.6 == QEMU 2.2.1
> > qemu-xen-4.5 == QEMU 2.0.2
> >
> > and the change to use --backends was between 2.0.50 and 2.0.90 (AKA
> > 2.1.0-
> > rc0).
> >
> > Do we require that Xen 4.7 will work with QEMU 2.0.x? Given that AFAICT
> > the
> > oldest QEMU upstream supported version is 2.2.1?
>
> No, but if somebody wants to use qemu-xen-4.5 with xen-unstable, which
> is not that crazy given that qemu-xen-4.5 is still supported (even
> qemu-xen-4.3 still is), this change in the Makefile would break the
> build.
"supported" is a bit of a stretch IMHO. qemu-xen-4.5 is supported as part
of xen-4.5, not as a standalone independent entity, surely.
> Anthony's suggestion is a good compromise.
I'd prefer the option given in my second followup suggestion in <1455115410
.19857.167.camel@citrix.com>.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-10 14:59 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 [this message]
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=1455116345.19857.169.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).