qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Paul Durrant <Paul.Durrant@citrix.com>,
	Anthony Perard <anthony.perard@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH 4/5] configure: detect presence of libxendevicemodel
Date: Thu, 2 Mar 2017 12:26:03 +0100	[thread overview]
Message-ID: <96cdf110-8fe4-1e47-c1cf-bbb7ca0760f0@suse.com> (raw)
In-Reply-To: <41a5070ecb3446658c55f807c37eb5ea@AMSPEX02CL03.citrite.net>

On 02/03/17 12:06, Paul Durrant wrote:
>> -----Original Message-----
>> From: Juergen Gross [mailto:jgross@suse.com]
>> Sent: 02 March 2017 11:01
>> To: Anthony Perard <anthony.perard@citrix.com>; Paul Durrant
>> <Paul.Durrant@citrix.com>
>> Cc: xen-devel@lists.xenproject.org; Stefano Stabellini
>> <sstabellini@kernel.org>; qemu-devel@nongnu.org
>> Subject: Re: [Xen-devel] [PATCH 4/5] configure: detect presence of
>> libxendevicemodel
>>
>> On 02/03/17 11:54, Anthony PERARD wrote:
>>> On Thu, Mar 02, 2017 at 09:06:43AM +0000, Paul Durrant wrote:
>>>>> -----Original Message-----
>>>>> From: Anthony PERARD [mailto:anthony.perard@citrix.com]
>>>>> Sent: 01 March 2017 17:18
>>>>> To: Paul Durrant <Paul.Durrant@citrix.com>
>>>>> Cc: xen-devel@lists.xenproject.org; qemu-devel@nongnu.org; Stefano
>>>>> Stabellini <sstabellini@kernel.org>
>>>>> Subject: Re: [PATCH 4/5] configure: detect presence of
>> libxendevicemodel
>>>>>
>>>>> On Thu, Feb 23, 2017 at 02:53:54PM +0000, Paul Durrant wrote:
>>>>>> This patch adds code in configure to set
>>>>> CONFIG_XEN_CTRL_INTERFACE_VERSION
>>>>>> to a new value of 490 if libxendevicemodel is present in the build
>>>>>> environment.
>>>>>>
>>>>>> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
>>>>>> ---
>>>>>> Cc: Stefano Stabellini <sstabellini@kernel.org>
>>>>>> Cc: Anthony Perard <anthony.perard@citrix.com>
>>>>>> ---
>>>>>>  configure | 19 +++++++++++++++++++
>>>>>>  1 file changed, 19 insertions(+)
>>>>>>
>>>>>> diff --git a/configure b/configure
>>>>>> index 8e8f18d..fc1e12b 100755
>>>>>> --- a/configure
>>>>>> +++ b/configure
>>>>>> @@ -1980,6 +1980,25 @@ EOF
>>>>>>    # Xen unstable
>>>>>>    elif
>>>>>>        cat > $TMPC <<EOF &&
>>>>>> +#undef XC_WANT_COMPAT_DEVICEMODEL_API
>>>>>> +#define __XEN_TOOLS__
>>>>>
>>>>> Isn't __XEN_TOOLS__ supposed to be reserved for some to tools inside
>>>>> xen.git?
>>>>>
>>>>> Also it seems to be the only time this define is used in your patch
>>>>> series.
>>>>>
>>>> No. QEMU falls under the definition of 'tools' as far as Xen goes and the
>> hypercalls and xendevicemodel API are protected by that. The reason you
>> don't see it elsewhere is that xenctrl.h defines it. (See
>> http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=tools/libxc/include/xenc
>> trl.h;hb=HEAD#l27).
>>>> I think that's a little underhand so I thought I'd make the new code in
>> configure more transparent. I can change it to just include xenctrl.h before
>> xendevicemodel.h if you'd prefer.
>>>
>>> I guess that is fine with __XEN_TOOLS__.
>>> You can add my
>>> Reviewed-by: Anthony PERARD <anthony.perard@citrix.com>
>>>
>>
>> Sorry for jumping in only now:
>>
>> Wouldn't it be better to base qemu's configure modification for support
>> of Xen 4.9 (and newer) on my just posted series introducing pkg-config?
>>
>> I'm just about to expand this series to all of Xen's libraries and I
>> already have a qemu patch at hand supporting this new scheme.
> 
> Ok, but I'm at v2 and I was literally just about to post. I guess it will also be pretty trivial to change configure after this change has been applied.

Sure, this will work.

Its your decision. :-)


Juergen

  reply	other threads:[~2017-03-02 11:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 14:53 [Qemu-devel] [PATCH 0/5] xen: use new xendevicemodel library Paul Durrant
2017-02-23 14:53 ` [Qemu-devel] [PATCH 1/5] xen: make use of xen_xc implicit in xen_common.h inlines Paul Durrant
2017-03-01 15:19   ` Anthony PERARD
2017-02-23 14:53 ` [Qemu-devel] [PATCH 2/5] xen: rename xen_modified_memory() to xen_hvm_modified_memory() Paul Durrant
2017-03-01 15:24   ` Anthony PERARD
2017-02-23 14:53 ` [Qemu-devel] [PATCH 3/5] xen: create wrappers for all other uses of xc_hvm_XXX() functions Paul Durrant
2017-03-01 16:13   ` Anthony PERARD
2017-03-01 16:16     ` Paul Durrant
2017-03-02 10:44       ` Anthony PERARD
2017-02-23 14:53 ` [Qemu-devel] [PATCH 4/5] configure: detect presence of libxendevicemodel Paul Durrant
2017-03-01 17:17   ` Anthony PERARD
2017-03-02  9:06     ` Paul Durrant
2017-03-02 10:54       ` Anthony PERARD
2017-03-02 10:55         ` Paul Durrant
2017-03-02 11:01         ` [Qemu-devel] [Xen-devel] " Juergen Gross
2017-03-02 11:06           ` Paul Durrant
2017-03-02 11:26             ` Juergen Gross [this message]
2017-02-23 14:53 ` [Qemu-devel] [PATCH 5/5] xen: use libxendevicemodel when available Paul Durrant
2017-03-02  2:05   ` Stefano Stabellini
2017-03-02  8:58     ` Paul Durrant
2017-02-23 14:55 ` [Qemu-devel] [PATCH 0/5] xen: use new xendevicemodel library Paul Durrant

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=96cdf110-8fe4-1e47-c1cf-bbb7ca0760f0@suse.com \
    --to=jgross@suse.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sstabellini@kernel.org \
    --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).