From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xen: make (set|get)_xen_guest_handle available
Date: Thu, 30 Jul 2009 14:24:33 +0100 [thread overview]
Message-ID: <C6975DA1.11059%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <200907301234.38307.Christoph.Egger@amd.com>
On 30/07/2009 11:34, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
>> Actually I don't see why you'd have code like this. *You*, the guest, gets
>> to specify __XEN_INTERFACE_VERSION__ -- that is the point of it -- so
>> ifdef'ing based on it in the guest is stupid.
>>
>> Just specify __XEN_INTERFACE_VERSION__ to be recent enough to have the
>> guest handles, and then remove your ifdefs. Simple.
>
> The point is to keep backward compatibility. The patch makes Xen more friendly
> with using the old non-structured guest handler if the user wants.
>
> NetBSD offers both way to build & run it with either using the old or new
> interface. This allows a smooth migration.
Am I going to regret asking: Why? You only need to pick one API version
(__XEN_INTERFACE_VERSION__) -- the resulting binaries will work with any Xen
3.x (since we guarantee ABI compatibility).
-- Keir
prev parent reply other threads:[~2009-07-30 13:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 9:12 [PATCH] xen: make (set|get)_xen_guest_handle available Christoph Egger
2009-07-30 10:06 ` Keir Fraser
2009-07-30 10:14 ` Keir Fraser
2009-07-30 10:34 ` Christoph Egger
2009-07-30 11:16 ` Boris Derzhavets
2009-07-30 11:55 ` Christoph Egger
2009-07-30 12:41 ` Boris Derzhavets
2009-07-30 12:53 ` Christoph Egger
2009-07-30 13:24 ` Keir Fraser [this message]
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=C6975DA1.11059%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Christoph.Egger@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.