From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
Juergen Gross <jgross@suse.com>
Cc: Stefano Stabellini <stefano@aporeto.com>,
anthony.perard@citrix.com,
xen-devel <xen-devel@lists.xenproject.org>,
Greg Kurz <groug@kaod.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v4 1/8] xen: import ring.h from xen
Date: Wed, 29 Mar 2017 10:06:11 +0200 [thread overview]
Message-ID: <25280fb4-5ffd-a523-b5c1-4725fa55e44b@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1703281653340.27589@sstabellini-ThinkPad-X260>
On 29/03/2017 01:54, Stefano Stabellini wrote:
>>> I understand your point of view, and honestly it wouldn't be a problem
>>> doing it the way you suggested either. However, I think that going
>>> forward it will be less of a maintenance pain to keep ring.h in sync,
>>> compared to maintaining a versioned build dependency between Xen and
>>> QEMU for the compilation of one PV backend. We do have version checks
>>> in QEMU for Xen compatibility, but not for PV backends or the xenpv
>>> machine yet.
>> For the pvUSB backend I just used a mandatory macro from the header for
>> the #ifdef. The backend will signal support when it was defined during
>> build and will refuse initialization otherwise. Xen tools are able to
>> recoginze qemu support of the backend by looking into Xenstore.
>
> What do you think of the following:
Let's just copy the header...
Paolo
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-29 8:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 18:18 [PATCH v4 0/8] xen/9pfs: introduce the Xen 9pfs backend Stefano Stabellini
2017-03-21 10:20 ` Greg Kurz
2017-03-21 20:14 ` [Qemu-devel] " Stefano Stabellini
2017-03-22 8:47 ` Greg Kurz
2017-03-22 18:32 ` Stefano Stabellini
2017-03-23 8:34 ` Greg Kurz
2017-03-23 16:49 ` Stefano Stabellini
[not found] ` <1490033952-26735-1-git-send-email-sstabellini@kernel.org>
[not found] ` <20170323140005.6b0853b3@bahia.lan>
[not found] ` <15207674-c5cd-3874-7ac9-5b23cdac8888@suse.com>
[not found] ` <28db5816-2ed9-0d92-a15d-af47b58a9da1@redhat.com>
[not found] ` <alpine.DEB.2.10.1703230953120.8001@sstabellini-ThinkPad-X260>
2017-03-24 6:02 ` [PATCH v4 1/8] xen: import ring.h from xen Juergen Gross
2017-03-24 17:37 ` Stefano Stabellini
2017-03-27 12:41 ` Juergen Gross
2017-03-27 22:48 ` Stefano Stabellini
2017-03-28 6:02 ` Juergen Gross
2017-03-28 23:54 ` Stefano Stabellini
2017-03-29 5:46 ` Juergen Gross
2017-03-29 8:06 ` Paolo Bonzini [this message]
2017-03-29 18:42 ` Stefano Stabellini
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=25280fb4-5ffd-a523-b5c1-4725fa55e44b@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=groug@kaod.org \
--cc=jgross@suse.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=stefano@aporeto.com \
--cc=xen-devel@lists.xenproject.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).