From: Christoph Egger <Christoph.Egger@amd.com>
To: Boris Derzhavets <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] xen: make (set|get)_xen_guest_handle available
Date: Thu, 30 Jul 2009 14:53:22 +0200 [thread overview]
Message-ID: <200907301453.22472.Christoph.Egger@amd.com> (raw)
In-Reply-To: <126880.30243.qm@web56105.mail.re3.yahoo.com>
On Thursday 30 July 2009 14:41:33 Boris Derzhavets wrote:
> Hi Christoph,
>
> > NetBSD 5.0 got Xen 3.x support (both 32bit and 64bit), kept Xen 2 support
>
> Sounds a bit strange for me. Like only 3.X Xen Hypervisor could be
> connected via hypercalls from NetBSD 5.0 DomU xenified kernel. ( For
> instance Solaris Nevada until build 84(5) ( or so) required patch to work
> with Xen 3.2 and higher Linux Dom0 )
Patches for NetBSD are maintained in NetBSD's package management (likewise
Gentoo or Debian have their own patches in their packages).
Most of them break non-NetBSD totally, that's why I can't just submit them at
once. xen-unstable is in a very good shape though. patch queue is very small
now.
> Would NetBSD 5.0 understand Xen 3.4.1 Dom0 on top
> of Ubuntu 9.04 or F11 (64-bit environment) ?
Yes.
>
> Thanks.
> Boris.
>
> --- On Thu, 7/30/09, Christoph Egger <Christoph.Egger@amd.com> wrote:
>
> From: Christoph Egger <Christoph.Egger@amd.com>
> Subject: Re: [Xen-devel] [PATCH] xen: make (set|get)_xen_guest_handle
> available To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Keir
> Fraser" <keir.fraser@eu.citrix.com> Date: Thursday, July 30, 2009, 7:55 AM
>
>
> Hi Boris,
>
> this is the history:
>
> NetBSD 2.0 got Xen 1.2 support (both Dom0 and DomU)
> NetBSD 3.0 got Xen 2 support, dropped Xen 1.2 support (both Dom0 and DomU)
> NetBSD 4.0 got Xen 3.0/3.1 support 32bit only, kept Xen 2 support (both
> Dom0 and DomU)
> NetBSD 5.0 got Xen 3.x support (both 32bit and 64bit), kept Xen 2 support
> (both Dom0 and DomU)
> NetBSD-current dropped Xen 2 support, about to move to new interface.
>
> Christoph
>
> On Thursday 30 July 2009 13:16:00 Boris Derzhavets wrote:
> > May the recent version of NetBSD run as PV guest ?
> > Sorry, for stupid question.
> > Boris.
> >
> > --- On Thu, 7/30/09, Christoph Egger <Christoph.Egger@amd.com> wrote:
> >
> > From: Christoph Egger <Christoph.Egger@amd.com>
> > Subject: Re: [Xen-devel] [PATCH] xen: make (set|get)_xen_guest_handle
> > available To: "Keir Fraser" <keir.fraser@eu.citrix.com>
> > Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
> > Date: Thursday, July 30, 2009, 6:34 AM
> >
> > On Thursday 30 July 2009 12:14:04 Keir Fraser wrote:
> > > On 30/07/2009 10:12, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> > > > Make (set|get)_xen_guest_handle() always available.
> > > > This avoids code snippets in the guest like this:
> > > >
> > > > #if __XEN_ITNERFACE_VERSION__ >= 0x00030201
> > > > set_xen_guest_handle(hnd, val);
> > > > #else
> > > > hnd = val;
> > > > #endif
> > >
> > > 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.
> >
> > Christoph
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2009-07-30 12:53 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 [this message]
2009-07-30 13:24 ` Keir Fraser
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=200907301453.22472.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=bderzhavets@yahoo.com \
--cc=keir.fraser@eu.citrix.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.