From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH, RFC 3/4] qemu: use new (replacement) mmap-batch ioctl
Date: Wed, 13 Jan 2010 07:59:41 +0000 [thread overview]
Message-ID: <C7732DED.6313%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4B4D893A02000078000299B5@vpn.id2.novell.com>
On 13/01/2010 07:50, "Jan Beulich" <JBeulich@novell.com> wrote:
>> This should be done by using the #ifdef arround the call to
>> xc_map_foreign_bulk, not by having a weak symbol compared to NULL.
>
> While indeed I wasn't sure about how (or if at all) to put in
> backward compatibility, this seemed to be the consolidated place.
>
> Using and #ifdef in the source file doesn't seem nice though, as it
> would tie a qemu built against older headers to using the old
> interface. But since I'm not sure about the compatibility needs in
> the first place, I will listen to whatever you say you deem
> appropriate.
Qemu is deemed part of the tollstack matched set, so compatibility with
older libxc is not an issue. The primary concern is to provide continued
compatibility with older dom0 kernels, which I believe you entirely handle
within libxc.
-- Keir
next prev parent reply other threads:[~2010-01-13 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 14:50 [PATCH, RFC 3/4] qemu: use new (replacement) mmap-batch ioctl Jan Beulich
2010-01-12 17:25 ` Ian Jackson
2010-01-13 7:50 ` Jan Beulich
2010-01-13 7:59 ` Keir Fraser [this message]
2010-01-13 8:03 ` Jan Beulich
2010-01-13 8:28 ` Keir Fraser
2010-01-13 8:56 ` Jan Beulich
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=C7732DED.6313%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/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).