From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: qemu-devel@nongnu.org, xen-devel <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH] xen: use vMSI related #define-s from public interface
Date: Fri, 1 Sep 2017 19:20:22 +0100 [thread overview]
Message-ID: <20170901182022.2m46ussfgiwo32c5@MacBook-Pro-de-Roger.local> (raw)
In-Reply-To: <59A9A6260200007800176A6A@prv-mh.provo.novell.com>
On Fri, Sep 01, 2017 at 10:25:42AM -0600, Jan Beulich wrote:
> Xen and qemu having identical #define-s (with different names) is a
> strong hint that these should have been part of the public interface
> from the very start. Use them if they're available, falling back to
> privately defined values only when using older headers.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
>
> --- a/hw/xen/xen_pt_msi.c
> +++ b/hw/xen/xen_pt_msi.c
> @@ -18,6 +18,11 @@
>
> #define XEN_PT_AUTO_ASSIGN -1
>
> +#ifndef XEN_DOMCTL_VMSI_X86_DEST_ID_MASK
> +#if XEN_DOMCTL_INTERFACE_VERSION >= 0x0000000e
XEN_DOMCTL_INTERFACE_VERSION is already 0xe (without you added
defines), I guess it doesn't matter much because we only care for
stable releases.
I would probably be fine without the interface check and the error,
but I don't know the approach we usually take regarding those.
Thanks, Roger.
next prev parent reply other threads:[~2017-09-01 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 16:25 [Qemu-devel] [PATCH] xen: use vMSI related #define-s from public interface Jan Beulich
2017-09-01 18:20 ` Roger Pau Monné [this message]
2017-09-04 9:04 ` [Qemu-devel] [Xen-devel] " Jan Beulich
2017-09-04 9:23 ` Roger Pau Monné
2017-09-04 9:45 ` Jan Beulich
2017-09-21 1:12 ` [Qemu-devel] " Stefano Stabellini
2017-09-21 6:21 ` Jan Beulich
2017-09-21 23:50 ` 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=20170901182022.2m46ussfgiwo32c5@MacBook-Pro-de-Roger.local \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.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).